April 11-12, 2005 Methodology in a Box™ For Citrix® Presentation Server 4.0 Douglas A. Brown President DABCC, Inc.

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 2 Agenda Project Management Overview Analysis Phase Design Phase Implementation Phase Readiness Phase Rollout Phase Summarize & Wrap Up

April 11-12, 2005 Project Management Overview

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 4 Project Methodology What is Project Methodology – Proven processes, tools, checkpoints to manage risks and deliver success. The scope and target audience of this presentation will address the small to medium size customer deployments best. Use this as a starting point, and then customize.

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 5 Project Methodology This presentation reviews the following five stages of a successful deployment: Analysis Design Implementation Readiness Rollout

April 11-12, 2005 Analysis Phase Vision / Scope (Statement of Work) Project Plan Infrastructure Assessment Proof of Concept

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 7 Vision (Statement of Work) To define the vision is to define the project! The vision is derived from business reason you are implementing the Citrix Presentation Server and the benefits you plan to achieve

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 8 Project Scope (Statement of Work) Format the scope into the 5 phases of project management and document at a 30,000 foot level the steps needed for a successful implementation Split scope into “in scope / out of scope” When finished present a completed Vision / Scope in the form of a Statement of Work to the customer. This acts as the framework the proposed project will follow.

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 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

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 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 the design or next phase and which need more attention

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 11 Infrastructure Assessment (cont) Review the following areas that are critical to successfully implementing Presentation Server: o Network Architecture o Hardware Environment o Operating Systems Environment o Any existing Presentation Server Environment (including Access Suite Licensing o Printing Environment o Client Environment o Any existing Change Control Environment

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 12 Proof of Concept Determine what assumptions must be proven Design the environment 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

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 13 Analysis Phase Checkpoint Now that you have completed the analysis phase you will be required to present your findings to your customer in the formal documentation in a formal meeting setting to reset expectations and mitigate risk of future rework The analysis checkpoint document should contain the following sections: –Preface –Vision / scope (Statement of Work) –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

April 11-12, 2005 Design Phase Server Design Access Suite Licensing Design Presentation Server Design Infrastructure Design

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 15 Server Design Hardware Requirements –Defines the hardware needed to achieve the project vision. Access Suite Licensing server(s) Presentation Server server(s) Secure Gateway for Windows server(s) Web Interface server(s) –Defines the hardware needed for each component of the Access Suite Operating System Requirements –Defines the software required to achieve the project vision –Defines the Operating Systems required, (NT 4.0 TSE, Windows 2000 and or Windows Server 2003), Presentation Server products and versions and any additional software required to achieve the vision.

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 16 Access Suite Licensing Design –Defines which access suite products will be licensed –Defines if the server will be deployed on a dedicated or shared server –Defines if the number, placement and membership of license servers

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 17 Presentation Server Design Presentation Server Architecture –Presentation Server Farm Design Defines the number and location of server farms –Presentation Server Zone Design Defines the number and location of zones –Presentation Server Data Collector Design Defines the farm’s Data Collector architecture –Presentation Server Data Store Design Defines the data storage type, recovery procedures, and the access method (direct or indirect) –Presentation Server Load Management Design Defines the data storage type, recovery procedures, and the access method

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 18 Presentation Server Design Presentation Server Architecture (cont) –Applications Defines what applications will be installed and with what method. (Published, desktop) Defines the lockdown specifications, any login script modifications and profile management –Citrix Conferencing Manager Design Defines the placement of the Citrix Conferencing Manager components Defines if you will be using the Microsoft Exchange Server or Lotus Notes integration capabilities Defines if you will be using the Guess Attendee capabilities

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 19 Presentation Server Design Presentation Server Architecture (cont) –Presentation Server Printing Design Gather a list of printers that will be supported on go-live day Defines how auto-created printers will be used Defines how network printers will be used Defines how policy based session printers will be used Defines how the Universal Print Driver will be used Defines policies & procedures for adding future printers

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 20 Presentation Server Design Applications Delivery Architecture –Presentation Server Web Interface Design Defines how / if the end-users will utilize the Web Interface to access the Presentation Server published resources Define if any custom development will be done to the Web Interface page

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 21 Presentation Server Design Applications Delivery Architecture (Cont) –Presentation Server ICA Client Design Defines the Presentation Server ICA Clients that will be utilized to access Presentation Server published resources, in the Presentation Server environment.

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 22 Presentation Server Design Security Architecture –Secure Gateway for Windows Design Define the security mechanism to be used to secure the Presentation Server deployment. –Citrix Password Manager Design Defines the directory service to be used, any applications that will need to be preconfigured and any custom agent settings.

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 23 Infrastructure Design File Storage –Defines the file servers that will be utilized to hold user profiles, Citrix related files shares and application data Login Scripts –Defines any modification that might be required Network Modifications –Defines any changes required to the network in order to rollout Citrix Presentation Server Existing Infrastructure Changes Client Drive Auto-creation User / Group Modification

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 24 Design Phase Checkpoint Now that you have completed the design phase you will be required to present your design document it to your customer in a formal meeting to reset expectations and mitigate risk of future rework The Presentation Server architecture design document should contain the following: License Server Server Design Presentation Server Design Network Design Statement of work (Vision / Scope) defining any modifications to the scope, deliverables, duration and costs for the build & test and rollout phases

April 11-12, 2005 Implementation Phase

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 26 Implementation Overview Follow the Project Scope and Project Plan to build out the initial Citrix environment –Prepare the Network Environment –Install and Configure Presentation Server –Install and Configure Applications –Install and Configure Application Delivery Mechanism –Lock Down Presentation Server Environment –License Environment Document EVERY keystroke! Follow the Project Scope and Project Plan to build out the initial Citrix environment –Prepare the Network Environment –Install and Configure Presentation Server –Install and Configure Applications –Install and Configure Application Delivery Mechanism –Lock Down Presentation Server Environment –License Environment Document EVERY keystroke!

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 27 Implementation Phase Checkpoint Now that you have completed the Implementation Phase you will be required to present your implementation document to your customer in a formal meeting The Implementation Phase document should contain the following: Procedures used to reproduce the Presentation Server environment Procedures used to install applications

April 11-12, 2005 Readiness Phase Test! Test! Pilot Implementation Rollout any remaining Servers Implement Change Management

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 29 Test! Test! Test! Create testing schemas of the criteria that will need to be passed for both Presentation Server and application functionality – leverage end users to create application functionality test schemas Test all the features of Presentation Server from the variety of client that you will be supporting Test all the features of the application from the variety of client that you will be supporting If you pass all testing criteria then you will be ready to take your deployment to Pilot!

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 30 Pilot Implementation You are now ready to take your deployment to a small slice of the proposed user community for the purpose of ensuring the following: –User Experience –Business Functionality –Overall usability Choose your pilot users carefully –Happy users first –Light, medium, heavy users –Cross skill levels

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 31 Pilot Implementation Create a Pilot Users Welcome Kit that includes the following: –Welcome letter –Instructions of how to perform the pilot –Test Schemas

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 32 Implement Change Management Create simple change management procedures by documenting what it will take to make a change in the Presentation Server Presentation Server environment Create a server log book for every server in the farm. This will assist with troubleshooting possible problems.

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 33 Rollout Remaining Servers Once you have passed the Pilot you will be ready to follow the policies and procedures gathered during previous sections of the project Go back and update design and implementation documents Once you have finished rolling out the new servers you will be required to retest the functionality of the farm.

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 34 Readiness Phase Checkpoint Now that you have completed the Readiness Phase you will want to present the findings of the Pilot in a formal meeting to reset expectations and mitigate risk of future rework The Readiness Phase document should contain the following: Executive summary of the testing and pilot results Change Management policies and procedures Server Log book(s)

April 11-12, 2005 Rollout Phase End-User Training Administrator Training Go Live!

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 36 End-User Training You will be required to prepare your end-users for their new environment through the following: Logon documentation in the form of a Welcome Kit Group training / one-on-one training Present them with any user credentials needed

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 37 Administrator Training You will be required to educate the administration staff that will be supporting the new Presentation Server implementation. Train all administrators on any day- to-day administration tasks.

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 38 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!

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 39 Rollout Phase Checkpoint Ok! Success! If you followed all the steps in each phase you will have significantly increased the chances of successfully implementing a Presentation Server rollout! Compile all the deliverables into 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 final approval!

April 11-12, 2005 Summary & Wrap Up Summary Additional Resources

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 41 Success = Happiness Project Management is the art of setting expectations! No surprises! You will be able to take what you have learned and apply it to other projects! When you learn to follow these five phases you will find that your Presentation Server projects go as planned leaving you and the end- users happy!

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 42 Additional Resources Doug Brown’s Web Site – Home page - Methodology in a Box

Friday, November 7, 2003April 11, 2005 © DABCC.COM BriForum 2005: Washington DC 43 “A Splendid Time is Guaranteed for All” Thank you! Download at: