Configuring Citrix MetaFrame for Windows 2000 Terminal Services

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

An effective change control procedure should do each of the following:

■    Provide a mechanism for testing changes in a lab environment before deployment to production.

■    Allow for formal approval of changes after the systems are in production.

■    Provide revision control and backup/restore procedures during the initial development stage.

■    Allow changes to the farm to be proposed and evaluated, for performance and availability impact to be assessed, and for approval or rejection in a controlled manner.

■    Allow all parties materially affected by proposed changes to the server farm to assess the impact of the changes.

■    Facilitate changes to platform development during the initial stages of configuration.

■    Provide documentation of the development of your server farm, including all proposed changes.

When making changes to a Citrix Server Farm, the impact of taking a server offline is usually large, affecting a large number of users. If the change causes the server to stop functioning, it is important to have procedures in place to restore the server to production quickly. There are two basic methods to achieve this goal: tape backup or imaging. Refer to Figure 13.1 for an illustration of a change control flowchart.

Figure 13.1 Change control flowchart.



Modify image to include change.

Tape Backup

Tape backup is the older and slower method, but it is sometimes more acceptable depending on your environment. Tape backup also allows you to perform the backup while the server is still online. Be aware that you must have the software and/or licenses to allow the backup of open files.

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