Lorenzo, I'm having the same issue (just created a discussion on it)... Are you having same symptoms as we are?
We are having some issue where deployments fail at various stages, and then we have to try a 2nd (and sometimes 3rd) time for the patching to complete.
We have noticed this behavior while using 2 different deploymnet templates, and they are both set to SHut down SQL & IIS. Once of these is set to reboot prior and the other does not reboot prior...
We can't seem to find a common issue, but have seen this on close to 12 different servers...
It does not look like the symptoms are the same.
1) we are deploying to W7 and XP PCs, not servers
2) it does not look like trying several times helps either
3) the deployment template is very simple, it just reboots after installation
I will look at your discussion in case I can glean something from it.
What's the last status you're seeing for the deployment? If it's staying at 'scheduled' it could be helpful to attempt reinstalling the Shavlik remote scheduler service on your target machines.
These documents may be helpful:
If you can provide any more details about where this is failing it would assist in figuring this out as well.
The Operations Monitor's deployment status is "Done" (green square).
The Deployment Tracker's last status is "Pending Rescan" (yellow squares).
If I keep an eye on the target machine and rescan it after it has rebooted I get the same number of missing patches as there were at the beginning.
After a bit, the Deployment Tracker status switches to "Unable to verify"
What other details could I provide to help with this?
1 of 1 people found this helpful
What patches are failing installation? Can you provide a screenshot of the scan result or a list of the Bulletin/Qnumbers this is happening with?
You can also attempt to manually run one or more of these patches to see if any specific errors are popping up by going to the target system, C:\Windows\Propatches\Patches and double click the patch file.
It is happening with all missing patches for all machines scanned.
Something just occured to me. Our 8.x consoles were XP 32 bit machines. In order to try to make things go faster our new W7 consoles are 64 bit machines. Does that matter? If not I will try running patches manually like you suggested above.
This discussion can be considered closed. We found the issue and the problem was simply that our sample set of test PCs was too small and the software that was deployed to it (Google Chrome and some Adobe Reader patch) failed for reasons independent of Shavlik.