There are many factors that can cause our scan to come out differently. Here are some common things that will help sort this out:
What type of scan template is being used in Protect?
The main thing is that it depends on what your scan template is actually set up to scan for. If using a custom scan template check to make sure of what Patch Type Filters are currently selected and whatever else is set up on your Filtering tab. Many items that could show up in WSUS would be listed as a 'Non security' or 'Security Tool' patch type within Protect.
It may also help to check the option to 'Include effectively installed patches' on the General tab of the scan template. This will allow the scan with Protect to show patches that are considered effectively installed through supersedence or registry key only detection.
Make sure that the patches being shown in WSUS are actually supported products within Protect. You can search for them in Patch View or also on our supported products list here: http://xml.shavlik.com/data/supportedproduct78.htm
I hope this helps.
I have verified that we have all of the settings correct within vCenter Protect to scan for ALL patches, but the reports that I get still do NOT match up with WSUS. WSUS says that patches have been applied and vCenter Protect says that there are patches still pending. Doing the research it looks like the
mismatch patches SHOULD fall under the "superseded" patch list, but for some reason vCenter Protect does not see the patches this way. Any ideas where to go or what do to next?
1 of 1 people found this helpful
With possible detection issues like this it may be best to contact support directly. We might need to take a look at each patch you're having trouble with on an indivdual basis.