Performing an In Place Upgrade from Prism Patch Manager 6.4 to 7.0

	Browse		Search		Ask a Question!		Admin

Home : Performing an In Place Upgrade from Prism Patch Manager 6.4 to 7.0

Q11165 - HOWTO: Performing an In Place Upgrade from Prism Patch Manager 6.4 to 7.0

Performing an In Place Upgrade of Prism Patch Manager Server from 6.4 SP2a to 7.0 SP1
This document will cover performing an “in place” upgrade of Prism Patch Manager 6.4 SP2a (build 6.4.6.1573) to Prism Patch Manager 7.0 SP1. Note: The SP1 version is New Boundary Technologies’ first release of Prism Patch Manager 7.0.

Important: New Boundary Technologies strongly recommends that you identify and use a dedicated server for Prism Patch Manager 7.0 SP1, and that the server not run any other mission-critical applications or websites.

Recommended Minimum Hardware Requirements: Your Prism Patch Manager 7.0 SP1 server must meet or exceed the specified hardware requirements, the requirements indicated are the recommended minimum needed to run Prism Patch Manager 7.0 SP1. Depending on your environment you should consider using hardware that meets your organizational needs.

2+ GHz multi-core processor
2 GB Ram
72 GB of available disk space (4 GB for application, 68 GB for storage cache)

Installing Prerequisite Items: The installation of Prism Patch Manager 7.0 SP1 will install, if needed, Microsoft .NET Framework 3.5 SP1 and Windows Installer 4.5.

Installation of the prerequisites will most likely require a reboot of your server. After the reboot, the setup of Prism Patch Manager 7.0 SP1 will launch again. If it doesn’t relaunch automatically, relaunch it manually.

Installing Prism Patch Manager 7.0 SP1 Upgrade: After the prerequisites are installed, you’ll be asked if you want to do an Upgrade or Fresh Install. Choose Upgrade.

In the next dialog, accept the license agreement.

Next you will see an informational screen about SQL Server Configuration Requirements.

In the example shown above, the Default Database Settings are not what Prism Patch Manager 7.0 SP1 is expecting them to be, so we’ll allow the installation of Prism Patch Manager to modify those settings by choosing “Next.” There is a “View Configuration Detail..” button that will provide details of what the Installer of Prism Patch Manager 7.0 SP1 will change. In our example, this is what the installer will change.

After allowing the SQL Configuration changes the next screen shows information about the Service Accounts. In Prism Patch Manager 7.0 SP1 both the Web Service and the Client need to have a “service level” (administrator) account associated with it. If you are in a domain setting, we recommend that you create two user accounts that have administrator privileges where the passwords do not change.

The next screen shows the server identity, and it is pre-filled with the name of the server you are installing on.

Next choose the default installation directory. You should keep this where it is currently installed since you are doing an in place upgrade.

The next screen shows what information will be saved and moved forward with the upgrade and what won’t. Please look through this screen very closely and contact Technical Support at New Boundary Technologies if you have any questions before moving forward.