> > Note that I am talking about naming contexts, not DIT structure. > > It is common practice for companies to use e.g. dc=bigcorp,dc=com, when > > their name is Bigcorp, Inc. > > When they get bought by Biggercorp, Inc, Biggercorp naturally wants to > > change the naming context to dc=biggercorp,dc=com. > > This is the unfortunately too-frequently occurring situation which I am > > trying to describe. > So what? This is going to be a rather small data migration project then. > I write a script for migrating the data usually in one hour. > There are much bigger directory issues during a merger, e.g. changing > the search base in all connected applications... ;-)
I agree, there may be arguments against using DNs as references (although we've done so for years without any real troubles beyond those generated by colossal stupidity [including mine. :)]). The process of assimilating one organizations IT infrastructure into another's has yet to be (for me anyway, and I've done it almost a dozen times) anything as simple as a DIT naming context change. Usually the original Dit (if any!) is ransacked and abandoned. --- You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the SUBJECT of the message.
