| Now that you have finished the Implementation phase, you are well on your way to a full-blown production rollout. By now you should have built at least two servers, rolled out a test group of users, developed and completed tests to guarantee the desired expectations and received a sign off you need to continue on to the Rollout phase. This is the final leg of our journey. During the Rollout phase, we will take what we have already learned and complete any unfinished project tasks along with the training of both the customers support staff and end-users. When you are finished with all that, you will be finally ready to go-live with the new MetaFrame XP farm. The rollout phase is broken down in to the following sections: End-user training Administrator training Go Live! After you have installed the remaining servers, you will need to create one last document that is written for the end-users to introduce them to their new environment. Give them screen shots of the logon process, instruct them on the basics of NFuse and educate them on where they will find their local drives. Remember that if the end-users perception is high then you will be coming to the completion of a successful project! The following is a sample document to end-users on how to logon to their new system: | Dear Customer, I am very happy to welcome you to your new Citrix MetaFrame Application Portal. Below I have documented how you will logon from any location, on any device, from any connection. If you have any questions or comments please email: helpdesk@mycompany.com Thank you, Network Administrator | The following is a sample end-user document on how to logon to their new system:
How to log on to the NFuse Portal Once you have connected to the Internet you will need to log in to the Citrix NFuse Application Portal. You can do this by browsing to http://www.mycompany.com/portal 1. Enter your username and password and click the Log In button. 
2. You will be presented with a list of application that you have access. 
Install the ICA 32-bit Windows Client 3. If you do not already have the latest version of the Citrix ICA client and you are connecting from a Windows 32 bit platform you will be promoted to download and install it. Click Yes to the security warning. 
4. Click Yes to install the Citrix ICA Web Client. 
5. Click Yes to agree to the Citrix Client Software License Agreement. 
6. Click OK to complete setup. 
Note: you do not need to restart you browser.
7. To launch an application all you need to do is click on it to logon. 
How to use the ICA Java Client. The following discribes how the end-user will configure the ICA Java Client. 1. In order to select the ICA Client version you will be using you will need to click on the Settings button as shown below. 
2. Scroll down to the ICA Client Deployment Preferences section of the settings page. 
3. Click the Embedded Client drop down box and select Java Client. 
4. Click the Submit button. You are now ready to take advantage of the ICA Java Client. You have now successfully logged on and launch an application from your new Citrix Application Portal. If you have any problem and or comments please contact the helpdesk at extension: 2342 or email: helpdesk@mycompany.com | Ok, one more thing and then we are ready to go live but before that, we need to make sure that you have trained everybody that will have access to the MetaFrame console and or share in responsibilities of end-user administration. You will also want to document any common administration tasks in the form of an Administrators Guide and present it to the Admins during training. Note: I will be adding a basic Administrators Guide in a later version of this document. As with the end-user, you will want to gather the Administrators together and give them a once over on all the tools they will use in their day-to-day administration. Tell them about the common issues they might experience and give them a 30,000-foot overview of MetaFrame and how it works. The goal is to educate them while allowing them to becoming familiar with the new product they will be supporting and at the same time getting them excited about the technology. Below I have documented a few of my administrators best practices Do not install third party print drivers. Third party printer drivers are not always tested in a Terminal Services environment. In order to guarantee stability, you must never install any un-trusted print drivers. You will want to contact the drive vendor and verify it has been tested in a Terminal Services environment and you will want to test it yourself on a test server prior to going live in production. Only install applications tested to run in a Terminal Services environment. As with print drivers, you will want to test all applications before loading them on production servers. This will guarantee the stability of your farm. DO NOT install applications with users logged in. I highly recommend only installing application during off hours with no users logged on. In fact, my best practice is that before I install any application, I reboot the server to clean the system and then install the application and reboot one more time, whether it needs it or not. In keeping with this practice, I always install applications with no users logged on. Do NOT perform maintenance that requires a reboot during production hours. NEVER perform maintenance during production hours! Use caution when remote administrating MetaFrame. Some things are better done from the server console. There are no steadfast rules but I highly recommend doing any system modification from the physical. However, you can perform CMC administration through a session. Schedule any downtime with the end-users. Give them as much notice as possible. Let them feel like you are doing everything you can to make them a part of the system. They will also appreciate that you are not wasting their time. Run disk defragmentation software at least once a month to optimize performance. There are a few great third party defrag products that let you schedule scans. Build a test box to test any change to the system environment. (i.e. policy changes, registry changes, print drivers, application compatibility) Follow ALL change management policies and procedures. In the templates folder you will find a Change Management Log Book that I highly recommend using. This guarantees that you will always know every change made to the system. It will also allow you the ability to roll back changes to assist in troubleshooting. Additionally it covers your behind when others make unwise changes. OK, we are almost there. Schedule your next to last meeting to present to your customer their MetaFrame farm. With the user and administrator base trained, announce that you are ready to go live. This will be a very short meeting with the objective of informing your customer that you are ready to roll in to production with the farm. Once you have approval, all you need to do is inform the users. Let the policies and procedures you have documented and the training you have done roll in to place while you kick back and watch a well-planned project wind up. Ok! Success! If you followed all the steps in each phase, you will have successfully implemented a MetaFrame rollout! Compile all the deliverables in to one document and add a final section on the results of the project. Document the end-users responses. Document the results of the trainings. Document any policies and procedures needed for on going day-to-day support. Present your completed project documentation to your customer for final approval! Again, this is the magic of project management. When you have completed, you will have created an enterprise, complete with everything needed to take action against any task. Congratulations!!! You will find the following Rollout Phase examples and templates located in Methodology in a Box 2.1. (MIAB2.1.ZIP) | Path \ Filename | Description | | \Examples\EXAMPLE End-user Welcome Letter.doc | Example of a End-user Welcome Letter | | Examples\EXAMPLE End-user Log In Document.doc | Example of a End-user Log In Document | This page left blank of purpose |