Remote App giving More Power and processor to specific Users / Groups

In Windows 2008 R2 , It come new exciting Feature call with Fair Share CPU Scheduling Features. Fair Share CPU Scheduling dynamically distributes processor time across sessions based on the number of active sessions and load on those sessions by using the kernel-level scheduling mechanism included with Windows Server 2008 R2.
In order for you to give exclusively resources for certain Group users or specific users, you can disable the  disable Fair CPU Sharing  feature by configuring the following registry entry
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\SessionManager\DFSS\EnableDFSS.

After you turn off the Fair Scheduling, next is to define who have the higher Priority where WSRM come into picture .

The administrator can allocate different CPU shares to different sessions using WSRM (Windows System Resource Manager). WSRM is an optional server feature used for managing system resource (processor and memory) usage. This feature has been part of the operating system since Windows Server 2008.

WSRM has a new built-in policy called “Weighted_Remote_Sessions”. This policy allows an administrator to categorize users into one of three priority groups: premium, standard and basic. WSRM ensures that users belonging to the premium group will get more CPU resources than those in standard, who will in turn get more CPU resources than users in basic.

You can use this feature by following the steps below.

  1. Open WSRM MMC (WSRM.msc). The “Weighted_Remote_Sessions” policy is listed under the “Resource Allocation Policies” node in the left pane. clip_image002
  2. To assign Users/Groups to different priority levels, right-click the “Weighted_Remote_Sessions” node and then select Properties. The Properties dialog looks like this:clip_image004
  3. Click Add to assign a priority to users or groups.
  4. In the next dialog, click Add to get the “Select Users or Groups” dialog.
  5. Choose the appropriate priority for selected users or groups, and then click OK:
    clip_image006
  6. The added users are then listed in the Properties dialog:
    clip_image002[4]
  7. The Edit and Remove buttons are self-explanatory. Clicking OK saves the configuration created on the WSRM server.
  8. This information is not used unless “Weighted_Remote_Sessions” is set as the managing policy. If it is already set as the “Managing” policy, then new changes will take effect immediately. When you click OK in the Properties dialog, the new information is communicated to the service and WSRM updates the weights of only those sessions that are run by users whose category has been modified. If you want to update the weights of all running sessions on the server, select the “Update priority for all remote desktop sessions” check box.
  9. To set the Weighted_Remote_Sessions as Managing Policy, right-click its node in the left pane and select “Set as Managing Policy.”
  10. If some other policy is in the managing state, then setting “Weighted_Remote_Sessions” policy as managing shows you a dialog stating that you will need to restart the WSRM server to make this policy active. If you click Yes, the WSRM server is restarted.
  11. If Weighted_Remote_Sessions is in a managing state, then setting some other WSRM Policy in managing mode again requires a restart of the server.

Weight Remote Sessions configuration Reference from Msdn side :http://blogs.msdn.com/b/rds/archive/2009/05/29/using-wsrm-to-control-rds-dynamic-fair-share-scheduling.aspx

Advertisements
This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s