Transcript Document

Applications Management:
The key to a successful OS Migration
Thomas C. LaMantia
Intrinsic Technologies
COO/Co-Founder
Introduction
 COO and Co-Founder of Intrinsic




Technologies
National IT consulting firm focused on
Systems Management
Founding Member of the SMS Alliance
Strategic partnerships with leading vendors
like Macrovision, 1E, Vintela, iAnywhere,
PS’Soft, Quest and Microsoft
Double Microsoft Gold Partner in
Infrastructure and Security
Agenda

Quick OS Deployment Background
–
–
–
–
–
–

Why Applications Management is critical to a Successful OS Migration
–
–

Players and Roles
Phases
High level view of the overall process
Application readiness process Map
Tools
Best Practices
–




What is it?
Benefits vs. Risks
Key components of Applications Management
–
–
–
–
–

OS Deployment Tools and Frameworks
Deployment Solution
OS Conundrum
Components of a Workstation
Deployment Lifecycle Challenges
High Level View
Top 10
Reasons to adopt Applications Management Processes
Reason to review your process
Maturity Model and Self Assessment
Q&A
OS Deployments are not new
 Does anyone remember migrating
windows 3.x, 95, 98, OS/2, NT?
 Deployments have not changed much
over the years only the processes,
tools and users expectations.
Myriad of OS Deployment Tools &
Frameworks
OSD

allows people to distribute images like
applications in SMS. A product and is
supported.
BDD

a framework containing scripts and
technical guidance. Not a product. Not
supported under PSS. No one to call
when you have a bug.
Zero Touch Installation

a set of scripts leveraging the BDD and
OSD Not supported under PSS. No one
to call when you have a bug.
Zero Touch Provisioning

NOTE:
Windows Vista deployment tools are to
be included with the operating system.
These tools include the following:
•Application Compatibility Toolkit
•User State Migration Tool (USMT)
•XImage
•Windows Setup Manager
•Windows Pre-installation
Environment (PE)
ZTI is required for ZTP requires BIZ Talk
Server. Not supported under PSS. No
one to call when you have a bug.
ITIL, MOF, COBIT,
ISO9000,SIX Sigma
The goal is to automate as much as possible!
Intrinsic OS Deployment Solution







SWIMAGE: is an end-to-end Zero Touch deployment Tool and framework with an open
architecture.
Addresses two key areas: Image Management and Deployment Management
Only tool that helps with Image Management. All the others like Ghost, Power-Quest,
Microsoft's own WIM only help with image creation.
Only known “out of the box” and working solution that leverages and integrates the
best of the BDD and OSD. It is a Dot Net application, that works harmoniously with the
Macrovision FLEXnet Workflow Manager. Not natively integrated, but very
complimentary.
Further, we leverage a mature infrastructure and solid Application Management
processes and tools. ITIL, and MOF Compliant Framework.
SWIMAGE is supported and you call us when you have a bug.
WWW.SWIMAGE.COM
New OS Conundrum
While everyone else is reading about
the new features and functionality of
a new OS, the seasoned IT
professional is thinking one thing
when Microsoft releases a new client
operating system:
How hard will it be for me to deploy?
Components of a Typical Business Workstation
Requires that IT manage this complexity effectively
Individual Applications
Group Policies
Group Applications
Enterprise Applications
Customizations
Additional Patches and Fixes
Device Drivers
Hardware
HAL
Service Pack & Critical Updates
Operating System
The Deployment Lifecycle
Inherent challenges in the process: People
Define/Review
Requirements
Maintain Systems
Manage Assets
Reporting and
Feedback
Create Image
Deploy Image
Package
Applications
Data and State
Management
Define Hardware
Define Systems
High Level View:
A successful OS Migration or Deployment
 Effectively combines people, processes,






and technology
Leverages “Best of Breed” technology
Is Zero Touch
Follows best practices and is a flexible and
repeatable process
Responds to business and environmental
changes
Is measurable and the people are
accountable
Reduces the Total Cost of Ownership
The Deployment Lifecycle
Why Application Management is critical to Success
Define/Review
Requirements
Maintain Systems
Manage Assets
Reporting and
Feedback
Create Image
Deploy Image
Package
Applications
Applications Management
The Key to a successful OS
Migration
Data and State
Management
Define Hardware
Define Systems
Why is Application Management critical to
the success of a OS Deployment
 Because without the applications the PC is
a giant paper weight!
 Application Layer is on top of the OSI
Model for a reason. Applications are critical
to delivering value to the business.
 If you want to achieve “Zero Touch” you
must package your applications and have a
strong and mature Application
Management process for doing so.
 Bottom-line: Don’t skimp on paying for
good people who know this well.
Applications Management
Overview
 Applications Management: What is it?
– The process of identifying, approving,
standardizing, engineering (packaging),
testing, controlling and supporting
application installations and co-existence
in the enterprise.
Applications Management
Benefits
 Greater control of operating environment
 Reduced expenses –
– Potential License Consolidation
– Elimination of Redundant Applications
– Reduced Installation Failure
– Reduced Support (Help Desk) Costs
 Predictable Application Installation
 Application Knowledge Capital
Bottom-line: Reduces TCO
Applications Management
Costs of Poor or No Process
 Licensing Costs tend to Increase
 Application Functionality Redundancy




Increases Costs (Multiple Versions)
Inefficiencies Grow – Reinventing
processes for each application and version
Support Costs Grow
Employee “Downtime” Grows
Increased Security Risks
Bottom-line: Increases your TCO
Applications Management
Key Players and Roles
– Business Unit
– Application Governance Board
– Application Owner
– Workflow Coordinator
– Packaging Team
– Development Team
– OS Build Team
– QA Team
– Distribution Team
Applications Management
Phases
– Application Readiness
• Compatibility
• Remediation
– Application Packaging
– Quality Assurance (QA) Testing
– Distribution
Applications Management
Overall Process
Documented Standards
Application
Readiness
APPLICATION
SUBMITTED FOR
REVIEW
APPLICATION
OWNER
ASSIGNED
Packaging
Package
distributed to
production
targets
Application
approved for
enterprise by
governing body.
Application
added to catalog
Application
Information
collected by
Application
Owner
AO and WC work
together to
create
packaging
request form
WORKFLOW
COORDINATOR
SELECTED
MECHANISM
Distribution
APPLICATION
PORTFOLIO
DATABASE
Source and
document reviewed.
Package is created.
PACKAGING
CENTER
ENGINEERING
Working with
AO and WC for
QA success
Package is tested for
basic functionality
PACKAGING
CENTER
TESTING
QA TESTING
STANDARDS &
BUSINESS
FUNCTIONALITY
Quality
Assurance
Applications Management
Application Readiness Detail: OS Migration
APPLICATION
IDENTIFIED FOR
NEW DESKTOP
ENVIRONMENT
APPLICATION
REVEIWED
APPROVE FOR
TESTING
APPLICATION
DEPLOYED AS
PART OF IMAGE
OR TO SINGLE
DESKTOP
Verify the
enterprise or
business unit
functionality
requirement for
the application
Verify that the
application
meets
documented
enterprise
requirements
Approve the
application for
testing in new
environment
EXISTING
APPLICATION
PORTFOLIO
Resolve code issues
and test again
TEST THE
APPLICATION
Test
application on
the target
image and
environment
REMEDIATE OR
UPGRADE AS
NECESSARY
Application is approved
by governing body
GET FINAL
APPROVAL FOR
APPLICATION
QA TESTING
STANDARDS &
BUSINESS
FUNCTIONALITY
APPLICATION IS
PACKAGED PER
DOCUMENTED
STANDARDS
Applications Management
Application Migration – Tools Available

MSFT Windows Application Compatibility Toolkit (ACT) V4.1
– Is available now
– Contains the tools and documentation to help test, design,
deploy, and support applications on Win2K, Win XP sp2,
and Windows Server 2003. Vista will include

MSFT Application Compatibility Testing and Mitigation Guide
for Windows XP Service Pack 2
– Is available now
– Documentation on issues, approaches and remediation
http://www.microsoft.com/technet/desktopdeployment/appcompat/toolkit.mspx
http://www.microsoft.com/technet/prodtechnol/winxppro/deploy/sp2apcom.mspx
http://www.microsoft.com/technet/desktopdeployment/default.mspx
Applications Management
High Level Best Practices
 Get Top Management Support
Applications Management
High Level Best Practices
 Get TOP Management Support
– Go as high as you can – Top level support is
crucial
– Evangelize the benefits to your business client
– Show the savings – ROI
– Get ready for the politics
– Have the top level managers communicate
support
Applications Management
High Level Best Practices
 Get Top Management Support
 Create an Application Readiness Process
Applications Management
High Level Best Practices
 Create an Application Readiness Process
– Have an Application Governance Board
– Screen applications coming into environment to
meet basic criteria
• Know your existing application catalog
• Determine if you already own the functionality
• Minimum OS compliancy
• Vendor stability/support
– Business needs drive application acquisition or
build (Buy vs. Build)
Applications Management
High Level Best Practices
 Create an Application Readiness Process, Cont.
– Start building application knowledge capital at
the beginning
• Application version
• Amount of licenses
• Business targets
• Business need justification
– Track the amount of savings due to elimination
of applications and/or the reduced cost of
licenses because of bulk purchase
Applications Management
High Level Best Practices
 Get Top Management Support
 Create an Application Readiness Process
 Identify Application Owners
Applications Management
High Level Best Practices
 Identify Application Owners
– Enterprise vs. business unit application
– As few owners as possible per application
– Responsible for detailed knowledge of
application usage
– Speaks for group(s) of users
– Maintains relationship with vendor/developer
– Works directly with Workflow Coordinator of
Packaging Team
Applications Management
High Level Best Practices
 Get Top Management Support
 Create an Application Readiness Process
 Identify Application Owners
 Establish Packaging Team and Skill set
Applications Management
High Level Best Practices
 Establish Packaging Team and Skillset
– Workflow Coordinator
• Business Analyst Skills
• Translate business to technical
• Understands packaging technical process
• Primary contact for packaging effort
– Lead Engineer and Packaging Engineer
• Packaging tool set expertise
• Scripting expertise
• OS expertise
Applications Management
High Level Best Practices
 Get Top Management Support
 Create an Application Readiness Process
 Identify Application Owners
 Establish Packaging Team and Skill set
 Develop Packaging Standards
Applications Management
High Level Best Practices
 Develop Packaging Standards
– Incorporate SLA and OLA requirements into
packaging process and outputs
– Do not create standards in a vacuum - work with
teams that have input into packaging process
• Developers
• QA testing team
• OS build team
• Deployment team
– Define and document standard, repeatable
workflow packaging process
Applications Management
High Level Best Practices
 Develop Packaging Standards, cont.
–
–
–
–
Determine standard packaging environment
Establish conflict management guidelines
Select packaging tools (MSI and Scripting)
Create review process for package readiness
Applications Management
High Level Best Practices
 Get Top Management Support
 Create an Application Readiness Process
 Identify Application Owners
 Establish Packaging Team and Skill set
 Develop Packaging Standards
 Create and Maintain a Packaging Lab
Applications Management
High Level Best Practices
 Create and Maintain a Packaging Lab
–
–
–
–
Use virtual environment whenever possible
Determine central repository for storing packages
Ensure adequate package storage space
Separate storage areas:
• Development
• Testing
• Production
– Create guidelines for updating and maintaining
packaging environment
Applications Management
High Level Best Practices
 Get Top Management Support
 Create an Application Readiness Process
 Identify Application Owners
 Establish Packaging Team and Skill set
 Develop Packaging Standards
 Create and Maintain a Packaging Lab
 Separate Packaging and QA Testing
Applications Management
High Level Best Practices
 Separate Packaging and QA Testing
– Separation of packaging and QA ensures checks
and balances
– Packaging Center responsible for providing some
QA with package standards checklist
– Workflow Coordinator is liaison between
packaging center and QA
Applications Management
High Level Best Practices
 Get Top Management Support
 Create an Application Readiness Process
 Identify Application Owners
 Establish Packaging Team and Skill set
 Develop Packaging Standards
 Create and Maintain a Packaging Lab
 Separate Packaging and QA Testing
 Establish Reporting and SLA Metrics
Applications Management
High Level Best Practices
 Establish Reporting Metrics
– Packaging status reports
– Package quality measurement
– Time-to-package and time-to-deployment
reporting
– Help desk incident tracking and reporting
– Tracking of money saved through appropriate
licensing and elimination of duplicate
applications (Application Readiness)
– Adherence to SLAs and OLAs
Applications Management
High Level Best Practices
 Get Top Management Support
 Create an Application Readiness Process
 Identify Application Owners
 Establish Packaging Team and Skill set
 Develop Packaging Standards
 Create and Maintain a Packaging Lab
 Separate Packaging and QA Testing
 Establish Reporting and SLA Metrics
 Develop a Fast Track Deployment Plan
Applications Management
High Level Best Practices
 Fast Track Deployment Plan
– Does not mean skipping steps in workflow!
– Give governing body authority to prioritize
applications outside of standard SLA to
accommodate shortened business timelines
– Create contingency plan for emergencies
– Communicate!
Applications Management
High Level Best Practices
 Get Top Management Support
 Create an Application Readiness Process
 Identify Application Owners
 Establish Packaging Team and Skill set
 Develop Packaging Standards
 Create and Maintain a Packaging Lab
 Separate Packaging and QA Testing
 Establish Reporting and SLA Metrics
 Develop a Fast Track Deployment Plan
 Complete a Proof of Concept Test
Applications Management
High Level Best Practices
 Proof of Concept Test
– Ensure that Application Packaging workflow is
validated and approved for environment
– Ensure involvement of support staff and other
relevant players
– Identify changes to Application Packaging
processes
– Try and break the process – find glitches!
Applications Management
Reasons to Adopt Applications Management Processes





Deployment day is a “sick day” for the Help Desk
staff
Support costs and the number of support calls
seem to be very high
There is no central review of applications going
into production
You know that there is more than one app in the
environment that has same functionality
Your end users are local admins or super/power
users because that’s the only way they can use
their applications
Applications Management
Reasons to Review Process





Deployment and installation errors appear in
production that didn’t occur in packaging or QA
Anyone can submit an application for packaging
Application packaging standards do not exist or
are generic and are not enterprise-specific
In-house developers, OS build team and
deployment team had no part in developing the
packaging standards
No one “owns” the applications
Applications Management
Maturity Model – Self Assessment
Rank
Description
Risk/Cost of
Deployment
0
•There is a complete lack of any
recognizable Applications Management
process.
High
Nonexistent
•The organization has not even recognized
that there is an issue to be addressed and
hence there is no communication about it.
•Processes are poorly defined and
undocumented.
Applications Management
Maturity Model – Self Assessment (continued)
Rank
Description
Risk/Cost of
Deployment
1 Initial / Ad
Hoc
There is evidence that the organization has recognized
that Applications Management is needed and that the
issues exist.
There are however, no standardized processes, but
instead, there are ad hoc approaches applied on an
individual or case by case basis.
Managements approach is chaotic and there is only
sporadic, non-consistent communication on issues and
approaches to address them.
Monitoring of the process is only implemented reactively
to an incident that has caused some loss or
embarrassment to the organization.
Project success is the result of individual efforts.
High
Applications Management
Maturity Model – Self Assessment (continued)
Rank
Description
Risk/Cost of
Deployment
2 Repeatable but
Intuitive
There is a global awareness of Applications Management issues.
Medium
Applications Management activities and Key Performance
Indicators are under development.
Applications Management activities are formally established into
the organizations standards.
Applications Management is understood by senior management
and they are involved and providing oversight.
Management has identified basic Applications Management
measurement and assessment methods and techniques.
No formal training and communication around Applications
Management standards and packaging within standards are left to
the individual.
Individuals drive the governance process and few governance
metrics established.
Tools may be new to the organization and therefore are not used
to their full capacity due to a lack of experience in their
functionality.
Applications Management
Maturity Model – Self Assessment (continued)
Rank
Description
Risk/Cost of
Deployment
3 Defined Process
Applications Management is understood and generally accepted.
Low
Procedures have been standardized, documented and
implemented.
Management has communicated standardized procedures and
informal training is established.
Although measurable, procedures are not sophisticated, but are
the formalization of existing practices.
Training is left to the individual. It is left to the individual to follow
standards and to apply them.
Root cause analysis is only occasionally applied.
Most processes are monitored against some baseline metrics, but
any deviation, while mostly being acted upon by individual
initiatives and would unlikely be detected by management.
Nevertheless, overall accountability for Applications Management
is clear and management is rewarded based on Key performance
measures.
Applications Management
Maturity Model – Self Assessment (continued)
Rank
Description
Risk/Cost of
Deployment
4 Managed and
Measurable
There is a deep understanding of who the customer is and
responsibilities are defined and monitored through Operating
Level Agreements (OLA’s) and/or Service Level Agreements
(SLA’s).
Lowest
There is a full understanding of Applications Management issues
at all levels, supported by formal training.
Responsibilities are clear and process ownership established.
Tools are standardized using currently available techniques.
Applications Management processes are aligned with the
business and with the IT Strategy.
A Baseline set of Applications Management KPI’s have been
developed and are being measured.
Accountability of key process performance is clear and
management is rewarded based on Key performance measures.
You are now on the way to Six Sigma…
Applications Management
Q&A
 Q&A