[TUTORIAL] Windows 2008 testing environment using Vmware Player part 2
In Part 1 we installed Vmware Player and installed Windows 2008 R2 Enterprise into a virtual machine. In this second part, we’ll look at setting up another virtual machine and deploying our first domain controller for the testing environment.
We could definitely go back and setup another virtual machine using the the same process as before. However, this takes too long; the least of which we have to wait for Windows 2008 R2 to re-install.
An easier option is to copy the existing virtual machine files to a new directory and paste it as a new virtual machine.
- Right click on our perviously built virtual machine (inv-dc01), select Copy and then right click and Paste into the same directory. This will create two copies of the virtual machine, inv-dc01 (the original) and inv-dc01 – Copy. This process can be repeated as many times as we like until the local drive is full.
For the moment, all that is required is the two copies of the virtual machine.
- Rename inv-dc01 – Copy to _TMPL-inv-dc01. Now we have a TEMPLATE version of a virtual machine with Windows 2008 R2 installed and can continue to take copies of it as needed.
Onto setting up our domain controller.
- Open the Vmware virtual machine configuration file by double clicking or right click and open the Vmware virtual machine configuration file with Vmware Player.
- Once the operating system has started, use CTRL+ALT+INSERT to get to the login screen.
At this point login as the user we created or login as Administrator. If you login as Administrator, Windows will prompt you to change the password. The Administrator password will also have to meet complexity requirements ie. uppercase, lowercase, letter, number and special characters.
- Next up is the all important Vmware Tools. VMware Tools package adds drivers and utilities to improve the graphical performance for different guest operating systems, including mouse tracking. The package also enables some integration between the guest and host systems, including shared folders, plug-and-play devices, clock synchronisation, and cutting-and-pasting across environments.
Click “Install Tools” in the bottom bar of the window to start the install process.
- You may want to close this window for the moment to allow the Vmware Tools installer to run.
- If this dialog fails to appear, open Windows Explorer, browse to the CD drive of the virtual machine and run setup.exe manually.
Install Vmware Tools using the default settings; there is no real benefit to be gained from changing the default options in our scenario.
Once the installer has completed, reboot the virtual machine and then log back in when it has restarted.
Once the desktop is initialised, there are a couple of configurations required before we can create the domain controller. Primarily, the IP address and the Windows machine name.
- The domain controller ABSOLUTLEY has to have a statically assigned IP address, and the easiest (and most fun!) way to do this is set it via the command line:
netsh interface ip show config
This will show all the adapters currently available to the virtual machine. The interface that we are interested in is Local Area Connection. Once we have establised that it is available and has an IP address allocated from DHCP, it needs to be changed to a static IP address.
netsh interface ip set address name="Local Area Connection" static 192.168.0.10 255.255.255.0 192.168.0.1 1
This set the static IP of 192.168.0.10, subnet mask of 255.255.255.0 and default gateway (which we don’t need for the moment) of 192.168.0.1. For the purposes of completeness, it’s best to put the gateway in.
DNS is still required, but configuring the domain controller will automatically install this service on the domain controller.
ipconfigfrom the command line should verify the configuration has been applied.
- Finally we’re at the point of installing the domain controller! From the command prompt, run
dcpromoto start the install.
- From here it is a simple matter of following the prompts.
- At the
Active Directory Domain Services Installation Wizardmake sure Use advanced mode installation is NOT selected and press Next.
- The next window is a warning about incompatibilites with Windows NT 4.0. Just press Next.
Choose a Deployment Configuration– Check the Create a new domain in a new forest and press Next.
Name the Forest Root Domain– In the FQDN of the forest root domain enter the name of your network. For our purposes, any name will do. invurted.local is acceptable. Press Next.
Set forest functional level– Select Windows 2008 R2 from the drop down list. This will mean that all domain controllers have to have at least Windows 2008 R2 as their operating systems. Press Next.
Additional Domain Controllers– Make sure the DNS Server option is ticked and press Next. Select Yes for any dialog boxes that appear.
Location for Database, Log Files and SYSLOG– Accept the default locations and press Next.
Directory Services Restore Mode Password– Enter the password of P@ssw0rd in both fields and press Next.
Summary– Verify your settings and press Next.
Active Directory Domain Services Installation WizardActive Directory will now start installing. At the completion, reboot the virtual machine. If everything is successful, upon reboot, your domain controller setup is complete.
- At the
Upon successful restart and login using the Administrator username and password, we want to look at our new domain. From the start menu, select Administrative Tools and launch the Active Directory Users and Computer program. This will allow us to create any users, groups and Organisation Units that are required.
I almost forgot! We need to rename our domain controller. In previous versions of Windows this was painful, especially as the virtual machine is a domain controller. In Windows 2008 there is more tolerance to name changes. It’s not the sort of thing that I would want to do regularly, but is possible.
In the start menu, right click on Computer and select Properties.
Chose Change settings and accept any warnings that appear on screen.
In the Sytem Properties, select Change and, again, accept any warning that appear.
In the computer name field enter the new name for the computer. For our purposes, inv-dc01 will do fine. Press OK twice and then close the system properties. At this point, it is a good idea to restart the machine again.
That’s Part 2 complete. In Part 3 we’ll look at configuring the virtual machine as a domain member server.
As ever, if you have any questions, please email me (contactme [at] invurted dot com).