Make Windows 2008 R2 roar like a performance machine…

Hello Folks,Srv2008

I meet a lot of you during the last TechDays season.  And a few of you asked me if there were any information or guidelines for “tuning” servers. Well I found out that an old document has been updated and is  just as relevant today as it was when it was just published back in June 2009.

This guide describes tuning parameters and settings that you can tweak to improve the performance and energy efficiency of your Windows Server 2008 R2 servers. It describes each setting and its potential effect to help you make an informed decision about its relevance to your system, workload, and performance goals.

After going through it i figured i have to tell the guys about this document.  I know they will be interested.

The different workloads discussed in this whitepaper are :

  • Choosing and Tuning Server Hardware
  • Performance Tuning for the Networking Subsystem
  • Performance Tuning for the Storage Subsystem
  • Performance Tuning for Web Servers
  • Performance Tuning for File Servers
  • Performance Tuning for Active Directory Servers
  • Performance Tuning for Remote Desktop Session Host (formerly Terminal Server)
  • Performance Tuning for Remote Desktop Gateway
  • Performance Tuning for Virtualization Servers
  • Performance Tuning for File Server Workload (NetBench)
  • Performance Tuning for File Server Workload (SPECsfs2008)
  • Performance Tuning for Network Workload (NTttcp)
  • Performance Tuning for Remote Desktop Services Knowledge Worker Workload
  • Performance Tuning for SAP Sales and Distribution Two-Tier Workload
  • Performance Tuning for TCP-E Workload

download the white paper. Read it, Try the different setting and make that server hmmm like the performance machine it’s meant to be.


Pierre Roman, MCITP, ITIL | Microsoft Canada Co.| Senior Technical Account Manager|

Twitter | LinkedIn

Comments (2)
  1. TomazicM says:

    The above link does not seem to work.

  2. Pierre Roman says:

    the link has been fixed.

    Thanks for catching the error.


Comments are closed.

Skip to main content