<div>
I've not a lot of experience with Terminal Services but in the absence of comments from anyone else, here's my thought:<br />
<br />
It probably depends how much activity you expect on your terminal server - ie how many users and what are they doing? &nbsp;If expected memory consumption is to be high so you predict the pagefile will need to be heavily used then get it on a disk of its own. &nbsp;Despite what I quote below, there's probably no reason to not let the system then control its maximum size anyway - if it's getting massive then that's probably a suggestion you need more RAM anyway.<br />
<br />
Have a look here:<br />
<a href="http://technet.microsoft.com/en-us/library/cc786809.aspx" rel="ugc">http://technet.microsoft.com/en-us/library/cc786809.aspx</a><br />
&quot;For Terminal Server, it is best to put your page files on a dedicated hard drive. In addition, because of the multiuser nature of Terminal Server, be sure that your page file is twice the size of your RAM. For example, if your Terminal Server has 2 gigabytes (GB) of RAM, you should have a 4 GB paging file. You should also have two paging files if necessary. &quot;
</div>


I've not a lot of experience with Terminal Services but in the absence of comments from anyone else, here's my thought:

It probably depends how much activity you expect on your terminal server - ie how many users and what are they doing?  If expected memory consumption is to be high so you predict the pagefile will need to be heavily used then get it on a disk of its own.  Despite what I quote below, there's probably no reason to not let the system then control its maximum size anyway - if it's getting massive then that's probably a suggestion you need more RAM anyway.

Have a look here:
http://technet.microsoft.com/en-us/library/cc786809.aspx [http://technet.microsoft.com/en-us/library/cc786809.aspx]
"For Terminal Server, it is best to put your page files on a dedicated hard drive. In addition, because of the multiuser nature of Terminal Server, be sure that your page file is twice the size of your RAM. For example, if your Terminal Server has 2 gigabytes (GB) of RAM, you should have a 4 GB paging file. You should also have two paging files if necessary. "

<div>
<div class="content wysiwyg-content">
I am looking to build a couple of win2003 terminal servers with 32gig ram each. &nbsp;What is the best way to setup the page file?
</div>
</div>


I am looking to build a couple of win2003 terminal servers with 32gig ram each.  What is the best way to setup the page file?

Win2003 EE 64bit  Page File

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.

Microsoft Legacy OS

Microsoft server applications are those applications developed specifically, but not necessarily exclusively, on the Windows Server platform. In addition to well-known products like SQL Server, Exchange, Internet Information Services (IIS), Microsoft Dynamics, Forefront, Lync and Sharepoint, they include applications like Skype, BizTalk, Hyper-V, Groove and Commerce Server. Server applications are managed with the Microsoft System Center.

Microsoft Server Apps

Microsoft hardware includes mice, keyboards, webcams, headsets, display adapters, gaming consoles (including the Xbox One) and the Microsoft Surface family of tablets