Active Directory Test envioroment.

Hello All,

I'm trying to setup a test lab that mimics production as close as possible. I have a root and a child domain with many 2003 DC's in each one. I'm considering adding a 2003 VM DC to production, then backing up the system state on  it and restoring to a hyper-V isolated guest. Has anyone done this before or may have a better suggestion? I don't care to test everything, my main concern is to be able to add a 2012 DC to the root domain and promote it.
CNBELGINAsked:
Who is Participating?
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.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
What we do is P2V or V2V existing Real Domain Controllers, and move them into a virtual environment, we've been doing this for many years.
0
Manojkumar RaneCommented:
You can use Disk2vhd tool to convert your existing 2003 DC and create VM using that VHDs. Then you can add 2012 DC in existing domain and if you want to configure 2012 DC as FSMO roles holder, you can transfer all roles on 2012 DC.
0
CNBELGINAuthor Commented:
Is there anyway to restore a system state backup to a VM?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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
CNBELGINAuthor Commented:
Hello Andrew,

Thanks for this information,

I'm testing with Hyper-V and my production DC's are windows 2003. Will the latest version of this converter work with windows 2003? Is there any risk associated with converting a production 2003 DC as long as the copy does not touch the production network?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Okay, 2003, is not going to work with the latest free Microsoft tools.

Is there any risk associated with converting a production 2003 DC as long as the copy does not touch the production network?

none. no -risk!
0
CNBELGINAuthor Commented:
Which product could i use for 2003?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Disk2VHD or VMware Converter (to VMware), and then V2V (using StarWind V2V) to VHD.
0
CNBELGINAuthor Commented:
Hello Andrew,

Sorry for the back and forth,

I found the below article will Disk2VHD affect my production 2003 servers?

When shouldn’t I convert?

I don’t recommend converting a physical server if it’s running DC. Instead, you’d need to create a VM from scratch, enable the DC role there, sync it with your main DC and then pass the FSMO role over there. There are plenty of articles to help you with this situation.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
In production this is true, but it can be done! (Best Practice is to create a new and transfer roles, but P2V does work!)

Disk2VHD will not affect the running DC...

and is acceptable for Test Labs.
0
CNBELGINAuthor Commented:
Thanks, i will try it and report back.
0
CNBELGINAuthor Commented:
Hello Andrew,

After P2V-IN two DC's, DNS is not available on both of them. Any ideas?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
You need to check the logs.
0
CNBELGINAuthor Commented:
Ok i discovered that TCP/IP  is somehow broken, i cannot ping or even do an ipconfig on both servers. The production servers are HP Blade servers. It may also be a problem with HP branded software on the VM's
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
That's because, your virtual hardware does not have any network interface!!!!

Did you install the Integration Tools for Hyper-V, so you have a Network Interface?

Check Device Manager, any missing hardware or drivers!
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.