Supported Operating System |
Supported Database Options |
---|---|
Windows® Server® 2022 (64-bit) Windows® Server® 2019 (version 1809 or later) (64-bit) |
SQL Server® 2022 Express (64-bit) SQL Server® 2019 with CU18 (64-bit) SQL Server® 2017 with CU31 (64-bit) Note: Reporting Services is only supported on SQL 2017. If you
are not installing Reporting Services, you do not require SQL Server on the
Web/Application computer.
|
Follow these steps to upgrade the web/application component of the ADX on a split Metasys 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. |
Backup the Fault Manager Global Attributes. |
Refer to the Potential Problem Areas widget section in the Metasys UI Help (LIT-12011953). |
3. |
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) . |
|
4. |
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) . |
5. |
Uninstall the Metasys Export Utility software if currently installed. Note:
Energy Essentials is not supported from Metasys
Release 12.0.
|
In Control Panel, click Programs > Programs and Features. Select the program from the list and click Uninstall. |
6. |
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. |
7. |
Select the appropriate action:
|
In Control Panel, click Programs > Programs and Features. Select the program from the list and click Uninstall. |
8. |
Select the appropriate
action:
|
In Control Panel, click Programs > Programs and Features. Select Johnson Controls - Launcher from the list of programs and click Uninstall. |
9. |
Select the appropriate action:
|
In Control Panel, click Programs > Programs and Features. Select the program from the list and click Uninstall. |
10. |
Uninstall the existing MVE software if present. |
|
11. |
Select the appropriate action:
|
|
12. |
If you followed any steps 4-11, restart the computer. |
Refer to the information for restarting the computer that came with your operating system. |
13. |
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. |
14. |
Verify that SQL Server Reporting Services is configured properly. |
Refer to the Verifying SQL Server Reporting Services Configuration section of SQL Server Installation and Upgrade Instructions (LIT-12012240). |
15. |
If you
uninstalled ADS/ADX software in a previous step because the site was at Release 7.x or
earlier, install the Metasys Server 13.0
software. Otherwise, upgrade the Metasys Server 13.0 software.
Note: When you install or
upgrade, specify the SCT archive database in the SCT Archive Db field on the Reporting tab
screen of the Metasys Server 13.0 installer.
Make sure you install the new Metasys Server 13.0 software on the Site Director first. If you have other ADSs/ADXs, upgrade
them after the Site Director.
|
|
16. |
License the Metasys Server software and any other software you require for the Web/Application server with the Software Manager. |
Refer to the Software Manager Help (LIT-12012389). |
17. |
Start Metasys UI to verify proper operation. |
Refer to the Metasys UI Help (LIT-12011953) for more information. |
18. |
(Optional) Start Launcher on the computer and launch the Site Management Portal (SMP) for the upgraded ADS/ADX. |
Refer to Launcher Help (LIT-12011742) . |
19. |
To verify ADS/ADX operation, log in to the ADS/ADX using the MetasysSysAgent user and password. |
|
20. |
Log on to SCT 16.0 with a commissioning laptop, then use the Manage Archive wizard to upgrade the ADS/ADX device to Release 13.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 13.0 for the first time. |
Refer to SCT: System Configuration Tool Help (LIT-12011964) . |
21. |
If you upgraded the
device in your SCT archive from a Metasys
version up to Release 12.0, to Release 13.0, confirm the following:
|
To check the configuration of the Third party BBMDs, see Checking third party BBMDs compatibility for ADS/ADX upgrades. To check the configuration of the Email DDA destinations, see Checking email DDA compatibility for ADS/ADX upgrades.
Note: The archive download to a Release 13.0 ADS/ADX fails if these
attributes have an incompatible configuration. For more information, see General Troubleshooting.
|
22. |
Download the Site
Director archive database from SCT 16.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.
Note: Before you
attempt a download/upload to the server from SCT, wait for it to become operational. If
you perform a download/upload before then, the server does not operate correctly. To fix
this, restart the Metasys server host, wait for it to become operational, and try the
process again.
|
Refer to Database Uploading, Downloading, and Synchronization in SCT: System Configuration Tool Help (LIT-12011964) for information on downloading. |
23. |
If the site has other ADS/ADX servers, upgrade and download each ADS/ADX archive database from SCT 16.0 to the other ADS/ADX servers. The download also restores user accounts. |
Refer to Database Uploading, Downloading, and Synchronization in SCT: System Configuration Tool Help (LIT-12011964) for information on downloading. |
24. |
(Optional) If you want to move the Metasys historical databases now, use SQL Management Studio to move the databases to your chosen location. |
See Moving Metasys Historical Databases to a Custom Location. |
25. |
Update the network engines
that you want to upgrade to Release 13.0. You can only upgrade SNx engines to Release 13.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 16.0 supports devices at multiple Metasys software releases,
beginning with Release 5.2.
|
Refer to NAE Update Tool Help (LIT-12011524) and SCT: System Configuration Tool Help (LIT-12011964) . |
26. |
If you updated network engines to Release 13.0, use SCT 16.0 to download the archive database of each network engine. 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 engines (NxE55s, NxE59s, SNEs, and SNCs). |
Refer to Database Uploading, Downloading, and Synchronization in SCT: System Configuration Tool Help (LIT-12011964) for information on downloading. |
27. |
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.
|
|
28. |
(Optional) If you need the server to be FIPS compliant, enable FIPS mode and install the Metasys FIPS component. |
|
29. |
Restore the Fault Manager Global Attributes. |
Refer to the Potential Problem Areas widget section in the Metasys UI Help (LIT-12011953). |
30. |
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. |