Monitoring Citrix performance?
Monitoring Citrix performance?
Can anybody walk me through a rough list of tests for a Citrix server? I need to manage "on box" stuff like CPU/disk/mem obviously, but what are the other key services/processes/DLL's? How could I do "synthetic" tests for user logons from another box? Test NFuse? Etc.. If anyone has done this before and could share, I'd be grateful. Thanks!
-
zacherynuk
- Posts: 26
- Joined: Thu Jul 20, 2006 10:24 am
Citrix
Hi,
Citrix has so many inbuilt reporting mechanisms that I think the basics are fine.
On top of the usual server stuff, check ports 80 / 443 and perhaps that IIS services are running for the Nfuse, also check the CSG if you are using it.
There are a few Performance monitors relating to Windows terminal services which are also relevent - number of users, logons etc. - keep an eye on paging and memory especially.
With Citrix it is more important (IMHO) to treat the system a 'normal system' but built in a very carefull and methodical way - therefore any tests pertinent to a 'normal' system are pertinent to the Citrix system.
As far as Citrix management goes, I rebuild the work horses every few weeks, scheduled and scripted of course and have at least 2 tiers of perimiter tolerance for the Secure gateways and Nfuse FE servers. My point being, that Citrix Servers are so disposable, if built correctly, other than the standard monitoring, nothing much else can actually go wrong...
I shall be writing my due diligence docs on my own Citrix systems, should this software carry on performing as it has, within the next few weeks. I shall update then on my methods.
z
Citrix has so many inbuilt reporting mechanisms that I think the basics are fine.
On top of the usual server stuff, check ports 80 / 443 and perhaps that IIS services are running for the Nfuse, also check the CSG if you are using it.
There are a few Performance monitors relating to Windows terminal services which are also relevent - number of users, logons etc. - keep an eye on paging and memory especially.
With Citrix it is more important (IMHO) to treat the system a 'normal system' but built in a very carefull and methodical way - therefore any tests pertinent to a 'normal' system are pertinent to the Citrix system.
As far as Citrix management goes, I rebuild the work horses every few weeks, scheduled and scripted of course and have at least 2 tiers of perimiter tolerance for the Secure gateways and Nfuse FE servers. My point being, that Citrix Servers are so disposable, if built correctly, other than the standard monitoring, nothing much else can actually go wrong...
I shall be writing my due diligence docs on my own Citrix systems, should this software carry on performing as it has, within the next few weeks. I shall update then on my methods.
z