Server 2012 WDS under Virtualbox
I teach a Systems Administration course for the university where I work. As such, I like to take the students through real-world examples using virtual labs. In researching one such lab, I ran across several snafus and figured a blog post was in order.
In trying to setup Server 2012 under Virtualbox with Windows Deployment Services to both deploy new installations and create images for deployment, I ran into some issues. To bring you up to speed, my setup is:
In trying to setup Server 2012 under Virtualbox with Windows Deployment Services to both deploy new installations and create images for deployment, I ran into some issues. To bring you up to speed, my setup is:
- Active Directory Domain controller running Server 2012 x64 and serving DHCP requests
- This server has two NIC's (acts as a router)
- One setup for NAT to the outside world
- One setup for Internal Network "intnet" for domain local traffic on 192.168.1.1/255.255.255.0
- Remote Access Role installed with NAT routing configured with the NAT NIC as the route to the outside world
- Windows Deployment Services server running Server 2012 x64 1 NIC on internal network "intnet"
- A client machine setup for 32 bit windows 7 with 1 NIC on internal network "intent"
This is a brief summary of what I had to do; and a few steps that I did do that go in the way...
- Setup Domain Controller (2012)
- Make sure DNS is part of DC setup
- Add DHCP scope to server
- **** DO NOT DO THIS --> Configure the “Server Options”
- These two options are for cross domain functionality
- Add 66 (WDS server name)
- Add 67 (bootfile name: boot\x86\wdsnbp.com)
- This option is only if you are using DHCP on the WDS server; which I am not
- Add 60 (pxeclient)
- Setup Windows Client
- Install Virtualbox Extension pack
- https://www.virtualbox.org/wiki/Downloads
- ***Enables PXE booting for Virtual Intel Cards
- The PC-net adapters have pxe capabilities, but the windows image doesn't (by default) have drivers for them; it will start to boot the installer image then fail and restart
- On a side note: the PC-net nics work just fine for a similar setup with FOG as the imaging server
From here, you should be able to set things up as normal, use a Windows 7 client iso to add an installer image and a boot image, install Windows 7 to a pre-staged client and then create a capture image to capture the Windows 7 machine and deploy it to yet another new VM.
Comments