Environment
Situation
If you have a large number of Windows Update Agents you wish to upgrade, the best approach to deploying the ZPM Update Agent 6.3 P-1 (version 6.3.2.858) is from the ZPM Update Web Management Console. This article describes the known behavior when deploying the Windows Update Agent v6 P-1 upgrade patch to your existing agents.
Applies To:PatchLink Update Agent for Windows 6.x
- Update Server must already be at version 6.3
- When deploying this patch client machines must have Windows Installer 2.0 or higher
- When deploying this patch client machines must have Update Agent for Windows v6.0 or higher.
Resolution
The Update Agent for Windows v6.3.2.858 upgrade package will be available as a deployable set of vulnerabilities on your Update Server. The vulnerabilities are described below.
C - Novell ZENworks Patch Management Update Agent Upgrade for Windows 6.0 and higher to 6.3.2.858 (See Notes)
This vulnerability is only deployable to an agent version that is a minimum of 6.0.x but a maximum of 6.2.x, which only support x86 operating systems. After a successful deployment of this patch the agent will no longer show applicable (Patched or Not Patched) for this vulnerability.
C - Novell ZENworks Patch Management Update Agent 6.3 P-1 for Windows (See Notes)
This vulnerability is only deployable to an agent version that is a minimum of 6.3.2.669 but a maximum of 6.3.2.849, both for support x86 and x64 operating systems. After a successful deployment of this patch the agent will show as patched.
Note:When deploying the package to upgrade legacy agents they will show up as Patched for this vulnerability after a successful upgrade.
- The reboot may be suppressed by clicking the Suppress Reboot check box on the Package Deployment Behavior Options page of the deployment wizard. When the reboot is suppressed, the agent may go offline until such time as the device is physically rebooted in a small percentage of deployments. Best practice is to carefully plan the deployment of this package to coincide closely with scheduled maintenance windows to minimize the devices offline relating to this behavior.
- When suppressing the reboot via the above steps, the agent has a higher chance of going offline on Windows NT and Windows 2000 devices. This is not exclusive to the operating systems mentioned but the deployment of this package should be reviewed with the above caveat.
FAQ
How does one determine if the patch is installed?
The following registry key will exist.
HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\{023DBB60-2689-4EFC-A2A6-4CCDB3A9A5BF}\DisplayVersion\6.3.x.858
The following files will exist (with version number of 6.3.x.858):
C:\Program
Files\PatchLink\Update Agent\GravitixAgentEngine30.dll
C:\Program Files\PatchLink\Update Agent\DAgent.exe
C:\Program Files\PatchLink\Update Agent\GravitixService.exe
C:\Program Files\PatchLink\Update Agent\IntegPt.dll
C:\Program Files\PatchLink\Update Agent\pddm.exe
C:\Program Files\PatchLink\Update Agent\plar.exe
C:\Program Files\PatchLink\Update Agent\plaud.dll
C:\Program Files\PatchLink\Update Agent\plcpl.dll
C:\Program Files\PatchLink\Update Agent\PLInv32.exe
C:\Program Files\PatchLink\Update Agent\WInvColl.dll
What fixes are included in the Windows Update Agent v6.3.2.858?
Re-Released Notes
- Agents weren’t upgrading from 6.2 to 6.3 P-1 when manually running the upgrade on some NT 4.0 machines.
- The
DAgent.exe shut down with no error message during a DAU, and no
results were posted back to the PLUS or the Windows Event
Viewer.