Overview

This article goes over the steps to move Azure controllers when the UnityIS system has been migrated to a new Server. This article assumes you've backed up the UnityIS database from the original server and restored the database on to the new Server. See this KB article for steps to backup and restore database on new server

There are 4 scenarios that affect the operation of Azure Controllers when the existing system has been migrated to a new Server and/or new server IP Address. In every scenario, it is imperative to have a backup of the "azure.pfx" file located in the UnityIS\Drivers folder.

Scenario 1:  You migrated to a new Server and backed up the original "azure.pfx" file and new server has the same IP address as original server

Scenario 2:  You migrated to a new Server and did not backup the original "azure.pfx" file and the new server has the same IP address as original server

Scenario 3:  You migrated to a new Server and backed up the original "azure.pfx" file and the new server has a new IP address 

Scenario 4:  You migrated to a new Server and and did not back up the original "azure.pfx" file and the new server has a new IP address 

Steps:

If Scenario 1 applies to your situation:  

1. Copy the backed up "azure.pfx" file from the original server and copy it to the same location (UnityIS\Drivers) on the new server
2. Start up UnityIS Web Service
3. Start up the IMRON Access Driver service
4. Azure controllers should come online without any additional steps
   
   

If Scenario 2 applies to your situation:  

1. Make sure the UnityIS Web Service and IMRON Access Driver are running on the new server
2. Login to UnityIS Web Client using an operator account with access to Hardware Manager
3. Go to Configuration>Hardware Manager
4. Click on the  IMRON Access Driver
5. In the Property section for the Driver, scroll down to the "Host COM Certificate" property
6. Click on the 'Download Certificate' link and save the file to any location
7. Login to an Azure controller (model IC2 or IC4)
8. Go to the Admin>Host Communications section
9. Click on the "Upload Certificate" button and select the certificate that was downloaded in Step 6
10. Click Save
11. Back in UnityIS Web>Configuration>Hardware Manager, you should see the IC2/IC4 come online. 
12. Repeat Steps 7 to 11 for ALL IC2/IC4 controllers
    
    

If Scenario 3 applies to your situation:  

1. Copy the backed up "azure.pfx" file from the original server and copy it to the same location (UnityIS\Drivers) on the new server
2. Start up UnityIS Web Service
3. Start up the IMRON Access Driver service
4. Login to an Azure IC2/IC4 controller
5. Go to Admin>Host Communications section
6. In the Host Communications Enabled, make sure this box is checked
7. In the Host section, enter the IP address to the new server
8. Click Save
9. In UnityIS Web Hardware Manager, the Azure controller should come online in a few seconds
10. Repeat Steps 4 to 9 for the rest of the Azure IC2/IC4 controllers
    
    

If Scenario 4 applies to your situation:  

1. Make sure the UnityIS Web Service and IMRON Access Driver are running on the new server
2. Login to UnityIS Web Client using an operator account with access to Hardware Manager
3. Go to Configuration>Hardware Manager
4. Click on the  IMRON Access Driver
5. In the Property section for the Driver, scroll down to the "Host COM Certificate" property
6. Click on the 'Download Certificate' link and save the file to any location
7. Login to an Azure controller (model IC2 or IC4)
8. Go to the Admin>Host Communications section
9. Click on the "Upload Certificate" button and select the certificate that was downloaded in Step 6
10. In the Host Communications Enabled, make sure this box is checked
11. In the Host section, enter the IP address to the new server
12. Click Save
13. In UnityIS Web Hardware Manager, the Azure controller should come online in a few seconds
14. Repeat Steps 7 to 12 for the rest of the Azure IC2/IC4 controllers