Creating a test Domain - Advice

[maxrebo]

Id like to set up a test domain for me to test PS scripts and OS deployments. I'm conscious of it interfering with our live domain,

 

it will need internet access to update various things.

 

I will be using VM Workstation or similar.

 

Any tips to get started?

[PotNoodleTech]

If your live domain is virtualised why not restore a copy to a seperate server use a seperate switch build a couple of PCs and run it totally offline - that way you cna test whatever you want for real first.

[Aprice]

If it's being Natted by workstation, it should be ok. Provided nothings using the test domains as its DNS servers it should be OK.

[Davit2005]

It's potentially a fair bit of work depending on what you want to test. I ran a full domain at home for a few years with domain controllers(domain services, DNS and DHCP), certificate services, MDT/WDS for OS deployment, Azure sync tool for Office 365.

 

As long as you are aware of what the PowerShell scripts are doing and not jus some random script found on the Internet what are you expecting in terms of conflict or issues?

 

It is pretty simple to setup a test domain and you have a few options if you go ahead i.e. put it all behind it's own router or firewall zone, you can use vlans on switches to keep it separate.