<div>
What applications will be running on the RDSH?<br />
<br />
In a Hyper-V setting our general rule of thumb is 512MB to 768MB of vRAM per user. If they are heavy on the browsers then bump that up.<br />
<br />
Start with 2 vCPUs and test. <br />
<br />
Note that performance can be impacted by assigning more vRAM that spans more than 1 NUMA node and also more vCPUs then there are physical cores on one CPU socket.
</div>


What applications will be running on the RDSH?

In a Hyper-V setting our general rule of thumb is 512MB to 768MB of vRAM per user. If they are heavy on the browsers then bump that up.

Start with 2 vCPUs and test.

Note that performance can be impacted by assigning more vRAM that spans more than 1 NUMA node and also more vCPUs then there are physical cores on one CPU socket.

<div>
<div class="content wysiwyg-content">
We are investigating setting up an RDS server with 20 user CALs.<br />
The question I have is... can I set it up RDS on a new instance of 2008 R2, running in a Hyper-V VM if I dedicate enough resources to it?<br />
My google-fu must be slipping, because I keep coming across conflicting answers.<br />
We already have a big 2008 R2 enterprise server in our COLO with a lot of beef in it, so spinning up another VM with a ton of CPU and RAM is not that big of a deal. <br />
Is this possible, or does it violate laws of physics?<br />
Am I about to divide my server by zero?<br />
<br />
Thanks in advance!
</div>
</div>


We are investigating setting up an RDS server with 20 user CALs.
The question I have is... can I set it up RDS on a new instance of 2008 R2, running in a Hyper-V VM if I dedicate enough resources to it?
My google-fu must be slipping, because I keep coming across conflicting answers.
We already have a big 2008 R2 enterprise server in our COLO with a lot of beef in it, so spinning up another VM with a ton of CPU and RAM is not that big of a deal. 
Is this possible, or does it violate laws of physics?
Am I about to divide my server by zero?

Thanks in advance!

2008 R2 RDS Infrastructure Guidance

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.

Hyper-V

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.