I am new to LandDesk (nice to meet you!!), and I have been diligently watching the videos and doing the recommended reading.
I am having trouble creating a baseline of patches from a barebones Win7 SP1 x64 install. I have scanned against all available critical and Important updates. After that I have hunted down patches that were marked as N/A in Landesk but marked as important in Windows Update.
I am left with Windows Update alerting me to 13 patches. The patches have been scanned in LanDesk and were not detected and/or already installed on the system. I verified most were already installed on Windows up running Quick and Easy Way to List All the Windows Updates Installed on Your System | Gizmo's Freeware
I have also checked the detection logic in LanDesk and validated the detection to be true on the target machine.
I checked the detection rules for replaced rules, and in most cases those replacements were also scanned/passed or there are no replacements.
To focus on a specific example, MS15-029_MSU.
1. In the definition affected product is Win7 x64 with KB 2670838. This KB2670838 is already installed on the target, so affected product passes.
2. custom script detection logic... The only piece I could not validate because I do not understand how it works
3. Detecting the Patch Registry Setting. The Key already exists on the target, so the patch is already detected.
4. There are no replacements for this definition in Landesk
5. There are no pre-requisites for this definition in Landesk
6. Windows Update reports MS15-029 is still needed, but Landesk says MS15-029 passes.
Is it normal to have some of these already installed updates still being detected by Windows Update? Is it possible to achieve 100% patch on a barebones machine which was updated by Landesk, and validated through Windows Update?
Thanks,
-Lee