| When administering a MetaFrame Access Suite environment, it is important to have a stringent change control process in place. An unmanaged environment creates instability and is difficult to maintain and support. Throughout the lifespan of a deployment, many changes are made to the environment and the servers themselves. Changes such as additional services brought on line, additional hardware or software and changes to the MetaFrame Access Suite Servers themselves. These changes directly impact the stability of the MetaFrame Access Suite environment. With this in mind, it is your responsibility to implement a change process to track these changes in order to insure the stability of the MetaFrame Access Suite environment. Keeping with the scope of this document, I recommend sticking with two basic rules. Test all software on test servers prior to installing on the production network Implement a change management log for all the MetaFrame Access Suite Servers. Every change made to a server should be documented. You will find a MetaFrame Access Suite Log Book template located in the templates folder of the MIAB3.0.ZIP file. (Downloaded from: http://www.dabcc.com/miab/MIAB3.0.ZIP) |