James B
asked on
Windows server 2016 setup
I am setting up windows server 2016 for the first time and wanted to know if I wanted to setup additional server AD, hyper-v, other servers to add to a domain etc, would I need to have a separate server for each (physical) or create them as I've seen in videos after installing the initial windows server 2016?
This is for a home production environment?
This is for a home production environment?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hyper-V is a role in Windows Server.
You install Windows Server to the hardware. Then, you add the Hyper-V role. Then the PHYSICAL server can do NOTHING ELSE - ONLY HYPER-V.
Then you install UP TO 2 Windows VMs (unless you buy more Windows LIcenses). The VMs can become a DC and another server.
I would suggest you read my Servers Sharing Service Article for more information on what can go where.
https://www.experts-exchange.com/articles/28694/Servers-Sharing-Services.html
And MAKE SURE you set this up as a test first. If you don't know what you're doing, you'd be foolish to make your first setup your production setup. Setup once, test, learn, ask questions. Frankly, I'd then suggest repeating the test adjusting with what you've learned. THEN setup a third time in production. Else, hire a pro to help you get it right the first time.
You install Windows Server to the hardware. Then, you add the Hyper-V role. Then the PHYSICAL server can do NOTHING ELSE - ONLY HYPER-V.
Then you install UP TO 2 Windows VMs (unless you buy more Windows LIcenses). The VMs can become a DC and another server.
I would suggest you read my Servers Sharing Service Article for more information on what can go where.
https://www.experts-exchange.com/articles/28694/Servers-Sharing-Services.html
And MAKE SURE you set this up as a test first. If you don't know what you're doing, you'd be foolish to make your first setup your production setup. Setup once, test, learn, ask questions. Frankly, I'd then suggest repeating the test adjusting with what you've learned. THEN setup a third time in production. Else, hire a pro to help you get it right the first time.
Your idea sounds good. One drive for Windows, then when you start creating VMs you use the separate drive. You can ise the OS drive as a file repository too (Isos, installers, etc)
ASKER