Our local JCI tech wanted to ensure we had a solid backup of our entire system before making any major chances to our existing server. Getting SCT installed in the SCT server was the first step in the installation process. If you lose an NAE, NCE or even have a server crash, you can reload those devices from the SCT backup if you have it. SCT is the database that contains all of your system programming, user views and much more. Your IT department needs to be involved with this part of the process to ensure all network security changes can be made. It is also important to keep your SQL database server and SCT server in the same subdomain to ensure smooth operation of your system. As part of the installation process you will need to tell the system the address for each of the other servers in the system. Make sure the new webserver has the same IP address as your previous machine unless you want to go to every device in your system and point it to a new server IP address. Pay close attention to the Server IP addresses Changes you make after a backup of your system is made will be blown away during the process.
SCT DEVICE UPDATER ISSUES UPGRADE
However, you should limit any database changes as much as possible until after the overall upgrade is completed. There is no need to shut down a running system until it becomes the last piece in the upgrade. Since we were moving to a split ADX server system, we left the original, single server, running on Metasys 10 until all of the upgrade work on the two new machines was completed before upgrading it to Metasys 11. Leave the existing system running as long as possible during the upgrade If you regularly use HVAC scheduling of areas in your organization, it is a good idea to bring all of those areas occupied within the system to ensure occupant comfort in the event the upgrade process takes longer than expected. Consider your abilities to directly access supervisory devices directly in the event of a delay in getting the servers operational. The goal should be to minimize the unintended effects as much as possible. It is impossible to implement this big of an upgrade without some disruptions in operation. Work with the technicians, not the sales representatives, to get a good idea of the potential downtime you could face in the event of problems. It is important to plan this into your upgrade process. It took us a total of three days to get the system back to a useable condition due to the time it took overcoming issues we encountered. We were on a very limited schedule of operation that increases the closer we get to the next semester. Our decision was driven by the way our campus was operating at the time. Consider your timeframe for upgrading your systemīefore you begin the process of upgrading your system to Metasys 11, it is important to consider how the disruption will affect your organization. We added a virtual machine to be used as the SCT Database. The existing machine was repurposed to become the webserver and we purchased another server that would become the SQL database server. During the discussions it was recommended that we migrate to a split ADX server due to the size of our site in order to give optimum performance of the system. We held a couple meetings with representatives from our local Johnson Controls branch as well as our IT department to discuss the best options for our system. We also needed to upgrade to a newer version of Microsoft Server and SQL Server as part of the process. The ADX server we had been running was not compatible with the latest version of the Metasys 11 software. The hardware and the operating system you’re running play a critical role in the reliability of your overall system. It is important for any organization to first consider the system requirements for the latest version of Metasys. Reviewing System requirements is the first step
0 kommentar(er)
