In the NetChk application, go to Tools -> Options -> Logging and set selections to ALL.
Close NetChk and stop the Shavlik services.
Delete the contents of the logs folder.
Start the Shavlik services
On a single target machine, stop the Shavlik services, delete the c:windowspropatches folder.
Open NetChk, Scan only the same single machine (above) using the WUscan template. View the scan results; View the scan results.
Does each of the missing patches have a green down arrow? If not, select the missing patches and right click to select the option to download the missing patches.
Select a single downloaded patch, right click the patch and select to deploy the single patch using the Standard deployment template.
Once deployed, give it some time. Does the target machine reboot?
On the NetChk console machine, view the deployment, select the machine, what does it show about the deployment to that machine?
Scan only the one target machine in question using the WUscan template. Is the patch no longer listed as a missing patch in the new scan results? If the patch is still listed as a missing patch, select the machine within the scan, next select the missing patch. What is the reason the scan shows the patch missing?
If the deployment failed and you gave the target machine enough time for the deployment to complete and the machine rebooted, then look at the target machine under C:WINDOWSProPatchesPatches. Does the patch exist (did the patch get copied to the target machine)? Is the file digitally signed by the vender (right click patch.exe -> Properties)
Next, look on the target machine within C:WINDOWSProPatchesInstall.
Do you see a .bat or a .his file that was created at the time of the deployment?
If you see a .BAT, the scheduled task never ran at the scheduled time or the deployment did not complete.
If you see a .HIS, this should be correct, the last step of the deployment is to rename the .bat to .his, showing the deployment did run and finished.
If you manually run the patch.exe from C:WINDOWSProPatchesInstall, does the patch install complete?
If the deployment failed to work, the logs should give us details about what occurred in the deployment process
Send the logs and a screenshot of the deployment results to support.
The NetChk 7.X logs can be found in:
On Vista and later: C:ProgramDataShavlik Technologies
On earlier OS’s: C:Documents and SettingsAll UsersApplication DataShavlik Technologies
I went through what you suggested and it failed again on the deployment. Here is what the console said:
W2SQLHA: Copying file: WindowsServer2003-KB2483185.exe
W2SQLHA: File complete: WindowsServer2003-KB2483185.exe
W2SQLHA: Copying file: qchain.exe
W2SQLHA: File complete: qchain.exe
W2SQLHA: Copying file: cl5.exe
W2SQLHA: File complete: cl5.exe
W2SQLHA: Copying file: silent.exe
W2SQLHA: File complete: silent.exe
W2SQLHA: Copying file: SafeReboot.exe
W2SQLHA: File complete: SafeReboot.exe
W2SQLHA: Copying file: SafeReboot64.exe
W2SQLHA: File complete: SafeReboot64.exe
W2SQLHA: Copying file: 2011.02.14-03.52.45-M5WSUS-W2SQLHA.bat
W2SQLHA: File complete: 2011.02.14-03.52.45-M5WSUS-W2SQLHA.bat
W2SQLHA: Copying file: 2011.02.14-03.52.45-M5WSUS-W2SQLHA.cfg
W2SQLHA: File complete: 2011.02.14-03.52.45-M5WSUS-W2SQLHA.cfg
W2SQLHA: Copying file: winhttp.dll
W2SQLHA: File complete: winhttp.dll
W2SQLHA: Initiating the task
Error - W2SQLHA: '': parameter name: 'encoded'
Deployment complete, finishing process...
I normally scan up to 20 machines at a time. I've had scans the work fine then I have scans that 1 or 2 have this problem.
Please also be certain to review your current naming conventions employed. If you are using any non-alphanumeric characters, this may be causing an issue (particularly characters which are part of the XML codeset, such as the ampersand '&'). This applies to machine names, machine group names, and custom template names.
machine name is w2sqlha, I put it into a special group to scan only it, the group was called zz and was scanned with the WUscan and deployed with the Standard template per your instructions.
I just went out to this machine and the ProPatches directory was created and all the patches were copied to the machine. The .bat and .cfg is there.the STSchedEX.exe and STSchedulerview.exe are there. Other files include cl5.exe, qchain.exe, SafeReboot64.exe, safereboot.exe, silent.exe and winhttp.dll. It looks to me that all the files needed are there it just seem to be an issue with the scheduler.
Try rebuilding the scheduler service on the target machine, then scan the machine with the default 'Security Patch Scan' template, and attempt to deploy a single patch (preferably an operating system patch) using the default 'Standard' template (please keep in mind that this template includes a post-deployment reboot).
Complete these steps on the target machine on which you wish to remove the scheduler:
1) From a command prompt, browse to the 'c:windowspropatchesscheduler' directory.
2) Execute the following command:
3) Delete the 'c:windowspropatches' directory.
4) Delete the following registry key(s) (if they exist):
32 bit - 'HKEY_LOCAL_MACHINESOFTWAREShavlikScheduler'
64 bit - 'HKEY_LOCAL_MACHINESOFTWAREWow6432NodeShavlikScheduler'
5) Validate the 'Shavlik Remote Scheduler Service' isn't listed as a service.
That appears to work but it was wierd. I scanned a machine, it showed 8 patches missing. I choose one, MS11-013 and deployed it. After the reboot I rescanned the machine and it showed ALL the patches installed. I will do this rebuilding of the scheduler service on all other machines I have been having trouble with. Think it could be a stub left over from my 6.5 version?
Most often, we see the scheduler service corrupted due to non-alphanumeric characters being employed. If this was not the case, it is difficult to say what may have caused the issue apart from some very extensive trouble-shooting.