1. Copy the ‘Data' folder from the old (existing) UnityIS server (Typically: "C:\Program Files (x86)\UnityIS\Data") into a USB or network folder (which must be accessible from new UnityIS Server Computer). (See Figure 1)

Figure 1 

  1. After installing UnityIS, ensure that you are using the same version of UnityIS as your old computer. On the new UnityIS Server computer, rename the "Data" folder to something other than "Data," such as "Data1". Navigate to your old "Data" folder (by opening the USB or network folder) and copy the "Data" folder then paste it on the new UnityIS server. (See Figure 2)

Figure 2 

  1. In the new UnityIS Server, launch UnityIS and go to the "Hardware Manager". Unlock the module and click on a driver to view the properties pane. In the properties pane, change the "Computer_Name" to the new computer name (Note: you can see the new computer name in the UnityIS information box located on the top right-hand corner of the UnityIS application). In the "Service Username" field, enter the Windows User name of the user currently logged into Windows. In the "Service Password" field, enter the password for the Windows User currently logged into Windows. Click the "Save" button to save these changes. Repeat this step for every driver in UnityIS. (See Figure 3)

Figure 3 

  1. Open Windows File Explorer and navigate to the UnityIS installation folder (Typically: "C:\Program Files (x86)\UnityIS" ). Open the "Configuration" application and click the "Save Changes" button. (See Figure 4)

Figure 4 

  1. Select an UnityIS Driver and right-click on the driver. From the "Driver Commands" sub-menu, click on "Start Driver". The gear icon next to the driver should turn green to indicate the driver is running. Repeat this step for every driver. After you have started all of your UnityIS drivers, open Windows Services and verify that all of your drivers show as "Running". (See Figure 5)

Figure 5 

  1. Verify all your data (Personnel Records, Access Levels, Time Schedules, etc.) is correct. Perform a full (i.e. all databases) download to all the controllers. (See Figure 6)

Figure 6