Defining /O and /OU structure

Our company is splitting into three separate groups, two of which will be standalone LLC’s but identified as divisions of the parent holding company. All incoming e-mail will go through a single Domino mail server, and all three divisions will send Notes mail to each other. I need to separate all the users into their respective new companies and make it appear to the outside world that the three are completely separate.

I’m thinking I need to create a new O certifier and new OU certifiers for each division. Then I need to recertify the users with the appropriate OU certifiers.

My main question is: how do I change the O and all servers registered in it without bringing everything down? And how do I get outgoing mail to show mail.division.com rather than mail.parent.com?

I apologize if this has been covered previously, I did some searches and most of the other posts refer to xSP, which I don’t think is what I need.

Thanks,

Charles

Subject: defining /O and /OU structure

Several points to consider:

Renaming a server is a complicated process. It needs a thourough planning. Think about the impact of renaming the server on issues like cross-certificate docs, location documents (on the client workstations), any mail routing tables (for example if you have a separate SMTP server), etc.

Best approach might be through the use of Decommissioning Tool, to build a base “to-do” list.

Recertifying users with new OUs also requires careful planning, as there are certain steps that the users need to get involved in the entire process so that their ID files on their workstations get updated with the new certificate. Main item to consider is end-user awareness or education.

You can write an agent to update the user’s email address to reflect the new email address. You may also need to create a Domain document(s) and update the records on your DNS server.