Please follow the Standard Installation Steps to add all necessary components to the new server (IIS, .Net Framework, SQL Native Client, ADOMD.NET 11, and AMO, etc.), you can find all this information in the Standard Installation Steps. When installing the Analyzer, it will ask you to enter a serial number (key), please use the main server key.
Once installed, I would recommend this one extra step as recently the Windows security has changed. Please go to the folder where the Analyzer is installed, select the Analyzer folder property, go to the Security tab and specifically add the Windows user that you are using to the folder and give it Full Control so it has the Write privilege to all the files under the Analyzer folder.
Once done, launch the Analyzer as an administrator, go through the initial configuration process to register the server key, and go through the steps to create a new system database for the Analyzer (the initial configuration option only allows to create a new database so we will create it but delete it later). Once the Analyzer is up and running, go to the System Administration Page > License Manager, then add the remaining keys.
Now you should have a brand new working system so we can now redirect it to the old database. The steps are:
1. Delete the dbo.Licenses table in the existing database (the old database migrated to the new server).
2. Recycle the Analyzer application pool in the IIS or do an IISreset at the command line to ensure the Analyzer will restart from scratch. Don't launch the Analyzer yet.
3. Go to the analyzer\web\config folder, open the dbconfig.config file. Change the current database name (the dummy database that we have created at the initial configuration step) to the existing database name.
4. Open the sysconfig.config file. Search for "Upgrade Flag". Change the value from "1" to "0". This should trigger the Analyzer to update the database with any new additional table or fields.
5. Launch the Analyzer, it will now connect to the target database that we specified in the dbconfig file and re-create the dbo.licenses table in the database.
6. Once you are in the Analyzer, it is possible that the user that you are using no longer is an Analyzer administrator, this is due to the Analyzer now reading the old UserProfiles table. Also please remember that all the user names have the old domain so none of your users can access the Analyzer as of now. We can quickly correct the administrator problem by running the below SQL statement (changing the user name to your Windows user name), this will grant the user the Analyzer administrator privilege once more:
INSERT INTO dbo.RoleMembers ( RoleId, MemberId, MemberType )
VALUES( 1133263532, (select UserId from dbo.UserProfiles where UserName = 'GNZ\User1'), 0)
7. Now the only remaining step is to update all the usernames in the dbo.UserProfiles and duo.SecurityMembers to have the new domain name if it has changed. Once changed, your user should be able to access the Analyzer as before.
8. This step is for scheduling and subscription and only if you have moved your system database of the Analyzer (BOStore). When the database is moved to a new server, the SQL Agent jobs created by the Analyzer that handles the scheduling cannot be moved (it will end up with a different ID), therefore, the Analyzer will need to re-generate all these jobs. Please go to the System Administration Page > Database Server Configuration. Check the Re-deploy all subscriptions box at the bottom then click the OK button to regenerate all the SQL Agent jobs.
9. You will also need to install the Analyzer Export Service either on the same server or on any other server(s) in order for the Analyzer to perform Excel, PDF, or PPT export. Recently a few of the anti-virus software would mistakenly identify the AES module as a threat, therefore, to ensure running properly, please first white-list the Program Files\Analyzer Export Service folder so the AES can install properly.