Posts Tagged ‘Remote Desktop Services’

Windows Server 64-bit recommended page file size

March 19, 2016 Leave a comment

I picked this up a while back when I was doing research for my RDS cluster.

Recommended page file sizes:

  • Windows Server 2008 R2:
    Minimum page file size: 1x RAM
    Maximum page file size: 3 x RAM or 4 GB, whichever is larger
  • Windows Server 2012 and R2:
    Minimum page file size: Depends on crash dump setting*
    Maximum page file size: 3 x RAM or 4 GB, whichever is larger

    More Info: Technet

I found this from a forum on the internet:

For WS 2008/R2, C drive 66 GB irrespective of OS version and platform. C drive should have 6GB page file.

Aforementioned are basic requirements.

As best practice, you need to set page file 1.5 Times the RAM available on any Windows Servers.

For instance,

Say, you have 16 GB RAM on a server, 1.5 times the RAM 16 GB = 24 GB;  you need to set 24 GB Page file on the Server.

Now, how would you ditribute the page file ?

Here is the way, You need create a separate Drive and split the Page file (other than the preset page file on C drive)

For WS 2008/2, C drive already has 6 GB, now on a newly created drive set 18 GB page file (i.e. 24 -6=18 GB), make sure you have at least 23 – 25 GB Drive to accomodate 18GB page file.

I use the above settings on my RDS servers.



Windows Server 2003 Terminal Server Licensing notes

October 20, 2009 Leave a comment

In Windows Server 2003 Terminal Server a client access license is issued to every type of client that will access it. Basically it includes Windows Server 2003 client connections Windows XP, Thin clients etc.

There is now two types of licenses: Per User and Per Device. Built-in ones still exist so that Windows Server 2003 Terminal Server Licensing Server supports Windows 2000 Terminal Servers and can issue licenses to them.

Per User

Basically if you selected this mode, it means that in Terminal Server Configuration console the Terminal Sever must be able to discover an activated terminal server license server. As long as its doable, users will never be denied a connection to the terminal server based on licensing and the number of available licenses will not drop.

Per Device

If you selected this mode, it means that if a computer connects to the terminal server, it gets a temporary license. If it connects again, then gets a permanent license. This license only last for 90 days. At some point before it expires license will be renewed. Now if the client doesn’t connect back before the license expires, it will be returned to the pool of licenses and will be available again.


These type of licenses only exist for backward compatibility for Windows 2000 Terminal Servers.


Prompting Server name on Server Core Command Prompt

April 28, 2009 2 comments

Lets say you got or you plan to deploy several Windows Server 2008 Server Core installations and you are connecting to them by using the Terminal Services Remote Programs. So you get a default simple prompt. Using the following tip you can change the default prompt and add a servername. Open the registry and navigate to the following key:

HKLM\System\CurrentControlSet\Control\Session Manager\Environment

Look for a key called Prompt, if it’s not there then use the following settings to create one:

Value Name: Prompt
Value Data: $_Server:[%servername%]$_Username:[%username%]$_$T$_$p$g

Here are some special codes you can also use:

* $A – & (Ampersand)
* $B – | (pipe)
* $C – ( (Left parenthesis)
* $D – Current date
* $E – Escape code (ASCII code 27)
* $F – ) (Right parenthesis)
* $G – > (greater-than sign)
* $L – < (less-than sign)
* $N – Current drive
* $P – Current drive and path
* $Q – = (equal sign)
* $S – (space)
* $T – Current time
* $_ – Carriage return and linefeed
* $$ – $ (dollar sign)