Domain Consolidation & Desktop Policy Questions

I am in the process of upgrading our Domino infrastructure to R7 servers with R8 clients. I will be consolidating several disparate domains into one new domain. My plan is to cross-certify the new Organizational certificate with the Domino directory of each domain and then on a domain-by-domain basis recertify the users under the new certifier. Once all of the users of a given domain have authenticated and their IDs have updated my plan is to copy their person documents into the new Domino directory.

My expectation is that AdminP will update the ACLs, Reader & Author fields in the datbases on the servers of the domain being migrated with the new hierarchical user information. I would copy the groups from the Domino Directory of the domain being migrated into the Domino Directory of the new master domain.

After the users are dealt with my plan is to create new server IDs in the new domain for the servers in the domain being migrated and configure the server, configuration and connection documents for those servers in the Domino Directory. I would then bring down the servers during to copy the new server IDs to the servers and would update the notes.ini for each server as well as file-level replicas of the new names.nsf, certlog.nsf and admin4.nsf to each server. I am anticipating that when the servers are brought back online that they will start up as their new names and part of the new domain. I would then use the admin client to set admin server for the databases on the server en masse. Hoping that this method will be sucessful I would then repeat the process on a domain-by-domain basis until all of the domains have been rolled into one.

My question is can I use desktop policy to push down the new server info to the notes.ini and names.nsf files on the workstations after the “new” servers come online? I am concerned because the workstations will all be looking for their old servers so I am guessing that unless the users try to open a database that they will not receive a policy update. Mail is not an issues as this is an application-only environment, but the matter of directory servers and bookmarks would still be unresolved.

I was wondering if I write an agent to replace the server names in the database catalog with the new server names will the fact that the path and replica ID remains unchanged in the database catalog allow client requests for a database to redirect sucessfully?

Any feedback offered on my ideas would be greatly appreciated as I am certain that I’m not hitting all my marks so far. I’ve never undertaken a project of this scope and it’s pretty daunting. I have to get it right the first time as there is no room for error.

Subject: Check out CMT For Domains

This tool from BinaryTree will greatly reduce your efforts and make the migration much simplier. Visit http://www.binarytree.com/domains