Moving an UNICOM Intelligence Interviewer server to a different Microsoft Windows domain
The following instructions explain the process for moving an UNICOM Intelligence Interviewer server to a different Microsoft Windows domain.
1 In the Microsoft SQL server, make a backup of every UNICOM Intelligence related database (for example, mrInterviewData, mrUserData, Participants). You must also backup each UNICOM Intelligence project database. The project database names are the same as the project names in UNICOM Intelligence).
2 Backup the UNICOM Intelligence folder:
[INSTALL_FOLDER]\IBM\SPSS\DataCollection\<version>\Interviewer Server\FMRoot
3 Backup the UNICOM Intelligence folder:
[INSTALL_FOLDER]\IBM\SPSS\DataCollection\<version>\Interviewer Server\Projects
4 Uninstall UNICOM Intelligence Server, and delete all UNICOM Intelligence related files under C:\Program Files and C:\Program Files\Common Files.
5 Restart the server and connect it to the new domain (for example DOMAIN-B).
6 Set the new domain (DOMAIN-B) as the SQL admin role, and confirm that SQL server works with new domain (DOMAIN-B).
7 Create the necessary Windows users and groups for installing DC 6.0.
8 Install UNICOM Intelligence Server with a new domain user (DOMAIN-B).
9 Because the Microsoft SQL server in not reinstalled, all of the UNICOM Intelligence databases are available. However, you must run the following scripts to replace the domain name in database user tables:
use mrUserData;
UPDATE Users
SET UserName = REPLACE(UserName,'DomainA\','DomainB\')
WHERE CHARINDEX('DomainA\', UserName)>0
use mrInterviewData;
UPDATE AccessControl
SET SecurityId = REPLACE(SecurityId,'DomainA\','DomainB\')
WHERE CHARINDEX('DomainA\', SecurityId)>0
AND SecurityType = 1
10 Rebuild the Users table indexes in the mrUserData database, and the AccessControl table indexes in the mrInterviewerDatadatabase. The indexes can be rebuild in Microsoft SQL Server Management Studio (Databases > [database name] > tables > [table name] > indexes. Right click indexes and select Rebuild all.
11 Restart the UNICOM Intelligence server and confirm that the migration is successful.
See also