Upgrade to Prism Patch Manager 7.0 - Switch to new hardware
This scenario is preferred if:
· You want to use new hardware for the Prism Patch Manager server and/or for the SQL server and instance.
· You want the legacy agents to automatically re-register with the new Prism Patch Manager server
Important: For this type of upgrade, you must use the same product serial number as your current Prism Patch Manager server. In preparation, procure new hardware (metal or virtual), and install Windows Server 2003, Windows Server 2008 or Windows Server 2008R2 with the latest service pack.
1. Power down existing Prism Patch Manager 6.4 Server.
IMPORTANT! At a minimum, you must block communication with Prism Patch Manager subscription service to ensure that content on the 6.4 server is not removed and replaced with incompatible content format that is part of 7.0.
2. Install Prism Patch Manager 7.0 SP1 Server on new hardware using the same serial number that you used for Prism Patch Manager 6.4. See Related Articles link below for a KB article about installing 7.0.
3. Modify DNS to re-direct Agent traffic to Prism Patch Manager 7.0 Server
NOTE: The 6.4 Prism Patch Manger server must be powered down before this step. After the server is installed and DNS has redirected legacy agents to the new Prism Patch Manager server, the legacy agents will re-register with the Prism Patch Manager 7.0 server.
Upgrading the Agents
Please refer to the Agent Install Guide for full details.
Note: If you do not want to upgrade your version 6.4 agents, you must deploy the Native Scan Content Enhancement patch to the endpoints running version 6.4 agents so that they can receive enhanced content that is part of version 7 of Prism Patch Manager.
You can upgrade an agent on an endpoint in any of the following ways.
· Use a Command Task in Prism Deploy to upgrade the agent or a GPO in Active Directory.
· Download the appropriate installer to the endpoint that you want to manage, and then run the installer locally on the endpoint. To download the installer, log into the Prism Patch Manager console from the endpoint, then download the appropriate agent installer to that computer.
· Create an agent management job to install the agent that targets the endpoint (Windows operating systems only). When the job executes, an agent is installed on the endpoint.
Note: You should not perform the agent upgrade procedures listed above on the New Boundary Prism Patch Manager server, only on the managed endpoints. The agent on the Prism Patch Manager server is installed and configured during the server installation process.
Optionally provide your comments to help us improve this article...
Thank you for your feedback!