×
×

Knowledgebase & Downloads

Windows Virtual Machines - FAQ

Windows Virtual Machines - Frequently Asked Questions

What Windows OS templates are free?

Windows 2012 Standard and Windows 2012 Enterprise licenses are free.

What Resources should I select for a Windows Virtual Machine?

Windows itself requires 2GB RAM, 2 CPU cores, 30GB SSD just to install and run the operating system.
It is not recommended that you select resources below these values, and in almost all cases 30GB or more SSD storage will be required to allow for more storage than just the operating system's files.
You can select lower than 2GB ram, 2 CPU cores, 30GB SSD however your performance will suffer.

What version of Windows should I select?

We recommend our Windows 2012 Datacenter edition template.

How will I access my Windows Virtual Machine?

Windows Virtual Machines are accessed by Remote Desktop (RDP).
Remote Desktop comes standard with all Windows systems and can generally be found in the Start menu -> all programs -> accessories.
You can have two concurrent RDP sessions active on your Virtual Machine. If you need more than two concurrent users to be signed on RDP you will need to purchase CALs from Microsoft to increase this - we do not sell CALs.
View our article on Connecting via Remote Desktop Here

How long does it take to create a Windows Virtual Machine?

On average it will take 30-45 minutes for the installation to fully complete.
During this your Windows Virtual Machine will show as "Online" before it is actually ready to use.
The best way to test that the system is ready is to try connecting to RDP.
When RDP can connect and asks for the login password the system is ready.
Before the system is ready, even if it says the server is Online, you will get a connection error when trying to log in with RDP.
It is important to note that you should NOT Start, Stop, Reboot the server until you can access RDP, nor should you try to access the backed console through OnApp at cp.togglebox.com Doing so will risk breaking the installation of Windows, and will result in you having to start the build process from the beginning.