Technote 020
Some Windows patches not installing in a timely fashion
Problem:
Why do some patch packages, such as Windows XP Service Pack 2, not install on target computers in a timely fashion?
Solution:
In all likelihood, the patch that you are trying to deploy requires a user to be logged in at the time of installation. The installation options for these patch packages are automatically generated using metadata from the Windows Update servers. For some patch packages this metadata causes the installation option 'Only install if a user is logged in' to be checked. If there is no user logged in on the client computer at installation time the patch is not installed.
The LANrev Agent will attempt to install the patch package again at the next software distribution check if a user is logged in at that time. Otherwise LANrev will continue to try to install it at every software distribution check thereafter until a user is logged in and the installation is successfully initiated.
While the Windows Update metadata for the patches in the list below indicate that they can only be installed when a user is logged in, LANrev is still able to install them with some special handling, even if no user is logged in. To get these patches to install when no user is logged in, edit their software package definitions in the LANrev Software Distribution Center and uncheck the "Only install if a user is logged in" installation option.
- Windows Messenger 4.7
- Q327405: Recommended Update (Windows XP Professional)
- Microsoft Java Virtual Machine (VM)
- Windows Media Player 9
- Windows XP Service Pack 2
- Internet Explorer 6 Service Pack 1
- Windows XP Service Pack 1
- Q320174: Recommended Update (Windows XP Professional)
- EURO setup tool
- Microsoft GDI+ Detection Tool (KB873374)
This issue will be addressed in future versions of LANrev so that the installation option 'Only install if a user is logged in' will be unchecked by LANrev for these specific patch packages regardless of metadata received from the Windows Upate servers.
|