–Citrix Confidential–
Elements of a Successful
Enterprise Implementation
Doug Dobson, Senior Manager CCS
Craig Stilwell, Senior Manager CCS
Citrix Confidential
Non Disclosure Agreement
This presentation is confidential. By virtue of your
relationship with Citrix, you are bound to retain in confidence
all information in this presentation.
Please…
• No Photography
• No Video Recording
• No Audio Recording
• Cell Phones & Pagers
–Citrix Confidential–
Introduction
This presentation reviews some of the key elements
of a successful Enterprise MetaFrame deployment.
This presentation demonstrates how the Citrix
Implementation Methodology can help to ensure a
successful roll out. This presentation reviews the
following components of a hypothetical case study:





Project Management
Analysis
Design
Implementation
Readiness
–Citrix Confidential–
Case Study
ABC Company, a large enterprise organization is
planning to deploy a MetaFrame server farm where
they will be hosting a custom developed Order Entry
application that is currently in system test in addition
to MS-Office and Outlook. These applications will
eventually support 5,000 users. ABC Company has
budgeted 2 months for the project and is eager to
begin.
–Citrix Confidential–
Project Management Checkpoint #1
• Conduct initial meeting to determine
services required
• Create a Statement of Work defining scope,
deliverables, estimated duration and costs
Infrastructure Assessment
 Proof of Concept
• Agree to discuss next steps following this
phase
 Design
 Implementation
 Readiness
 On-Going Support

Week 1
2
3
4
5
6
7
8
–Citrix Confidential–
Analysis – Infrastructure Assessment
• Conduct sessions with ABC to discuss:
Application Requirements
Hardware
Network (LAN, WAN, Subnets, Domains)
Systems Management
Security





• Document the assessment with the following
recommendations:
Unattended server build process
Pilot to 100 Shift Managers
Increased network security for Internet
Revise Testing & Migration Procedures
Several Server OS Tuning Opportunities
Identified potential MetaFrame for UNIX
application on the Order Entry database server
NFuse for simplified application delivery







Week 1
2
3
4
5
6
7
8
–Citrix Confidential–
Analysis – Proof of Concept
•Determine what assumptions must be proved
Application compatibility with terminal server
 Bandwidth requirements
 Server resource estimates

•Create Test Environment
Not production
 Start with ‘clean’ server
 Create test scripts
 Install and test applications

•Make adjustments as necessary
OS tuning
 Application configuration

•Document findings
Environment setup
 OS & application configuration
 Issues & recommendations

Week 1
2
3
4
5
6
7
8
–Citrix Confidential–
Analysis – Summary
• Benefits
Both you and the client come to an agreement on
requirements and estimates
 Risk mitigation


Opportunity to identify gaps early in project lifecycle
Findings & recommendations guide the project
 Detailed documentation

• What could be missed without formal Analysis
Clear understanding of overall technical environment
 Agreement on the scope & budget for the project
 Opportunity to identify need for additional products &
services
• Extranet 2.0
• MetaFrame for UNIX
• NFuse
• On-going support

–Citrix Confidential–
Project Management Checkpoint #2
• Present deliverables and recommendations
from Assessment & Proof of Concept
• Create a Statement of Work defining scope,
deliverables, estimated duration and costs
Design

• Server
• MetaFrame
• Network
Implementation
 Readiness
• Agree to discuss next steps following this
phase
 On-Going Support

Week 1
2
3
4
5
6
7
8
–Citrix Confidential–
Design
•Server Design
Hardware Configuration
 Operating System
 Based on Proof of Concept estimates 40 users can
consume 80% of system memory which was
determined to be primary system constraint. This
translates into 125 servers for 5,000 users, 15 extra
servers are added for contingency and redundancy.

•MetaFrame Design
Application Publishing
 Design lockdown specifications, login scripts, and
profile management
 Automated installation scripts for server rollouts.

•Network Design
Client access
 Determine how to integrate servers into ABC’s current
production environment
 New subnet with required redundancy on the
production network for this project

Week 1
2
3
4
5
6
7
8
–Citrix Confidential–
Design Summary
• Benefits




Potential issues should be identified & resolved
Documentation of build plans
Detailed understanding of next steps
Plan of action to build the infrastructure
• What could be missed without formal Design




Understanding between different project areas
• Project Management
• Network Group
• Application Group
• Operations Group
Another opportunity to agree on scope
Opportunities to introduce additional products
and services
Another opportunity to fix something before it’s
too late
–Citrix Confidential–
Implementation
• Automation procedures

Build and test automation scripts:
• OS
• MetaFrame
• System lockdown
• Applications
• Infrastructure integration
Plan and develop a strategy for adding new
users
 Test the integration of the new servers with
the file and print services existing on the
network

• Build pilot servers

Week 1
2
Build 4 servers to support 100 users
3
4
5
6
7
8
–Citrix Confidential–
Implementation Summary
• Benefits



No surprises
Confidence
Maintainable solution
• What could be missed without formal
Implementation



Confidence in solution
Scope creep
New requirements surface that were missed
during analysis phase
–Citrix Confidential–
Readiness
• Scalability testing
Stress test the servers individually and then as a
load balanced farm
Monitor network usage
Verify designs and estimates for the 5,000 user
community



• Pilot implementation
Roll the servers out to 100 user community
defined during analysis phase
Verify user experience
• Business functionality
• Overall usability


• Revise build scripts as needed
• Build remaining servers
Week 1
2
3
4
5
6
7
8
–Citrix Confidential–
Readiness Summary
• Benefits



Stress test numbers are verified and the server
farm is observed to run successfully at “full
throttle”
Verification of designs
Prepare for production
• What could have been missed without formal
Readiness


Without a stress test, it is difficult to accurately
predict user load
Surprises and “gotchas” would surface
everywhere with 5,000 users rather than 100
–Citrix Confidential–
Project Management Checkpoint #3
• Project wrap-up
• Verify support structure
• Discuss future opportunities
Week 1
2
3
4
5
6
7
8
–Citrix Confidential–
Q&A
Questions
–Citrix Confidential–
–Citrix Confidential–