Omnissa Access DB Migration 

Introduction

We’ve encountered numerous cases where customers have requested assistance with migrating both the UEM Database Server and Application Server, typically for two key reasons: 

  • Outdated Windows Server OS 
  • Internal Restructuring 

In addition to these, there are instances where customers also seek help migrating their Access Database. While these requests are not as frequent, they do occur. This brief blog will outline the process for migrating an Access Database to a new server, as well as how to reconfigure Access Nodes to point to the new database server. 

Migration Process

Like most database migrations, moving an Access Database follows a similar process of performing a full backup and restoring it on the new server.

Steps (to be performed with the Database Administrator):

  1. Perform a Full Database Backup:
    • Select the Database → Right-click → Tasks → Backup 
    • Choose Full Backup 
    • Specify the backup location 
  2. Restore the Backup:
    • Open SQL Server Management Studio (SSMS) and navigate to the Object Explorer 
    • Right-click on the Database and select Restore Database 
    • Follow the prompts to complete the restore process 
    • Confirm that the restore is successful and that the database catalog is visible 
  3. Configure Workspace ONE Access:
    • Log in to Access as the root user using an SSH client 
    • Navigate to the following directory: 
      /usr/local/horizon/conf/runtime-config.properties 
    • Modify the JDBC URL as needed 
    • Save the changes 
    • If in a multi-node cluster, repeat the process on other nodes 

Conclusion

This migration process is fairly straightforward, and you should not encounter any issues if followed correctly. Once completed, your Access Database should be successfully migrated and reconfigured to work with the new server. 

If you have any questions, regarding the Access DB migration and/or post migration issues, please feel free to reach out.

Leave a comment