Consider the following before installing SCT:
- SCT software requires 16 GB minimum of available hard disk space. This requirement is to ensure that enough room exists for future database storage used by SCT.
- The System Configuration Tool Setup installs Microsoft .NET Framework version 4.7.2 if it does not already exist on the computer. SCT Setup also installs .NET Framework version 3.5.1.
- To avoid any incompatibility issues, install SCT on a computer that does not have other non-Metasys applications that use Internet Information Services (IIS).
- You can use SCT to maintain a variety of release engines at Metasys Release 5.2 and later. The Site Director must be at an equivalent or greater release version than the highest version engine. For example, if you have a Metasys Release 6.5 engine and a Metasys Release 5.2 engine in your archive, your Site Director needs to be greater than or equal to Metasys Release 6.5. For more information, refer to SCT: System Configuration Tool Help (LIT-12011964).
- The Ethernet network interface card (NIC) must have a valid connection status for the installation to complete successfully. Connect your Ethernet NIC to the powered-up Ethernet hub, switch, or router or to a live Ethernet network.
- The initial logon user name for the SCT UI is MetasysSysAgent and is not case sensitive. For the MetasysSysAgent default password, contact your local Johnson Controls® representative. For new SCT installations, change the logon account password to a valid, complex password when you log on for the first time. If the currently installed SCT is upgrade eligible, the MetasysSysAgent password is retained during the upgrade, so you are not prompted to change the password. For more information about passwords, refer to the Security Administrator System Technical Bulletin (LIT-1201528).
- The NAE/NIE Update Tool is bundled with SCT. When you install SCT, the NAE/NIE Update Tool is also installed in the background. At SCT Release 13.0 or later, the tool is renamed to the NAE Update Tool. To launch the NAE Update Tool, navigate to . The NAE Update Tool does not have a desktop icon and you cannot uninstall the NAE Update Tool without also uninstalling SCT.
- If your computer has an older version of the NAE Update Tool, you cannot upgrade SCT until you uninstall the older version of the NAE Update Tool. The releases must match because the SCT and NAE Update Tool share the same code base for some upload and download operations.
- For SCT Release 14.0 or later, use SCT Pro in place of the NAE Update Tool.
- SCT Pro includes some of the same functions as the NxE Information and Configuration Tool (NCT). For NCT functions to work, open port 9910 (TCP) and port 9911 (UDP) on the SCT computer. For details about the NCT, refer to NxE Information and Configuration Tool Technical Bulletin (LIT-1201990) . For details about opening ports, see Opening ports and configuring the Windows firewall. SCT and NCT remain separately installed and maintained tools.
- To upload CAFs into the SCT archive, you no longer need to install CCT on the same computer as SCT. The CAF upload feature is only available for network engines at Release 6.0 or later. At SCT Release 12.0 or later, you can use the Trunk utilities option to transfer CAFs to and from the SCT archive.
- The security database for the SCT application is not available after uninstalling and re-installing SCT. You must document the existing list of users and add them manually after you install the latest release of the SCT.
- From SCT Release 14.1 and later, you require device package files, field controller package files, and Generic SA Bus packages to use all features in SCT. If you do not install device packages, you cannot add servers, supervisory devices, and field devices. Use the Software Manager, an application that is installed with SCT to license these package files after you download the package files from the license portal. You must import the package files before they can be licensed. Follow the steps in Licensing SCT and importing and licensing packages for SCT to import and license all package files. For further information on software licensing, refer to the Software Manager Help (LIT-12012389).
- If you decide to move your IIS folder or files before you
install SCT, please complete the following steps:
Note: Refer to Microsoft documentation for further information about moving your IIS site.
- Choose a new location for C:\inetpub and copy the existing files from C:\inetpub to the new location.
- Run the following command to change the Default Web Site physical site location
to the new inetpub location:
%windir%\system32\inetsrv\appcmd set vdir "Default Web Site/ -physicalPath:f:\inetpub\wwwrootreplacing f:\inetpub\wwwroot with the location you choose.
Run the following command to update the IIS registry settings for the new location:
reg add HKLM\Software\Microsoft\inetstp /v PathWWWRoot /t REG_SZ /d f:\inetpub\wwwrootreplacing f:\inetpub\wwwroot with the location you choose.
- When you install SCT, do not manually delete the MetasysIII\Packages folder or any files under that folder. You can import new package collections as they are released without removing previous files and SCT finds the files it needs. The contents of this folder come from four separate sources: the SCT installer, Metasys Device Packages, Metasys Field Controller Packages, and Johnson Controls SA Bus Device Packages.