Running WS08 Terminal Server as a virtualized guest under Windows Server 2008 R2 Hyper-V

Running WS08 Terminal Server as a virtualized guest under Windows Server 2008 R2 Hyper-V

Rate This
  • Comments 5

One question that the RDS team is asked is whether running Terminal Server virtualized is supported and recommended.  To answer this question we’ve recently conducted some performance testing of this configuration using WS08 Terminal Server running as a guest on Windows Server 2008 R2 Hyper-V.   To answer the first part: this is a supported scenario.

The second question is what recommendations would we make for any customer planning to run Terminal Server 2008 virtualized.  To answer this question, we conducted performance testing using our internal knowledge worker simulation which mimics users logging on to their desktop, conducting tasks using the Office productivity suite as well as other applications, and logging off.  We conducted our testing using both non-SLAT and SLAT hardware and found that SLAT enabled processors increased the number of sessions by a factor of 1.6x to 2.5x compared to non-SLAT processors.

Given that the Terminal Server workload is highly variable as far as scaling based on the usage scenario of the users, we recommend that customers test virtualized Terminal Server with their specific client usage and utilize SLAT enabled processors given the scale improvement that SLAT provides the Terminal Server workload.

We do plan on posting a performance / scale white paper for Windows Server 2008 R2 in the coming months that will include more detail.

Leave a Comment
  • Please add 8 and 7 and type the answer here:
  • Post
  • Can somebody give me a clue how to make this kind of load simulation?

  • You should really begin to talk to all our customers not just the few you rely on, or is it citrix that complained?

  • I have seen that TS on a Virtualization Platform with 32 Bit is running better as 64 Bit System with 4 instance and dedicated CPU.

    The test was that i have a hardware and i want find out in which configuration of the system is scaling beter and can bring so more user one the same plattform. So it was on a 8 processrr  (2 Quad) with 16 gbyte was use a hyphervisor and put 4 32 Bit machine with terminal service on it. The 64 system (windows 2003) was not so good in scale out. The feeling was that the operation system are not so scaled out. So that is they to get on  the same hardware with virtualization more user on the system. I look at the response time for users and not the performance counters.  THe feeling for the user is for me more impotant. Not the statisctis from performance counters. therfor i have a bad feeling in the performance measuring.

    So i now very interetet if one TS on 64 bit is better scale out again 4 virtual system on a using a terminal server. if the Operating system scale not enough so it is better to put on the same hardware the virtualization. I have that with the overhead from virtualiztion the systenm scale out.

  • Running WS08 Terminal Server as a virtualized guest under Windows Server 2008 R2 Hyper-V

    Usually at the end of the day when users are logging out. Server hangs....

    http://www.brianmadden.com/forums/t/36251.aspx

    7011 - A timeout (30000 miliseconds) was reached while waiting for a transaction response from the RasMan service.

    7011 - A timeout (30000 miliseconds) was reached while waiting for a transaction response from the NlaSvc service.

    7011 - A timeout (30000 miliseconds) was reached while waiting for a transaction response from the CryptSvc service.

    10010 - The server {AAC1009F-AB33-48F9-9A21-7F5B88426A2E} did not register with DCOM within the required timeout.

  • Yeah so when's this white paper meant to come out? Real informative (Not!)

Page 1 of 1 (5 items)