Rolling Out Citrix MetaFrame: A Project-Oriented Approach

1. Rolling Out Citrix MetaFrame: A Project-Oriented Approach Presented by: Douglas A. Brown Systems Engineer, Northern California

2. Agenda • Project Management overview • Analysis phase • Design phase • Build & test phase • Rollout phase • Summarize & wrap up

3. Project Management Overview

4. Project Methodology • The scope of this presentation is the small to medium size deployments. • This presentation reviews the following four stages of a successful MetaFrame deployment: • Analysis. • Design. • Build & test. • Rollout.

5. What Makes a Good Meeting? • Set objectives • Establish an agenda and distribute in advance • Start the meeting on time on keep to the agenda (don’t allow sidetracking) • Work through each agenda item (assign and document action items) • Summarize meeting • Send out meeting minutes

6. Analysis Phase Vision Scope Project Plan Infrastructure Assessment Proof of Concept

7. Vision • To define the vision is to define the project! • The vision is derived from business reason you are implementing MetaFrame and the benefits you plan to achieve.

8. Project Scope • Format the scope into the 4 phases of project management and document at a 30,000 foot level the steps needed for a successful implementation. • Split scope in to “in scope / out of scope.” • Assign parties to be responsible for each “out of scope” task. • Present finding to the customer and get them to “sign off” on the vision / scope.

9. Project Plan • A project plan is a detailed list of tasks needed for a successful deployment. • Derived by expanding out the project scope with more detail. • Assign parties to be responsible for each task along with the estimated time for completion.

10. Infrastructure Assessment • Through a combination of meetings and in the trenches analysis, you will document readiness, requirements, risks, and considerations for each infrastructure component. • This information will allow you and your customer to understand which areas of the current environment are ready for a rollout of MetaFrame and which need more attention.

11. Infrastructure Assessment • During an infrastructure assessment you are tasked to review several areas that are critical to successfully implementing MetaFrame. These areas are as follows: • Applications • Hardware • Operating Systems • Any existing MetaFrame Environment. • Network Environment. • Printing Environment. • Client Environment

12. Proof of Concept • Determine what assumptions must be proved • Create test environment • Not a production • Build the environment from scratch • Install and test applications • Make adjustments as necessary • OS tuning • Application configuration • Document findings • Environment setup • OS & application configuration • Issues & recommendations

13. Analysis Phase Checkpoint • Now that you have completed the analysis phase you will need to present your findings to your customer in the form of formal documentation in a formal meeting setting. • The analysis checkpoint document should contain the following sections: • Preface. • Vision / scope. • Infrastructure assessment findings. • Proof of concept assumptions and findings. • Statement of work defining scope, deliverables, estimated duration and costs for the design, build & test and rollout phases.

14. Design Phase Server Design MetaFrame Design Network Design

15. Server Design • Hardware Recommendations • Domain Structure • This section defines the Domain structure required to support a deployment of MetaFrame and provide extensibility to support future growth. • Server Installation Process • This section defines the processes and procedures required to perform installations of the desired Operating System and MetaFrame. • User Profiles • Appropriate user profile configuration is defined.

16. MetaFrame Design • Farm design. • Defines the number and location of server farms. • Zone design. • Defines the number and location of zones. • Data store design. • Defines the data storage type, recovery procedures, and the access method (direct or indirect). • Application integration design. • Defines what applications will be installed and with what method. (Published, desktop). • Defines the lockdown specifications, any login script modifications and profile management.

17. Network Design • Client access. • Defines what method the end-user will communicate with the server farm. (NFuse, PN client). • File storage. • Defines the file servers that will be utilized to hold user profiles, MetaFrame related files shares and application data. • Login scripts. • Defines any modification that might be required. • Network infrastructure. • Defines any changes required to the network in order to rollout MetaFrame. • Security. • Defines the manner in which the network will be secured, including firewalls, NAT, SSL, etc.

18. Design Phase Checkpoint • Now that you have completed the design phase you will want to present your design document it to your customer in a formal meeting. • The MetaFrame architecture design document should contain the following: • Server design. • MetaFrame design. • Network design. • Statement of work defining modified scope, deliverables, duration and costs for the build & test and rollout phases.

19. Build & Test Phase Install MetaFrame Servers Test, Test, Test Pilot Implementation

20. Install MetaFrame Servers • Make any modification to the existing infrastructure • Document and implement the following: • Build OS and MetaFrame servers • Application integration • NFuse integration / application delivery mechanism • Infrastructure integration • Implementing scripting / cloning procedures

21. Test! Test! Test! Test! • Testing is used to identify and fix potential issues with your MetaFrame XP architecture and implementation prior to production rollout. • Develop and document tests. • Test, Test, Test

22. Pilot Implementation • A pilot implementation allows you to “test drive” your implementation in a live production environment. • The pilot consists of an actual production environment with live users. The pilot provides the baseline environment on which additional enhancements can be tested. • The pilot implementation is the proving ground for the items documented during the design phase. • Verify and document the following. • User experience. • Business functionality. • Overall usability.

23. Build & Test Checkpoint • Now that you have completed the build & test phase you are well on your way to a successful deployment! • Call a meeting to present the installation procedures, test and pilot results. • Present the finding of the tests to your customer and get a “sign-off” to move on to the rollout phase

24. Rollout Phase Rollout Remaining Servers End-User Training Administrator Training Go Live!

25. Rollout Remaining Servers • Utilize the policies and procedures you created during the design phase and fine tuned during the build & test phase to rollout the remaining servers • Complete any remaining tasks defined in the project plan • Test – test - test

26. End-User Training • You will want to prepare your end-users for their new environment through the following: • Logon documentation • Group training / one-on-one training • Present them with any user credentials needed

27. Administrator Training • You will want to prepare the administration staff (MetaFrame Admins & any help desk staff) that will be supporting the new MetaFrame implementation. • Train administrators on any day-to-day administration tasks.

28. Go Live! • Now that you have created the design, implemented a pilot implementation, rolled out any additional servers, successfully completed system / user tests and trained the end-users and administrators, you are ready to go live with the new server farm. • Set a date, inform the support staff & end-user base and sit back and enjoy a successful project oriented deployment!

29. Rollout Phase Checkpoint • 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 finial 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 finial approval!

30. Summarize & Wrap Up

31. Success = Happiness! • Project Management is the art of setting expectations and following the steps it takes to achieve success! • You will be able to take what you have learned and apply it to your next project • When you learn to follow these four phases you will find that your MetaFrame projects go as planned leaving you and your customer's happy!

32. Questions! Thank You!

33. Making the virtual workplace real.