Here are the revised instructions for moving an existing Key Management
server to another server in the same site:
It is recommended that you DO NOT move the Key Management server from one
Microsoft Exchange Server computer to another because of the critical
information kept in the Key Management database. There is, however, a
mechanism for moving the Key Management server if the need arises.
- Back up the advanced security data on the Microsoft Exchange Server
computer that hosts the Key Management server. See "Backing Up and
Restoring Advanced Security Data" in the Microsoft "Administrator's
Guide," Chapter 6.
- Use the Services option in Control Panel to stop the Microsoft Key
Management Service.
- Run the Key Management server Setup program and select the REMOVE ALL
option. This will rename your Security directory to Security.bak and
remove the Key Management server components.
- Go to the Microsoft Exchange Server that will now host the Key
Management server.
- Run the Key Management server Setup program, which is on the Microsoft
Exchange Server compact disc in the EXCHKey Management directory.
- Use the Services option in Control Panel to stop the Microsoft Key
Management Service.
- Restore the advanced security data on the server where you ran the Key
Management server. See "Backing Up and Restoring Advanced Security Data"
in the Microsoft "Administrator's Guide," Chapter 6.
- Place the ORIGINAL Key Management server disk (from the original install
of the Key Management server) into drive A and start the Key
Management server service.
- After allowing for replication to occur within your organization
(this could take several hours depending on your topology), run the Key
Management server setup program on each of the other sites in your
organization.
The original Key Management disk is needed because it contains the 64-bit
encryption key for the database. Because the data that is being moved was
created with this key, it needs to be present to issue and revoke
certificates on the new location. If this disk is not used, new tokens
will need to be issued for all users in the organization.