Redesigning OU structure in AD - best implementation technique?

- January 25, 2010

hi,

my question regarding implementation technique rather design. have redesigned new ou structure companies ad on paper , required make changes on infrastructure itself.

the current set follows:

2 x physical dc servers, dc1 , dc2 (replicating)

windows server 2008 r2

no test vlan of yet (planning implemented asap)

as per above, plan far to:

1. create test vlan

2. create dc3 virtual machine , put in vlan

3. import objects minus ou folders dc1/2 dc3 via admt

4. organise objects new ou structure.

5. test in development vlan

6. if working ok, add production vlan , enable replication other dc's transfer changes.

i know...

will work? there better way? , need mindful of?

thanks!

i not convinced approach taking friend. if think in place ou redesign, computers affected, same thing happens if migrate them new domain because lose relationship old gpos. if want build clean , fresh environment different story.

but mentioned earlier in place redesign of ou structure have no impact unless have third party application rely on ou names instead of guid in ldap based functions. have done many times , far experienced no problems in long term. best practice document old gpos linked old ous in order keep them linked after redesign.

regards.

mahdi tehrani | | www.mahditehrani.ir
please click on propose answer or mark post , helpful other people.
posting provided as-is no warranties, , confers no rights.