|
Revised 28 December 2018 |
Upgrading to Diagnostics 4.7
Summary
Upgrading to NetMotion Diagnostics version 4.7 may require moving to a currently supported server system: Windows Server 2012 R2 or Windows Server 2016. When upgrading from versions 1 through 3 of Locality (former name of Diagnostics), refer to the following:
- Version 1.x: Contact NetMotion support for information on how to upgrade Locality 1.x
- Versions 2.x and 3.x: Upgrading these versions can be done directly if on 2012 R2 provided hardware and software specifications are met. For installations on 2008 R2 or 2012, upgrade to 4.1 first and then export database to use for a new install of 4.7 on 2012 R2 or 2016 Server.
Upgrading from Version 1.x of Locality
Do not attempt to upgrade Locality v1.x to the latest release of Diagnostics without assistance from NetMotion Technical Support. Due to changes in system architecture, there are various possible scenarios for upgrading Locality v1.x. NetMotion Technical Support will help you to determine the best upgrade method for your Diagnostics deployment; you can contact us through our Support page.
Obtaining Version 4 License Keys
To obtain version 4 license keys, log onto the Customer Portal or contact our Customer Service Team. They can be reached at 888 723 2662, Option 1 or customerservice@netmotionsoftware.com. You cannot obtain version 4 license keys through the Get New License link from the Diagnostics server console.
Upgrading when Client Authentication is Enabled
If Client Authentication is enabled, then when upgrading and moving to a new server, the new server must have the exact same Fully Qualified Domain Name as the old server.
Upgrading when using at Trusted Certificate
If you are using a Trusted Certificate, then you will also need to follow this procedure to use a Trusted Certificate.
Upgrading from Version 2.x of Locality or Version 3.x of Diagnostics
If the system to be upgraded is installed on Windows Server 2012 R2, you can add version 4 license keys and can upgrade directly to Diagnostics 4.x. Please see the section below on In-place upgrade to Diagnostics 4.7. Hardware and software specifications based on deployment size have changed, so be sure to check prior to doing an in-place upgrade by reviewing the Recommendations for Deploying a Diagnostics Server. If the system is installed on Windows Server 2008 R2 or 2012, the process is as follows:
1) Add version 4 license keys.
2) Upgrade to version 4.1.
3) Back up the database: See Backing up the Diagnostics Database
4) Then follow the instructions below for installing 4.7 on a new server.
In-place upgrade to Diagnostics 4.7
Review Installing the Diagnostic Server which consists of the Pre-Install Check List and Diagnostics System Deployment Task List. Then install the Diagnostics Server System.
Installing Diagnostics 4.7
Review the Recommendations for Deploying a Diagnostics Server to make sure the new installation meets the version 4 requirements based on your deployment size. In addition review the following before installing:
Installing the Diagnostic Server including the Pre-Install Check List and Diagnostics System Deployment Task List. Use the backup database from an install of 4.1 on Server 2008 R2 or 2012. Follow the procedure in this link: Installing the Diagnostics Server System to install the version 4.7 server. From step 7 in this link: Re-run the configuration wizard again to restore the database.
Comments
0 comments
Article is closed for comments.