Client Automation Standard Practitioners Forum
cancel

XP SP2 Deployment without Patch Manager

SOLVED
Go to solution
Highlighted
NR_1
Collector

XP SP2 Deployment without Patch Manager

Has anyone done this? Any gotchas?

Could someone attacht his doc:
Title: Acquiring and Deploying Windows XP Service Pack 2 via the HP OpenView Patch Manager Using Radia
Document ID: OV-EN019562
Product: Patch Manager using Radia
OS: Windows
Updated: 2005-Aug-26

There's something wrong with our SAID and until HP figures it out I can't access any documents.

Thanks!
2 REPLIES
Solution

Re: XP SP2 Deployment without Patch Manager

The biggest gotcha is the firewall blocking Radia ports. If you use the patch manager to deploy the service pack this is not as big of an issue. The article on SP2 can be found here...

http://openview.hp.com/ecare/getsupportdoc?docid=OV-EN019562&urlN=http%3A%2F%2Fsupport.openview.hp.com%2Fselfsolve%2Fdo%2Fsearch&fromOV=false&urlB=http%3A%2F%2Fsupport.openview.hp.com%2Fselfsolve%2Fdo%2Fsearch%3Faction%3Dresults&f=ss&hl=true


This document describes how to automatically acquire and distribute Microsoft Windows XP Service Pack 2 via the HP OpenView Patch Manager Using Radia, which must be at version 1.2.3.

Requirements & Prerequisites
Product Versions: HP OpenView Patch Manager Using Radia (Agent and Patch Manager Infrastructure/Server components), version 1.2.3 and later
Platforms: Windows XP Gold, Windows XP Service Pack 1 (specifically to apply Windows XP Service Pack 2)
Components: HP OpenView Patch Manager Using Radia (Patch Manager)
Processes: acquisition, deployment

WARNINGS: Do not attempt this acquisition and deployment in an environment that does not meet these minimum Patch Manager-version criteria; doing so will cause failures of Radia client programs (such as radtray, radiauishell, nvdkit, and radexecd) that are using well-defined ports.

If your environment does not meet these minimum requirements, contact HP Technical Support for information about migrating the Patch Manager to the minimum recommended version.

HP recommends that any Microsoft Service Pack be tested in a test environment prior to being part of an automated distribution because the Service Pack could affect the operation of resident applications.


Solution


Details

According to information from Microsoft, Windows XP Service Pack 2 (SP2) includes numerous product updates and security enhancements. One new feature, Microsoft Windows Firewall, replaces the Internet Connection Firewall (ICF) that was included in prior releases. This firewall, which is enabled by default when SP2 is installed, can disable some of the basic capabilities that are built into the HP OpenView Using Radia product suite, such as:

The blocking of TCP network communications between HP OpenView Using Radia infrastructure components and management clients.
The blocking of TCP ports that are used by a service or application.
This could cause Warning panels to be displayed when using an application; or worse, the application could fail. Therefore, it might be necessary to add exceptions for ports and/or applications in order to prevent Windows Firewall blocking a TCP port that is used by an application or service.

Impact on HP OpenView Using Radia Components

The default installation of SP2 will block several applications that are part of the HP OpenView Using Radia suite, such as the Radia notify daemon, the Radia system tray, and the user interface of the HP OpenView Software Manager Using Radia (Software Manager). This could result in a failure to manage applications on a desktop that is using either the HP OpenView Application Manager Using Radia (Application Manager) or the Software Manager client.

Blocking the notify daemon will result in the inability to notify a subscriber from the HP OpenView Management Portal Using Radia (Management Portal), the HP OpenView System Explorer Using Radia, and other remote clients.
Launching the Software Manager will result in a Windows Security Alert message about a blocked program.
Launching the Application Manager will result in a Windows Security Alert message when the system tray starts running.
Finally, customers that are using the Management Portal will encounter errors when attempting to perform operational tasks, such as refreshing the HP OpenView Management Agent Using Radia (Management Agent), and stopping and starting HP OpenView Using Radia services on a client machine. This is because the port that is used by the Management Agent is blocked.

By default, Internet Control Message Protocol (ICMP), which prevents network discovery of new machines by the Management Portal, is also disabled.

Implementation Details

A number of HP OpenView Using Radia client application programs (refer to the Application Programs list that follows) use communications ports; they can use either a dynamically assigned port or a static port as assigned by an administrator. Applying SP2 via the Patch Manager enables an administrator to set a port-exclusion list which is based on application name rather than port number.

Application Programs
The following is a list of client application programs (and default installation location) that use communications ports.

Integration Server (C:\Novadigm\IntegrationServer\nvdkit.exe)
HP OpenView Management Agent Using Radia (C:\Novadigm\\ManagementAgent\nvdkit.exe)
Radia notify daemon (C:\Program Files\Novadigm\radexecd.exe)
HP OpenView Software Manager Using Radia (C:\Program Files\Novadigm\raduishell.exe)
Radia client system tray (C:\Program Files\Novadigm\radtray.exe)
IMPORTANT NOTE

HP recommends using the Application Manager if you want to:

Customize the installation and management of Windows XP Service Pack 2 (including the addition of specific applications and port numbers to the Microsoft Windows Firewall exclusion list).
Disable the Microsoft Windows Firewall.
For more information, refer to the Engineering Note, OV-EN018781: Service Packs & Updates and select the Microsoft Windows XP Service Pack 2 entry.


Acquiring and Distributing the Service Pack

1. Download the Service Pack 2 file, MSSP-WINXP_2.xml from the link below, and place it in the Patch Managerâ s directory data\patch\custom. (The default path to this directory is C:\Novadigm\IntegrationServer\data\patch\custom.)

Click on the file name to download this file: MSSP-WINXP_2.xml.

2. Perform an acquisition and specify Windows XP Service Pack 2 in the bulletin selection list.

Note: If the command-line interface is used, specify -bulletins MSSP-WINXP_2.

3. Perform a Patch Manager Vulnerability Assessment, and entitle the intended target machines to the service PRIMARY.PATCHMGR.ZSERVICE.MSSP-WINXP_2. This will allow the target machines to apply SP2 to an agent computer that is running either Windows XP Gold or Windows XP Service Pack 1 when the agent installs the requested service.

Note: The Microsoft Knowledge Base article http://support.microsoft.com/default.aspx?kbid=837783 states that SP2 requires approximately 1100 MB of peak free disk space for the installation.

After successfully applying the Windows XP Service Pack 2 service, Patch Manager will open the ports that are used by the Radia client application programs (radtray, radiauishell, nvdkit, and radexecd), provided these components are installed on the client workstation.

Additional Reading

HP OpenView Configuration Server Using Radia: Userâ s Guide (Configuration Server Guide)
HP OpenView Patch Manager Using Radia: Installation and Configuration Guide (Patch Manager Guide)
HP OpenView Reporting Server Using Radia: Installation and Configuration Guide (Reporting Server Guide)
Engineering Note OV-EN018781: Service Packs & Updates
6 years with Radia and counting
NR_1
Collector

Re: XP SP2 Deployment without Patch Manager

Cheers!
//Add this to "OnDomLoad" event