The steps are somewhat different in case of migration to a new version of SQL Server. For the purpose of this discussion, let us assume the following names:
• IntrmSRV Interim server; for instance, a Windows Server 2008 based computer running SQL Server 2008. This server should meet the system requirements of both your current production version and new version of Quest One ActiveRoles.
• TgtSQLSRV SQL Server that will host the Quest One ActiveRoles database for your pilot deployment; for instance, Microsoft SQL Server 2012. This SQL Server should meet the system requirements of the new version of Quest One ActiveRoles.
• TgtARSRV Computer that will run your pilot Administration Service; for instance, a Windows Server 2012 based computer. This server should meet the system requirements of the new version of Quest One ActiveRoles.
• TgtARSWI Computer that will run you pilot Web Interface; for instance, a Windows Server 2012 based computer. This server should meet the system requirements of the new version of Quest One ActiveRoles.
Given these assumptions, the steps will look as follows:
1. Install your current production version of the Administration Service on IntrmSRV, with the option to create the database on SQL Server running on IntrmSRV. Use the replication function to update the newly installed Administration Service with the configuration data from your production environment.
2. Install your current production version of the Web Interface on IntrmSRV, with the option to use the Administration Service running on IntrmSRV (select the Administration Service on this computer option button on the Administration Service Selection page in the Setup wizard).
3. On IntrmSRV, use the Web Interface Sites Configuration tool to create the custom sites based on existing custom configurations. This step is required if any custom Web Interface sites, in addition to the three default Web Interface sites, are deployed in your production environment.
4. Use SQL Server Management Studio to create a backup of the Administration Service’s database on SQL Server running on IntrmSRV:
a) In Object Explorer, right-click the database and select Tasks | Back Up.
b) On the Back Up Database page, in the Destination area, confirm the default path and name of the backup file or specify a different path and name of the backup file, and then click OK.
c) Wait while SQL Server creates the backup.
5. Use SQL Server Management Studio to create a database on TgtSQLSRV by restoring it from the backup you created on IntrmSRV:
a) In Object Explorer, right-click Databases and click Restore Database.
b) On the Restore Database page, type the database name in To database, click From device and select the database backup file you created on IntrmSRV, select the check box next to the name of the backup set to restore, and then click OK.
c) Wait while SQL Server restores the database.
6. Upgrade the Administration Service on IntrmSRV by installing the new version of the Administration Service with the option to create a new database. On the Database and Connection Settings page in the Setup wizard, complete the following settings:
a) In SQL Server, specify the SQL Server instance running on TgtSQLSRV.
b) In Database name, type the name of the database to be created by the Setup wizard for the upgraded Administration Service.
c) In Import data from this database, type the name of the Administration Service’s database you have restored on TgtSQLSRV.
d) Under Connection, choose the appropriate authentication method for connection of the Administration Service to the database.
7. Upgrade the Web Interface on IntrmSRV by installing the new version of the Web Interface.
On the Administration Service Selection page in the Setup wizard, verify that the Administration Service on this computer option is selected.
8. Install the new version of the Administration Service on TgtARSRV, with the option to use the database of the new version you have prepared on TgtSQLSRV. When installing the Administration Service, choose the following options in the Setup wizard:
a) On the Service Deployment Options page, select Install additional Service.
b) On the Configuration Synchronization Options page, select Share common configuration database.
c) On the Database and Connection Settings page:
• In SQL Server, specify the SQL Server instance running on TgtSQLSRV.
• In Database name, type the name of the database you have prepared on TgtSQLSRV (this is the database name you specified in Step 6, sub-step b).
• Under Connection, choose the appropriate authentication method for connection of the Administration Service to the database.
d) On the Provision of Encryption Keys page, select Retrieve keys from existing Service. For this option to perform as expected, ensure that the Administration Service on IntrmSRV is up and running.
9. Install the new version of the Web Interface on TgtARSWI. On the Administration Service Selection page in the Setup wizard, select Any Administration Service of the same configuration and type the fully qualified DNS name of the TgtARSRV computer.
10. On TgtARSWI, use the Web Interface Sites Configuration tool to create the custom sites based on existing custom configurations. This step is required if any custom Web Interface sites, in addition to the three default Web Interface sites, are deployed in your production environment.
11. Decommission server IntrmSRV by uninstalling the product components on that server, in the following order:
a) Uninstall the console (MMC Interface). Skip this step if you did not install the console on IntrmSRV.
b) Uninstall the Web Interface.
c) Uninstall the Administration Service.
As a result of these steps you achieve a pilot deployment of the new version of Quest One ActiveRoles with the following characteristics:
• The pilot Administration Service on a computer running the new version of the Microsoft Windows Server operating system (TgtARSRV)
• The Quest One ActiveRoles database on the new version of SQL Server (TgtSQLSRV)
• The pilot Web Interface on a computer running the new version of the Microsoft Windows Server operating system (TgtARSWI)
The pilot Administration Service and Web Interface have the same configuration as in your production environment. To add the Quest One ActiveRoles console (MMC Interface) to the pilot deployment, simply install the new version of the console on an appropriate server and have the console connect to your pilot Administration Service.