Jump to content

cyn3rgy

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

My Information

  • Agent Count
    Less than 100
  1. I'll chime in here... why not keep the zombie alive... well living dead. For anyone who comes upon this in another few years. The MS dcdiag tests run a dns test and the default dns test attempts to connect to downstream DNS to do some type of evaluation. The problem arises when downstream dns is not a windows box, dcdiag causes a DNS Error event to be generated in the event logs because it's connection attempt fails (it's trying to connect using rpc). This then causes the dcdiag to fail because there is a DNS error event. It also raises an error event relating to the failed rpc
  2. updating this with more discoveries. After spending an hour with support their tier1 guys obviously have no idea how the disk cleanup works. I'm now waiting for a tier 2 call back. So I have discovered that the disk cleanup COMMAND is the one that uses the Dashboard\Config\Disk Cleanup tab settings. The DRV - Disk Cleanup Server monitor has the alert template 'Autofix action temp file cleanup' set on it. The alert template runs the disk cleanup script, which calls the 'disk cleanup setup' script. The disk cleanup setup script installs the Desktop Experience feature then checks if it's ins
  3. Old ticket but I thought I would add what I found: The disk cleanup has 2 scripts, Disk Cleanup and Disk Clean Setup. The Setup script adds a bunch of reg keys in the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\VolumeCaches area of the registry. This is where cleanmgr.exe looks (so presumably that's what gets set when you run /SAGESET However I still haven't found any correlation between the Disk Clean scripts and the folders listed in the Dashboard\Config\Disk Clean tab. There is a log file in the LTSvc folder that lists all the folders and subfolders that match the Dis
  4. @Igs141 thanks for providing this script. I'm doing some testing at the moment and the output from the Console Shell command is saying it can't be run in elevated mode. I am aware that the powershell command can't be run with elevated privileges. The current user is potentially an admin on the machine. Have you hit this issue with your script? thanks
  5. In your script choose Variable Set, and option to Expand on Agent (assuming you are running it on an agent) and enter something like the following {%=http://portal.domain.com:8080/secure/Dashboard.jspa||||=%} If you set it to store in a variable, you can then use string functions to check the output of the get. can't help you with the post though...
  6. yep I have same issue. Recently support asked me to try something on our server and I had to tab and count to get down to the save button. The account is very restricted so pretty sure there would be no way for us to change the screen res.
  7. Wow that looks great. Will have to figure out why my cloud setup doesn't have it. Thanks for the heads up!
  8. thanks for this. It wasn't working on the 2012 systems here so I modified the script, and swapped the process check for a service check, and specified vmicheartbeat as the service name. That seems to be a common service on various versions of HyperV. Hope it helps someone. thanks again.
  9. This link is a great starter for Intel SCS provisioning, hope it helps someone. http://windowsmasher.wordpress.com/2013/10/05/intel-vpro-configuration-part-4-install-and-configure-intel-scs/
×
×
  • Create New...