Windows and Office Engagement Findings and RecommendationsPrepared for: Customer NameNameTitle{Date}Version

Prepared by:Partner NameNameTitleMicrosoft Deployment Planning Services Partner

Microsoft Software Assurance Desktop Deployment Planning Services

Windows and Office Engagement Findings and Recommendations

ContentChange Record................................................................................................................................... 2Reviewers........................................................................................................................................... 2Document Guidance – Delete before Providing to Customer.......................................................2Document Purpose............................................................................................................................2Session Participant Record...............................................................................................................3Problem Statement............................................................................................................................3Solution Statement............................................................................................................................4

Current Physical and Operational Infrastructure.......................................................................5Current Application Management Environment........................................................................6Current Software Update Management Environment...............................................................7Current Operating System Deployment Environment..............................................................7Current Client Backup Environment............................................................................................8Current Security Environment.....................................................................................................8Current Compliance Requirements.............................................................................................9

Deployment Plan................................................................................................................................9Business Requirements................................................................................................................9Technical Requirements.............................................................................................................10Operational Requirements.........................................................................................................10Assumptions.................................................................................................................................10Constraints................................................................................................................................... 10Issues and Risks..........................................................................................................................10

Office Deployment Considerations................................................................................................11Application Compatibility Considerations.....................................................................................11Conceptual Design...........................................................................................................................11Next Steps........................................................................................................................................ 14

1

Windows and Office Engagement Findings and Recommendations

Change RecordDate Author Version Change ReferenceDecember 2012 ACOE 1.0 Updated for DDPS 2013November 2013 ACOE 1.1 Updated for DDPS 2013 Win8.1October 2015 1.2 Updated for DDPS 2015

ReviewersName Version Approved Position Date

Document Guidance – Delete before Providing to CustomerNote to Delivery Consultant: Any text in italic blue is there to assist in determining how to answer a question.At the beginning of each section you will see if the section is required or optional with a large blue text such as this:

<<REQUIRED SECTION>>It will also provide any additional comments for the requirements of that section. This document is intended to represent the effort and accomplishments at the customer. Feel free to delete anything (other than required sections) and add any sections necessary to reflect the engagement. Remember to update all applicable blue text and delete what is not needed.

Document Purpose<<REQUIRED SECTION for ALL engagements>>The following document is a summary of the X day Desktop Deployment Planning Session held for Customer Name. It documents the findings and tasks accomplished during this engagement. Customer Name can use this document to engage internal IT teams, partners and vendors in deployment planning discussions and proposal or statement of work generation.

2

Windows and Office Engagement Findings and Recommendations

Session Participant Record<<REQUIRED SECTION for ALL engagements>>

The following table lists the participants of the engagement. Name Role Email/Phone Session Participation[Name1] [Role] [Email/Phone] [Session]

Problem Statement<<REQUIRED SECTION for ALL engagements>>Guidelines for writing a problem statement:This section provides a business description of the customer’s situation that will become the focus for the rest of the engagement. This could include actual technical problems or other business drivers. A business driver should be high level. Some common examples would be to improve operational efficiency, reduce costs, improve business integration, reduce risk exposure, etc.Be as detailed as necessary to describe the problem/driverBe as clear as possibleHere is an example:

Contoso wants to move away from their home-grown method of OS deployment and use standard Microsoft tools. Contoso places a high premium on end-user experience and cannot afford for user data and settings to be lost during migration from Windows 8.1 to Windows 10. They are also very concerned about user training for Office 2013, since Office 2007 is use throughout the organization.

Customer Name is facing the following challenges in their existing environment….

3

Windows and Office Engagement Findings and Recommendations

Solution Statement<<REQUIRED SECTION for 1 DAY>>Guidelines for writing a solution statement:This section provides a high level description of the platform solution and features that can be used to solve the customer’s problem(s) as identified in the problem statement. It should also indicate where further research is needed and becomes a basic for the Next Steps section.For a 1 day engagement be as detailed and clear as possible in the time allowed.For engagements that go beyond 1 day, skip and delete this section because a conceptual design and deployment plan are developed in more detail.Here is an example:

Contoso can take advantage of the Microsoft Deployment Toolkit (MDT) 2013 to deploy a Windows 10 image. Additional requirements gathering is needed to further engineer the specifics of a custom image. System Center 2012 R2 Configuration Manager could also be considered for application deployment, OS deployment, and management.The User State Migration Tool (USMT) provides enterprise level capabilities to migrate user data and settings. USMT integrates with MDT and Configuration Manager.Contoso can use Software Assurance benefits and choose various levels of end-user training.

Customer Name can use Microsoft’s well-proven tools…

4

Windows and Office Engagement Findings and Recommendations

Current Environment<< REQUIRED SECTION for ALL engagements >>Delivery Consultant: This section summarizes the key information regarding the customer’s environment. The data should include items from the Pre-Engagement Questionnaire and information discovered throughout the engagement. Also document any problems and recommendations that were discussed.

Current Physical and Operational InfrastructureInformation Type DetailsHow many PCs/Workstations does the Customer Name environment have in the overall enterprise?

Device OverallDesktopsLaptopsThin ClientsManaged Mobile Devices

Please provide a count of the current operating systems in the Customer Name environment.

Operating System Overall NumberWindows 10Windows 8.1Windows 8Windows 7Windows VistaOther (Mac, Linux, Unix, etc.)

Existing Office Suite breakdown in the overall enterprise.

Version Overall NumberMicrosoft Office 2016Microsoft Office Professional Plus 2013:Microsoft Office 2010:Microsoft Office 2007:Other (Open Office, etc.)

What Directory and User Account management tools are currently in place?Is a directory service migration to Active Directory needed or underway?What client deployment tool or tools are currently in place?What reporting tool or tools are currently in place?

5

Windows and Office Engagement Findings and Recommendations

ProblemsProblem Details

Recommendations Recommendation 1 Recommendation 2

Current Application Management EnvironmentInformation Type DetailsWhat product is used for software distribution? What type of Application Virtualization (i.e. (App-V) is in use today?Approximately how many software applications are currently owned by the customer?Of that number, approximately how many are currently installed? Of that number, approximately how many are currently being used? How was this number identified (if such information is available)?Currently, are software applications packaged by the customer administrative staff, or are they installed in an informal manner?Does the customer develop in-house applications? If so, of what type are they? If they are packaged, what product is used to do so? Briefly, how are the packages tested in the environment?

ProblemsProblem Details

Recommendations Recommendation 1 Recommendation 2

6

Windows and Office Engagement Findings and Recommendations

Current Software Update Management EnvironmentInformation Type DetailsDo you plan to use software updates management functionality?Do you have systems which are excluded from patch management?What product are you using for patch management?Do you have group policies which control windows updates agent targeting?

ProblemsProblem Details

Recommendations Recommendation 1 Recommendation 2

Current Operating System Deployment EnvironmentInformation Type DetailsDoes the customer use a documented, standard desktop image? If so, provide this documentation to the engagement team. If not, provide a brief overview.If you currently use a standard desktop image, do multiple variations of the image exist for different business units? If so, provide a list of the business units and variations.What products are currently used in the desktop imaging process?Does the customer have documented enterprise desktop policies and standards? If so, provide this documentation to the engagement team. If not, provide a brief overview.Does the customer have documented enterprise security policies and standards? If so, provide this documentation to the engagement team. If not, provide a brief overview.When do you deploy images (business hours, off-hours)?Are standard Windows user profiles managed? If so then provide details of the profile configuration.

7

Windows and Office Engagement Findings and Recommendations

ProblemsProblem Details

Recommendations Recommendation 1 Recommendation 2

Current Client Backup EnvironmentInformation Type DetailsWhat is the <CUSTOMERNAME> client backup policy?What is the current client backup and recovery solution?

ProblemsProblem Details

Recommendations Recommendation 1 Recommendation 2

Current Security EnvironmentInformation Type DetailsDoes the customer have documented IT security policies applying to the transfer and storage of electronic data?What is the current anti-virus strategy?What is the current anti-spam strategy?Is there a requirement for Transport Rules?What is the current VPN and/or client remote connectivity solution?What is the current disk encryption technology?What is the current Public Key Infrastructure (PKI) technology?

ProblemsProblem Details

Recommendations

8

Windows and Office Engagement Findings and Recommendations

Recommendation 1 Recommendation 2

Current Compliance RequirementsInformation Type DetailsDoes the customer have documented Governance and Archiving policies?Please list any operational standards compliance requirements (OSI compliance, ISO Compliance, IT Infrastructure Library (ITIL) Operations Model, etc.) that are applicable Please list any regulatory standards requirements (HIPAA, Sarbanes-Oxley, etc.) that are applicable toPlease list any current or past operations reviews (Six Sigma, Microsoft Operations Framework Readiness Review, ITIL Review) that are applicable

ProblemsProblem Details

Recommendations Recommendation 1 Recommendation 2

Deployment Plan<< REQUIRED SECTION for 3 DAY >>Delivery Consultant: Requirements identify what the solution must deliver. Examples are provided to better understand the type of requirements desired for each section. These should be replaced with the ones discussed during the DDPS engagement. Be sure the requirements address the problems/drivers listed earlier in this document.

Business RequirementsBusiness requirements define what the solution must deliver in order to meet a business challenge or opportunity. The following are the business requirements discussed during the engagement: Regulations dictate that data encryption is maintained during and after OS deployment. Any solution must provide access to corporate resources in a secure manner for remote employees

and vendors. Acquisition of an Asian Pacific company is pending and may affect the language support.

9

Windows and Office Engagement Findings and Recommendations

Technical RequirementsTechnical requirements specify the technical parameters and feature characteristics of the solution. The following are the technical requirements discussed during the engagement: A thin image will be used – all apps will be applied at deploy time of the OS or post-install. OS deployment must support over-the-wire and stand-alone deployment solution. PXE-support is needed at major locations. User state migration is needed and there are at least 5 custom applications that need their settings

and data migrated. A 64bit OS is desired throughout the company.

Operational RequirementsOperational requirements describe the supportability and usability of a solution. The following are the operational requirements discussed during the engagement: Centralized reporting is needed to track OS deployments. Centralized management is needed for application deployment and patch management.

AssumptionsDelivery Consultant: This is a description of the assumptions that were made as part of the solution concept.The following assumptions were made and need to be considered as part of the design:

ConstraintsDelivery Consultant: This is a description of the business, project, or technical restrictions/limitations that need to be considered as part of the solution concept.The following constraints were identified that need to be considered as part of the design:

Issues and RisksDelivery Consultant: Document issues and risks identified during the project.

The following issues and risks were identified:Issue or Risk Description Mitigation or ImpactIssue Remote sites have limited bandwidth Research use of Branch Cache and stand-alone

media

Risk Limited development staff to evaluate in-house applications

Additional external resources may be needed

Risk Driver support for 64bit OS for certain devices used inthe field

Investigate with OEM if compatible with Windows 10

10

Windows and Office Engagement Findings and Recommendations

Office Deployment ConsiderationsDelivery Consultant: Provide an overview of the approach for the deployment of Office 2016 tailored to the customer’s environment. OverviewCustomer Name will customize Office 2016 using the Office Customization Tool and then deploy using System Center 2012 R2 Configuration Manager. At this time only English is needed but the design should accommodate additional languages. Group Policies must be evaluated for ongoing management.Office Telemetry will be used to assist with potential compatibility issues.

Office Compatibility Challenges Access databases are based on Office 2007 and are scattered on local drives and various shares Older Excel add-ins are needed by the Finance group, can they be migrated? Will they work with Excel

2013?

Application Compatibility ConsiderationsDelivery Consultant: Provide an overview of the approach for Application Compatibility tailored to the customer’s environment. OverviewCustomer Name will use the Application Compatibility Toolkit to inventory a subset of machines, primarily in the HR and Finance departments where most of the third part and in-house developed applications reside.

Application Compatibility Challenges There are several 16-bit applications that need immediate attention and evaluation. Uncertain if devices in the field are compatible with Windows 10

Conceptual DesignDeployment Consultant: This is a description of the high level solution ideas that were derived from the various workshops. It should describe how product features could work together to solve the problem statement and meet the requirements as defined earlier in the document. Provide as detailed a description as possible given the time allowed in the engagement. Use the diagrams below as basis to describe the proposed CONCEPTUAL DESIGN. This is NOT A FULL DESIGN and my not meet all the requirements. Please delete any diagrams not necessary.

11

Windows and Office Engagement Findings and Recommendations

Example follows:The following figure illustrates the solution CONCEPT that was discussed during the engagement. This solution concept IS NOT A FULL DESIGN and may not meet all of Contoso’s requirements. This concept is a model that should be used as a starting point for future more detailed design discussions. The concept may change over time with more detailed discussions and as requirements evolve.

12

Image Creation Service

Windows System Image File

(Customized)

Current Recommended Practice

CorporateBranding

Security Configuration

ApplicationSource Files

WindowsSource Files

Stakeholder Input

Service Inputs

Windows and Office Engagement Findings and Recommendations

Image engineering for Customer Name will utilize MDT 2013 to create the reference image. These are the inputs and customization that must be considered: [Provide inputs and customizations]

Image engineering will create the reference image and be deployed using System Center 2012 R2 Configuration Manager. Configuration Manager will also be used for application delivery and ongoing management for software updates. The service inputs for Platform delivery include:

13

Platform Delivery Service

Deployment Types

Current Recommended Practice

Deployment Methods

DeploymentTools

Deployment Components

WindowsSource Files

StakeholderInput

Service Inputs

Windows and Office Engagement Findings and Recommendations

Customer Name will use a standard deployment type along with Window To Go. The deployment of the 64bit image will be as automated as possible with minimal user input. At this time it’s expected that PXE is needed to support new computer builds but the solution should also support remote or disconnected sites using stand-alone media. User State Migration is required and further research is needed on how much storage should be allocated. A comprehensive list of data and settings to migrate if need first.

Next Steps<<REQUIRED FOR ALL ENGAGEMENTS>>Delivery Consultant: This is a summary of the next steps. These items should help summarize the scope of a follow-on engagement. An example is provided below:

The following next steps are recommended:1. Recommend a PoC Jumpstart to help validate certain application compatibility concerns as well as user

state migration requirements2. Create a full design covering the following topics

a. Image engineeringb. System Center 2012 R2 configuration migration strategyc. Remote access architectured. Windows To Go solutione. Group Policy Objects

For more information, visit the Planning Services partner portal at www.microsoftdps.com.

14

Deployment imaging Servicing

& Management (DISM)

User State Migration

Tool (USMT)

Windows System ImageManager (Windows SIM)

Windows Pre-installationEnvironment (Windows

PE)

Windows Reference Image(s)

Windows ADK 8.1

Image Answer File(s)

Deployment Components

System Center 2012 R2 Configuration Manager

Microsoft Deployment Toolkit 2013

System Center 2012 R2 Configuration Manager & Microsoft Deployment Toolkit 2013

Deployment Tools

VDIInstallation

OfflineInstallation

OEMInstallation

User Driven

Installation

Zero TouchInstallation

Life TouchInstallation

Deployment Methods

Refresh Device

Replace Device

New device

Deployment Capabilities (User Scenarios)

Window to GoVHD Native Boot

User Driven Install

OEM Pre-installStandard

Deployment Types