- This topic has 1 reply, 2 voices, and was last updated 10 years, 3 months ago by .
-
Posts
-
Hugo – There are a couple of possibilities here:
1. Make sure that BatchPatch is instructing computers to search the same WSUS server that is generating your reports. If BatchPatch is configured to have computers search for updates on Windows Update or Microsoft Update instead of your own WSUS server, then you might end up with different updates installed than what is approved on your WSUS.
2. Sometimes after installing updates and rebooting, a new update will become available for a computer. This has nothing to do with BatchPatch per se. It’s something that can occur when you use the regular Windows Update interface or BatchPatch or any update installation mechanism. For this reason, some users always build into their update process a second check for updates after reboot. In fact, BatchPatch even has a “Update + Reboot Cycle” option on the ‘Windows Update’ section so that you can have it cycle through as many times as you want. You could also use the ‘Job Queue’ for this.
I hope this helps.
-Doug
- You must be logged in to reply to this topic.