3.2

Table Of Contents
Understanding the Central Configuration Server
106
The following procedure is based on these assumptions:
Server A is the CCS.
You want to keep the CCS settings and user information that exist on server A, but move
them to server B.
You do not want to keep the original CCS information that exists server B.
c
Server B should be created by a clean installation and should serve as its own CCS. No
other database should point to Server B as a CCS, because any existing user data on Server
B will be lost.
To move a CCS to another server:
1. Back up the database. See “Creating and Restoring Database Backups” on page 29.
2. Make sure that the Interplay Engine on both servers is the same version. See
“Viewing
Server Information” on page 87
.
3. Start Interplay Administrator and log in to server A (which is the current CCS).
4. Lock server A. See
“Locking and Unlocking the Server” on page 89.
5. In Interplay Administrator, log out of server A.
6. Log in to server B.
7. Lock server B.
8. Log out of server B.
9. Use Windows Explorer to delete the _InternalData folder on server B.
The folder is located by default in \\IEServer\WG_Database$ (usually
D:\Workgroup_Databases\). See
“Identifying the Root Folder of the Interplay Server
Database” on page 85
.
10. Copy the _InternalData folder from server A to the default database location of server B.
11. In Interplay Administrator, log in to server A, unlock the server, and log out.
12. Log in to server B and unlock the server.
13. Make sure the CCS for server B is set as server B itself. If necessary, complete
“Viewing and
Changing the CCS for a Server” on page 107
.
14. Log out of server B.
15. On server A, change the CCS for server A to server B using
“Viewing and Changing the
CCS for a Server” on page 107
.