Setting up Windows Virtual Machines
Posted by Karl Zimmerman, Last modified by Kevin Stange on 06 November 2013 04:57 PM
Windows has some particular issues and qualities that don't always mix well with our virtual environment, so we have noted some specific directions relating to Windows based virtual machines here.
Linux VMs can be deployed almost instantly, but Windows requires various install scripts to be run forcing numerous system reboots. This means Windows installs can take up to two hours. If your VM says "Pending," it is still installing. Do not try to unlock it or alter it during this stage. Once it goes to the "Off" state, simply start it and login to the console.
Windows VMs are setup with Remote Desktop by default and you can access it using the Administrator account/password using any Remote Desktop client. You can also login to your VM by using the web based console by going to Overview -> Console when the VM is on. If the Console has trouble connecting you may need to shutdown your VM and start it again (a simple reboot may not work). If the console shows a garbled screen, simply disconnect from the console and reconnect.
Windows 2008 R2 and 2012 Licensing
Licensing is done automatically, but if you are having licensing issues verify that you can ping "kms.steadfast.net" (if not verify network settings) and be sure time and time zone are correct. To activate, go Start -> Run -> "cmd" and run the following commands in the console:
Windows 2003 Licensing
For Windows 2003 and Windows 2003 R2 the license should already be installed, but Windows may ask you to, "Select the licensing mode you want to use." If it does ask, select to use the "Per Device or Per User" method. Then, it should finish configuring your Windows install and you should be good to go.
If you experience any issues with activation or installation, please feel free to contact support.