To Merge, Trust, or Move? AD question

[techguru69]

Here's the scenario -
Company A has a complete AD setup on W2K with a somewhat complex structure due to software distribution and groups. They have about 700 objects in their AD.
Now, company B (also W2K AD) comes along and buys 50% of company A. The top exec's are asking both I.T. departments to set a plan for integration. Comapny B's Net Mgr. says that user integration is first and gives his opinion that Company B should just start adding Company A's objects into their AD. Company A's Net Mgr. disagrees since he sees that Company A has already established a working AD with some complexity and by just moving objects to Company B's AD would cause alot more work for him and would disable their ability to use some aspects of AD for their benefit.

My question is, as I see it, there are 3 options here:
1. Create a 2-way transitive trust between the two AD's and work it from there. (the easiest and quickest solution).
2. Move users from A to B as suggested. (more complex and disadvantages for A).
3. Upgrade both domains to 2003 AD and perform a Merge.

What do you think? Have you ever run into this before? Are there other options?

Thanks.

 

[wdoellefeld]

When you say company B bought 50% of A are talking about just a division or piece of company A or both companies have now become one?


FRCP

http://www.frcp.net

 

[techguru69]

Company B and Company A created a new company that is owned 50% by Company A's owner and 50% by Company B's owner.

 

[aftertaf]

so is it a move from 'A' to 'B' for 50% of users & objects?

and this percentage might change in the future... who knows!!

is there either A or B that could end up Root of a tree?
cause as it sounds, things could get complicated... 2 companies collaborating to make a third...
an upgrade with 2 trees, plus a child domain might be easiest, failing that, 2 forests that trust.
this does depend on how they plan the future of A, B and now C.
Tell them you need more info, cos a decision at his point could make it a lot morre complicated for the future. do they need separate namespaces for all 3 entities now?


Aftertaf
if its not broken, fix it anyway - with luck you might break it and have an excuse