I’m dreading this…
Our company (which uses notes for databases, but not mail) has been bought (again) and we’re being merged with another company (which does not use notes) . To add to this, we’re changing the name of our company.
We’re looking at not only changing our internet domain addresses, but also our notes OUs of at least our users, and possibly our servers as well.
The OU structure of our servers are;
Servername/location/companyname/country
The OU structure of our users is
Username/location/companyname/country
This is something I remember my Notes Administration teacher said; “Best just start from scratch”.
I see loads of articles addressing various small aspects of this.
Could anyone point me to the definative article on how to do this?
I guess at the very least we’d just want to change the companyname part. If I had my druthers and if I’m faced with such a massive change anyway, I’d rather go with something very generic like;
Servers;
Servername/location/NOTES
People
Personname/location/NOTES
btw… no budget to purchase anything…
Subject: Complete OU change
funny, the new OU structure you’ve proposed is exactly what we did a few years ago, exactly:
server/location/Notes
user/location/Notes
We did it for the same reason, been bought/sold a few time and got tired of changing OU/O. Well we recently got bought again and the company that bought us doesn’t like our new OU structure so guess what, we’ll be changing it yet again.
I don’t agree with the start-from-scratch approach. Yeah. it’s a bit of work and planning to run a smooth recert project for your entire org but it’s not all that bad.
Create your new org certifier and cross certify it with your existing org cert then create your new OU structure then start recertifying your users. Be sure you have adminP running. Not sure that there’s any really complete documentation out there. Try looking in searchdomino, in this forum and in the technotes section, collect everything you can and put together a plan.
One problem you may run into is if you use common names in Readers/Authors fields in your applications. Although this is a no-no we have a large app that was developed way bay in R3 that uses common names to control doc access. The caveat: if the user’s org cert does not match the org cert of the server then the user will lose access to their documents. We had to run 2 servers in parallel (clustered), certified by different org certs. Once users were recertified we moved them over to the server with the same org cert.
Recertifying your servers gets a little bit tricky. Since you don’t use Notes for mail I don’t want to mislead you so I will leave you to do your research on that topic. It may be worth your while getting in touch with IBM support if you have it.