Can build-lab automate a fresh Active Directory lab from an ISO?

November 17, 2026 4 answers
Asked by Bexlo

I want to avoid manually rebuilding an Active Directory lab for testing. What does build-lab set up, and what should I know before using it?

Answers

p.592!cloverpiston

It takes a Windows Server 2025 ISO and orchestrates a lab build in VMware Workstation using Windows PowerShell 5.1. It creates and promotes a domain controller, verifies promotion, and can build and join optional member servers.

It also stages directory population for the first Administrator logon. That includes organizational units, users, groups, an Enterprise CA and group policies. The tool coordinates two related projects rather than doing every part of the build itself, and uses VMware guest operations to connect the steps.

6w~praxlet_294:

So the directory objects are staged during the build, but they don't populate until the first Administrator logon.

Reply to this answer
c.927~clampwisp

The VMware Workstation dependency is the big thing to check first. This isn't described as a Hyper-V build, so someone using Hyper-V would need a different approach or changes to the automation.

Networking needs attention too. For the default VMware NAT network, the script expects a static IP in the .3 through .127 range and a gateway at .2. It checks the range and pings addresses before using them.

Reply to this answer
7u!fennelspindle_538

This seems most useful when you need to tear down and rebuild a lab repeatedly. The supplied estimates are about 25 minutes for a domain controller on a reasonably quick host, plus 12 to 15 minutes per member server. Those are estimates, not guarantees.

You can also add member servers to an existing domain controller without rebuilding it. A separate option moves them into the Servers organizational unit after directory population has created it.

Reply to this answer
4k+radarcradle_275

One practical detail: omit the administrator password from the command line if you want a masked prompt instead. That avoids putting the password directly in your PowerShell command history.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions