1、PPJ02PreEngagementConsultantDeliveryGuideMarConsultant Delivery GuideProduction Pilot JumpstartPrepared forMarch 21, 2010Version 1.0 FinalTable of Contents1 Introduction 11.1 Purpose 11.2 Service Summary 11.3 Engagement Overview 12 Using the Guide 32.1 Using the Offering Content 32.1.1 Templates 32.
2、1.2 Guidance and Job Aids 42.1.3 Additional Content 42.1.4 Workshop Material Preparation 43 Overview Typical Engagement Flow 64 Pre-Envision Phase 74.1 Process Steps 75 Envision Phase 95.1 Process Steps 95.2 Activities 105.3 Deliverables and Templates 106 Plan Phase 116.1 Process Steps Image Enginee
3、ring, Desktop Deployment, App-V 116.2 Activities Image Engineering, Desktop Deployment, App-V 126.3 Deliverables and Templates Image Engineering, Desktop Deployment, App-V 136.4 Conducting Proof-of-Concept Lab 147 Plan Phase: Application Compatibility 167.1 Application Compatibility Overview and Cri
4、tical Steps 167.2 Application Compatibility Kickoff 167.3 Application Compatibility Best Practices 177.4 Plan Phase Process Steps Application Compatibility 187.5 Activities Application Compatibility 187.6 Deliverables and Templates Application Compatibility 197.7 Quick Start Assessment POC 207.7.1 S
5、tatic Analysis 207.7.2 Tool Vendors 208 Build Phase 228.1 Process Steps 228.2 Activities 238.2.1 Image Creation Activities 238.2.2 Image Deployment and App-V Activities 238.3 Deliverables and Templates for Build Phases 248.4 Build Phase: Process Steps Application Compatibility 258.5 Build Phase: Act
6、ivities Application Compatibility 258.6 Deliverables and Templates for Build Phases Application Compatibility 269 Stabilize Phase 279.1 Process Steps 279.2 Activities 279.3 Deliverables and Templates 279.4 Pilot Guidance 289.4.1 Pilot Steps 2810 Deploy Phase 2910.1 Process Steps 2910.2 Activities 29
7、10.3 Deliverables and Templates 2910.4 Completion of the Scope 3011 Additional Resources 3111.1 Training Resources 3111.2 Solution Accelerators 3111.3 General Resources 3111.4 Mail Aliases 3211.5 Enterprise Features 321 Introduction1.1 PurposeThe goal of this document is to provide the Consultant, o
8、r Architect with an overview of the tasks required to deliver a successful Production Pilot Jumpstart engagement.1.2 Service Summary The Production Pilot Jumpstart Offering is designed to help your customers implement a formalized and scalable pilot solution to test the new platform and deployment a
9、pproach in a production environment. This is a critical step to assess infrastructure and organization readiness before a broad-scale adoption. The service includes four work streams to create the core capabilities needed to deploy a modern business desktop using Zero Touch deployment techniques. Pr
10、oduction Pilot Jumpstart is as a fixed priced Offering with scope and time limits. The engagement has been developed to provide customers with real-world hands-on experience to help develop a roadmap for a full production deployment. 1.3 Engagement OverviewThe Production Pilot Jumpstart solution is
11、a combination of the Offerings that make up Desktop Optimization using Windows and Microsoft Office, and App-V from the Desktop Virtualization Solutions Offering. The Production Pilot Jumpstart provides fixed-scope deployment-related services to enable accelerated and more efficient migration to the
12、 Windows 7 operating system, Microsoft Internet Explorer 8, and Microsoft Office. To accomplish the fixed cost and schedule of the Offering, we established a set of constraints to ensure the customer experiences key aspects of a desktop deployment while fitting within the scope. Scope and Constraint
13、s ItemScopeTimeline8 to 10 weeksPrice$100,000ScopeWindows 7, Office 2010, IE8, App-VItemConstraints ItemConstraints ItemConstraints Models of hardwaremax of 4Desktops Sites1Application Virtualization1 App-V ServerApps #10Deployment1000 clientsSequenced App1Apps Remediated5Images1Initialization ZTI w
14、ith ConfigMgr or LTILanguages2Printer/Accessories Must be supported by the Windows driver libraryEngagement Flow2 Using the GuideThis guide will walk you through the process of delivering the Production Pilot Jumpstart engagements. The Production Pilot Jumpstart engagement is based on the following
15、phases: Pre-Envisioning Phase. Provide initial guidance to the customer to ensure that the project starts quickly. This can include a kickoff teleconference with the customer to ensure that they have the information and resources required when the project starts. Envision Phase. Provide guidance for
16、 the envisioning phase, in which you will conduct the kickoff meeting, complete Discovery and Assessment, and deliver the Vision and Scope document and the initial project plan. Plan Phase. Provide guidance for the planning phase, in which you will map out the initial stages of discovery, strategy,
17、and architectural design, including a Proof of Concept (POC) in a lab environment for design validation. POC Ensure your environment is ready to go, including testing, evaluating, and collecting user feedback. In addition, determine the optimal way to deploy Microsoft Windows and the Microsoft Offic
18、e system, depending on your scenarios: Zero Touch Installation (ZTI) or Lite Touch Installation (LTI). Build Phase. Provide guidance for creating and testing the image, preparing the deployment environment, and conducting IT training. Organization Readiness Gain from end-user and IT technical traini
19、ng resources, including a user training plan and communication for the deployment of Windows, Internet Explorer 8, and the Microsoft Office system. Stabilize Phase. Implement the production pilot deployment, in a production environment, for validation by a group of users. Deploy Phase. Provide guida
20、nce for the deploying phase; you will deliver the final customer presentation and close out the engagement.The purpose of this guide is to help you understand the methodology behind delivering the Production Pilot Jumpstart Offering. It is not the intention of this guide to provide training on deskt
21、op deployment topics; it is highly recommended that all members of the consulting team have specific technology training on these topics. Links to training resources are listed in Section 8.This guide is organized to support those who are delivering an engagement. The layout is modeled after the app
22、roach you should take during the project; the guidance for the activities appears in the order in which they should be performed during a typical engagement.2.1 Using the Offering ContentThis section contains details about what you need to know to properly use the Offering content.2.1.1 TemplatesThi
23、s Offering provides templates for all engagement presentations and deliverables. Each of these templates is a Microsoft Office file that should be customized by the consulting team.Each template is built using the MSWork Tool, and also contains instructional text about required customization. Make s
24、ure that you remove the customization instructions before sending the document to the customer.The templates that are Microsoft Office Word documents use the field feature to facilitate the customization process. Use the MSWork buttons in the Add-Ins tab of Office to customize the fields.2.1.2 Guida
25、nce and Job AidsThe following guidance is included in the Offering: The Engagement Guide. This document helps the Engagement Manager (EM) and the Project Manager (PM) to scope the solution and to adjust both the timeline and the resources. The Consultant Delivery Guide (this document). By providing
26、descriptions of the engagement process and deliverables, this guide helps the consulting team to conduct a Production Pilot Jumpstart engagement.2.1.3 Additional ContentWhere applicable within the documents, we have provided resources and tools. In addition to the Offering content, please go to the
27、Additional Resources section of this guide for supplemental resource information. Also, periodically check our MS Engage site at: https:/msengage- At this location, we will post docs that are open for beta review before final release on http:/wwofferings. 2.1.4 Workshop Material PreparationBefore yo
28、u conduct the Workshop, you will need to prepare the Workshop presentations and the Workshop agenda, as well as any virtual machines you want to prepare for demos during the workshop. The following steps are critical to running a successful workshop.1. Preparation of the presentation deck In the pre
29、sentation deck, there are a set of slides that should contain customer-provided information. These are the slides titled Assumptions: your Environment and Discussion: your requirements. With the information provided through the Environment Survey Questionnaire, complete the fields in red in these sl
30、ides. The information is expected to be reviewed and adjusted during the presentation, but your basic understanding of the customers environment should be already there when the workshop begins.2. Preparation of the presenter The presenter should prepare for the delivery by thoroughly reading the pr
31、ovided materials. The presenter should read the Workshop presentation deck including all of its notes, and further research any additional topics he or she might not fully understand. 3. Delivering the Presentations Each slide deck has notes describing what should be explained with it. In each slide there are two types of contents. Contents under the Note marker, generally at the beginning of the slide notes, are instructions for the delivery or general explanations on what is expected during the slide. Contents under
copyright@ 2008-2022 冰豆网网站版权所有
经营许可证编号:鄂ICP备2022015515号-1