Joining a Domain Using a VM

I have a VM (Vmware) that is an AD controller on a specific domain.  I will call the domain testco.  I would like to join some more servers and PCs to this testco domain controller.  I'm sure this will work just fine.

Now I would like to take these servers and PCs that are now members of the testco domain and physically connect them into a LAN network at a different location (and leave the VM behind) that has an AD, DC and is in the domain called testco.

Server OS for the domain is Server 2003.

Will this actually work, or is there some trust relationships that would not exist?
TriCoreITAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Lee W, MVPTechnology and Business Process AdvisorCommented:
When you create a domain it gets a randomly assigned unique GUID (Globally Unique ID).  If the VM DC wasn't created as part of the physical domain if won't work and you'll have various errors around duplicate names.  And there is no way to "join" Domains that have the same name.
0
Adam BrownSr Solutions ArchitectCommented:
Unless the VM is on the *exact same* domain as the domains in the place you want to move the computers to it won't work. You would have to join the VM to the domain at the other location, promote it as a DC, add the computers in the location that has the VM in it and then move them to the other location for it to work.
0
TriCoreITAuthor Commented:
The VM was created from the actual AD that is at the physical location of testco.  This means I should be able to move the serer and PCs to the site and be ok, right?
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Lee W, MVPTechnology and Business Process AdvisorCommented:
Yes, PROVIDED:
1.  You didn't seize FSMO roles at any time, AND
2.  The DC hasn't been off the network more than 60 days (by default).  After 60 days, AD considers it dead and will no longer talk to it (by default).  
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
dave_itCommented:
Was the virtual DC replicating with the rest of the Testco DCs?  If the virtual DC was isolated, and the servers and PCs were added to that isolated DC, then you are going to have all sorts of problems when you try to attach those servers/PCs to the production LAN.  If the virtual DC was replicating with other DCs in the Testco domain, then you shouldn't have any problems plugging them into a network at a different location.
0
TriCoreITAuthor Commented:
This VM did work as is was isolated and the only AD.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.