Rolling Out Citrix MetaFrame: A Project- oriented Approach

(1)

Presented by: Douglas A. Brown

Systems Engineer, Northern California

Rolling Out Citrix

MetaFrame:

A

(2)

Agenda

• Project management overview • Analysis phase

• Design phase

• Build & test phase • Rollout phase

(3)

(4)

Citrix 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:

• Project management. • Analysis.

• Design.

(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 trough each agenda item (assign and document action items)

(6)

(7)

Vision

• To define the vision is to define the project!

(8)

Project Scope

• Split scope in to “in scope / out of 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.

• Assign parties to be responsible for each “out of scope” task.

(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.

(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

(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:

• Application information • Hardware environment

• Systems management environment • Operating systems

• Network architecture • Backup architecture • Printing architecture

(12)

Proof of Concept

• Determine what assumptions must be proved • Create test environment

• Not production

• Start with ‘clean’ server

• Install and test applications

• Make adjustments as necessary

• OS tuning

• Application configuration

• Document findings

• Environment setup

(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.

(14)

(15)

Server Design

• Document the hardware that will be used. • Document the operating system that will be

deployed.

(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).

(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.

(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.

(19)

(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

(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.

• Testing includes system and scalability testing.

• System test.

– The system test tests the MetaFrame XP

architecture to ensure that all functionality and quality requirements have been met.

– Every component in the overall environment is tested alone and in conjunction with the other

components (as they would be used in a production environment).

• Scalability testing.

(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.

(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

(24)

(25)

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

(26)

Administrator Training

• You will want to prepare the administration staff (MetaFrame Admins & any help desk staff) that will be supporting the new

MetaFrame implementation.

(27)

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

(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 &

(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.

(30)

(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 all your MetaFrame projects go as planned leaving you and your

Rolling Out Citrix MetaFrame: A Project- oriented Approach