Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Patch Manager > SolarWinds Patch Manager Upgrade Guide

SolarWinds Patch Manager Upgrade Guide

Last Updated: 3-14-2017 | SolarWinds Upgrade Guide

Supports: SolarWinds® Patch Manager 1.80 and later. See Currently supported software versions for more information.

This guide walks you through upgrading your Patch Manager product and includes checklists and gotchas to help you prepare and complete your upgrade and troubleshooting steps.

Upgrading multiple products? See the SolarWinds multiple products upgrade guide.

Important for Patch Manager 2.1.4 and later: Use the Product Upgrade Advisor for your Upgrade Path. When downloading the installations, please use the Customer Portal. For details, see this article: Upgrade Adviser showing Orion Platform (Core) 2017 as Maintenance Expired.

Preflight upgrade checklist

This preflight checklist details important information to help plan and prep for your upgrade.

Review the release notes Review the product release notes and available documentation in our Success Center.
Review system requirements

Make sure your environment includes all required hardware and software for your installation. Check the administrator guide for your product to locate requirements.

Review licenses Review your current product licenses and determine if updates are required. You can download any updated license keys for your upgrade through the SolarWinds Customer Portal. Verify any license upgrades and needs with your SolarWinds account manager or contact SolarWinds for assistance. 
Do you need to migrate?

You may need to migrate products and databases to dedicated servers or shared servers. Check if you need to migrate by reviewing the product requirements and your current environment.

Migrating adds time to your upgrade, but you have the best opportunity to update to new servers during an upgrade.

Gather credentials

Make sure you have the credentials for your:

  • Accounts
  • SQL database
  • SolarWinds account
  • Local admin server
Build your upgrade path

See the Product Upgrade Advisor to build your upgrade path.

Run all Windows updates

Locate and run all Microsoft Windows Updates on your Patch Manager servers and primary application server (PAS). During the upgrade, your system may reboot when a Windows update is completed.

To ensure local publishing continues to work in your environment, apply the updates to all Patch Manager and Windows Server Update Services (WSUS) systems. When you are finished, generate a new 2048-bit publishing certificate on your primary application server.

If you are running Microsoft Windows Server 2008 or Windows Server 2008 R2 and you have not applied Microsoft KB2720211 or KB2734608 to your WSUS and Patch Manager systems, the upgrade to version 2.1 and higher automatically applies KB2734608 to your local WSUS console.

Schedule the upgrade Set up the maintenance window, preferably during non-business hours. Depending on the number of servers and size of your environment, you may need an extended amount of time to complete your upgrade.
Notify your company Send a message to all stakeholders regarding the upgrade schedule and maintenance window. If you need additional help, contact and allocate specific staff to be available.

How long does an upgrade take?

The time it takes to complete an upgrade depends on:

  • Hardware
  • Database server performance and database size
  • Environment performance

Because every configuration is different, SolarWinds cannot predict exactly how long your upgrade will take. After feedback from the THWACK community is received, that information can be compiled to help give you an estimate. This guide includes steps and tips to help reduce your upgrade time.

Gotchas

This section includes gotchas for each product version that may impact your upgrade.

  • The upgrade automatically installs Microsoft .NET FrameWork 3.5 and 4.5 during the installation, if required. After the upgrade, you must reboot your Patch Manager server. Back up your Patch Manager environment before you upgrade any .NET Framework, as removing older versions break the Patch Manager installation. The .NET Framework version 4.6 replaces version 4.5, but you still need version 3.5. 
  • During the upgrade, make sure to upgrade one version at a time on each Patch Manager server.
  • If you are upgrading from an End of Life product version, consider installing the latest Patch Manager software instead of performing an upgrade, saving, or migrating your data. SolarWinds Support can provide the best advice for these upgrade scenarios.
  • If you are migrating your Patch Manager database to a remote Microsoft SQL Server computer, be sure that the computer hosting Patch Manager meets the necessary requirements.
  • If you have more than 200 trusted root certificates, you may not be able to upgrade Patch Manager due to a limitation in the Microsoft Remote Procedure Call (RPC) implementation. Contact Support for assistance.

Patch Manager 2.0 and later

  • When upgrading to Patch Manager 2.1.4, if you added a site binding to a host name before you upgrade, you must bind the Orion Web Console to a fully qualified domain name (FQDN). See this article.
  • When upgrading to Patch Manager 2.1.4 with custom menus, you can not see the Performance Dashboard link in the menu. For details, see this article.
  • After integrated Patch Manager 2.1.4, future releases will no longer support Windows OS 2008 and 2008 R2 and Microsoft SQL Server 2008 R2 for Orion Platform installations. Integrated Patch Manager 2.1.4 currently supports these versions. SolarWinds recommends that you upgrade to Windows Server 2012, 2012 R2, or 2016 at your earliest convenience. For more information, see End of support notices.
  • Patch Manager 2.1.2 and later is not supported on systems running Windows Server 2008 and Windows Server 2008 R2 without SP1.
  • If you are migrating Patch Manager 2.1 to another server, read Uninstall Patch Manager from an old server and install it on a new one before you upgrade to the latest release.

Patch Manager 1.80 and 1.85

  • If you are upgrading from Patch Manager 1.80 or 1.85 to the latest release, upgrade your Patch Manager servers and consoles to Patch Manager 2.1.1 first. After you have finished, follow the upgrade path to install the latest release.
  • For Patch Manager 1.85 and later, install the Common Language Runtime v4.0 (CLR4.0) environment before you upgrade. This adds the Patch Manager MMC snap-in as a sub-node of the Microsoft System Center Configuration Manager (SCCM) 2007 console. If you do not change the runtime, the Patch Manager snap-in runs as a separate console on SCCM 2007.

Patch Manager 1.73 and earlier

  • If you are upgrading from a version prior to Patch Manager 1.72, ensure that you have:
    • A Windows user account with administrator rights on the Patch Manager server
    • A Patch Manager Web Console account in the Patch Manager Enterprise Administrator security role 
  • SolarWinds no longer provides technical support for Patch Manager 1.73 or earlier. See Currently supported software versions for details.

General Orion Platform gotchas

  • If you have written your own code, such as changing SolarWinds .css files or adding .js files, or been directed to make changes by Support, the code may be overwritten during the upgrade. You can learn more about upgrading with custom code here.
  • Always check that you have enough hard drive space for zipped and unzipped installers. One unzipped installer could consume a couple GBs of space.
  • During your upgrade, use the Scalability Engine Installer. If you use downloaded installers or the installer bundle, you must install one product and version at a time. The versions must match between the main and additional poller or you will receive a Database Configuration Failure Error.
  • If you are upgrading from a very early or End of Life SolarWinds product version, you may want to install a new product instead of performing an upgrade, saving or migrating your data. SolarWinds Support can provide the best advice for these upgrade scenarios.
  • If you have enabled SolarWinds High Availability, you must disable High Availability before you can upgrade. You must have the same versions of SolarWinds products on your primary and secondary server before you can re-enable your HA pools. See the Upgrade with HA section.

Prepare your environment to upgrade

The steps below include the common actions you need to complete before upgrading Patch Manager to the latest release.

If you have a test or staging environment, we highly recommend testing the upgrade first. You cannot roll back an installation once completed.

1. Back up the database

Back up your Patch Manager database. If you need help, check the database vendor site for documentation and instructions.

You cannot roll back an upgrade. Always create a database backup.

2. Exclude files on anti-virus software

To ensure the best performance on your server host and to provide full-file access, exclude specific file paths and directories from anti-virus software scans. See Files and directories to exclude from antivirus scanning for details.

You can also place your systems behind a firewall to completely disable your anti-virus software during an upgrade.

3. Verify your admin account Locate the database connected to Patch Manager and verify that your admin account is a member of the SYSADMIN DATABASE role.

Upgrade Patch Manager

See the Product Upgrade Advisor to build your upgrade path.

This checklist details the steps for upgrading your Patch Manager servers and consoles to the latest release.

Upgrade Tip! If you have a test or staging environment, SolarWinds highly recommends testing the upgrade first. You cannot roll back an installation after it is completed.

1. Prepare for the upgrade Determine the upgrade path for your environment. 
2. Download the upgrade packages
  1. Navigate to the Customer Portal.
  2. Download the Patch Manager 2.0 upgrade package to your Patch Manager servers and Web Console.
  3. Download the Patch Manager 2.1 upgrade package to your Patch Manager primary application server.
  4. (Optional) Download the Patch Manager 2.0 upgrade package to your downstream servers and Web Consoles. 
3. Upgrade your servers Unzip the Patch Manager 2.0 upgrade package and run the installer on each Patch Manager server. 
4. Upgrade your Web Console Unzip the Patch Manager 2.0 upgrade package and run the installer on the Patch Manager Web Console. 
5. Upgrade your primary application server Unzip the Patch Manager 2.1 upgrade package and run the installer on your primary application server. 
6. (Optional) Upgrade your downstream servers Unzip the Patch Manager 2.0 upgrade package on each downstream Patch Manager server and Web Console, and then run the installer.
7. Upgrade your systems to the next version in the upgrade path After you install the upgrade in your environment, check the version using the upgrade path. If you have additional versions to install, repeat step 2 through 6 on your Patch Manager servers. 

Check your system after the upgrade

All product versions should be installed properly. Open the application and verify that the upgrade version displays in the footer of the Web Console. Try current and new features with your system to check performance and expected functionality. If you run into issues, check the troubleshooting tips.

Troubleshooting

Error messages

Product licensing

Other issues

Want to learn more?

Legal notices

© 2017 SolarWinds Worldwide, LLC. All rights reserved.

This document may not be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the prior written consent of SolarWinds. All right, title, and interest in and to the software and documentation are and shall remain the exclusive property of SolarWinds and its respective licensors.

SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The SolarWinds and other SolarWinds marks, identified on the SolarWinds website, as updated from SolarWinds from time to time and incorporated herein, are registered with the U.S. Patent and Trademark Office and may be registered or pending registration in other countries. All other SolarWinds trademarks may be common law marks or registered or pending registration in the United States or in other countries. All other trademarks or registered trademarks contained and/or mentioned herein are used for identification purposes only and may be trademarks or registered trademarks of their respective companies.

 
Last modified
12:59, 6 Jun 2017

Tags

Classifications

Public