Terminal Services as a Hyper-V virtual machine


Is there any reason that Microsoft Terminal Services (on 2003 or 2008) is unsuitable for virtualisation on Hyper-V?

For example, if we're running a moderately busy  terminal server on a dedicated box - with "X" processors, "Y" GB of RAM, and a gigabit NIC -  is there any reason we couldn't rebuild the server as a virtual machine with a roughly equivalent allocation of processors, RAM and NIC?

I can't think why not, but you never know - really just after a reality-check.  I've tried Googling it, but haven't been able to find anything specific.  Does anyone have any real-world experience with this?

Who is Participating?
tigermattConnect With a Mentor Commented:

You can virtualise a Terminal Server under Hyper-V or VMWare ESXi - there is no reason not to. Particularly if the virtual machine has access to similar resources in terms of RAM, CPU, NIC and HDD, then you will have no issues whatsoever in virtualising it in a Hypervisor (Hyper-V, VMWare ESXi and so on).

Though these articles might not be very near to your actual query... but this will be helpful for you.


or download the book "Understanding Microsoft Virtualization Solutions" at
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.