Terminal Services as a Hyper-V virtual machine
G'day
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?
Thanks.
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?
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://blogs.technet.com/jhoward/archive/2008/02/09/terminal-services-gateway-and-terminal-services-web-access-using-hyper-v-part-1.aspx
or download the book "Understanding Microsoft Virtualization Solutions" at
http://csna01.libredigital.com/?urmvs17u33