Configuring Citrix MetaFrame for Windows 2000 Terminal Services

Скачать в pdf «Configuring Citrix MetaFrame for Windows 2000 Terminal Services»

2.    If using a desktop, define Active Directory and group policy parameters and test thoroughly to ensure users have sufficient rights to be productive, but no permissions that could compromise the environment.

Underpromise, overdeliver

1. Be conservative in establishing performance standards and in reporting benchmark results, especially if users will connect via the Internet or dial-up connections.

Once all of your applications are running without issue and to the stated performance goals, it is time to scale your production hardware. For MetaFrame servers, the best rule of thumb is to buy the fastest of everything you can from disk to CPU, and use your baseline application data to ensure you have enough RAM. For each application you tested, measure the amount of RAM in use while the application is running. Multiply by the amount of RAM consumed by each application by the required number of simultaneous users. Total the RAM requirements for each application, plus the amount of server overhead (RAM in use when idle/no connections), and you will have a fairly accurate measure of the RAM requirements for your production environment. I always like to add the construction planning rule of adding 10 percent to the total as a buffer. Other hardware considerations should include disk configuration and CPU. When configuring hard disks, duplexing is the fastest fault-tolerant method for this application. When choosing Intel CPUs, several studies have found that higher cache levels for XEON CPUs does not appreciably increase performance. As with all things, budgets may constrain your hardware options. Compromise on CPU speed if you must, but never on RAM.

Скачать в pdf «Configuring Citrix MetaFrame for Windows 2000 Terminal Services»