Articles in this section

See more
Print

Migrating Cayosoft Administrator to new server

  • Updated
Follow

In this article:

Preparation steps

  1. Make sure you create a backup of all Cayosoft Administrator databases. Learn more in the following article: Backing up and handling Cayosoft Administrator databases. 
  2. Copy and save your Cayosoft Administrator service account credentials for the existing server. Learn more in the following article: Cayosoft Administrator service accounts. 
  3. Install Cayosoft Administrator to a new server using the same credentials. Learn more in the following article: Installing Cayosoft Administrator. 
  4. Stop the Cayosoft Administrator Service on the new server: navigate to the Services snap-in, locate the service, and click Stop.

Video tutorial

In this video tutorial, you will learn how to migrate Cayosoft Administrator to a new server.

Migrating the Cayosoft Administrator configuration to a new server is a straightforward operation that can be undertaken when necessary. One common reason for migration is transitioning from an on-premises deployment to a public or private cloud environment.

Important Notes:

  1. The configuration database should only be moved when changing servers. If you require a second server for load-balancing, regional support, or performance enhancements, consider using server-to-server replication instead. Review the following Cayosoft knowledge base article for more information: High availability & replication. 
  2. You can deploy the Cayosoft Management and Protection Suite VM from the Azure Marketplace and migrate it to this VM. Review the following Cayosoft knowledge base article for more information: Virtual deployment.

Copy configuration and reporting databases to a new server

On the original server:

  1. Open the Cayosoft Administrator console.

  2. Navigate to Home > Configuration > Settings > Configuration Databases.

  3. Click Export the encryption key (Make sure to save the password). Copy the key file somewhere to a new server. You will need it later.
    MigrateNewServerDBSettings.png

  4. Navigate to the Services snap-in and stop the Cayosoft Administrator Service.

  5. In the File Explorer navigate to C:\Program Files\Cayo Software\AdminAssistant\.

  6. Copy all files from this folder to C:\Program Files\Cayo Software\AdminAssistant\ on the new server (replace the files on the new server with the files from the old server).

On the new server:

  1. Navigate to the Services snap-in and start the Cayosoft Administrator Service.

  2. Open the Cayosoft Administrator console

  3. Navigate to Home > Configuration > Settings > Configuration Databases.

  4. Click Import the encryption key: navigate to the path where you saved the key file and use the password you noted in step 3 for the original server).

  5. Navigate to Home > Configuration > Web Portal > Web Portal Settings.

  6. In the Server URL specify the new server URL. For example https://corp-administrator.corp.net/.
    MigrateNewServerDBSettingsWebPortalURL.png

  7. If the Self-Service Password Reset was enabled, provide an encryption password used to protect data stored in Active Directory:
    MigrateNewServerDBSettingsSelfService.png

    • Navigate to Home > Configuration > Web Portal > Web Actions > Common.
    • Select the Self-Service - Password Self-Service Enrollment Details rule.
    • Enter the encryption password, configured in the Cayosoft Administrator console on the original server, to the Password to encrypt data in AD setting.

  8. Close the Cayosoft Administrator console and restart the Cayosoft Administrator Service.

Additional Tasks

By default, the Administrator archives the Execution History log to C:\ProgramData\Cayo Software\AdminAssistant\Backup\RunHistory. To preserve these archive files, copy them from the existing server to the new server.

Recommendations

Before decommissioning the existing server, ensure that the service is stopped and thoroughly test the new server. It is crucial to avoid running the services on both the new and old servers simultaneously, as duplicate rules could cause environmental issues.

Getting help

If you need assistance, please open a support case here and we will be happy to help you.

Related articles

Comments

0 comments

Article is closed for comments.