[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1029
  • Last Modified:

High Pages/sec

I am running a Windows 2003 Terminal Server with 16 GB RAM, 2 Intel(R) Xeon(R) CPU X5450 @ 3.00GHz 4 Core processors.  This server is my Domain Controller, DNS server, & application server.  I typically have about 30 users logged in at any given time during a normal working day.  I typically get complaints of server slowness particulary related to Adobe Acrobat (9.3.4).  All the research I have done so far points to a disk latency issue.  My page file generally stays around 13% used, Availble RAM around 10 GB, but my pages/sec Avg is generally over 200.  Any suggestions as to how I can improve this or am I pushing this server too hard and need to bring another one online?
0
a245439
Asked:
a245439
3 Solutions
 
rindiCommented:
Never mix Terminal server, DC, DNS and application server together. A TS should always only be a member server, and not also a TS. Apart from speed issues, this also opens up vulnerabilities. A TS should always be dedicated to TS only.
0
 
Elwin3Commented:
Yes definitely, bring a second server online as a dedicated Terminal server. Imagine every session using the hard disks, then respondingto every quary the DNS and the DC. Also the app server.  

0
 
KCTSCommented:
Its never a good idea from both a performance point of view and security to have Terminal Services on a DC, Microsoft recommend strongly against this (and actually physically prevent it in SBS Server)
0
 
a245439Author Commented:
As I suspected the consensus seems to be to segment the DC from the TS.  Thanks to all who replied.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now