

To setup your virtual machines, click the prickly blue New button in the Oracle VM VirtualBox Manager and pick your OS version and memory size. The name should also match for all hosts participating in the same internal network. The only difference is that under the Network tab in your VirtualBox Settings, Adapter 1 must be set to Internal Network. Setting up Windows 8.1 Pro in VirtualBox is almost identical to setting up Windows 10 in VirtualBox. Once you have all the ISOs on your computer we can setup the virtual machines. These files are gargantuan (4GBs per file) so make sure you have ample space on your hard drive before you start the download frenzy. pFsense is our special sauce.Ĭompleting the above four steps could take several hours because of the sheer size of the Windows ISO files. PFSense will be the virtual router that gives us the liberty to connect our internal VirtualBox guest machines to the internet. Without this our Active Directory burger is nothing. This is the 1/4 pound of grass fed organic beef. You can get the Windows Server 2012 R2 iso directly from the Microsoft Evaluation Center. In fact, if you can actually legally download every version of Windows for free. You can download the Windows 8.1 Pro media directly from Microsoft. Next, we need to obtain a real Windows 8.1 Pro ISO image. This is the bun for our proverbial burger. If our virtual Active Directory Domain controller were a big juicy burger we would need a few ingredients to make it:įirst, download and install Virtualbox on your host machine. So although it’s easy to get going it will take a few hours to download all the files and configure your virtual environment. Then you could install Windows 8.1 and Windows Server 2012 virtual machines and configure a virtual switch to connect both computers.Īre you with me on option 3? I hope so! Let me show you how simple it is to pull this off. You could setup a free virtual environment on your computer in a completely isolated network.You could cough up a butt load of money to buy real equipment.You could completely abase yourself by buying your boss’s children Christmas presents so he would be more amenable to letting you setup a lab in the office.You need to interact with the software.īut how can you realistically do this? Well there are two options no wait – three options: You need to join a real Windows workstation to the domain. You need to sit in front of a real Windows Server 2012 machine. Over the next three days I’m going to show you how to setup Active Directory and join a PC to your new domain but I want you to know this isn’t something you can learn by reading.
