Migrate SQL server to Devolutions Server

Devolutions Server Console includes a Migrate SQL Data Source wizard to ease transitions from Microsoft SQL Server (MSSQL), including Azure, to Devolutions Server. When operating an Remote Desktop Manager SQL advanced data source, the recommendation is to use a security provider for additional encryption of data. Devolutions Server does not support security providers, but has equivalent protection via encryption keys stored on the IIS web host for Devolutions Server.

Removing the Security Provider

You must remove the Remote Desktop Manager Security Provider, before running the migration wizard, or an error message will prompt you to do so.

When removing a Security Provider, it is important to complete these steps beforehand:

  • Prior to removing an existing security provider, make sure that all users are disconnected from the data source.

  • Removing a security provider does process the whole database, therefore we advise you to create a backup prior to this operation.

  1. Go to the desired Microsoft SQL Server data source.

  2. Select the Administration tab in the ribbon.

  3. Click on Security Provider. Security Provider

  4. Click on Change Security Settings. Change Security Settings

  5. In the dropdown select the Default option and click Apply. Default security type

  6. Click Yes after the warning window appears (this may take some time with larger data bases). Warning window

  7. Click Close. Close

Migrating MSSQL to Devolutions Server

This operation assumes that you have Devolutions Server Console installed on your target Devolutions Server Console host. You may migrate an MSSQL data source prior to fully installing an instance of Devolutions Server.

This procedure operates on the existing database, not a copy. To revert this process, you would need to restore from a backup, therefore it’s recommended to make a full backup.

  1. Open the Devolutions Server Console.

  2. Navigate to ServerNewIIS Web ServerMigrate SQL Data Source. Migrate SQL Data Source

  3. Enter the information in the Database and Credentials sections.

  4. Enable Activate Encryption At Rest. With this option enabled, a new encryption.config file is generated and data re-encrypted via the newly created key.

  5. Click on Test Connection. Test Connection

  6. Click OK. OK

    The “Database contains encrypted data” warning is specific to Devolutions Server encryption keys and not default Remote Desktop Manager data encryption.

  7. Enter the Server name and click Next. Server name

  8. Choose which version of Devolutions Server to download and click Next. Download version

  9. Fill the information fields for the IIS Settings of the new Devolutions Server installation. IIS Settings

  10. Enter the information for the new administrator user. Administrator user

    Install the Scheduler Service if this is the first instance of Devolutions Server Console.

  11. Configure the Recovery Kit and click Next. Recovery Kit

  12. Click Install. Install

Once the process is completed, the new Devolutions Server installation will be immediately available for use. At this time, you will want to add a new data source for your Remote Desktop Manager clients to connect to the Devolutions Server data source.

Migrating database users

For security reasons, it is strongly advised to migrate database users to a new Authentication method, after adding a new authentication provider. The Authentication migration tool can be used in this process.

See also

Devolutions Forum logo Give us Feedback