Posted by Perry Hiltz, Solutions Architect
Today's blog post was originally posted on June 21, 2011 on Perry Hiltz's wildly popular blog, Domino Diversions. As most of you may know, Perry is a Solutions Architect at Binary Tree and a long-time
IBM Domino solutions expert. Today, Perry is heavily involved
in the success of Binary Tree's pre-sales, technical, and support teams, and focuses primarily on educating and supporting customers during their Microsoft Exchange migrations.
The thought of renaming a Domino Server is a daunting task at best. There are innumerable considerations to address when undertaking this task. There is the server security, groups, connection documents, mail-in-databases, access control lists, and not to mention the user desktop icons. As I continue to work with various organizations, the thought of Domino server virtual clustering has proven to be a way to simplify some of these processes.
The concept entails an Enterprise version of Domino. The administrator will still need to register a new server in the Address book. This will be the new name of the server. Then the next step is to create a cluster with the old server name, then the new server name. Once the cluster directory and cluster replicator tasks are initiated, the cluster directory database will contain cluster information for only the old server.
The next step involves the creation of agents to scan all ACL’s to add the new server entry. Beware of roles, the agents will likely not associate the new server listing with any roles the old server had. Then connection documents to and from the old server need to be copied, and modified to use the new server name. Similarly group membership of the old server will require the new server to be added. Next will be to copy and paste, then modify all of the mail-in-database names. This will need to reflect the new server name. Once all of these aspects are in place, then the server’s Notes.ini can be modified to use the new server ID file for serverid= and keyidfile= to use the new server ID file.