Supported Operating System |
Supported Database Options |
---|---|
Windows® Server® 2019 (version 1803 or later) (64-bit) Windows® Server® 2016 with Update (KB4512495) (64-bit) |
SQL Server® 2019 (64-bit) SQL Server® 2017 with CU17 (64-bit) SQL Server® 2016 with SP2 CU10 (64-bit) SQL Server® 2014 with SP3 CU4 (64-bit) |
Use the steps in the following table for upgrading the Metasys Server software on a computer with a server operating system.
Step |
Action |
Reference or Additional Steps |
---|---|---|
1. |
Create a full disk image backup of the computer's hard drive to external media before upgrading any Metasys software (optional but recommended). |
Refer to the documentation that came with your operating system backup software. |
2. |
Check if the computer has a SHA256 self-signed certificate bound to Default Web Site in IIS. If the ADS/ADX computer has a purchased certificate from a certificate authority (CA), determine if this is a SHA256 (Secure Hash Algorithm) certificate. If so, follow the steps on the right. If not, skip to the next step. Also, for more details, refer to the Network and IT Guidance Technical Bulletin (LIT-12011279) . |
|
3. |
Upload and back up all ADS/ADX and network engine archive databases to the existing SCT. Make sure you select the Include Security option for the upload. |
Refer to Database Uploading, Downloading, and Synchronization of Metasys SCT Help (LIT-12011964) or the SCT Technical Bulletin (LIT-1201534) for the release you have currently installed (not the new release). |
4. |
Determine if you need to record
existing user accounts and roles:
|
Log in to SCT and open the Security Administrator tool (Tools > Administrator). In Security Administrator, record all roles, local user accounts, and Active Directory user accounts that you want to recreate in the upgraded SCT. All customized roles and user accounts are lost when you uninstall SCT 5.2 (or earlier) and install a newer version of SCT. For easy recall later, you may find it helpful to use the computer's print screen function to capture the user access permissions and other information for each role. Refer to the Metasys Site Management Portal Help (LIT-1201793) for Release 5.2 or earlier. |
5. |
Forward all trend samples from each network engine to the ADS/ADX Site Director by using the Route Samples command at each engine. This step ensures that the Site Director has all possible samples before you begin the upgrade. Wait a few minutes to ensure that all samples have been forwarded. |
Refer to Metasys Site Management Portal Help (LIT-1201793) for information about the Route Samples command. |
6. |
Stop the Metasys III Device Manager service on the ADS/ADX computer. This action prevents the collection of any new audits, alarms, trends, and annotations while you perform the upgrade. If the customer can accept the loss of data samples during an upgrade, you can skip to the next step. |
Right-click the Windows taskbar and start Task Manager. Click the Services tab. Locate a service called Metasys III Device Manager. Select this service and right-click and select Stop Service. The Metasys III Device Manager service stops. |
7. |
Perform a complete backup of all historical data in the ADS/ADX computer with the Metasys Database Manager. If the system to be upgraded is at Release 8.0 or 8.1, after the historical databases are backed up, use the SQL Server Management Studio to backup the SpacesAuthorization database. |
Refer to Backing Up a Database in Metasys Database Manager Help (LIT-12011202) . |
8. |
Make a copy of each historical database backup file and archive backup file and store them on removable media (for example, a flash drive or DVD). |
Use Windows Explorer to prepare and archive the file copies. |
9. |
Uninstall the Ready Access Portal software if currently installed. |
Refer to the Uninstalling Ready Access Portal Software section in the Ready Access Portal Software Installation Instructions (LIT-12011523) . |
10. |
Uninstall the NxE Information and Configuration Tool (NCT) if present. |
In Control Panel, click Programs > Programs and Features. Select the program from the list and click Uninstall. |
11. |
Uninstall the Metasys Export Utility software if currently installed. |
In Control Panel, click Programs > Programs and Features. Select the program from the list and click Uninstall. |
12. |
Uninstall Energy Essentials if present. This uninstall step is required before you uninstall the ADS/ADX software in a later step. |
In Control Panel, click Programs > Programs and Features. Select the program from the list and click Uninstall. |
13. |
Select the appropriate action:
|
In Control Panel, click Programs > Programs and Features. Select the program from the list and click Uninstall. |
14. |
Select the appropriate action:
|
In Control Panel, click Programs > Programs and Features. Select the program from the list and click Uninstall. |
15. |
Select the appropriate action:
|
In Control Panel, click Programs > Programs and Features. Select Johnson Controls - Launcher from the list of programs and click Uninstall. |
16. |
Select the appropriate action:
|
In Control Panel, click Programs > Programs and Features. Select the program from the list and click Uninstall. |
17. |
Uninstall the existing MVE software if present. |
|
18. |
Select the appropriate action:
|
|
19. |
Verify that the currently installed version of SQL Server software is supported for the new release of Metasys software. If necessary, apply the supported service pack or cumulative update. |
See Verifying your computer has a supported version of SQL Server software installed. |
20. |
If you intend to use the Metasys Advanced Reporting System or Energy Essentials, verify that Reporting Services is configured properly. |
Refer to the Verifying SQL Server Reporting Services Configuration section of SQL Server Installation and Upgrade Instructions (LIT-12012240). |
21. |
Install support files if the job site requires Metasys software in languages other than English. |
Refer to the Appendix: Reporting Services Language Support for Metasys Advanced Reporting System of SQL Server Installation and Upgrade Instructions (LIT-12012240). |
22. |
Uninstall the Metasys Database Manager if currently installed. |
Refer to the Metasys Database Manager Installation Guide (LIT-12011553) . |
23. |
If you uninstalled ADS/ADX software in a previous step because the site was at Release 7.x or earlier, install the Metasys Server 11.0 software now. Otherwise, upgrade the Metasys Server 11.0 software now. |
To install, see Metasys Server Software. To upgrade, see Upgrading Metasys Server. |
24. |
License the ADS/ADX software with the Software Manager. |
Refer to the Software Manager Help (LIT-12012389). |
25. |
Start Launcher on the computer and launch the Site Management Portal (SMP) for the upgraded ADS/ADX. |
Refer to Launcher Tool Help (LIT-12011742) . |
26. |
To verify ADS/ADX operation, log in to the ADS/ADX using the MetasysSysAgent user and password. |
|
27. |
Log on SCT 14.0 with a commissioning laptop, then use the Manage Archive wizard to upgrade the ADS/ADX device to Release 11.0. When asked to enter the ADS/ADX user credentials, specify the MetasysSysAgent user and password. If during the upgrade process an Upgrade Warning dialog box appears regarding password resets, set a default password for the affected users, then contact the users of their new default password. Each affected user is prompted to change this default password when logging on the Metasys ADS/ADX Release 11.0 for the first time. |
Refer to Metasys SCT Help (LIT-12011964) . |
28. |
Download the Site Director archive database from SCT 14.0 to the ADS/ADX Site Director, making sure that you click Include Security. When asked to enter the ADS/ADX user credentials, specify the MetasysSysAgent user and password. If the login for the ADS/ADX fails, click the Clear Security Database tab and click Set to be cleared. The device is upgraded, but the security database is removed from the archive. |
Refer to Database Uploading, Downloading, and Synchronization in Metasys SCT Help (LIT-12011964) for information on downloading. |
29. |
(OPTIONAL) If you want to move the Metasys historical databases now, use SQL Management Studio to move the databases to the desired location. |
See Moving Metasys Historical Databases to a Custom Location. |
30. |
Install the Metasys Database Manager to Release 11.0. Metasys Database Manager and the Metasys Server software must be at the same release. |
Refer to the Metasys Database Manager Installation Guide (LIT-12011553) . |
31. |
Update the network engines that
you want to upgrade to Release 11.0.
Note: If you are upgrading from Release 5.2 or later, you do not need to
update all devices to the newer release (except the Site Director). SCT 14.0 supports
devices at multiple Metasys software releases, beginning with Release 5.2.
|
Refer to NAE Update Tool Help (LIT-12011524) and Metasys SCT Help (LIT-12011964) . |
32. |
If you updated network engines to Release 11.0, use SCT 14.0 to download the archive database of each network engine, downloading the Site Director first (if a network engine is used as the Site Director). The download also restores the Security database. After the download completes, issue the Reset Device command to each downloaded N40-class device (NxE35, NIE39, NxE45, NIE49, NxE25, or NIE29s) to ensure that the security database is archived to non-volatile memory. This step is new beginning at Release 8.0, but is not required for any other network engine (for example, NxE55s, NxE59s, SNEs, and SNCs). |
Refer to Database Uploading, Downloading, and Synchronization in Metasys SCT Help (LIT-12011964) for information on downloading. |
33. |
If you need to bind a
purchased SHA256 certificate from a public certificate authority, follow the steps on the
right.
Note: The purchased
certificate must be SHA256 to work with Metasys UI.
|
|
34. |
(OPTIONAL) If you need the server to be FIPS compliant, enable FIPS mode and install the Metasys FIPS component. |
|
35. |
Create a full disk image backup of the computer's hard drive to external media (optional but recommended). |
Refer to the documentation that came with your operating system backup software. |