HealthCast

Create a backup of your current database.

Restore these backups to a different database name, With an updated naming convention as it will be used to migrate the data.

Run the Update SQL script to upgrade the restored backup.

(Repeat the previous 3 steps for each database to bring them all to a 4.10 functional level)

If you are attempting a full 4.11 upgrade. Continue on to Migrate 4.10 to 4.11.

Install at least two new 4.11 servers to support client/endpoint load.

Create a backup of your current XA 4.10 database

1. Restore this backup to a different database name, as it will be used with a 4.11 server.

2. Run the Update_04_11_00.SQL to upgrade the restored backup.

3. Use this database exclusively by your 4.11 XA/SSO server.

Create a backup of your current Prox 4.10 database.

1. Restore this backup to a different database name, as it will be used with a 4.11 server.

2. Run the Prox Migration Update 1 (MSSQL).sql to upgrade the restored backup.

   Warning

   You will receive an error that is safe to ignore (The Pin and PinTime fields already exist in 4.10, but do not exist in previous versions):

   Column names in each table must be unique. The column name 'PIN' in table 'dbo.RFIDtoXAName' is specified more than once.

3. Use this database exclusively by your 4.11 Prox server

There is no reason to change or migrate the AUDIT database – the update simply adds 2 indexes (these indexes are not used by auditSERVER, so there is no compatibility problem) to the database. These are intended for use by the Audit Reporting Tool (installed separately).

1. Alternately, the database can be backed up for retention, and a new empty database can be created for use with both 4.10 and 4.11 servers using the database.sql from the 4.11 server install (adding the indexes on a large database can take a significant amount of time, depending on the amount of data that must be sorted/indexed).

2. Alternately, a new 4.11 database can be created for exclusive use by the 4.11 auditSERVER service.

Install a new 4.11 HCIDeploy database for exclusive use by the 4.11 HCIDeploy server service.

1. Get with your project manager for rebuilding the deployment packages for use with the new server.

2. Please note that 4.10 clients cannot be remotely managed by 4.11 client tools and 4.11 clients cannot be remotely managed by 4.10 client tools.

3. In addition, 4.10 client tools cannot be used to maintain (e.g. publish) packages on the 4.11 server, nor can 4.11 client tools be used to maintain packages on a 4.10 server.

4. In addition, 4.10 clients will not install if the package install/uninstall scripts are renamed with the new 4.11 server features where the user can flag a particular file (.vbs, .bat, or .exe) as the install or uninstall script. (4.10 clients ONLY execute .vbs or .bat files, and they MUST be named install.* and uninstall.*)

Once all Server services are operational, a final step to complete is to register the DESKTOP_SERVER.XML if you were using the Toolbar Desktop in the previous version. This can be found on the server in C:\Program Files (x86)\HealthCast\ExactAccess\DESKTOP_SERVER.XML This file adds support for the new work-space display in the 4.11 client.

Remove the current XA server from the load-balanced pool so that traffic is no longer directed to this server.

(Optional) Stop the ExactAccess services to avoid a reboot.

Export the HKEY_LOCAL_MACHINE\Software\HealthCast registry key, and save the file.

Run the server update 4.11_server_update1_x64.msp

Import the registry key from step 3, to restore your original XA server settings.

After installation, locate and Run the Update4111.sql script (using Microsoft SQL Server Management Studio) against the current 4.11 proximity card database. This is a minor update to the database that adds a new stored procedure that will be used by the 4.11.1 ProxCard server service.

Either reboot or restart the services to complete the installation.

Put the server back into the load-balanced environment.

Repeat these steps for each additional server in the load-balanced pool.

Remove the current XA server from the load-balanced pool so that traffic is no longer directed to this server.

(Optional) Stop the ExactAccess services to avoid a reboot.

Export the HKEY_LOCAL_MACHINE\Software\HealthCast registry key, and save the file.

Run the server update 4.11_server_update2_x64.msp

Import the registry key from step 3, to restore your original XA server settings.

Open the server configuration tool to automatically generate the database encryption keys for both the SSO and ProxCard databases

If this is the FIRST server to be upgraded, EXPORT the keys to a password-protected file for use on subsequent servers.

If this is NOT the first server, overwrite the auto-generated keys by IMPORTING the previously saved keys from the first upgraded server.

After installation, locate and Run the Update_04_11_02.SQL.sql script (located in C:\Program Files (x86)\HealthCast\ExactAccess\SQL\MSSQL\xa\Migration) against the current 4.11 ExactAccess server database (using Microsoft SQL Server Management Studio). This is a minor update to the database that adds new stored procedures that will be used by the updated server to indicate the encryption key configured

Return to the XA Server Configuration Tool and choose to set the server to LEGACY encryption mode until all SSO servers have been updated.

Locate and Run the Update_04_11_02.SQL.sql script (located in C:\Program Files (x86)\HealthCast\ExactAccess\SQL\MSSQL\prox) (using Microsoft SQL Server Management Studio) against the current 4.11 Proxcard database (using Microsoft SQL Server Management Studio). This is a minor update to the database that adds new stored procedures that will be used by the updated server to indicate the encryption key configured

Return to the XA Server Configuration Tool and choose to set the Proxy server to PROX_LEGACY encryption mode until all Prox servers have been updated

Either reboot or restart the services to complete the installation.

Put the server back into the load-balanced environment.

Repeat these steps for each additional server in the load-balanced pool.

Once all servers have been updated, and there are no longer older versions using the SSO or Prox databases, re-visit each server and change the Encryption Method to something other than LEGACY - such as AES192 - a server reboot or service restart is NOT necessary when making this change. The servers will then begin using the new encryption method while maintaining the ability to read existing legacy data. Records will be encrypted with the new method when some portion of the data has been changed or new records are created.