none
RDS in 2012 R2 - requirements RRS feed

  • Question

  • Hello,

    I searched the technet site and then the web looking for hardware requirements about the deployment of remote desktop services on 2012 R2. And also software requirements like what roles can be co-located. Didn't find anything official. Would you happen to have that information somewhere ?

    Thanks !

    Best regards,

    Liliana

    Wednesday, June 24, 2015 2:54 PM

Answers

  • I found the following extract for hardware sizing up options for 2008R2 that you can use as a base template foryou 2012r2

    http://blogs.technet.com/b/iftekhar/archive/2010/02/10/rds-hardware-sizing-and-capacity-planning-guidance.aspx

    Here are some bullet points which I recommend to my partners and customers to consider:

    • 2GB Memory (RAM) is the optimum limit for each core of a CPU. E.g. If you have 4 GB RAM then for optimum performance there should be Dual core CPU.
    • 2 Dual Core CPU perform better then single Quad core processor.
    • Recommended bandwidth for LAN of 30 users and WAN of 20 users.  Bandwidth (b) = 100 megabits per second (Mbps) with Latency (l) Less than 5 milliseconds.
    • On a Terminal Server 64 MB per user is the Ideal Memory (RAM) requirement for GP Only use + 2 GB for OS E.g. (100 users * 64) + 2000 = 8.4 GB i.e. 8GB RAM.
    • More applications used (i.e. Office, CAD Apps and etc.) will require more memory per user to be added to this calculation over the 64 MB base memory per user.
    • 15 TS session per CPU core is the optimum performance limit of a Terminal Server.
    • Network should not have more than 5 hops, and latency should be under 100ms.
    • 64 kbps is the Ideal Bandwidth per user session. (256 color, switched network, bitmap caching only)
    • CPU performance degrades if %processor time per core is constantly above 65%.
    • Terminal servers performance doubles when it is running on a X64 HW and OS.

    Cheers,

    Andrew

    MCSE, MCSA, VCP, CCNA, SNIA

    Microsoft Infrastructure Consultant

    Blog: Network Angel LinkedIn:

    Note: Please remember to mark as "propose as answer" to help other members. Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    • Marked as answer by Splawinski Monday, June 29, 2015 6:24 AM
    Wednesday, June 24, 2015 3:12 PM

All replies

  • I found the following extract for hardware sizing up options for 2008R2 that you can use as a base template foryou 2012r2

    http://blogs.technet.com/b/iftekhar/archive/2010/02/10/rds-hardware-sizing-and-capacity-planning-guidance.aspx

    Here are some bullet points which I recommend to my partners and customers to consider:

    • 2GB Memory (RAM) is the optimum limit for each core of a CPU. E.g. If you have 4 GB RAM then for optimum performance there should be Dual core CPU.
    • 2 Dual Core CPU perform better then single Quad core processor.
    • Recommended bandwidth for LAN of 30 users and WAN of 20 users.  Bandwidth (b) = 100 megabits per second (Mbps) with Latency (l) Less than 5 milliseconds.
    • On a Terminal Server 64 MB per user is the Ideal Memory (RAM) requirement for GP Only use + 2 GB for OS E.g. (100 users * 64) + 2000 = 8.4 GB i.e. 8GB RAM.
    • More applications used (i.e. Office, CAD Apps and etc.) will require more memory per user to be added to this calculation over the 64 MB base memory per user.
    • 15 TS session per CPU core is the optimum performance limit of a Terminal Server.
    • Network should not have more than 5 hops, and latency should be under 100ms.
    • 64 kbps is the Ideal Bandwidth per user session. (256 color, switched network, bitmap caching only)
    • CPU performance degrades if %processor time per core is constantly above 65%.
    • Terminal servers performance doubles when it is running on a X64 HW and OS.

    Cheers,

    Andrew

    MCSE, MCSA, VCP, CCNA, SNIA

    Microsoft Infrastructure Consultant

    Blog: Network Angel LinkedIn:

    Note: Please remember to mark as "propose as answer" to help other members. Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    • Marked as answer by Splawinski Monday, June 29, 2015 6:24 AM
    Wednesday, June 24, 2015 3:12 PM
  • Hi Andrew

    Isn't that a bit theoretical? If You have a look at what users are running today, i would like to see hw resources for an environment with the following:

    10-20 users
    Applications: Office 2016, Using Outlook 2016 as mail program up against Office 365 (running Office Licensing and Exchange), OST files stored locally on TS (for fast searching in mails), user mailbox typical size 6 Gb,

    Users using Internet Explorer (with Java and Flash), Adobe Reader, CutePDF writer.

    These are some of the basics You'll need to have a productive workday :)

    The TS environments I've seen are brought down on their knees when using "normal" servers. Just running IE eats CPU and Memory like H..... You can bring the CPU down, by canceling the use of flash, but then a lot of home pages won't work as intended. The shocking part is actually just using IE, that comes with the server is almost enough to "kill" it :) Or how would You handle that?

    KR

    Kim

    Thursday, November 3, 2016 4:01 PM