preferred practices for office 365 proplus deployment...deploying office 365 proplus requires the...

84
Welcome to the Preferred Practices for Office 365 ProPlus Deployment – An IT Pro guide to Office 365 ProPlus deployment for Office 2016 What are the Preferred Practices for Office 365 ProPlus Deployment? The Preferred Practices for Office 365 ProPlus Deployment has been created by a team of subject matter experts from the Offic e 365 Product Group, Office 365 Product Marketing Group, and delivery experts from Microsoft Services to provide a single location for delivery re sources to access when deploying Office 365 ProPlus to customers. The Preferred Practices for Office 365 ProPlus contains recommended guidance for d iscovery of applications, deployment preferred practices, channel management, and reporting to provide Office 365 customers with a consis tent Office 365 ProPlus deployment experience. The document contains centralized information collected from the Office Product Group, Office Product Marketing Group, Micros oft Consulting Services, Microsoft Premier Services, and Microsoft FastTrack teams to ensure customers have a consistent end user experience when moving to Office 365 ProPlus 2016. Who is the target audience for the Preferred Practices for Office 365 ProPlus? The Preferred Practices for Office 365 ProPlus are targeted at IT Pros who are familiar with running software deployment proj ects. The Preferred Practices for Office 365 ProPlus provide guidance and a recommended design of Office 365 ProPlus to address the various deplo yment and usage scenarios. This set gives you actionable guidance and real-world examples on how you can deploy Office 365 ProPlus successfully in various scenarios. Why are Preferred Practices for Office 365 ProPlus Deployments important? The Preferred Practices for Office 365 ProPlus provide a single source for Microsoft preferred deployment configurations for Office 365 ProPlus, and offer a simple mechanism to capture real world feedback from customers, partners, and Microsoft teams to provide the latest r ecommended guidance to successfully deploy Office 365 ProPlus. The Preferred Practices for Office 365 ProPlus also provides key technical details for deploying Office 365 ProPlus to drive consistency in customer experience when moving to Office 365 ProPlus. The Preferred Practices for Office 365 ProPlus will continue to be updated as new features and deployment capabilities are released by Microsoft, and will collect feedback from customers, partners, and Microsoft deployment experts to refine the preferred practices in a centrally managed location. You can quickly access the key resources below to learn about deploying Office 365 ProPlus to our customers. In the sections below you will find recommended practices for environment assessment, deployment scenarios, channel management, and reporting. Assess Plan Deploy Manage Reference Materials Preferred Practices for Office 365 ProPlus Deployment An IT Pro guide to Office 365 ProPlus deployment Version: v1 September 26th, 2016 Overview Page 1

Upload: others

Post on 16-Jul-2020

16 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Welcome to the Preferred Practices for Office 365 ProPlus

Deployment – An IT Pro guide to Office 365 ProPlus deployment for

Office 2016

What are the Preferred Practices for Office 365 ProPlus Deployment?

The Preferred Practices for Office 365 ProPlus Deployment has been created by a team of subject matter experts from the Offic e 365 Product Group,

Office 365 Product Marketing Group, and delivery experts from Microsoft Services to provide a single location for delivery re sources to access when

deploying Office 365 ProPlus to customers. The Preferred Practices for Office 365 ProPlus contains recommended guidance for d iscovery of

applications, deployment preferred practices, channel management, and reporting to provide Office 365 customers with a consis tent Office 365

ProPlus deployment experience.

The document contains centralized information collected from the Office Product Group, Office Product Marketing Group, Micros oft Consulting

Services, Microsoft Premier Services, and Microsoft FastTrack teams to ensure customers have a consistent end user experience when moving to

Office 365 ProPlus 2016.

Who is the target audience for the Preferred Practices for Office 365 ProPlus?

The Preferred Practices for Office 365 ProPlus are targeted at IT Pros who are familiar with running software deployment proj ects. The Preferred

Practices for Office 365 ProPlus provide guidance and a recommended design of Office 365 ProPlus to address the various deplo yment and usage

scenarios. This set gives you actionable guidance and real-world examples on how you can deploy Office 365 ProPlus successfully in various

scenarios.

Why are Preferred Practices for Office 365 ProPlus Deployments important?

The Preferred Practices for Office 365 ProPlus provide a single source for Microsoft preferred deployment configurations for Office 365 ProPlus, and

offer a simple mechanism to capture real world feedback from customers, partners, and Microsoft teams to provide the latest r ecommended

guidance to successfully deploy Office 365 ProPlus. The Preferred Practices for Office 365 ProPlus also provides key technica l details for deploying

Office 365 ProPlus to drive consistency in customer experience when moving to Office 365 ProPlus. The Preferred Practices for Office 365 ProPlus

will continue to be updated as new features and deployment capabilities are released by Microsoft, and will collect feedback from customers,

partners, and Microsoft deployment experts to refine the preferred practices in a centrally managed location.

You can quickly access the key resources below to learn about deploying Office 365 ProPlus to our customers. In the sections below you will find

recommended practices for environment assessment, deployment scenarios, channel management, and reporting.

Assess Plan Deploy Manage Reference Materials

Preferred Practices for Office 365 ProPlus Deployment

An IT Pro guide to Office 365 ProPlus deployment

Version: v1

September 26th, 2016

Overview Page 1

Page 2: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

What are the customer scenarios?

The following are example customers that are an amalgam of the most common customer scenarios that we encounter. If the examp le customer

does not match your environment precisely, that is okay because between all three of the customer examples, we should cover m ost of the of the

situations any customer could face.

We have named these customer scenarios Enterprise Managed, Locally Managed, and Cloud Managed based on the primary distribution and update

management solution leveraged by each scenario.

Call to action

Please review the three scenarios and decide which one best fits your current environment. Lead with this scenario and feel f ree to add portions

from other scenarios. For example, your scenario might be almost exactly like the Enterprise Managed scenario, except you allow Mac users to

configure their own software. You would follow all the guidance from Enterprise Managed except when it comes to Mac. Check Locally Managed and

Cloud Managed if the other ways to deploy Mac clients described there would fit your needs better.

The Enterprise Managed scenario

Enterprise Managed represents large to very large organizations, and has tens of thousands of employees distributed globally. The work force is

leveraging nearly every single technology that exists, ranging from desktops to notebooks to tablets, software distribution t ools, and virtual

environments like Remote Desktop Services and Virtual Desktop Infrastructure. The IT department manages the client software u sing software

management tools such as System Center Configuration Manager, and has dedicated teams that administer the company’s Active Di rectory

components such as Active Directory Domain Services (AD DS), Active Directory Federation Services (AD FS), Group Policy, etc.

If this scenario represents your organization, then continue to read here.

The Locally Managed scenario

Locally Managed represents medium to large organizations, with a range of thousands of employees up to possibly ten thousand. They may have

offices in multiple countries, but is not considered to be globally distributed. Employees are generally located out of a cen tralized office in the

country, with limited small offices throughout. The work force is primarily leveraging newer productivity software, including some VDI, but the IT

department does not have software distribution tools to manage client software. IT Administrators leverage a Distributed File System (DFS) and

network shares to host installation packages that end users will install, and utilize custom scripts and batch files for auto mated deployments for end

users as they do not have local admin rights. They do not have dedicated IT teams to specific products, and instead leverages shared teams that

manage multiple technologies of the IT environment such as Active Directory Domain Services (AD DS), Active Directory Federat ion Services (AD FS),

Group Policy, etc.

If this scenario represents your organization, then continue to read here.

The Cloud Managed scenario

Cloud Managed represents generally small businesses, who typically have a range in the hundreds of employees who are generally located out of a

small centralized office in a single country; however, they may have smaller remote offices throughout the country. The work force leverages the

newest productivity devices and software on the market, as having a smaller organization allows for more rapid adoption of ne w technology. They

have a small IT team that manages the entire organizational IT environment technologies such as Active Directory Domain Servi ces (AD DS), Azure

Active Directory Password Sync, GPO, etc. The IT team does not have software distribution tools to manage client software, an d no Distributed File

System (DFS) exists. Network shares are leveraged for installing software, and users have administrative privileges on their client devices. The IT

team provides batch files or scripts for end users to automate deployments.

If this scenario represents your organization, then continue to read here.

Office 365 ProPlus Customer Scenario Overview

Overview Page 2

Page 3: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Office 365 ProPlus Assessment Overview

Overview

Deploying Office 365 ProPlus requires the same level of planning as any large -scale Office client deployment. The focus of the Preferred Practices for

Office 365 ProPlus focuses on key actives that are specific to deploying Office 365 ProPlus. This section will cover the key infrastructure assessment

components and App Compatibility discovery processes, as well as tools to aide with understanding the scope and remediation n eeds for Office 365

ProPlus.

For Office 365 ProPlus, there are two key areas that the assessment should focus on. We should focus on understanding the inf rastructure and

environment, as well as focus on application compatibility for legacy Office client products. It is important that when prepa ring for the Office 365

ProPlus deployment that we focus on understanding the current state of the environment, and fully understand the differences of Office 365 ProPlus

and legacy MSI based clients. The high level overview for environment details and application compatibility processes are bel ow.

Environment Assessment

When deploying Office 365, the Assess phase is all about planning and requirements gathering.

For Office 365 ProPlus specifically, below is a list of the key areas that are discussed and documented:

Understanding the Office 365 components already leveraged in the environment, and determining any settings or configurations that may

need to be enabled to support Office 365 ProPlus

Understanding the software distribution solutions currently used•

Network bandwidth capabilities to determine the best distribution method for first installation, as well as update management•

Understanding the current versions of client software in the environment•

Understanding the Office applications required by the customer for each segment of the users•

Application Compatibility Assessment

The second area to focus on when planning an Office 365 ProPlus deployment is application compatibility. The common applicati on compatibility

headaches when moving to a new version of Office are: VBA, Macros, third party add -ins, and complex documents. Most customers have a difficult

time collecting the relevant data in their environment, as well as defining what components are business critical and which c omponents are used by

individuals in the environment.

In order to simplify these activities, we have developed the four -phase approach to help identify the components that must be remediated prior to

migrating to Office 365 ProPlus. The process involves leveraging the business users, as well as Telemetry Dashboard, to:

Discover the components•

Rationalize the business-critical components•

Remediate the critical components•

Manage the components for future validation of critical components.•

Phase Description

Discover what is being used, by whom, and how often. This helps determine what to test for compatibility with the new versionof

Office. Documents and solutions that are used frequently and by large numbers of users are good candidates for testing.

Partner with business groups to identify what's critical to the business. The discovery data can help jumpstart and guide this discussion.

The goal is to identify the business-critical documents and solutions that have to be ready on the first day of the Office deployment.

Start a pilot deployment where users test the documents and solutions that are required to run the business by using Office. We call

this user acceptance testing. Troubleshoot any issues that occur for documents and solutions that need to be ready on the first day of

deployment.

Deploy Office and continue to monitor documents and solutions. Watch for trends in Office performance and behavior as updated

Office solutions are deployed. Use your Help Desk resources to troubleshoot issues as they occur for non-business-critical documents

and solutions.

For specific guidance on each phase of the application compatibility framework, please see the following TechNet article: Assess Office compatibility

with other versions of Office.

For specific guidance on the Telemetry Dashboard installation and usage, please see the following section: Office Telemetry

Focus Areas for Assessment

Please review the suggested questionnaire for the different focus areas•

Identify the right contact for each area and discuss the questions with them•

Note down all responses and use them as the foundation for your planning•

Call to Action

Assess Page 3

Page 4: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Assess Reference Materials

Overview

The following articles provide deeper technical information on specific areas of the Assess phase that are not covered in dep th in the customer scenarios.

Frequently Asked Questions

Overview of Click-to-Run

Changes in Office 2016 for Windows

What is Office Click-to-Run? What are the differences between Office 365 ProPlus and previous versions of Office?

Overview of licensing and activation in Office 365 ProPlus

Licensing and activation data sent to Office 365 by Office 365 ProPlus

Office 365 ProPlus uses the Office Licensing Service to activate and requires an Internet connection to the OLS at least once every 30 days.

Does it still use KMS/MAK to activate? Does it require Internet connection?

Overview of activation for Office 2016 for Mac

How does activation work for Office 2016 for Mac?

System requirements for Office

What are the Office 365 ProPlus and Office 2016 for Mac system requirements?

Determine the deployment method to use for Office 365 ProPlus

Deployment options for admins for Office 2016 for Mac

Can I still leverage my existing deployment tools and processes?

Office Telemetry is a compatibility monitoring framework to help reduce the time and risks of an Office upgrade. For more inf ormation about Office Telemetry and how it

should be used, please see the following section: Office Telemetry

How can I assess if my current add-ins, macros, and complex documents will work in Office 365 ProPlus?

Overview of the upgrade of Office 365 ProPlus to the Office 2016 version

I'm current running Office 365 ProPlus 2013, how does the upgrade process work to the Office 2016 suite?

Assess Page 4

Page 5: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Focus Areas for Assessment

Number of devices targeted for the deployment•

List of countries and regions to cover•

List of languages supported by central IT department•

Travelling users

Users working from home

Employees sharing a device (e.g. shift and factory floor workers)

Estimated number of:•

Size and Distribution

Operating Systems (OS) supported by central IT department, if multiple (e.g. Windows 7 x86 and x64)•

Number of devices per OS type•

Number and type of Bring Your Own Device (BYOD)s•

Number of mobile and fixed devices•

Do all devices have a common base language (e.g. en-us)?•

Do users have administrative rights on their machines?•

Remote Desktops Service servers

Remote Desktops Service Farms

Remote Desktops Service Users

Static VDI clients

Dynamic VDI clients

Number of:•

How is software currently distributed? System Center Configuration Manager (which version, how many sites)?•

How are clients and users managed? Active Directory Domain Service?•

Are all devices and users located in the same Directory Service or spread across several forests (e.g. one per region)?•

List of sites and number of targeted devices per site•

Is it at least Exchange 2010?

Is Autodiscover enabled?

If planning to leverage on premises Exchange servers:•

Is it at least Lync 2010?

If planning to leverage on premises Lync or Skype for Business Servers:•

IT Infrastructure

Are well connected to the internal software distribution solution (e.g. System Center Configuration Manager)

Are averagely connected to the internal software distribution solution

Are poorly connected to the internal software distribution solution

From a software deployment perspective, which sites:•

Which sites are well connected to the internet?•

Can the network handle the impact of the deployment and management scenarios selected?•

Network Infrastructure

Which version and editions of Office are currently deployed?•

Is there a mix in CPU architecture (Office 32-bit and 64-bit in production)?•

How many installations of Project exist? Which version(s) and editions?•

How many installations of Visio exist? Which version(s) and editions?•

Is InfoPath used in production?•

Is there a need to exclude applications from the deployment (e.g. Access)?•

Should end users be able to add applications if they were excluded to the base install (e.g. Access)?•

Is Office configured and managed by Group Policy settings today?•

How many Group Policy objects exist to configure the client? Any subsets for specific user groups?•

What are the number of Office languages packs deployed per region?•

Which applications are out of scope (e.g. Publisher or OneDrive)?•

Any known dependencies on legacy, end of life, or discontinued products (e.g. Access 97)?•

Is there a known group of users which test new releases and updated first (e.g. Application Owners, QA group, Pilot group)?•

Application Landscape

Is the Office 365 tenant configured and ready for production?•

Are the user licenses available in the tenant? Which SKU was purchased?•

Is identity already setup up? Which flavor (Cloud IDs, Synchronized IDs or Federated IDs)?•

If you are using Federated IDs, which identity provider is used (e.g. Active Directory Federation Services)?•

Is the identity synchronization set up and working?•

Are all users accounts already synchronized to the tenant?•

Do the user accounts have the necessary Office 365 ProPlus license assigned?•

Is the self-service Office 365 ProPlus installation from the Office 365 portal blocked today?•

Are all URLs and IPs listed required for Office 365 whitelisted in the web proxies?•

Is the cloud infrastructure signed off by the security and compliance department?•

Cloud Infrastructure

Assess Page 5

Page 6: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Office 365 ProPlus Planning Overview

Overview

Creating a deployment plan is a key component when migrating to Office 365 ProPlus. Planning is based on assessment items discovered, including constraints and how to implement Office

365 ProPlus in order meet the goals of the project. The following items should be considered when creating an Office 365 ProPlus deployment plan.

Planning Source Locations

When planning for the Office source locations, it is recommended for the customer to utilize the existing tools and processes in place. Office 365 ProPlus can be deployed and

updated directly from the Office Content Delivery Network (CDN), System Center Configuration Manager, or an internal share, such as leveraging a network share or Distributed

File System (DFS).

For more information on deployment source locations, please see: Office 365 ProPlus Deployment Overview

Channel Membership

In order to establish a build validation process within the organization, Microsoft recommends the following channel membership guidance:

1% get Current Channel•

10% get First Release for Deferred Channel•

89% get Deferred Channel•

For specific guidance on channel membership and management, please see the following section: Managing Channels for Office 365 ProPlus

Base Client Packaging

Since Office 365 ProPlus is a customizable package, you should determine what application sets each business group should get. Applications that are initially excluded can be

added back in later, as well as specific applications can be removed after Office 365 ProPlus has already been installed. If an application is going to be excluded from the Office

365 ProPlus deployment, a plan to restore or replace the application should be created.

Architecture

Planning should be completed to identify the deployment scenarios and use cases for the 64-bit architecture version of Office 365 ProPlus. The deployment plan should include

how existing Office 64-bit users will be transitioned to the new Office 365 ProPlus client.

Configuring Deployments

Appropriate planning needs to be done in order to create all of the required install XMLs for the various end user deployment scenarios in the organization. The install XMLs

should also include the option to install individually supported language packs for users who need a language that was not part of their original Office 365 ProPlus installation.

Shared Computing

Since Office 365 ProPlus has a specific Shared Computer Activation mode, the deployment plan should include how shared workstations and VDI environments will receive the

correct installation package, as well as how they will be continually managed.

Side by Side

While Office 365 ProPlus supports generally an N-1 coexistence scenario with previous versions of Office, careful consideration and planning must be completed for any side by

side scenarios. If Office side by side is going to be leveraged in the environment, the deployment plan should contain an estimated timeline of when users will transition off of

the legacy Office applications and rely solely on Office 365 ProPlus. It should be noted that while Office side by side is generally supported by Microsoft, it is not recommend as a

long term solution for end users.

For more information on coexistence planning for side by side, InfoPath, and Project and Visio deployments, please see the following section: Plan Reference Materials

InfoPath

Since InfoPath is no longer part of the Office 2016 suite, a separate standalone installation of InfoPath 2013 must be configured and deployed. It is important to note that

InfoPath will no longer be a part of the Office suite moving forward, and planning should be done accordingly.

Project and Visio

There are multiple versions of Project and Visio that are supported to run alongside with Office 365 ProPlus. Customers can leverage their existing Project and Visio MSI versions,

or leverage the Click-to-Run (C2R) versions that support traditional volume licensing and Office 365 licensing models. The deployment plan should also include how users will

request a Project or Visio install, and whether or not the process will be automated or not.

Office Scrub Tool (OffScrub)

OffScrub should leveraged to remove the legacy versions of Office prior to installing Office 365 ProPlus. The deployment plan should include how the OffScrub tool will be

utilized and integrated into the task sequence or deployment script.

For more information on the OffScrub tool, please see the following section: OffScrub

Office 2016 for Mac

When planning for Office 2016 for Mac, existing Mac distribution methods and solutions should be considered.

For more information about Office 2016 for Mac deployments, please see the following section: Office 2016 for Mac Clients

Licensing

When planning an Office 365 ProPlus deployment, careful considerations and planning should be done to ensure all users will be assigned the appropriate Office 365 license that

includes Office 365 ProPlus prior to the deployment.

Network

Office 365 ProPlus requires the following ports and protocols to be open: Office 365 URLs and IP address ranges

Additionally, it requires a reliable sustainable connection to the Office CDN during both the deployment and management phases. Therefore adequate planning should be done

to ensure the network can support the customers deployment and management methodology.

For more network considerations, please see the following section: Plan Reference Materials

Skipping Builds and Rollbacks

When Office 365 ProPlus updates to the next available version, it uses binary delta compression. However, when you skip a build or roll back, full file delta replication is used

which uses more bandwidth. You can switch from channel to channel; however, it is a 100% file download and should be avoided unless absolutely required. It is important to

plan for the unlikely scenarios that a build will be skipped, or that a rollback to a previous version must be completed. Both scenarios will have an impact on the network, so

careful considerations should be made on when the actions would be completed to minimize network impact.

The following table provides examples (the actual numbers very from build to build):

Explanation Current Build Next Build Compression Type Size

Update to next current build 2060 2062 Binary Delta ~134 MB

Roll back small jump 2062 2060 File Delta ~558 MB

Roll back large jump 2060 1078 File Delta ~677 MB

Changing Channel Deferred Current 100% File Delta ~1,000 MB

For more information about performing a rollback, please see the following section: Channel Management

Group Policy Settings

Office offers about 3,000 group policy settings to allow a granular control of security, privacy, and user experience. The good news is that in most cases only a subset of these are

needed to adjust the configuration to the needs, requirements, and intended user experience of an organization. It is important to include other departments responsible for IT

security, data protection, and privacy to be involved early to get a sign-off of the GPOs before the actual deployment happens.

Plan Page 6

Page 7: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Review the RSOPs of the Preferred Practices settings with more than 250 proven, commonly set policies for users and computers. Check the additional settings listed,

too

1.

Adjust the settings to fit your needs and requirements2.

Get a Resultant Set of Policy (RSOP) of today’s policies and review them. Identify settings not covered in the Preferred Prac tices for Office 365 ProPlus, and consider

adding them if the setting is still needed

3.

Check which settings where introduced in Office 2013 and Office 2016 and consider adding them to your list of settings4.

Identify which entity in your organization must sign off security and privacy related settings, present them and get a sign-off.5.

Get a sign off and hand the settings over to the team which administers the group Policy Settings. The Preferred Practices Settings can easily be imported into your

environment

6.

Call to Action

Plan Page 7

Page 8: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Plan Reference Materials

Overview

The following articles provide deeper technical information on specific areas of the Assess phase that are not covered in dep th in the customer scenarios.

Frequently Asked Questions

Office 365 URLs and IP address ranges

Network requests in Office 365 ProPlus

What are Office 365 ProPlus related items I should plan for in my network impact?

How big was this month’s Office ProPlus update?

How can I measure the network impact Office 365 ProPlus builds have?

Supported scenarios for installing different versions of Office, Visio, and Project on the same computer

How should I plan for my coexistence scenarios, such as preexisting versions of Office, Project, and Visio?

What's new to help admins deploy and manage Office 365 ProPlus

What's new to help me plan and manage an Office 365 ProPlus deployment?

What's new for admins in Office 2016 for Mac

What's new to help me plan and manage an Office 2016 for Mac deployment?

Plan for Multilanguage deployment of Click-to-Run-based Office installations

How can I plan for a multi-language deployment of Office 365 ProPlus?

Language identifiers and OptionState Id values in Office 2016

Do I need a language pack, Language Accessory Pack (LAP), or a Language Interface Pack (LIP)?

Companion proofing languages for Office 2016

Language Accessory Pack for Office 2016

What are the language packs and proofing tools available for Office 365 ProPlus?

Overview of shared computer activation for Office 365 ProPlus

I have shared workstations and/or a VDI environment, how does Office 365 ProPlus support shared devices?

Prepare to upgrade Office 365 ProPlus to the Office 2016 version

Configure updates of Office 365 ProPlus to prepare for the upgrade to the Office 2016 version

I'm currently running Office 365 ProPlus 2013, what planning needs to be done in order to upgrade to the Office 2016 suite?

Plan Page 8

Page 9: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Office 365 ProPlus Deployment Overview

Overview

When planning for and implementing a modern Office 365 ProPlus deployment for a customer, it is critical to understand the de ployment options

available to customers. In this section we will cover the preferred deployment options for customers, as well as provide the high level description of

the different architecture components.

Deployment Options

There are three common deployment options for delivering Office 365 ProPlus to customer’s end user devices:

Enterprise Managed leverages software distribution tools for deploying Office 365 ProPlus•

Locally Managed leverages on-premises file distribution systems for deploying Office 365 ProPlus•

Cloud Managed leverages the Office CDN for deploying Office 365 ProPlus•

For additional information on these customer scenarios, they are outlined in the Office 365 ProPlus Deployment Scenario Overv iew page. Below is a

high level overview of the general deployment components and tools used in an Office 365 ProPlus deployment.

High Level Client Distribution and Update Maintenance Infrastructure Overview

In general, the modern Office 365 ProPlus deployment solution includes functionality to deploy, maintain, and update clients from both an on

premise infrastructure, as well as from an off premise Office Content Delivery Network (CDN) infrastructure. The on premise and off premise

deployment infrastructures provide IT administrators flexibility to manage the initial deployment and maintenance of the Offi ce client for different

connectivity and end user segments of their environment.

The image below represents a high level overview of the on premises and off premises deployment infrastructure components for Office 365

ProPlus.

The deployment solution is comprised of two main source file distribution locations:

Off premises distribution (A) - distribution from the Office Content Delivery Network (CDN)•

On premises distribution (B) - distribution from local file shares, software distribution systems, or distributed file systems•

Other supporting processes that contribute to the overall deployment solution:

Office Deployment Tool – Tool used to customize and configure Office 365 ProPlus distribution packages•

Deployment Package – components required to install Office 365 ProPlus•

Office Build Maintenance – For each channel release, a proper patching protocol must be established•

Network Bandwidth – It is recommended to use maintenance windows to distribute Office builds to mitigate network bandwidth impact•

Security Management – Group Policies (GP) are recommended for managing Office 365 ProPlus first run and user experience, as well as

leverage Group Policies to manage incompatible Office Add-Ins

Overview of Key Infrastructure Components

Source File Distribution locations

There are two preferred source file distribution locations when deploying and managing Office 365 ProPlus. When planning and building an Office

365 deployment solution with customers, it is recommended to understand the distribution locations and understand the benefit s of each location.

Each source file location has benefits to our customers, and most deployment solutions will leverage both locations to provid e the IT administrators

with the flexibility to use the best location based on the connectivity and delivery requirements of the end user segments in the environment.

Off Premises distribution using the Office CDN

While it is not common for an enterprise to use the Office 365 portal for the initial Office 365 ProPlus client install, ther e are scenarios where

customers should leverage the Office CDN as the "SourcePath" location in the Office 365 ProPlus client deployment package. Le veraging the

Office CDN as a "SourcePath" allows the IT department to manage the deployment through a controlled deployment process, and t hen

leverage the Office CDN for the source file locations. This method allows the customer's IT department to have direct control over when end

users will receive the new Office client, allow the IT department to configure what applications will be installed on the end user’s client device,

and take advantage of Microsoft's file replication and distribution capabilities on the Office CDN.

The IT managed deployment method using the Office CDN provides enterprises with the flexibility to support remote users and s maller branch

offices with minimal corporate connectivity to deploy, update, and patch the end users devices. For an in depth overview of t he Office 365

CDN, please refer to the following article: Content delivery networks

On Premises distribution locations

A majority of enterprise customers already have tools and processes in place for managing software and file distribution with in their

environment by leveraging existing software distribution tools such as System Center Configuration Manager (System Center Con figuration

Managed), distributed file system (DFS) solutions, or other software distribution systems. For customers that have already in vested in software

distribution solutions, it is preferred to leverage these systems for the Office 365 ProPlus client. By leveraging existing i nfrastructures, the

customer can lower the education ramp for their employees by not having to invest in training for a new system as part of the overall

deployment.

Office Deployment Tool

Office Deployment Tool is the engine that downloads and installs Office 365 clients. The most recent version of the 2016 Office Deployment Tool

TO DO: Need to remove the graphic?

Deploy Page 9

Page 10: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Office Deployment Tool is the engine that downloads and installs Office 365 clients. The most recent version of the 2016 Office Deployment Tool

can be downloaded from the Microsoft Download Center, and it is highly recommended for customers to continually check for a n ewer version of

the Office Deployment Tool as it may contain updates.

For detailed information on the Office Deployment Tool, please see: Office Deployment Tool

Download the 2016 Office Deployment Tool 1.

Double-click on officedeploymenttool.exe2.

Accept the Microsoft Software License Terms in order to continue the installation3.

Select a destination folder. For example: C:\ODT and click OK to continue4.

Click OK to finish5.

You will now have a folder structure that looks similar to the following screenshot:

Follow the steps below to extract the executable and a sample configuration XML.

Deploying with Software Distribution Tools

This section covers the general steps for deploying Office 365 ProPlus using existing software distribution tools. For specif ic instructions and

prescribed guidance for software distribution tools, please see: System Center Configuration Manager Configuration

Deploying Office 365 ProPlus with an existing software distribution tool is the recommended solution for a majority of enterp rise customers since it

is already leveraged for other software distribution, and the infrastructure required to distribute the Office 365 ProPlus cl ient already exists. The

follow steps are the generalized recommended steps for a successful deployment

Prepare the Office 365 ProPlus Installation Files1.

Create an application in the software distribution system2.

Create a deployment type for the application3.

Distribution the application to distribution points4.

Deploy the application to appropriate device collection5.

A critical change in deploying with software distribution tools is that in the configuration XMLs, the SourcePath attribute m ust be removed because

software distribution tools typically copy the installation files to a different named subfolder on each computer and the Sou rcePath cannot be

specified for every computer. When the SourcePath isn’t specified or left out, the Office Deployment Tool automatically looks for the Office 365

ProPlus installation files in the same folder that the Office Deployment Tool is located in.

Group Policy Settings

Please refer to the step-by-step instructions on how to deploy the desired Group Policy settings into production.

Deploy Page 10

Page 11: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Office 365 ProPlus Deployment Scenario Overview

The Enterprise Managed scenario

The Enterprise Managed scenario represents large to very large organizations, with tens of thousands of employees who are dis tributed globally. Enterprise Managed scenarios

utilize software management tools, such as System Center Configuration Manager, to manage end user client devices and softwar e and users are not local administrators on their

machines. The IT department in the Enterprise Managed scenario typically controls and automates most of the technologies leve raged.

The Locally Managed scenario

The Locally Managed scenario represents medium to large organizations who range up to ten thousand employees. There may be mu ltiple sites in different countries or

continents, but locally managed is not considered to be distributed globally. Locally Managed does not have software distribu tion tools to manage client software, but instead

utilizes a Distributed File System and network shares to host deployment packages for end users. Locally Managed leverages ba tch files or scripts that run with elevated

privileges so the deployment is automated for end users, who are generally not local administrators on their machines.

The Cloud Managed scenario

The Cloud Managed scenario represents small businesses who typically range in the hundreds of employees, and are generally lo cated out of one country or a single office.

Cloud Managed does not have software distribution tools to manage client software, but instead utilizes network shares to hos t deployment packages for end users. Cloud

Managed leverages batch files or scripts so the deployment is automated for end users, but since users have local administrat or rights some software installation is left up to the

end user.

Deploy Page 11

Page 12: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Deploy Reference Materials

Overview

The following articles provide deeper technical information on specific areas of the Deploy phase that are not covered in dep th in the customer scenarios.

Frequently Asked Questions

Office Deployment Tool

What is the Office Deployment Tool?

Reference: Configuration options for the Office Deployment Tool

What are the configuration options available in the Office Deployment Tool?

Download Click-to-Run for Office 365 products by using the Office Deployment Tool

How can I obtain the Office 365 ProPlus installation files?

Determine the deployment method to use for Office 365 ProPlus

Deploy Click-to-Run for Office 365 products by using the Office Deployment Tool

Deploy Office 365 ProPlus by using System Center Configuration Manager

Deploy Office 365 ProPlus by using Remote Desktop Services

Step by Step Installation using CDN

Step by Step installation using DFS

Installing Office 365 ProPlus from CDN or DFS Overview

What are the deployment methods for Office 365 ProPlus?

Exclude certain Office programs when deploying Office 365 ProPlus

How do I exclude certain applications from the Office 365 ProPlus install?

Deploy Office 365 ProPlus as part of an operating system image

Can Office 365 ProPlus be deployed in an image?

Managing Group Policy ADMX Files Step-by-Step Guide

How do I implement the Office 2016 ADMX and ADML files?

Office 2016 for Mac Clients

Deployment options for admins for Office 2016 for Mac

Deploy updates for Office 2016 for Mac

Deploy preferences for Office 2016 for Mac

How can I deploy Office 2016 for Mac?

Deploy Page 12

Page 13: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Office Deployment Tool

Office Deployment Tool Overview

The Office Deployment Tool (ODT) is a command line based binary used to download and configure an Office 365 ProPlus deployme nt package.

This approach is the most common and supported deployment method for large or complex organizations, managed environments, or for

organizations that do not want to their end users to leverage self -service installs from the Office 365 portal. The Office Deployment Tool performs a

complete download of the Office product; it is not streamed.

Office Deployment Tool References

Overview: Office Deployment Tool

Download the Office 2016 Deployment Tool

Reference: Configuration options for the Office Deployment Tool

Download Click-to-Run for Office 365 products by using the Office Deployment Tool

Deploy Click-to-Run for Office 365 products by using the Office Deployment Tool

Exclude certain Office programs when deploying Office 365 ProPlus

Sample Download XML Examples

Sample Install XML Examples

The following links provide detailed information about the Office Deployment Tool, as well as the configuration options avail able:

Deploy Page 13

Page 14: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Download XML Examples

Sample Download File XML’s

Below are some common example XML files for downloading Office 365 ProPlus source files.

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Product>

</Add>

</Configuration>

Sample Download File with all Office Applications – Deferred Channel

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being downloaded

Channel=”Deferred” The channel build of Office 365 ProPlus being downloaded

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being downloaded

Language ID=”en-us” The default language being i for Office 365 ProPlus

<Configuration>

<Add OfficeClientEdition="64" Channel="Current">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Product>

</Add>

</Configuration>

Sample Download File with all Office Applications in 64-bit – Current Channel

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”64” The architecture of Office being downloaded

Channel=”Current” The channel build of Office 365 ProPlus being downloaded

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being downloaded

Language ID=”en-us” The default language being downloaded for Office 365 ProPlus

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="O365ProPlusRetail">

<Language ID="es-es" />

<Language ID="en-us" />

</Product>

</Add>

</Configuration>

Sample Download File with all Office Applications with English and Spanish – Deferred Channel

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being downloaded

Channel=”Deferred” The channel build of Office 365 ProPlus being downloaded

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being downloaded

Language ID=”en-us” The default language being downloaded for Office 365 ProPlus

Language ID="es-es" The additional language being downloaded for Office 365 ProPlus

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Product>

<Product ID="VisioProRetail">

<Language ID="en-us" />

</Product>

<Product ID="ProjectProRetail">

<Language ID="en-us" />

</Product>

</Add>

</Configuration>

Sample Download File with all Applications including Visio and Project 2016 Click to Run – Deferred Channel

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being downloaded

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being downloaded

Channel=”Deferred” The channel build of Office 365 ProPlus being downloaded

Language ID=”en-us” The default language being downloaded for Office 365 ProPlus

Product ID="VisioProRetail" Visio 2016 Office 365 ProPlus

Note: Visio 2016 Office 365 ProPlus must be on the same update channel as Office 365 ProPlus

Language ID="en-us” The default language being downloaded for Visio 2016 Click to Run

Product ID="ProjectProRetail” Project 2016 Office 365 ProPlus

Note: Project 2016 Office 365 ProPlus must be on the same update channel as Office 365 ProPlus

Language ID="en-us” The default language being downloaded for Project 2016 Click to Run

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="O365ProPlusRetail">

<Language ID="es-es" />

<Language ID="en-us" />

</Product>

<Product ID="VisioProRetail">

<Language ID="es-es" />

<Language ID="en-us" />

Sample Download File with all Applications including Visio and Project 2016 Click to Run with English and

Spanish – Deferred Channel

Deploy Page 14

Page 15: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

<Language ID="es-es" />

</Product>

<Product ID="ProjectProRetail">

<Language ID="es-es" />

<Language ID="en-us" />

</Product>

</Add>

</Configuration>

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being downloaded

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being downloaded

Channel=”Deferred” The channel build of Office 365 ProPlus being downloaded

Language ID=”en-us” The default language being downloaded for Office 365 ProPlus

Language ID=”en-es” The additional language being downloaded for Office 365 ProPlus

Product ID="VisioProRetail" Visio 2016 Office 365 ProPlus

Note: Visio 2016 Office 365 ProPlus must be on the same update channel as Office 365 ProPlus

Language ID="en-us” The default language being downloaded for Visio 2016 Click to Run

Language ID=”en-es” The additional language being downloaded for Visio 2016 Click to Run

Product ID="ProjectProRetail” Project 2016 Office 365 ProPlus

Note: Project 2016 Office 365 ProPlus must be on the same update channel as Office 365 ProPlus

Language ID="en-us” The default language being downloaded for Project 2016 Click to Run

Language ID=”en-es” The additional language being downloaded for Project 2016 Click to Run

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Product>

<Product ID="VisioProXVolume">

<Language ID="en-us" />

</Product>

<Product ID="ProjectProXVolume">

<Language ID="en-us" />

</Product>

</Add>

</Configuration>

Sample Download File with all Applications including Visio (VL) and Project (VL) 2016 Click to Run –

Deferred Channel

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being downloaded

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being downloaded

Channel=”Deferred” The channel build of Office 365 ProPlus being downloaded

Language ID=”en-us” The default language being downloaded for Office 365 ProPlus

Product ID="VisioProXVolume" Visio 2016 Office 365 ProPlus volume licensed

Note: Visio 2016 Office 365 ProPlus must be on the same update channel as Office 365 ProPlus

Language ID="en-us” The default language being downloaded for Visio 2016 Click to Run

Product ID="ProjectProXVolume” Project 2016 Office 365 ProPlus volume licensed

Note: Project 2016 Office 365 ProPlus must be on the same update channel as Office 365 ProPlus

Language ID="en-us” The default language being downloaded for Project 2016 Click to Run

Deploy Page 15

Page 16: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Install XML Examples

Sample Configuration File XML’s

Below are some common example XML files for configuring and installing Office 365 ProPlus.

<Configuration>

<Add OfficeClientEdition="32" >

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Product>

</Add>

<Updates Enabled="TRUE" />

<Display Level="Full" AcceptEULA="TRUE" />

</Configuration>

Sample Configuration with all Office Applications with Updates enabled from CDN, Interface Display,

License Agreement

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being installed

Language ID=”en-us” The default language being installed for Office 365 ProPlus

Updates Enabled="TRUE" Updates are enabled to automatically download from CDN

Display Level="Full" Full UI when installing Office 365 ProPlus

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add SourcePath="\\Server\Share" OfficeClientEdition="32" >

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Product>

</Add>

<Updates Enabled="TRUE" UpdatePath="\\Server\Share\Updates" />

<Display Level="Full" AcceptEULA="TRUE" />

</Configuration>

Sample Configuration with all Office Applications with SourcePath, Updates enabled from internal source,

Interface Display, License Agreement

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being installed

Language ID=”en-us” The default language being installed for Office 365 ProPlus

Updates Enabled="TRUE" Updates are enabled

UpdatePath="\\Server\Share\Updates" Updates to install from \\Server\Share\Updates

Display Level="Full" Full UI when installing Office 365 ProPlus

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add SourcePath="\\Server\Share" OfficeClientEdition="32" >

<Product ID="O365ProPlusRetail">

<ExcludeApp ID="Word" />

<Language ID="en-us" />

</Product>

</Add>

<Updates Enabled="TRUE" UpdatePath="\\Server\Share\Updates" />

<Logging Level="Standard" Path="%temp%" />

<Display Level="Full" AcceptEULA="TRUE" />

</Configuration>

Sample Configuration with Word excluded with SourcePath, Updates enabled from internal source,

Interface Display, License Agreement, Logging

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being installed

Language ID=”en-us” The default language being installed for Office 365 ProPlus

ExcludeApp ID="Word" Excludes Word from being installed

Updates Enabled="TRUE" Updates are enabled

UpdatePath="\\Server\Share\Updates" Updates to install from \\Server\Share\Updates

Display Level="Full" Full UI when installing Office 365 ProPlus

AcceptEULA="TRUE" Accept the License Agreement

Logging Level="Standard" Logging is enabled

Path="%temp%" Log is written to %temp%

<Configuration>

<Add SourcePath="\\Server\Share" OfficeClientEdition="32" >

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

<Product ID="ProjectProRetail">

<Language ID="en-us" />

</Product>

<Product ID="VisioProRetail">

<Language ID="en-us" />

</Product>

</Product>

</Add>

<Updates Enabled="TRUE" UpdatePath="\\Server\Share\Updates" />

<Display Level="NONE" AcceptEULA="TRUE" />

</Configuration>

Sample Configuration with all Applications including Visio and Project 2016 Click to Run with SourcePath,

Updates enabled from internal source, no Interface Display, License Agreement

XML Configuration File Breakdown:

Deploy Page 16

Page 17: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Component Explanation

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being installed

Language ID=”en-us” The default language being installed for Office 365 ProPlus

Product ID=”ProjectProRetail” SKU of Project being installed

Language ID=”en-us” The default language being installed for Project 2016 Click to Run

Product ID=”VisioProRetail” SKU of Visio being installed

Language ID=”en-us” The default language being installed for Visio 2016 Click to Run

Updates Enabled="TRUE" Updates are enabled

UpdatePath="\\Server\Share\Updates" Updates to install from \\Server\Share\Updates

Display Level="NONE" No UI when installing Office 365 ProPlus, Project, and Visio

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add SourcePath="\\Server\Share" OfficeClientEdition="32" >

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

<Product ID="ProjectProXVolume">

<Language ID="en-us" />

</Product>

<Product ID="VisioProXVolume">

<Language ID="en-us" />

</Product>

</Product>

</Add>

<Updates Enabled="TRUE" UpdatePath="\\Server\Share\Updates" />

<Display Level="NONE" AcceptEULA="TRUE" />

</Configuration>

Sample Configuration with all Applications including Visio (VL) and Project (VL) 2016 Click to Run with

SourcePath, Updates enabled from internal source, no Interface Display, License Agreement

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being installed

Language ID=”en-us” The default language being installed for Office 365 ProPlus

Product ID=”ProjectProXVolume” SKU of Project being installed - volume licensed

Language ID=”en-us” The default language being installed for Project 2016 Click to Run

Product ID=”VisioProXVolume” SKU of Visio being installed - volume licensed

Language ID=”en-us” The default language being installed for Visio 2016 Click to Run

Updates Enabled="TRUE" Updates are enabled

UpdatePath="\\Server\Share\Updates" Updates to install from \\Server\Share\Updates

Display Level="NONE" No UI when installing Office 365 ProPlus, Project, and Visio

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add SourcePath="\\Server\Share" OfficeClientEdition="32" >

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

<Product ID="ProjectProRetail">

<Language ID="en-us" />

</Product>

<Product ID="VisioProRetail">

<Language ID="en-us" />

</Product>

</Product>

</Add>

<Updates Enabled="FALSE" UpdatePath="\\Server\Share\Updates" />

<Display Level="Full" AcceptEULA="TRUE" />

</Configuration>

Sample Configuration with all Applications including Visio and Project 2016 Click to Run with SourcePath,

Updates disabled from internal source, Interface Display, License Agreement, Logging

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being installed

Language ID=”en-us” The default language being installed for Office 365 ProPlus

Product ID=”ProjectProRetail” SKU of Project being installed

Language ID=”en-us” The default language being installed for Project 2016 Click to Run

Product ID=”VisioProRetail” SKU of Visio being installed

Language ID=”en-us” The default language being installed for Visio 2016 Click to Run

Updates Enabled="FALSE" Updates are disabled

UpdatePath="\\Server\Share\Updates" Updates to install from \\Server\Share\Updates

Display Level="Full" Full UI when installing Office 365 ProPlus, Project, and Visio

AcceptEULA="TRUE" Accept the License Agreement

Logging Level="Standard" Logging is enabled

Path="%temp%" Log is written to %temp%

Deploy Page 17

Page 18: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Installing Office 365 ProPlus from CDN or DFS Overview

Deployment Overview

When planning for and implementing a modern Office 365 ProPlus deployment for a customer, it is critical to understand the de ployment options

available to customers. In this section we will cover the high level description of the different architecture components use d in the CDN and FS client

deployment processes.

Platform Architecture

Office 365 ProPlus is available in both 32-bit and 64-bit editions. It is critical to understand the advantages and disadvantages in full before selecting

a specific architecture.

The following table details the advantages and disadvantages of selecting 64 -bit Office:

Note

For detailed guidance, refer to 64-bit editions of Office 2013

Advantages Disadvantages

64-bit can address more memory than 32-bit. Native 64-bit Office 365 ProPlus cannot be installed on

computers that have 32-bit Office applications and third-

party add-ins installed.

Excel 2016 can load much larger workbooks. Excel 2016 made updates to use 64 -bit

memory addressing in order to move beyond the 4 gigabytes (GB) addressable

memory boundary that limits 32-bit applications. (must be on version 1602 and

current channel. The update for Deferred Channel is expected to release in Oct

2016)

Macros and add-ins may need to be re-written to work in an

64-bit environment

Some applications may not render graphics correctly.

Some tools, like Power Query are only supported on 64-bit environment

It is recommended that 32-bit is used for both 32-bit and 64-bit operating systems if users in your organization depend on existing extensions to

Office, such as Microsoft ActiveX® controls, third-party add-ins, in-house solutions built on previous versions of Office, or 32 -bit versions of

programs that interface directly with Office.

Click-to-Run Technology

Click-to-Run is a Microsoft streaming and virtualization technology that reduces the time that is required to install Office and helps you run

multiple versions of Office on the same computer. The streaming technology enables you to download and begin to use an Office product

before the whole product is installed on your computer.

The virtualization technology provides an isolated environment for Office to run on your computer. This isolated environment provides a

separate location for the Office product files and settings to be stored so that they don’t change other applications that ar e already installed on

the computer. This enables you to run the latest version of Office side -by-side with an earlier version of Office that is already installed on your

computer.

The earlier version of Office that is already installed on the computer must be one of the following versions of Office: Offi ce 2010, Office

2007, or Office 2003. Microsoft only tests the N-1 for side by side compatibility.

The versions of Office that you install must be the same edition. For example, both installations of Office are the 32 -bit edition.

Important

Even though the Office product runs in a self-contained environment, the Office product can interact with the other applications that are

installed on the computer. Macros, in-document automation, and cross-Office product interoperability will work. Click-to-Run is also designed

to allow locally-installed add-ins and dependent applications to work with it. However, there is the possibility that some add -ins or other

integration points with Office might behave differently or might not work when you are using Click -to-Run.

Click-to-Run is used to install and update Office products. These streaming and virtualization capabilities are based on technologies include in

Microsoft Application Virtualization (App-V).

Installation Process

Start an installation and perform core Click-to-Run tasks such as streaming and application start

Maintain state for the virtualized package

Initiate integration tasks

Monitor for updates

Provide an interface into the Click-to-Run platform

Click-to-Run uses a multi-process framework to do the following:

Applications and processes use this interface to query for state and to communicate information.

A single executable program contains the logic that is required to initiate Click -to-Run streaming and application start processes. It includes all

the components that are required to stream Click-to-Run packages.

Streaming of Office, a core component of the Click-to-Run infrastructure, allows for parts of the product to be prioritized, grouped into blocks,

and delivered over time while the applications run. The streaming process is controlled by the streaming engine.

The streaming engine manages downloads of items in the streaming queue, prioritizes incoming streaming requests, determines w hether to

display streaming user interface, and publishes the downloaded information to the native file system. The streaming engine al so maintains a

streaming queue, a prioritized list of all the Office sources and components that are to be downloaded to the local cache to complete the

installation or to fulfill on-demand requests that are generated by an application's runtime. Every Click -to-Run package has a default streaming

queue prioritization at first. This prioritization may change dynamically in response to application use before the product i s fully cached locally.

If some users in your organization are Excel expert users who work with Excel spreadsheets that are larger than 4 GB, they ca n install the 64-bit

edition of Office 365 ProPlus. In addition, if you have in -house solution developers, we recommend that those developers have access to the 64 -bit

edition of Office 365 ProPlus so that they can test and update your in -house solutions on the 64-bit edition of Office 365 ProPlus.

Feature Selection

Due to the nature of Click-to-Run deployment, customizations and feature selections at the application level are not possible, unlike Office MSI

versions, where the Office Customization Tool (OCT) can still be used to generate customized .msp files for use at install ti me.

Customization

During deployment•

Post deployment•

Deployment Customization

Setup Customization File (XML)

Specify languages to install

The following options can be configured in the XML file:

The XML file is used to configure the way of setup will interact with user and how Office 365 ProPlus will be install and mai ntain.

The Office 365 ProPlus installation architecture offers only one method to perform customization during deployment: using XML definition file.

After the Office configuration decisions have been made, an approach must be defined to apply these settings to the Office in stallation.

Customization of Office deployment can be broken into two key approaches:

Deploy Page 18

Page 19: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Specify platform architecture to install (32-bit or 64-bit)

Specify license activation feature

Specify installation logs usage

Specify display information

Specify update settings

Multiple Language Deployment

When configuring the deployment of multiple languages, it is important to consider the approach the deployment of these langu ages. By

default, Setup installs only the language version that match elements defined in xml customization file.

Information

You can install more than one language on a single computer without using more than one license. The 1st language defined in the

configuration file will be the default language. Each language size is between 150 -250 MB.

Preparing to Deploy

Review and record the customization settings in the legacy version of Office•

Download the Office 2016 Administrative Template files•

Choose the 32 or 64-bit template files•

Compare the recorded customizations settings with the Office 2016 Administrative Template Excel spreadsheet for Office 365 Pr oPlus

Customization.

Import the Office 2016 Administrative Template Files into Active Directory and set the appropriate group policy objects setti ngs. A Step-by-

Step Guide for ADMX templates can be found here

The MSI version of Office allows for the Office Customization Tool (OCT) to be utilized to customize Office installation. Th e OCT tool cannot be

leveraged for Office 365 ProPlus. Instead customization is doing using group policy.

Information

Languages

It is a preferred practice that Office 365 ProPlus languages are installed with the initial installation. Additionally, lang uages can be deployed

post installation. Review the languages supported for Office 365 ProPlus.

Office Applications

Review the applications

Decide which applications will be deployed

The following applications are included with Office 365 ProPlus. InfoPath is not included in Office 365 ProPlus, and is available for Office 365

ProPlus subscribers. The download for InfoPath 2013 for Office 365 ProPlus Subscription is located here

The Office 2016 Administrative Template files will be updated as new settings to control the look and feel of Office 365 ProP lus

Visio and Project 2016

Visio 2016 and Project 2016 are not included with Office 365 ProPlus, and require a separate license. It is now supported to install the volume

licensed versions of Project and Visio 2016, with the requirements are located here. Note that the installs still leverage C2R technology, but activate

using a traditional MAK/KMS system.

Side by Side - It is a preferred practice that the legacy versions of Office are removed during the installation of Office ProPlus. Side by side

should be only be used for limited testing during the pilot deployment.

Removal of Legacy Office -The preferred practice for the removal of legacy versions of Office is to utilize OffScrub for the specific version

Office. OffScrub is fully supported by Premier and should be contacted to obtain the required versions.

Side by Side or Removal of Legacy Office

Deploy Page 19

Page 20: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Step by Step Installation using CDN

Deployment Overview

In this section we will cover installing and managing Office 365 ProPlus by leveraging the CDN, as well as provide the high l evel description of the

different architecture components.

Create XML File for Installation

Product and Languages

Level of interface to display

Logging options

Product updates behavior

The XML file for installation will specify the following:

The parameters and settings for the XML file can be found here. The parameters for Project and Visio 2016 volume licensing can be found here

A graphical UI for creating the XML file can be found at the Office GitHub Repository Office Click-To-Run Configuration XML Editor

Create OffScrub.vbs Configuration File

An OffScrub configuration command must be created to automate the removal of Office.

Obtain the appropriate version of OffScrub from Premier for the Office version to be removed1.

Example: cscript Offscrub10.vbs /preview /log c:\temp

cscript <OffScrub file>.vbs /preview /log <path to log out file>

From an elevated command prompt with administrative privileges run the following to get the SKU ID’s of the Office products i nstalled2.

Example Output:

Found registered product(s): PRJSTDR,PROPLUSR,VISIOR

The products found in the above example are Project 2010 Standard, Office ProPlus 2010 and Visio 2010.

Review the out offscrub /preview command and look for the following line:3.

cscript OffScrub10.vbs clientall /bypass 1 /log c:\temp /nocancel /q

cscript OffScrub10.vbs PROPLUSR /bypass 1 /log c:\temp /nocancel /q

Sample Offscrub10.vbs removing Office 2010 and keeping Visio 2010 and Project 2010

cscript OffScrub10.vbs PROPLUSR, VISIOR /bypass 1 /log c:\temp /nocancel /q

Sample Offscrub10.vbs removing Office 2010 removing Visio 2010 and keeping Project 2010

Execute the following command from an elevated command prompt with administrative privileges to remove all Office 2010 client products4.

Ensure the update channel has been set in the Office 2016 Group policy object1.

Copy OffScrub, the ODT, and the install XML file to a local directory on the workstations to be deployed2.

From an elevated command prompt with administrator privileges, run the OffScrub.vbs with the appropriate command line switche s3.

Each version of OffScrub will have the same or similar Error/Success codes. Review each script for respective codes.

Information

Review the OffScrub exit codes contained within the script4.

From an elevated command prompt with administrator privileges run setup.exe /configure <installXMLfilename>.xml5.

Review the installation log6.

Reboot the workstation to cleanup any files that were unable to be cleared from the registry from the OffScrub process . 7.

Install Office 365 ProPlus and Remove Legacy Version of Office – Non-Shared Workstation

Ensure the update channel has been set in the Office 2016 Group policy object1.

Copy OffScrub, the ODT, and the install XML file to a local directory on the workstations to be deployed2.

From an elevated command prompt with administrator privileges run the OffScrub.vbs with the appropriate command line switches3.

Each version of OffScrub will have the same or similar Error/Success codes. Review each script for respective codes.

Information

Review the OffScrub exit codes contained within the script:4.

From an elevated command prompt with administrator privileges run setup.exe /configure <installXMLfilename>.xml5.

Review the installation log6.

Reboot the workstation to cleanup any files that were unable to be cleared from the registry from the OffScrub process. 7.

Install Office 365 ProPlus and Remove Legacy Version of Office – Shared Workstation

Install Office365 ProPlus and Remove Legacy Version of Office

Deploying Office365 ProPlus

Remove an Application from Office 365 ProPlus

It is possible to remove a program from the Office Suite post deployment. A configuration XML will need to be utilized.

<Configuration>

<Add Channel="Deferred" OfficeClientEdition="32">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

<ExcludeApp ID="Word" />

</Product>

</Add>

<Updates Channel="Deferred" Enabled="TRUE" />

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Logging Level="Standard" Path="c:\Officeinstall" />

<Display Level="Full" AcceptEULA="TRUE" />

</Configuration>

Sample Configuration File for Removing Word Post Install – Deferred Channel

XML Configuration File Breakdown:

Component Explanation

Channel=”Deferred” The channel build of Office 365 ProPlus being installed

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”

O365ProPlusRetail”

SKU of Office 365 ProPlus being installed

Language ID=”en-us” The language being installed for Office 365 ProPlus

ExcludeApp ID="Word" Remove Word from deployed Office 365 ProPlus

Updates Channel =

“Deferred”

The Update Channel for Office 365 ProPlus. This parameter should match the Channel build being installed. If

it does the product will switch to the channel defined.

For example: If the channel being installed is Current Channel and the Updates Channel is set to Deferred

when the client updates Office 365 ProPlus will update to Deferred channel which may or may not contain all

the features/non-security updates as Current Channel.

Enabled="TRUE" Updates are enabled

The parameters and settings for the XML file can be found here. A graphical UI for creating the XML file can be found at the Office GitHub

Repository Office Click-To-Run Configuration XML Editor

Post Deployment Tasks

Deploy Page 20

Page 21: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Enabled="TRUE" Updates are enabled

Property

Name="FORCEAPPSHUTD

OWN" Value="TRUE"

Force the Office365 ProPlus apps to shutdown. This should be set to True. If the applications are not closed

install may fail

Logging Level=”Standard”

Path=”c:\office install”

Logging level and location of log file

Display Level="Full" Full UI when installing Office 365 ProPlus

AcceptEULA="TRUE" Accept the License Agreement

Copy ODT and the configuration XML file to a local directory on the workstations to be deployed.1.

From an elevated command prompt with administrator privileges run setup.exe /configure <configurationXMLfilename>.xml2.

Review the installation log3.

Steps to Remove an Application Post Install

Add an application back to Office 365 ProPlus

It is possible to add a program back to the Office 365 ProPlus suite post deployment. An install XML will need to be utilize d.

<Configuration>

<Add Channel="Deferred" OfficeClientEdition="32">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Product>

</Add>

<Updates Channel="Deferred" Enabled="TRUE" />

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Logging Level="Standard" Path="c:\Officeinstall" />

<Display Level="Full" AcceptEULA="TRUE" />

</Configuration>

Sample Configuration File Adding Word to an Already Deployed Office 365 ProPlus – Deferred Channel

XML Configuration File Breakdown:

Component Explanation

Channel=”Deferred” The channel build of Office 365 ProPlus being installed

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”

O365ProPlusRetail”

SKU of Office 365 ProPlus being installed

Language ID=”en-us” The language being installed for Office 365 ProPlus

Updates Channel = “Deferred” The Update Channel for Office 365 ProPlus. This parameter should match the Channel build being

installed. If it does the product will switch to the channel defined.

For example: If the channel being installed is Current Channel and the Updates Channel is set to

Deferred when the client updates Office 365 ProPlus will update to Deferred channel which may or

may not contain all the features/non-security updates as Current Channel.

Enabled="TRUE" Updates are enabled

Property

Name="FORCEAPPSHUTDOW

N" Value="TRUE"

Force the Office365 ProPlus apps to shut down. This should be set to True. If the applications are

not closed install may fail

Logging Level=”Standard”

Path=”c:\office install”

Logging level and location of log file

Display Level="Full" Full UI when installing Office 365 ProPlus

AcceptEULA="TRUE" Accept the License Agreement

Copy ODT and the configuration XML file to a local directory on the workstations to be deployed.1.

From an elevated command prompt with administrator privileges run setup.exe /configure <configurationXMLfilename>.xml2.

Review the installation log3.

Steps to Add an Application Post Install

The parameters and settings for the XML file can be found here. A graphical UI for creating the XML file can be found at the Office GitHub

Repository Office Click-To-Run Configuration XML Editor

Add a Language Post Install

An additional language can be installed post install to Office 365 ProPlus.

<Configuration>

<Add Channel="Current" OfficeClientEdition="32">

<Product ID="LanguagePack">

<Language ID="es-es" />

</Product>

</Add>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

</Configuration>

XML Configuration File Breakdown:

Component Explanation

Channel=”Current” The channel build of Office 365 ProPlus being installed

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”LangaugePack” Language Pack

Language ID=”es-es” The language being installed for Office 365 ProPlus

Property Name="FORCEAPPSHUTDOWN"

Value="TRUE"

Force the Office365 ProPlus apps to shutdown. This should be set to True. If the

applications are not closed install may fail

<Configuration>

<Add Channel="Deferred" OfficeClientEdition="32">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

<Language ID="fr-fr" />

</Product>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

</Add>

</Configuration>

Sample Configuration File with all Applications with English and French Languages – Non-Current Channel

XML Configuration File Breakdown:

Component Explanation

Channel=”Deferred” The channel build of Office 365 ProPlus being installed

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being installed

Language ID=”en-us”

Language ID="fr-fr"

The languages being installed for Office 365 ProPlus

Property Name="FORCEAPPSHUTDOWN"

Value="TRUE"

Force the Office365 ProPlus apps to shutdown. This should be set to True. If the

applications are not closed install may fail

Sample XML Add Spanish to Post Deployment – Current Channel

Steps to Add a Language Post Install – Current Channel and Non-Current Channel

If the Office 365 ProPlus is on Current Channel greater than update 2062, using the newest ODT and install XML file identifyi ng the language to

be installed can be leveraged. If Office 365 ProPlus is not using the above requirements, a full XML configuration must be us ed.

Deploy Page 21

Page 22: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Copy ODT and the configuration XML file to a local directory on the workstations to be deployed.1.

From an elevated command prompt with administrator privileges run setup.exe /configure <configurationXMLfilename>.xml2.

Review the installation log3.

Change from Non-Shared Workstation to Shared Workstation

<Configuration>

<Add Channel="Deferred" OfficeClientEdition="32">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Product>

</Add>

<Updates Channel="Deferred" Enabled="TRUE" />

<Property Name="SharedComputerLicensing" Value="1" />

</Configuration>

Sample Configuration File with all Applications Shared Computer Activation – Deferred Channel

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being installed

Channel=”Deferred” The channel build of Office 365 ProPlus being installed

Product ID=”

O365ProPlusRetail”

SKU of Office 365 ProPlus being installed

Language ID=”en-us” The language being installed for Office 365 ProPlus

Updates Channel =

“Deferred”

The Update Channel for Office 365 ProPlus. This parameter should match the Channel build being installed. If

it does the product will switch to the channel defined.

For example: If the channel being installed is Current Channel and the Updates Channel is set to Deferred

when the client updates Office 365 ProPlus will update to Deferred channel which may or may not contain all

the features/non-security updates as Current Channel.

Enabled="TRUE" Updates are enabled

Property

Name="SharedComputer

Licensing" Value="1"

Shared Computer Licensing is enabled

Copy ODT and the configuration XML file to a local directory on the workstations to be deployed.1.

From an elevated command prompt with administrator privileges run setup.exe /configure <configurationXMLfilename>.xml2.

Review the installation log3.

Steps to Change from Non-Shared to Shared Workstation Post Install

To change from a non-shared workstation to shared workstation a configuration XML should be redeployed.

Change Update Channels

It is a preferred practice to change the update channel by changing it in the Office 2016 Group Policy object if required. Th e changing of

channels will result in a 100% delta change to the product. For more information on switching channels, please see the follow ing section:

Channel Management

Rollback or Downgrade Strategy

In the unlikely scenario that the pilot or production group deems that the newly updated build is not suitable for use, a rol lback or downgrade

can be completed in order to get the group back on a previously known good or approved build of Office 365 ProPlus. For more information

on rollbacks, please see the following section: Channel Management

Deploy Page 22

Page 23: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Step by Step Installation Using DFS

Deployment Overview

In this section we will cover installing and managing Office 365 ProPlus by leveraging an existing Distributed File System (D FS), as well as provide the

high level description of the different architecture components.

Folder Structure Creation

Create the following folder structure in the network shares:

Folder Path Purpose

\\Server\Share\O365 This is the parent folder that will be used for storing all Office 365 ProPlus related items

\\Server\Share\O365\CC Use this folder to store the most current Office 365 ProPlus Current Channel build that pilot users will receive

\\Server\Share\O365\FRDC Use this folder to store the most current Office 365 ProPlus First Release for Deferred Channel build that pre-

production users will receive

\\Server\Share\O365\DC Use this folder to store the most current Office 365 ProPlus Deferred Channel build that production users will

receive. Production channel should be Deferred Channel

\\Server\Share\O365\Archive

\%channel%

Use this folder to host N-1 previously known good builds in case a rollback or downgrade is needed

Download Office365 ProPlus Builds

The downloads will contain the Office 365 ProPlus build for the most up -to-date channel release. Specify all products and languages that will

be deployed.

Download latest Current Channel build. For example XML see Download XML Examples1.

Save the configuration file as GetLatestCCBuild.xml2.

Ensure Office Deployment Tool (setup.exe) is in \\Server\Share\O3653.

Copy GetLatestCCBuild.xml to \\Server\Share\O365\CC4.

From an elevated command prompt with administrator privileges run \\Server\Share\O365\Setup.exe /Download \\Server\Share

\O365\CC\GetLatestCCBuild.xml

5.

Once executed, Office Deployment Tool will download the latest Office 365 ProPlus Current Channel build into \\Server\Share

\O365\CC

6.

Download Current Channel Build

Download latest current First Release Deferred Channel build. For example XML see Download XML Examples1.

Save the configuration file as GetLatestFRDCBuild.xml2.

Ensure Office Deployment Tool (setup.exe) is in \\Server\Share\O3653.

Copy GetLatestFRDCBuild.xml to \\Server\Share\O365\FRDC4.

From an elevated command prompt with administrator privileges run \\Server\Share\O365\Setup.exe /Download \\Server\Share

\O365\FRDC\GetLatestFRDCBuild.xml

5.

Once executed, Office Deployment Tool will download the latest Office 365 ProPlus First Release Deferred Channel build into

\\Server\Share\O365\FRDC

6.

Download First Release for Deferred Channel Build

Download latest current Deferred Channel build. For example XML see Download XML Examples1.

Save the configuration file as GetLatestDCBuild.xml2.

Ensure Office Deployment Tool (setup.exe) is in \\Server\Share\O3653.

Copy GetLatestDCBuild.xml to \\Server\Share\O365\DC4.

From an elevated command prompt with administrator privileges run \\Server\Share\O365\Setup.exe /Download \\Server\Share

\O365\DC\GetLatestDCBuild.xml

5.

Once executed, Office Deployment Tool will download the latest Office 365 ProPlus Deferred Channel build into \\Server\Share

\O365\DC

6.

Download Deferred Channel Build

The parameters and settings for the XML file can be found here. The parameters for Project and Visio 2016 volume licensing can be found here

A graphical UI for creating the XML file can be found at the Office GitHub Repository Office Click-To-Run Configuration XML Editor

Deploying Office365 ProPlus from DFS

Copy OffScrub on the workstations to be deployed. 1.

From an elevated command prompt with administrator privileges run the OffScrub.vbs with the appropriate command line switches .2.

Each version of OffScrub will have the same or similar Error/Success codes. Review each script for respective codes.

Information

Review the OffScrub exit codes contained within the script:3.

From an elevated command prompt with administrator privileges run \\Server\Share\O365\Setup.exe /Configure \\Server\Share

\O365\CC\CC_configuration.xml

4.

Review the installation log5.

Reboot the workstation to cleanup any files that were unable to be cleared from the registry from the OffScrub process. 6.

Install Office 365 ProPlus and Remove Legacy version of Office –Current Channel Build

Copy OffScrub on the workstations to be deployed. 1.

From an elevated command prompt with administrator privileges run the offscrub.vbs with the appropriate command line switches .2.

Each version of OffScrub will have the same or similar Error/Success codes. Review each script for respective codes.

Information

Review the OffScrub exit codes contained within the script:3.

From an elevated command prompt with administrator privileges run \\Server\Share\O365\Setup.exe /Configure \\Server\Share

\O365\FRDC\FRDC_configuration.xml

4.

Review the installation log5.

Reboot the workstation to cleanup any files that were unable to be cleared from the registry from the OffScrub process. 6.

Install Office 365 ProPlus and Remove Legacy version of Office – First Release for Deferred Channel Build

Copy OffScrub on the workstations to be deployed. 1.

From an elevated command prompt with administrator privileges run the OffScrub.vbs with the appropriate command line switches .2.

Each version of OffScrub will have the same or similar Error/Success codes. Review each script for respective codes.

Information

Review the OffScrub exit codes contained within the script:3.

From an elevated command prompt with administrator privileges run \\Server\Share\O365\Setup.exe /Configure \\Server\Share

\O365\DC\DC_configuration.xml

4.

Review the installation log5.

Reboot the workstation to cleanup any files that were unable to be cleared from the registry from the OffScrub process. 6.

Install Office 365 ProPlus and Remove Legacy version of Office – Deferred Channel Build

Install Office365 ProPlus and Remove Legacy version of Office

Remove an application from Office ProPlus 365

Post Deployment Tasks

Deploy Page 23

Page 24: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Remove an application from Office ProPlus 365

It is possible to remove a program from the Office Suite post deployment. A configuration.xml will need to be utilized.

Configure XML file to exclude application. For example XML see 'Download XML Examples'1.

Save the configuration file as DCExcludeword_configuration.xml 2.

Ensure Office Deployment Tool (setup.exe) is in \\Server\Share\O3653.

Copy DCExcludeword_configuration.xml to \\Server\Share\O365\DC4.

From an elevated command prompt with administrator privileges run \\Server\Share\O365\Setup.exe /Configure \\Server\Share\O365

\DC\DCExcludeword_configuration.xml

5.

The parameters and settings for the XML file can be found here. A graphical UI for creating the XML file can be found at the Office GitHub

Repository Office Click-To-Run Configuration XML Editor

Add an application to Office ProPlus 365 to already deployed

It is possible to add a program from the Office Suite post deployment. A configuration.xml will need to be utilized.

Configure XML file and remove any excluded applications1.

Save the configuration file as DC_configuration.xml 2.

Ensure Office Deployment Tool (setup.exe) is in \\Server\Share\O3653.

Copy DC_configuration.xml to \\Server\Share\O365\DC4.

From an elevated command prompt with administrator privileges run \\Server\Share\O365\Setup.exe /Configure \\Server\Share\O365

\DC\DC_configuration.xml

5.

The parameters and settings for the XML file can be found here. A graphical UI for creating the XML file can be found at the Office GitHub

Repository Office Click-To-Run Configuration XML Editor

Add a Language Post Install

An additional language can be installed post install to Office 365 ProPlus.

<Configuration>

<Add Channel="Deferred" OfficeClientEdition="32" SourcePath="\\Server\Share\O365\DC">

<Product ID="LangaugePack">

</Product>

<Language ID="es-es" />

</Add>

</Configuration>

Sample XML Add Spanish to Post Deployment – Deferred Channel

XML Configuration File Breakdown:

Component Explanation

Add Channel="Deferred” Channel build to be downloaded

OfficeClientEdition=”32” The architecture of Office being installed

SourcePath="\\Server\Share\O365\DC" Path where Channel build will be downloaded

Product ID=”LangaugePack” LangaugePack

Language ID=”es-es” The language being installed for Office 365 ProPlus

Save the configuration file as DCLanguage_configuration.xml 1.

Ensure Office Deployment Tool (setup.exe) is in \\Server\Share\O3652.

Copy DCLangauge_configuration.xml to \\Server\Share\O365\DC3.

From an elevated command prompt with administrator privileges run \\Server\Share\O365\Setup.exe /Configure \\Server\Share\O365

\DC\DCLanguage_configuration.xml

4.

If the Office 365 ProPlus is on Current Channel greater than update of 2062, using the newest ODT an XML file identifying the language to be

installed can be leveraged. If Office365 ProPlus is not using the above requirements a full XML configuration must be used.

Change Update Channels

It is a preferred practice to change the update channel by changing it in the Office 2016 Group Policy object if required. Th e changing of channels

will result in a 100% delta change to the product. For more information on switching channels, please see the following secti on: Channel

Management

Rollback or Downgrade Strategy

In the unlikely scenario that the pilot or production group deems that the newly updated build is not suitable for use, a rol lback or downgrade can

be completed in order to get the group back on a previously known good or approved build of Office 365 ProPlus. For more info rmation on

rollbacks, please see the following section: Channel Management

Deploy Page 24

Page 25: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Group Policy Implementation

Download the Administrative Templates for Office 2016

Extract the content and import it into your Central Store for Group Policies on

a Domain Controller (see: Managing Group Policy ADMX Files Step-by-Step

Guide)

Import the Office 2016 Administrative Templates into AD DS:1.

Copy and extract the Preferred Practices Group Policy Settings

Create new group policy objects (GPOs) for user and computer settings

Import the extracted backups into the respective GPOs

Link the GPOs to the respective OUs and start testing

Leverage the Preferred Practices GPO Baseline2.

How to Implement the Preferred Practices GPOs

Deploy Page 25

Page 26: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

OffScrub

Office Scrub tool (OffScrub)

Utilizing OffScrub is the best method of removing a previous version of Office. OffScrub helps achieve a higher level of clea n Office removals by

having a better success rate of removing Office than traditional methods. It will call the setup.exe and msiexec.exe to remov e the previous bits. It is

best equipped to deal with machine or software corruption and completely removes the Office app shortcuts for the previous Office versions. It is

recommended to use OffScrub in almost every situation of migrating from previous versions of Office. OffScrub is supported by Premier and should

be contacted in order to obtain the latest version for your specific Office deployment.

If Office source bits, or cache is missing or not healthy – legacy product does not uninstall•

Guarantees a clean uninstall•

Does not touch the User Hive•

Verbose Logging•

Removes legacy add on products such a Visio Viewer etc.•

Can remove Project and Visio and Office in one command•

Removes legacy add on products such a Visio Viewer etc.•

Remove non-standard company approved Office Applications – this really applies to companies that allow users to install and leverage non

corporate products

Reasons for OffScrub to be used with Legacy Office to Office 2016 C2R migrations:

Office 2013 Icons on task bar are not removed•

Short cut Icons are not removed•

Upgrade process doesn’t always do a clean uninstall. Removal of the bits with off scrub typically ensures a clean uninstall•

Quicker than native process•

Does not touch the User Hive •

Verbose Logging•

Can remove Project and Visio and Office in one command•

Removes legacy add on products such a Visio Viewer etc.•

Reasons for OffScrub to be used with Office 2013 CR2 to Office 2016 C2R migrations:

Deploy Page 26

Page 27: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Office Telemetry

Office Telemetry Overview

Office Telemetry is the new compatibility monitoring framework that replaces the previous Office 2010 compatibility tools and helps minimize the

time and risks of an Office upgrade. When an Office document or solution is loaded, used, closed, or raises an error in certa in Office applications, the

application adds a record about the event to a local data store. The record is then uploaded to the Office Telemetry database , where it is used in

conjunction with the Telemetry Dashboard in order for IT admins to get a complete view of the Office Telemetry data being col lected in the

organization.

Telemetry Dashboard Overview

Telemetry Dashboard is an Excel workbook that is configured to connect to a telemetry database, and comes installed together with Office versions

starting with Office 2013. The Telemetry Dashboard also allows IT admins to utilize pre-built reports, or create custom reports, that can help with

guiding the discovery of critical applications.

The Telemetry Dashboard should be used in conjunction with interviewing and working with key business stakeholders to identify the critical

business applications that must be validated prior to deploying Office 365 ProPlus in the environment. It should not replace working with the

business groups, and it should instead be leveraged to assist with the identification of how often users access specific comp onents and identifying

the number of users for those particular components.

Office Telemetry References

Assess Office compatibility with other versions of Office

Telemetry Dashboard topology, sizing, and bandwidth planning

Office Telemetry tools and components

Update Office Telemetry components for Office 2016

Deploy Telemetry Dashboard

Data that the telemetry agent collects in Office

Document and solution types monitored by telemetry in Office

Monitor Office compatibility and deployments by using Telemetry Dashboard

Manage the privacy of data monitored by telemetry in Office

Manage add-ins by using Telemetry Dashboard in Office

Let’s manage add-ins using Telemetry Dashboard

Telemetry Dashboard worksheet reference

Custom reporting and database schema reference for Telemetry Dashboard

The links below give additional details on Telemetry Dashboard components and configuration options recommended to assist cus tomers with their

application compatibility assessment:

Deploy Page 27

Page 28: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Office 2016 for Mac Clients

Introduction

This section defines the system requirements and deployment information for Office 2016 for Mac.

System Requirements

Component Requirement

Operating system Mac: At least Mac OS X 10.10

Computer and processor Mac: Intel Processor

Memory Mac: 4 GB of RAM

Disk space Mac: 6 gigabytes (GB) available, HFS + hard disk format

Display Mac: 1280 x 800

Browsers Current or immediate previous versions of Internet Explorer

Current version of Safari, Chrome, Firefox, or Microsoft Edge

.Net PC: .NET 3.5 required, some features may require .NET 4.0, 4.5, or 4.6 CLR to also be installed

The following table outlines the standard system Office System Requirements. However, system requirements are subject to chan ge. Therefore, the

following link should be referenced for the most current Office system requirements: Office System Requirements.

Office 2016 for Mac References

What's new for admins in Office 2016 for Mac

Overview of activation for Office 2016 for Mac

Deployment options for admins for Office 2016 for Mac

Deploy preferences for Office 2016 for Mac

Deploy updates for Office 2016 for Mac

Office 2016 for Mac upgrade to 64-bit

Download and Install Office 2016 for Mac Step by Step Instructions

What to try if you can't install or activate Office 2016 for Mac using Office 365 for business

Troubleshoot Office 2011 for Mac issues by completely uninstalling before you reinstall

The following links provide detailed information about Office 2016 for Mac deployments:

Deploy Page 28

Page 29: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Common Debugging Steps

The following steps below are common issues that customers come across when deploying and managing Office 365

ProPlus:

OfficeC2RClient.exe

OLicenseHeartbeat.exe

Utilize a network scanning utility such as Process Monitor, Wireshark, or Fiddler to see if throughput or connections are

being blocked:

1.

Does the system account running the processes have proxy access?2.

Are the network and firewall rules open?3.

Ensure you are using the latest version of the Office Deployment Tool (updated regularly)4.

Ensure your XML syntax is correct by using the GitHub XML script editor to verify5.

Check for new GPOs in the Office 2016 Administrative Template files (update regularly)6.

Does the account installing Office 365 ProPlus have administrative privileges?7.

Deploy Page 29

Page 30: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Office 365 ProPlus Management Overview

Overview

Since Office 365 ProPlus is an Evergreen product, it is important to account for the ongoing management after Office 365 ProP lus has been

deployed. The following sections will provide a high level overview of the components involved with Office 365 ProPlus manage ment.

IT Managed and Unmanaged Deployment Scenarios

In general, the modern Office 365 ProPlus deployment solution includes functionality to deploy, maintain, and update clients from both an on

premise infrastructure, as well as from an off premise Office Content Delivery Network (CDN) infrastructure. The on premise a nd off premise

deployment infrastructures provide IT administrators flexibility to manage the initial deployment and maintenance of the Offi ce client for different

connectivity and end user segments of their environment.

For more information on the deployment scenarios as they pertain to channel management, please see the following section: Managing Channels

for Office 365 ProPlus

Patching and Update Channels with Office 365 ProPlus

With the 2016 release of Office 365 ProPlus, Microsoft incorporated the concept of Update Channels. Update Channels allow cus tomer IT admins to

have control over when new features will be rolled out to the end users. It also allows IT admins more time available to vali date critical business

applications with new features, as well as allow the IT admins to manage communications and training needs of their end users . While a majority of

Enterprise customers will use the Deferred Chanel for their general end user population, customer IT admins should also lever age other channels

within their environment for their pilot and pre-production user groups to create validation, communications, and training processes to ease feature

roll outs to their end users.

Each device in the customer’s environment can be a member of a specified channel, which will control the rhythm of feature ad option and code

stability. In order to balance the speed of adoption, running a stable environment, and preparing for the next round of updat es and product

changes, it is recommended to leverage all channels and segment the customer end user base by purpose and function in order t o streamline the

overall update rollout within the environment. By segmenting the work force and having multiple groups, customer’s IT admins will have more

flexibility and control to adequately achieve these goals. For detailed information on the Office 365 Update Channels, pleas e see: Update Channels

The below image is a visual representation of how new features and non -security updates are propagated from Current Channel, to First Release for

Deferred Channel, to Deferred Channel.

Change management for Office 365 clients

Ongoing Office 365 ProPlus Management and Maintenance

In addition to checking for new Office 365 ProPlus build releases, customers should periodically check for newer builds of th e 2016 Office

Deployment Tool and Office 2016 Administrative Template files. New releases of these items can include new features or capabi lities that are

designed to help IT admins manage Office 365 ProPlus deployments. It is recommended for customers to have a process in place to ensure that the

Office Deployment Tool and Office 2016 Administrative Template files used are the latest available versions from Microsoft.

Manage Page 30

Page 31: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Managing Channels and Updates for Office 365 ProPlus

Overview

In this section we will cover the recommended channel membership roles, as preferred practices for ongoing channel management .

Channel Membership Roles

Customers appreciate the value of constantly getting new features with Office 365 ProPlus; however, there is a concern about how often the product

updates and how to have adequate time to validate the new features so that they don’t break existing business processes. Addi tional time is also

needed to train the help desk and end users before the feature is enabled through the production environment. Customers have done this

previously with software and patches they release by first releasing it to a QA group that represents a population sample of all business groups and

apps. After the QA group has the software/patch and has not reported any adverse effects in 1 -2 weeks, the IT team then starts the production roll

out to the entire organization. This process can now be achieved by leveraging the different Office 365 client channel builds so that the QA group

has the features for at least 4 months before the rest of the enterprise receive those features.

The diagram below is recommended to use when deploying Office 365 ProPlus 2016 in order to have appropriate channel represent ation across the

environment. Each group can have Office 365 ProPlus deployed and managed via the Office CDN, an on premises source location, or a mix between

the Office CDN and an on premises source location. Additionally, pilot and pre -production groups should have instructions on how to report

abnormalities or issues immediately so they can be addressed before they are released in the Deferred Channel build.

Ring Channel Client

Population

Primary Function Roles

Pilot Deployment Current < 1% Evaluate new features and functionality

before released across all available

channels

Developers, testers, application/add-in owners, IT and

O365 champions, Office project team members, training

and communication leads

Pre-Production

Deployment

First Release for

Deferred Channel

~10% Business group feature and functionality

validation, provide direct feedback to IT

and Office admins

Developers, testers, training and communication leads,

business group champions, and designated end users

from each business group

Production

Deployment

Deferred ~89% End user production All end users not in the pilot or pre-production groups

Managing Updates Overview

This section describes how to implement an automated process to publish Office 365 ProPlus builds. By default, each client is set to pull from the

Office Content Delivery Network (CDN) using the Deferred Channel update channel method. The client will check the specified u pdate path location

and if there is no new version, it will remain as is. If there is a newer version, the client will perform a delta binary to calculate the difference between

itself and the update location’s build, compress the data, and then start the transmission to update. Office will use Backgro und Intelligent Transfer

Service (BITS) to control bandwidth if downloading from the Office CDN, but will not be applied if downloading from an SMB fi le share. It is

important to note that the client does not need administrative privileges to update, and it checks for updates regularly via a scheduled task and can

be seen in Task Scheduler.

Channel Management

Managing Updates through the Office CDN

The high-level steps below are recommended for a fully automated testing and deployment process using the Office CDN for patching:

When updating directly from the Office CDN, channel management will be managed by the cloud service. This means that based on the channel

membership, the Office client will get the appropriate build of Office. The Office update engine is not able to distinguish b etween the channels

natively, and is purely driven by build numbers. If deciding to control patching on premises it is critical to review the fol lowing sections, as the Office

client is missing the proper channel management control from the Office CDN. There will be no channel awareness by the Office client when the

update source is managed on premises, meaning the update engine will pick up the latest available build that is advertised th rough the v32.cab file.

Careful consideration, planning, and organization will be required when managing patching on premises with Office 365 ProPlus 2016 to ensure

Office clients are receiving the correct channel builds.

Identify and configure a pilot group to use Current Channel1.

Identify and configure a pre-production or QA group to use First Release for Deferred Channel2.

Configure all others to be in the production group to use Deferred Channel3.

Configure all groups to receive updates directly from the Office CDN4.

As a new build is released for the various channels, the update mechanism via scheduled task will download the latest build a utomatically5.

Have pilot and pre-production groups use Office as usual with instructions to immediately report any issues or concerns6.

Managing Updates On Premises

If your organization does not have the network capacity in place to adopt updates directly from the Office CDN, the builds ca n instead be

hosted in an on premises source location. An important note with Office 365 ProPlus is that once the builds are hosted on pre mises, the Office

client is missing the proper channel management control as previously stated and the update engine will pick up the latest av ailable build

rather than the associated channel membership.

Due to the availability dates of the builds, it is recommended to check for build updates multiple times per month. An automa ted task can be

created to check the Office CDN to see if there is a newer build available in a specific channel, and if so the automated tas k can download the

build source files to a specified location. An administrator would then take the newly download source files and distribute t hem out to the

appropriate channel membership group.

Switching Update Channels

If switching channels, careful consideration and planning should be done to account for the full delta change. Switching Chan nels is not

advised, as it is not a small task and will be a 100% file delta install. Simply put, if the channel you are switching to is 1.2 GB then a complete 1.2

GB of network bandwidth will be consumed if installing locally (700 -800 GB if using Office CDN). There is no need to uninstall and then re -

install; however, the network impact is the same of a new install. The task of switching update channels should leverage the existing

deployment infrastructure.

For step by step guidance on switching update channels, please see the following section: Channel Management

Out-Of-Band Build for Deferred Channel

Microsoft may release an out-of-band build outside of the estimated release timeline for Deferred Channel. In these cases, it is recommended that

Manage Page 31

Page 32: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Microsoft may release an out-of-band build outside of the estimated release timeline for Deferred Channel. In these cases, it is recommended that

for the deployment administrators to evaluate the out-of-band build and decides whether to deploy or skip the out of band build.

If deemed critical for deployment, please follow the same deployment procedures previously stated and process it as usual.

Otherwise, skip the out-of-band build and deploy the released out of band Patch Tuesday build as planned.

Rollback or Downgrade Strategy

A rollback or downgrade strategy should be planned for in the unlikely event that a new Office 365 ProPlus build causes a dis ruption in service. The

update engine is able to perform a downgrade, but the engine must be instructed to rollback by specifying a previous build nu mber to rollback to. If

the target version is not specified, the Office 365 ProPlus client will not be able to complete a downgrade. Similar to updat e scenarios, the rollback

should take the client channel membership into account. The downgrade should respect the current channel membership of the cl ient, and a target

build version correlating to that current channel membership should be specified in order to maintain channel membership. If the target version

specified is of a different channel than the channel that the client is currently on, the downgrade will succeed and a full d elta will be performed in

downgrading to the different channel.

For guidance on how to perform a rollback using the OfficeC2RClient.exe update engine, please see the following section: Channel Management

Group Policy ManagementCustomers should incorporate the Office 2016 Administrative Template files (ADMX/ADML) to configure update settings for Office 365 ProPlus.

It is important to note that when using Group Policy settings to manage Office 365 ProPlus, the Group Policy settings will ta ke precedence over any

configuration settings set by the install XML and Office Deployment Tool. For instance, if in the install XML updates were se t to disabled but the

Group Policy set them to enabled, Group Policy would take precedence and updates would be disabled. Therefore it is recommend ed for customers

to use Group Policy settings as additional enforcement to settings specified via the install XML and Office Deployment Tool

The following Group Policy objects can be leveraged to manage Office 365 ProPlus:

Update Settings Group Policy Setting

Set updates to occur automatically Enable automatic updates

Specify a location to look for updates Update path

Specify the version of Office 365 ProPlus to update to Target version

Set a deadline by when updates have to be applied Update deadline

Hide update notifications from users Hide update notifications

Hide the option to enable or disable Office automatic updates Hide options to enable or disable updates

For more information on managing updates using Group Policy, or to manage Office 365 ProPlus update settings using the Office Deployment Tool

configuration options, please see the following article: Configure update settings for Office 365 ProPlus

Manage Page 32

Page 33: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Manage Reference Materials

Overview

The following articles provide deeper technical information on specific areas of the Manage phase that are not covered in dep th in the customer scenarios.

Frequently Asked Questions

Overview of the update process for Office 365 ProPlus

How does Office 365 ProPlus update, does it leverage WSUS like previous Office versions? How does it detect that updates are available?

Choose how to apply updates to Office 365 ProPlus

Configure update settings for Office 365 ProPlus

How are update settings applied, and how are they managed? Can I still use Group Policy to manage Office 365 ProPlus updates?

End-user update notifications for Office 365 ProPlus

What are the update notifications that users will see?

Channel Management

Can I switch update channels if needed?

Channel Management

How do I rollback to a previous build of Office 365 ProPlus if needed?

Managing Group Policy ADMX Files Step-by-Step Guide

How do I implement the Office 2016 ADMX and ADML files?

Manage Office 365 client updates with System Center Configuration Manager

How can I utilize System Center Configuration Manager 1602+ to manage Office 365 ProPlus updates?

Change management for Office 365 clients

What change management should I be aware of with Office 365 ProPlus?

Links for Administration Education

Links for Help Desk and End User Training

What training or resources can I provide my IT teams, help desks, and end users to prepare for Office 365 ProPlus?

Manage Page 33

Page 34: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Update Channels

Update Channels OverviewWith the 2016 release of Office 365 ProPlus, Microsoft incorporated the concept of Update Channels to allow IT admins to have more control over

new feature rollouts and business application validation. Customer IT admins should leverage all channels within the environm ent in order to create

validation, communications, and training processes. Preexisting QA or validation groups should be leveraged.

Current Channel (CC)Current Channel for Office 365 ProPlus provides monthly releases that may contain new or updated features, security updates, and non-security

updates, such as updates that provide stability or performance improvements for Office. Not every Current Channel release wil l contain all of

these features and updates. A Current Channel release is supported only until the next Current Channel release is available, meaning that no

new security updates will be provided for previous Current Channel releases.

Leveraging Current Channel is ideal for users and/or organizations that want to provide users with the newest Office features as soon as they

are available, and are not concerned about testing these features before deploying to production. Current Channel is released at quality-driven

intervals rather than date-driven. Current Channel is also ideal for users in a customer's pilot group that are evaluating new features and

functionality prior to rolling the features out to the broad user community.

First Release for Deferred Channel (FRDC)

First Release for Deferred Channel for Office 365 ProPlus provides monthly releases that may contain new or updated features, security

updates, and non-security updates, such as updates that provide stability or performance improvements for Office. It is intended to give pre -

production users and compatibility testers a chance to adequately test the upcoming Deferred Channel release to identify poss ible issues that

may need to be fixed with line-of-business applications, add-ins, and/or macros. First Release for Deferred Channel is a fully supported version

of Office 365 ProPlus. When using the Deferred Channel for production users, it is strongly recommended to have approximately 10% of the

overall end user population on First Release for Deferred Channel in order to do ample testing in preparing for the next Defe rred Channel

release.

Deferred Channel (DC)

Deferred Channel for Office 365 ProPlus provides releases every four months, that may contain new features, security updates, and non-

security updates, such as updates that provide stability or performance improvements for Office. Subsequent Deferred Channel builds, released

monthly for three months after the primary Deferred Channel release, will contain security updates only. Deferred Channel may not have all of

the new features included in the most recent Current Channel. After it has been released, no new features are added to the De ferred Channel

and it will only receive monthly security updates. A Deferred Channel release is supported for eight months, but after the ei ght-month period

no new security updates will be provided. There will always be two Deferred Channel releases available.

Deferred Channel is recommended for users and/or organizations that do not want to deploy the latest features of Office right away without

adequate testing. Deferred Channel is also ideal for users and/or organizations that have a significant number of line -of-business applications,

add-ins, and/or macros that need to be tested with each release. It is critical to note that Deferred Channel is the default update branch for

Office 365 ProPlus 2016.

Security updates will be released every month for each production Update Channel in support. The Deferred Channel builds will be released on the

second Tuesday of a month (Patch Tuesday), while the First Release for Deferred Channel and Current Channel builds are qualit y-driven rather than

date-driven, and may have slight variation to the patch Tuesday release cadence. The following sections should be reviewed in orde r for the

customer to understand each Update Channel.

Update Channel References

Overview of update channels for Office 365 ProPlus

Version and build numbers of update channel releases for Office 365 clients

Office 365 client update channel releases

What's new and improved in Office 2016 for Office 365 (update release notes)

The following links provide detailed information about the Update Channels, as well as the versions available:

Manage Page 34

Page 35: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Channel Management

Channel Management Overview

There are two common ways for organizations to apply updates to Office 365 ProPlus:

Automatically from the Internet•

Automatically from an on-premises location, such as a network share, DFS, or leveraging a software distribution tool such as System Center Configurati on Manager•

When choosing how to manage updates within the organization, the customer should look to utilize their existing software depl oyment and management tools and processes,

such as a DFS system or System Center Configuration Manager. IT admins should also leverage the Office Deployment Tool config uration settings either via the install XML or

Group Policy to configure and control the Office 365 ProPlus client update settings. Proper planning should be included for t he unlikely cases that a user requests to switch their

update channel cadence, as well as the event that a user or channel membership group needs their Office 365 ProPlus build rev erted back to a previously known good version.

Switching Channels

Switching Channels is not advised unless required as it is not a small task, and will be a100% file delta install. Simply put , if the channel you are switching to is 1.2 GB, then a

complete 1.2 GB of network bandwidth will be consumed if installing locally (700 -800 MB if using Office CDN). There is no need to uninstall and then re -install; however, the

network impact is the same of a new install. It is important to note that if the source files are hosted on premises, changin g the Update Channel Group Policy object will have no

impact on the channel switch. The Update Channel Group Policy object can only be utilized if using the Office CDN for the sou rce location.

Rollback

Run the ODT setup.exe in configure mode with a new install XML utilizing the "version: element•

Call OfficeC2Rclient.exe update engine and perform a command line rollback using the "updatetoversion" element•

There are two supported methods to perform a rollback or downgrade:

Re-Run ODT Setup.exe with new Install XML

To perform a rollback, an administrator re-run the ODT setup.exe in configure mode and push out a new install XML file that includes the build version specified in the

install XML to rollback to. When utilizing this method, the client must have access to the appropriate build source files; th erefore, the administrator should either have the

client install the specified version from the Office CDN, or utilize the UpdatePath element to point to a local source that c ontains the appropriate Office 365 ProPlus build

source files.

Identify the version of Office365 ProPlus that will be utilized (version numbers can be found here)1.

Copy ODT setup.exe and the new install XML file the appropriate source distribution location to be deployed to the client mac hines2.

Note that if users are not local administrators on the machine, a software distribution tool or script that runs with elevated privileges must be utilized

From an elevated command prompt with administrator privileges, run setup.exe /configure <configurationXMLfilename>.xml3.

Open an Office 365 ProPlus Application >> File >> Office Account >> Verify Office 365 ProPlus version

After the above the command has completed verify the version of Office 365 ProPlus is at the desired version4.

Steps for Re-Running the ODT Setup.exe with new Install XML to Rollback

It is important to note that if the customer is patching from an on premises source location, the new install XML re -run with a specified version must contain an UpdatePath

that specifies the network location of that specified build. If the specified build version cannot be found, the rollback wil l fail.

Utilize OfficeC2RClient.exe

By specifying a previous Office 365 ProPlus build version in the command line, the OfficeC2RClient.exe will roll back the Off ice 365 ProPlus client to that specified build. The

OfficeC2RClient.exe takes into account the UpdatePath location set either via the ODT or Group Policy, and will look to that location for the source files for the specified

build version in the command line. The OfficeC2RClient.exe feature can be automated by utilizing a batch file and script, or by leveraging an empty System Center

Configuration Manager packaged, in order to call the OfficeC2RClient.exe with the appropriate elements and variables specifie d.

To utilize the OfficeC2RClient.exe, please see: How to revert to an earlier version of Office 2013 or Office 2016 Click -to-Run

The below table represents additional command line switches that can be included:

Steps for Utilizing OfficeC2RClient.exe to Rollback

Identify the version of Office365 ProPlus that will be utilized (version numbers can be found here)1.

"%Program Files%\Common Files\Microsoft Shared\ClicktoRun\OfficeC2RClient.exe" /update user updatepromptuser=false

forceappshutdown=true displaylevel=true updatetoversion=16.0.xxxx.xxxx

Note: Be sure to note the forceappshutdown=true in the command line as updates cannot occur unless all off the applications are shut down. The

updatetoversion will be the specified version that the client will be rolling back to. Additionally, ensure that the updatetoversion specified correlates to the

current channel membership the client is on

Note: if users are not local administrators on the machine, a software distribution tool or script that runs with elevated privileg es must be utilized to perform the

command line

From an elevated command prompt with administrator privileges run the following command:2.

Open an Office 365 ProPlus Application >> File >> Office Account >> Verify Office 365 ProPlus version

After the above the command has completed verify the version of Office 365 ProPlus is at the desired version3.

Variable Values Description

UpdatePromptUser True, False

(Default: False)

Specifies whether or not a user will see the "Office updates are available" dialog box before applying updates

ForceAppShutdown True, False

(Default: False)

Specifies whether or not a user will be given the option to postpone the update. If set to "True", Office applications will shut

down immediately when the update process begins

DisplayLevel True, False

(Default: True)

Specifies whether or not a user will see a user interface (UI) during the updates. If set to "False" all update UI will be hidden,

including any errors that are encountered during the update scenario

UpdateToVersion 16.0.XXXX.XXXX

(Default: Install latest

released build)

Specifies the version of Office 365 ProPlus to update to, which can be used to install a newer or older version than the

current Office 365 ProPlus build installed

If a rollback is required, one of the following two solutions is recommended:

Channel Management References

Configure update settings for Office 365 ProPlus

Manage Office 365 client updates with System Center Configuration Manager

Change management for Office 365 clients

How to revert to an earlier version of Office 2013 or Office 2016 Click -to-Run

The following links provide detailed information about channel management:

Manage Page 35

Page 36: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Group Policy

Default UI Theme•

Disable Outlook Update Notifications•

Enable Retrieval of Remote Certificate Authority Information•

Hide the Office Store button in Outlook•

Hide Update Notification•

Show OneDrive Sign In•

Target Version•

Update Deadline•

Update Path•

Updates to existing IE Security settings•

Policy Settings Added with Office 2013

Age out the locally cached copies of server document versions that are more than n days old.•

Block macros from running in Office files from the Internet•

Conversion Service Options•

Disable Real Time Coauthoring for Word•

Do not promote InfoPath forms properties into Outlook properties•

Document Information Panel Beaconing UI•

Enable DLP on application boot•

Hide built-in shape style presets•

Office 365 Client Management•

Office document cache location•

Offline Mode for Document Information Panel•

PowerPoint Designer Options•

Prevent personal Microsoft accounts from using MAPI•

Prioritize BITS•

Publish to Docs.com•

Send personal information•

Set the minimum operating system for verifying agile VBA signatures•

Trust legacy VBA signatures•

Turn off audio recording for screen recording•

Update Branch•

Policy Settings Added with Office 2016

Overview of all Office 2016 Group Policy Settings

The office2016grouppolicyandoctsettings.xlsx spreadsheet will contain all of the Office 2016 Group Policy settings. It should be noted that Microsoft provides updates to the

Office 2016 Group Policy settings, and the following link should be checked periodically for new releases of the Office 2016 Administrative Template files

Resultant Set of Policy for User, Computer, and Additional Policies

PreferredPractices_O...

Preferred Practices Group Policy Settings

Manage Page 36

Page 37: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Goal

Enterprise Managed success criteria is to deploy Office 365 ProPlus in a like-for-like fashion. Users should get the application set they had before,

including Project and Visio, and their existing languages. 32-bit users should be kept on 32-bit, and 64-bit users should receive the appropriate 64-

bit version. All InfoPath-based LOB applications must continue to work. Everything must work as before, with a minimal user impact and

management overhead.

Assessment Results

20,000+ employees•

17 supported languages•

Worldwide across the Americas, EMEA and APAC regions•

1,000s of travelling users, most who are offsite for extended periods•

Sites are ranging from small offices up to a larger campus•

Size and Distribution

Windows 7 64-bit•

Small pockets of Mac users, ~500 total, managed by a third party Mac software distribution tool•

All systems have en-us language pack installed with additional languages per region or pulled by the user•

Desktops, notebooks, and shared devices for shift workers•

Remote Desktop Services and Citrix farm with 1,000s of users•

Static and dynamic Virtual Desktop Infrastructure (VDI) for a smaller user group•

Network bandwidth is sufficient for daily business•

Windows clients managed by System Center Configuration Manager•

High bandwidth deployments (like a 1 GB Office package) would require pre-caching and staged deployment•

Users do not have administrative rights on their machines•

Network is a distributed layout with a small number of high-bandwidth internet interconnection points•

IT Infrastructure

Office 2010 Volume License (MSI) 32-bit•

Groups of users using Project 2010 and Visio 2010 (MSI) 32-bit•

Finance department uses Office 2010 64-bit due to working with large data sets•

Small pockets still run Office/Visio/Project 2007 (MSI) 32-bit•

OneDrive is in the evaluation phase and should not be deployed until signed off on•

Due to legacy Line-of-Business (LOB) applications, InfoPath is required•

Application Landscape

Office 365 tenant with Azure AD Connect•

On-Premises Active Directory Federation Services with Single Sign-on (SSO)•

Exchange Online deployed in production•

Self-service installations are blocked in the portal•

Cloud Infrastructure

Assessment - Enterprise Managed

Enterprise Managed Scenario Page 37

Page 38: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Planning Overview

Creating a deployment plan is a key component when migrating to Office 365 ProPlus. Planning is based on assessment items dis covered including

constraints and how to implement Office 365 ProPlus in order meet the goals of the project.

Planning Source Locations

Office 365 ProPlus can be deployed and updated directly from the Office Content Delivery Network (CDN), System Center Configu ration Manager,

or an internal share such as leveraging UNC shares or a Distributed File System (DFS). Since Enterprise Managed has System Center Configuration

Manager implemented in their environment, they will leverage System Center Configuration Manager for the initial deployment. Since their System

Center Configuration Manager has update 1602 or greater, they will be able to manage Office updates natively in System Center Configuration

Manager, as well as ongoing Office 365 channel and build management. The following Planning is focused around deployment of items di scovered

in Assessment using System Center Configuration Manager.

Channel Membership

Enterprise Managed understands the Microsoft channel membership guidance is the following:

1% get Current Channel•

10% get First Release for Deferred Channel•

89% get Deferred Channel•

Since they already have System Center Configuration Manager Collections for their QA and Production Groups, they are going to leverage the

existing System Center Configuration Manager collections as they are very close to the Microsoft Recommendations. Using the e xisting collections,

~1,500 users will get First Release for Deferred Channel and ~18,471 users will get Deferred Channel. There may be ~25 develo p, technology owner,

or business lead roles that will self-install and self-manage from CDN with Current Channel to have the features before anyone one else. These

Current Channel users will receive features ahead of FRDC and DC so they can be adequately planned for.

For more information about channel membership and management, please see the following section: Managing Channels for Office 365 ProPlus

Base Client Packaging

The packaging and deployment team at Enterprise Managed has a rich history of deploying MSI -based Office leveraging the Office Customization

Tool. Many of the MSI-based files have a large amount of customization in how Office looks and feels. They have decided to only implement

changes that adhere to their security polices in order to minimize any customizations to look and feel. Office 365 ProPlus wi ll be initially configured

without OneDrive for Business at deployment time, and they look to add it back in later. There is also a business requirement that all shared

computer scenarios are covered properly, as they make up a sizable user population. Distribution will continue to leverage th e existing System

Center Configuration Manager infrastructure to deploy the Office 365 clients with elevated privileges that are required for O ffice installation.

Downloading the Source Files

The Office 2016 Deployment Tool will be used to download the source media required to create an install package and language pack(s) for

customization and distribution. Enterprise Managed will create a download XML file used by the Office Deployment Tool setup.exe to download the

Office 365 client source files.

For more information about the Office Deployment Tool, please see the following section: Office Deployment Tool

Configuring Deployments

Github Office 365 ProPlus - Configuration XML Editor will be used

The install XML files are relatively simple and can be made by hand following the XML properties published at TechNet. However, since Enterprise

Managed will need to manage multiple download and install XML files, they chose to use a web-based tool to help them get it right and not spend

tedious amounts of time in notepad.

Enterprise Managed will need install XML files for:

32-bit Office 365 ProPlus Deferred Channel in each region and appropriate supported regional languages•

32-bit Project Pro (VL) Deferred Channel and supported language•

32-bit Visio Pro (VL) Deferred Channel and supported language•

64-bit Deferred Channel and appropriate supported language•

32-bit Office 365 ProPlus First Release for Deferred Channel and supported language•

32-bit Project Pro (VL) First Release for Deferred Channel and supported language•

32-bit Visio Pro (VL) First Release for Deferred Channel and supported language•

Having multiple XML files is not difficult to manage as they are less than 4 kilobytes each, and they make up the System Cent er Configuration

Manager programs attributes for the package.

Shared Computing

The shared computing property value needs to be set properly for each of the shared computing scenarios discovered during Ass essment.

<Property Name="SharedComputerLicensing" Value="1" />

The following table explains how the setting will be applied to each of the Shared Computer Activation deployment scenarios t hat were identified

during Assessment:

Client Type XML Value

Standard Desktop 0

RDS 1

Non-Persistent VDI 1

Persistent VDI 0

Shared Workstation 1

Languages

Languages will be downloaded and installed using the Office Deployment Tool. System Center Configuration Manager packages wi ll be broken up

by regions, where each region will have its own set of languages that accompany the Office 365 ProPlus files. Enterprise Managed has also decided

to add each language to the self-service catalog for users to install post-Office deployment. Since the language packs are about 200 MB each, and

they do not believe that self-service of languages outside the region is an occurrence that happens very often, all languages will not be replicated to

all regions. The default language will be the one most commonly used in that region, along with instructions on how to change the default

language. For the self-service languages, such as a user in the LATAM region wanting to add German, the plan is to use the Product ID=”

LanguagePack” element in the Office Deployment Tool.

A table of each region and the corresponding languages and identifiers are listed below:

Region Languages Geographic area Language ID Map

North America English

French

Spanish

United States

Canada

Mexico

EN-US

FR-FR

ES-ES

LATAM Spanish South America ES-ES

Planning - Enterprise Managed

Enterprise Managed Scenario Page 38

Page 39: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

LATAM Spanish

Portuguese

English

South America

Brazil

ES-ES

PT-BR

EN-US

AsiaPAC Chinese (Simplified)

Chinese

Indonesian

Japanese

Korean

Malay

Thai

English

People's Republic of China

Taiwan

Indonesia

Japan

Korea

Malaysia

Thailand

ZH-CN

ZH-TW

ID-ID

JA-JP

KO-KR

MS-MY

TH-TH

EN-US

EU Czech

Danish

Dutch

Finnish

German

Greek

French

English

Czech Republic

Denmark

Netherlands

Finland

Germany

Greece

France

CS-CZ

DA-DK

NL-NL

FI-FI

DE-DE

EL-GR

FR-FR

EN-US

Remove / Restore of Applications

OneDrive for Business will be excluded from the Office 365 ProPlus suite at time of deployment, but Enterprise Managed maintains the ability to add

it back in later once it has been sign off on and approved for deployment. They could use AppLocker in GPO to lock the .EXE, but users would still

see the icon so they have decided that the better approach would be to use the ExcludeApp element in the install XML file.

Customizations (GPO)Enterprise Managed will leverage the Office 2016 Administrative Template files (ADMX/ADML) and Office Customization Tool for Group Policy. They

have also went through their existing Group Policy settings and identified any preexisting Group Policy settings that will be utilize for Office 365

ProPlus. At this time, OneDrive is a separate GPO template download but will not need to be leveraged until Enterprise Managed approves and adds

OneDrive for Business back into the Office 365 ProPlus deployment package.

A sample set of the Preferred Practices policies and GPO backups can be found here: Group Policy

Side by Side

Enterprise Managed reviewed their assessment data and decided to avoid running side by side if at all possible, especially where Project and Vis io

are concerned. The plan of record is to use the Office Scrub tool (OffScrub) to remove any previous versions of Office (2007, 2010, or 2013), but

leave the user data intact such as the dictionary, mail file, signature, etc. If the user requests Project or Visio back, the y will be able to be pre-

approved by role (such as project manager) or manager approval in order to be allowed to get Project or Visio back. It is not an automated process,

but they want to try to get it under control during this deployment. If a user runs into macro or add -in issues, then they will attempt to remediate

the issue via the helpdesk first. If escalated further, Enterprise Managed will do side by side or a Published App model for the legacy versions of

Office. However, side by side scenarios will be determined on a case by case basis.

InfoPath

Enterprise Managed will need to download the 2013 MSI version of InfoPath from the portal or Microsoft download center and distribute it as part

of the payload of office. Enterprise Managed understands that this product is the last version that will be made, and is wor king on removing

InfoPath forms from their environment. It is being deployed with Office in parallel to finding an InfoPath replacement.

Project and Visio

Enterprise Managed has a number of different versions and users of Project and Visio that they do not want to run side by side. Additionally, th ey

will be transitioning from MSI based Project and Visio software to the Click-to-Run (C2R) based versions. They will still leverage their existing

KMS/MAK servers for activation of Project and Visio, but the applications will be deployed using an install XML file and Offi ce Deployment Tool.

For more information about deploying the C2R volume licensed editions of Project and Visio, please see: Use the Office Deployment Tool to install

volume licensed editions of Visio 2016 and Project 2016

Office Scrub Tool (OffScrub)

Enterprise Managed will use OffScrub to ensure that all previous Office versions, including Project and Visio installations, are properly removed with

no unwanted artifacts or "couldn’t uninstall" errors before Office 365 ProPlus is installed.

For more information on the OffScrub tool, please see the following section: OffScrub

Architecture

Enterprise Managed determined that only the finance and accounting departments needed 64-bit Office, and that there will only be a single

deployment channel (Deferred) for 64-bit in order to reduce the amount of storage and complexity of maintaining multiple channels, builds, and

levels of architecture.

Office 2016 for Mac

Enterprise Managed will leverage their existing Mac enterprise software management tool to install and manage Office 2016 for Mac deployments

for the ~500 Mac users. An Office 365 administrator will download the Microsoft_Office_2016_Installer.pkg from the Office 365 portal and utilize

the software distribution tool to distribute and manage it. Users will be blocked from installing Office 2016 for Mac from the Office 365 software

portal.

Licensing

Enterprise Managed has already synced all of their users, and the Exchange Online users already using E3/E5 licenses. They utilize PowerShell an d on

premises AD DS attributes to determine and assign the Office 365 Licenses. The majority of users are E3, with the exception b eing Enterprise Voice

E5 users which are well defined. The remaining E1 users are temporary employees that are in a very locked down OU, and are al so very easy to

manage with AD DS attributes. It is important to note that the license are all done with custom PowerShell, and the AD DS is just a reference point

for the PowerShell licensing script.

Network

Enterprise Managed has decided to bypass proxy services for all Office 365 ProPlus URLs. As such, the ability to activate and authenticate to Of fice

365 and maintain the subscription will not be blocked. 99% of the organization users will get the Office content from System Center Configuration

Manager, but System Center Configuration Manager still needs to get the content from the Office CDN. The following are the pl anning estimates

for monthly downloads from CDN to System Center Configuration Manager:

Name Approximate size Approximate frequency

32-bit Deferred Channel ~1024 MB Monthly

64-bit Deferred Channel ~1024 MB Monthly

32-bit First Release Deferred Channel ~1024 MB Every 2 weeks (for estimation purposes)

17 Languages 17*~200 MB = ~3,400 MB Monthly

Download from Internet to System Center Configuration Manager each month: ~ 7.4 GB

Largest regional Distribution Point update each month (1 channel, 1 architecture and 8 languages): 2.6 GB

Enterprise Managed Scenario Page 39

Page 40: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Largest regional Distribution Point update each month (1 channel, 1 architecture and 8 languages): 2.6 GB

Staying Current Versus Skipping Builds and Rollbacks

Enterprise Managed is planning on staying current because they understand that it is the most network optimized solution. However, they have

created an empty package in System Center Configuration Manager that contains the necessary items to perform a rollback to a previously known

good version. An administrator will need to provide the appropriate source files and version number to rollback the clients t o.

For more information about performing a rollback, please see the following section: Channel Management

Enterprise Managed Scenario Page 40

Page 41: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Deployment Activities

Now that Enterprise Managed has been through Assessment and Planning, it is time to implement the items that they have planned for.

The First Step is to Download the Office 365 ProPlus Files for Redistribution

Download the latest version of the Office Deployment Tool (ODT) and utilize the ODT setup.exe in download mode, in combination with the

download XML files to download the latest Office 365 client source files. The downloaded source files will need to be for 32 -bit Deferred and First

Release for Deferred Channel builds, Project Pro, Visio Pro, 64-bit Deferred Channel builds, and all supported languages for the Office 365 clients.

The downloads specifically have:

English, French, Spanish, Portuguese, Chinese (Simplified), Chinese, Indonesian, Japanese, Korean, Malay, Thai, Czech, Danish , Dutch,

Finnish, German, Greek

Office 365 ProPlus - Deferred Channel - 32-bit

English

Visio Pro Volume Licensed (VL) - Deferred Channel - 32-bit

English

Project Pro Volume Licensed (VL) - Deferred Channel - 32-bit

English

Office 365 ProPlus - Deferred Channel - 64-bit

English

Office 365 ProPlus, Project Pro (VL), and Visio Pro (VL) - First Release for Deferred Channel - 32-bit

The Second Step is to Configure the Deployment Files

The next step is to edit the install XML files for the deployment. Enterprise Managed made several install XML files, that along with the Office 365

client source files previously downloaded, will be used to configure and install Office 365 ProPlus.

GitHub was leveraged to edit the XML files.

The following XML files will need to be made:

English, French, Spanish

Excluding OneDrive for Business

Office 365 ProPlus - Deferred Channel - Desktops - 32-bit – North America Region•

Spanish, Portuguese, English

Excluding OneDrive for Business

Office 365 ProPlus - Deferred Channel – Desktops - 32-bit – LATAM Region•

Chinese (Simplified), Chinese, Indonesian, Japanese, Korean, Malay, Thai, English

Excluding OneDrive for Business

Office 365 ProPlus - Deferred Channel - Desktops - 32-bit – AsiaPAC Region•

Czech, Danish, Dutch, Finnish, German, Greek, English, French

Excluding OneDrive for Business

Office 365 ProPlus - Deferred Channel – Desktops - 32-bit - EU Region•

English

Project Pro Volume Licensed (VL) - Deferred Channel - Desktops - 32-bit•

English

Visio Pro Volume Licensed (VL) - Deferred Channel - Desktops - 32-bit•

English, French, Spanish, Portuguese, Chinese (Simplified), Chinese, Indonesian, Japanese, Korean,

Malay, Thai, Czech, Danish, Dutch, Finnish, German, Greek

Individual languages - Deferred Channel - Desktops 32-bit•

Shared Computer Activation

English, French, Spanish, Portuguese, Chinese (Simplified), Chinese, Indonesian, Japanese, Korean,

Malay, Thai, Czech, Danish, Dutch, Finnish, German, Greek

Excluding OneDrive for Business

Office 365 ProPlus - Deferred Channel - VDI - 32-bit - All regions•

English

Excluding OneDrive for Business

Office 365 ProPlus - Deferred Channel - Desktops - 64-bit•

English

Excluding OneDrive for Business

Office 365 ProPlus - First Release for Deferred Channel - Desktops - 32-bit•

English

Project Pro (VL)- First Release for Deferred Channel - Desktops - 32-bit•

English

Visio Pro (VL) - First Release for Deferred Channel - Desktops - 32-bit•

The Third Step is to Configure OffScrub to Remove all Previous Versions of Office

Enterprise Managed needs to obtain two different versions of the Office Scrub tool from Premier support. The first version removes Office 2007 a nd

2010 MSI versions, while the second removes Office 2013 MSI, 2013 C2R, 2016 MSI and 2016 C2R. The application will be run sev eral times via task

sequence, and since there are multiple versions of the tool, each command has to be performed separately.

The following sequence will be run:

Office 2007 Removal•

Office 2010 Removal•

User data will be persisted and all instances of Project and Visio will be removed with the accompanying version of the Offic e suite.

The Fourth Step is to Take the Individual Packages and Integrate Them into System Center Configuration Manager for

Distribution

System Center Configuration Manager has the ability to deploy to machines with elevated privilege and logging. Although the O ffice 365 ProPlus

package does not use normal KB patch updates, Enterprise Managed will also be using System Center Configuration Manager for continual

maintenance of Office 365 ProPlus since their System Center Configuration Manager version allows for integration of Office Bu ilds into the

management tool (System Center Configuration Manager 1602 or greater).

The Fifth step is to Configure Office 2016 for Mac for Distribution

Enterprise Managed has existing enterprise Mac software distribution that is different than System Center Configuration Manager. Additionally, t he

Deployment - Enterprise Managed

Enterprise Managed Scenario Page 41

Page 42: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Enterprise Managed has existing enterprise Mac software distribution that is different than System Center Configuration Manager. Additionally, t he

Office Deployment Tool is only for the Windows versions of Office 365 ProPlus, and as a result the deployment process is slig htly different.

Enterprise Managed will utilize their existing Mac software distribution tool to manage their Mac deployments.

Enterprise Managed Scenario Page 42

Page 43: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Download XML files for Enterprise Managed

Download Overview

Enterprise Managed needs download XMLs for the following:

17 languages

Office 365 ProPlus - Deferred Channel - 32-bit•

1 language

Project Pro (VL) - Deferred Channel - 32-bit•

1 language

Visio Pro (VL) - Deferred Channel - 32-bit•

1 language

Office 365 ProPlus - Deferred Channel - 64-bit•

1 language

Office 365 ProPlus, Project Pro (VL), and Visio Pro (VL) - First Release for Deferred Channel - 32-bit•

Remember that Enterprise Managed is expecting Current Channel users to self-provision and self-manage, and will be removing the OneDrive for

Business application at time of deployment for all users.

Example Download XML Files

Below are the Enterprise Managed example download XML files for downloading Office 365 client source files.

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

<Language ID="fr-fr" />

<Language ID="es-es" />

<Language ID="pt-br" />

<Language ID="zh-cn" />

<Language ID="zh-tw" />

<Language ID="id-id" />

<Language ID="ja-jp" />

<Language ID="ko-kr" />

<Language ID="ms-my" />

<Language ID="th-th" />

<Language ID="cs-cz" />

<Language ID="da-dk" />

<Language ID="nl-nl" />

<Language ID="fi-fi" />

<Language ID="de-de" />

<Language ID="el-gr" />

</Product>

<Product ID="ProjectProXVolume">

<Language ID="en-us" />

</Product>

<Product ID=”VisioProXVolume">

<Language ID="en-us" />

</Product>

</Add>

</Configuration>

Office 365 ProPlus, Project Pro (VL), and Visio Pro (VL) - Deferred Channel - 32-bit

XML Download File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being downloaded

Channel=”Deferred” The channel build of Office 365 ProPlus being downloaded

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being downloaded

Language ID=”ii-cc” The languages being downloaded for Office 365 ProPlus

Product ID=”ProjectProXVolume” SKU of Project Pro being downloaded

Language ID=”en-us” The language being downloaded for Project Pro

Product ID=”VisioProXVolume” SKU of Visio Pro being downloaded

Language ID=”en-us” The language being downloaded for Visio Pro

<Configuration>

<Add OfficeClientEdition="64" Channel="Deferred">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Product>

</Add>

</Configuration>

Office 365 ProPlus - Deferred Channel - 64-bit

XML Download File Breakdown:

Component Explanation

OfficeClientEdition=”64” The architecture of Office being downloaded

Channel=”Deferred” The channel build of Office 365 ProPlus being downloaded

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being downloaded

Language ID=”en-us” The language being downloaded for Office 365 ProPlus

<Configuration>

<Add OfficeClientEdition="32" Channel="FirstReleaseDeferred">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Product>

<Product ID="ProjectProXVolume">

<Language ID="en-us" />

</Product>

<Product ID=”VisioProXVolume">

<Language ID="en-us" />

</Product>

</Add>

</Configuration>

Office 365 ProPlus, Project Pro (VL), and Visio Pro (VL) - First Release for Deferred Channel - 32-bit

XML Download File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being downloaded

Channel=”FirstReleaseDeferred” The channel build of Office 365 ProPlus being downloaded

Download XML Files for Enterprise Managed

Enterprise Managed Scenario Page 43

Page 44: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being downloaded

Language ID=”en-us” The language being downloaded for Office 365 ProPlus

Product ID=”ProjectProXVolume” SKU of Project Pro being downloaded

Language ID=”en-us” The language being downloaded for Project Pro

Product ID=”VisioProXVolume” SKU of Visio Pro being downloaded

Language ID=”en-us” The language being downloaded for Visio Pro

Enterprise Managed Scenario Page 44

Page 45: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Install XML files for Enterprise Managed

Install Overview

3 languages

Office 365 ProPlus - Deferred Channel - Desktops - 32-bit – North America Region•

3 languages

Office 365 ProPlus - Deferred Channel – Desktops - 32-bit – LATAM Region•

8 languages

Office 365 ProPlus - Deferred Channel - Desktops - 32-bit – AsiaPAC Region•

8 languages

Office 365 ProPlus - Deferred Channel – Desktops - 32-bit - EU Region•

1 language

Project Pro (VL) - Deferred Channel - Desktops - 32-bit•

1 language

Visio Pro (VL) - Deferred Channel - Desktops - 32-bit•

17 languages

Office 365 ProPlus - Deferred Channel - VDI/Shared Computers - 32-bit - All regions•

17 languages

Individual languages - Deferred Channel - Desktops 32-bit•

1 language

Office 365 ProPlus - Deferred Channel - Desktops - 64-bit•

1 language

Office 365 ProPlus - First Release Deferred Channel - Desktops - 32-bit•

1 language

Project Pro (VL)- First Release for Deferred Channel - Desktops - 32-bit•

1 language

Visio Pro (VL) - First Release for Deferred Channel - Desktops - 32-bit•

Enterprise Managed needs install XMLs for:

Remember that Enterprise Managed is expecting Current Channel users to self-provision and self-manage, and OneDrive for Business will be

excluded from the installation in all cases.

Example install XML files

Below are the Enterprise Managed example install XML files for configuring and installing Office 365 clients.

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

<Language ID="fr-fr" />

<Language ID="es-es" />

<ExcludeApp ID="Groove" />

</Product>

</Add>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Logging Level="Standard" />

<Display Level="None" AcceptEULA="TRUE" />

</Configuration>

Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - North America Region

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being installed

Language ID=”en-us” The default language being installed for Office 365 ProPlus

Language ID=”ii-cc” The additional languages being installed for Office 365 ProPlus

ExcludeApp ID=”Groove” Excludes OneDrive from Office 365 ProPlus installation

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="None" Hides the UI when installing Office 365 ProPlus

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="O365ProPlusRetail">

<Language ID="es-es" />

<Language ID="pt-br" />

<Language ID="en-us" />

<ExcludeApp ID="Groove" />

</Product>

</Add>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Logging Level="Standard" />

<Display Level="None" AcceptEULA="TRUE" />

</Configuration>

Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - LATAM Region

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being installed

Language ID=”es-es” The default language being installed for Office 365 ProPlus

Language ID=”ii-cc” The additional languages being installed for Office 365 ProPlus

ExcludeApp ID=”Groove” Excludes OneDrive from Office 365 ProPlus installation

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="NONE" No UI when installing Office 365 ProPlus

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="O365ProPlusRetail">

<Language ID="zh-cn" />

<Language ID="zh-tw" />

<Language ID="id-id" />

<Language ID="ja-jp" />

<Language ID="ko-kr" />

Office 365 ProPlus - Deferred Channel – Desktops - 32-bit - AsiaPAC Region

Install XML Files for Enterprise Managed

Enterprise Managed Scenario Page 45

Page 46: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

<Language ID="ko-kr" />

<Language ID="ms-my" />

<Language ID="th-th" />

<Language ID="en-us" />

<ExcludeApp ID="Groove" />

</Product>

</Add>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Logging Level="Standard" />

<Display Level="None" AcceptEULA="TRUE" />

</Configuration>

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being installed

Language ID=”zh-cn” The default language being installed for Office 365 ProPlus

Language ID=”ii-cc” The additional languages being installed for Office 365 ProPlus

ExcludeApp ID=”Groove” Excludes OneDrive from Office 365 ProPlus installation

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="NONE" No UI when installing Office 365 ProPlus

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="O365ProPlusRetail">

<Language ID="cs-cz" />

<Language ID="da-dk" />

<Language ID="nl-nl" />

<Language ID="fi-fi" />

<Language ID="de-de" />

<Language ID="el-gr" />

<Language ID="en-us" />

<Language ID="fr-fr" />

<ExcludeApp ID="Groove" />

</Product>

</Add>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Logging Level="Standard" />

<Display Level="None" AcceptEULA="TRUE" />

</Configuration>

Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - EU region

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being installed

Language ID=”cs-cz” The default language being installed for Office 365 ProPlus

Language ID=”ii-cc” The additional languages being installed for Office 365 ProPlus

ExcludeApp ID=”Groove” Excludes OneDrive from Office 365 ProPlus installation

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="NONE" No UI when installing Office 365 ProPlus

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="ProjectProXVolume">

<Language ID="en-us" />

</Product>

</Add>

<Display Level="None" AcceptEULA="TRUE" />

<Logging Level="Standard" />

</Configuration>

Project Pro (VL) - Deferred Channel - Desktops - 32-bit

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office 365 Project Pro being installed

Product ID=”ProjectProXVolume” SKU of Office 365 Project Pro being installed

Language ID=”en-us” The default language being installed for Office 365 Project Pro

Display Level="NONE" No UI when installing Office 365 Project Pro

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="VisioProXVolume">

<Language ID="en-us" />

</Product>

</Add>

<Display Level="None" AcceptEULA="TRUE" />

<Logging Level="Standard" />

</Configuration>

Visio Pro (VL) - Deferred Channel - Desktops - 32-bit

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office 365 Visio Pro being installed

Product ID=”VisioProXVolume” SKU of Office 365 Visio Pro being installed

Language ID=”en-us” The default language being installed for Office 365 Visio Pro

Display Level="NONE" No UI when installing Office 365 Visio Pro

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

<Language ID="fr-fr" />

<Language ID="es-es" />

<Language ID="pt-br" />

<Language ID="zh-cn" />

<Language ID="zh-tw" />

<Language ID="id-id" />

<Language ID="ja-jp" />

<Language ID="ko-kr" />

<Language ID="ms-my" />

<Language ID="th-th" />

Office 365 ProPlus - Deferred Channel - VDI/Shared Computer Activation - 32-bit

Enterprise Managed Scenario Page 46

Page 47: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

<Language ID="th-th" />

<Language ID="cs-cz" />

<Language ID="da-dk" />

<Language ID="nl-nl" />

<Language ID="fi-fi" />

<Language ID="de-de" />

<Language ID="el-gr" />

<ExcludeApp ID="Groove" />

</Product>

</Add>

<Property Name="SharedComputerLicensing" Value="1" />

<Logging Level="Standard" />

<Display Level="None" AcceptEULA="TRUE" />

</Configuration>

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being installed

Language ID=”en-us” The default language being installed for Office 365 ProPlus

Language ID=”ii-cc” The additional languages being installed for Office 365 ProPlus

ExcludeApp ID=”Groove” Excludes OneDrive from Office 365 ProPlus installation

SharedComputerLicensing Value=”1” Places Office 365 ProPlus into Shared Computer Activation mode

Display Level="NONE" No UI when installing Office 365 ProPlus

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="LanguagePack">

<Language ID="es-es" />

</Product>

</Add>

</Configuration>

Individual Languages Deferred Channel - Desktops - 32-bit

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office language pack being installed

Product ID=”LanguagePack” SKU of language pack being installed

Language ID=”es-es” The language being installed for Office 365 ProPlus

<Configuration>

<Add OfficeClientEdition="64" Channel="Deferred">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

<ExcludeApp ID="Groove" />

</Product>

</Add>

<Logging Level="Standard" />

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" /> <Display Level="None" AcceptEULA="TRUE" />

</Configuration>

Office 365 ProPlus - Deferred Channel - Desktops - 64-Bit

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”64” The architecture of Office being installed

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being installed

Language ID=”en-us” The default language being installed for Office 365 ProPlus

ExcludeApp ID=”Groove” Excludes OneDrive from Office 365 ProPlus installation

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur.

Display Level="NONE" No UI when installing Office 365 ProPlus

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add OfficeClientEdition="32" Channel="FirstReleaseDeferred">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

<ExcludeApp ID="Groove" />

</Product>

</Add>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Logging Level="Standard" />

<Display Level="None" AcceptEULA="TRUE" />

</Configuration>

Office 365 ProPlus - First Release for Deferred Channel - Desktops - 32-bit

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being installed

Language ID=”en-us” The default language being installed for Office 365 ProPlus

ExcludeApp ID=”Groove” Excludes OneDrive from Office 365 ProPlus installation

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="NONE" No UI when installing Office 365 ProPlus

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add OfficeClientEdition="32" Channel="FirstReleaseDeferred">

<Product ID="ProjectProXVolume">

<Language ID="en-us" />

</Product>

</Add>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Display Level="None" AcceptEULA="TRUE" />

<Logging Level="Standard" />

</Configuration>

Project Pro (VL) - First Release for Deferred Channel - Desktops - 32-bit

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Project Pro (VL) being installed

Product ID=”ProjectProXVolume” SKU of Project Pro (VL) being installed

Enterprise Managed Scenario Page 47

Page 48: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Product ID=”ProjectProXVolume” SKU of Project Pro (VL) being installed

Language ID=”en-us” The default language being installed for Project Pro (VL)

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Project to shut down. Data loss may occur

Display Level="NONE" No UI when installing Project Pro (VL)

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add OfficeClientEdition="32" Channel="FirstReleaseDeferred">

<Product ID="VisioProXVolume">

<Language ID="en-us" />

</Product>

</Add>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Display Level="None" AcceptEULA="TRUE" />

<Logging Level="Standard" />

</Configuration>

Visio Pro - First Release for Deferred Channel - Desktops - 32-bit

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Visio Pro (VL) being installed

Product ID=”VisioProXVolume” SKU of Visio Pro (VL) being installed

Language ID=”en-us” The default language being installed for Visio Pro (VL)

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Visio to shut down. Data loss may occur

Display Level="NONE" No UI when installing Visio Pro (VL)

AcceptEULA="TRUE" Accept the License Agreement

Enterprise Managed Scenario Page 48

Page 49: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Example Uninstall XML Files for Enterprise Managed

Below are the Enterprise Managed example uninstall XML files for removing Office 365 clients.

<Configuration>

<Remove>

<Product ID="O365ProPlusRetail" >

<Language ID="en-us" />

<Language ID="fr-fr" />

<Language ID="es-es" />

</Product>

</Remove>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Display Level="None" />

</Configuration>

Office 365 ProPlus - North America Region

XML Configuration File Breakdown:

Component Explanation

Product ID=”Office365ProPlusRetail” SKU of Office 365 ProPlus being removed

Language ID=”ii-cc” The languages being removed from Office 365 ProPlus

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="NONE" No UI when removing Office 365 ProPlus

<Configuration>

<Remove>

<Product ID="O365ProPlusRetail" >

<Language ID="es-es" />

<Language ID="pt-br" />

</Product>

</Remove>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Display Level="None" />

</Configuration>

Office 365 ProPlus – LATAM Region

XML Configuration File Breakdown:

Component Explanation

Product ID=”Office365ProPlusRetail” SKU of Office 365 ProPlus being removed

Language ID=”ii-cc” The languages being removed from Office 365 ProPlus

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="NONE" No UI when removing Office 365 ProPlus

<Configuration>

<Remove>

<Product ID="O365ProPlusRetail" >

<Language ID="zh-cn" />

<Language ID="zh-tw" />

<Language ID="id-id" />

<Language ID="ja-jp" />

<Language ID="ko-kr" />

<Language ID="ms-my" />

<Language ID="th-th" />

</Product>

</Remove>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Display Level="None" />

</Configuration>

Office 365 ProPlus – AsiaPac Region

XML Configuration File Breakdown:

Component Explanation

Product ID=”Office365ProPlusRetail” SKU of Office 365 ProPlus being removed

Language ID=”ii-cc” The languages being removed from Office 365 ProPlus

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="NONE" No UI when removing Office 365 ProPlus

<Configuration>

<Remove>

<Product ID="O365ProPlusRetail" >

<Language ID="cs-cz" />

<Language ID="da-dk" />

<Language ID="nl-nl" />

<Language ID="fi-fi" />

<Language ID="de-de" />

<Language ID="el-gr" />

</Product>

</Remove>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Display Level="None" />

</Configuration>

Office 365 ProPlus – EU Region

XML Configuration File Breakdown:

Component Explanation

Product ID=”Office365ProPlusRetail” SKU of Office 365 ProPlus being removed

Language ID=”ii-cc” The languages being removed from Office 365 ProPlus

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="NONE" No UI when removing Office 365 ProPlus

<Configuration>

<Remove>

<Product ID="ProjectProXVolume" >

<Language ID="en-es" />

</Product>

</Remove>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Display Level="None" />

</Configuration>

Project Pro (VL)

Uninstall XML Files for Enterprise Managed

Enterprise Managed Scenario Page 49

Page 50: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

XML Configuration File Breakdown:

Component Explanation

Product ID=” ProjectProXVolume” SKU of Project Pro (VL) being removed

Language ID=”en-es” The language being removed from Project Pro (VL)

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="NONE" No UI when removing Project Pro (VL)

<Configuration>

<Remove>

<Product ID="VisioProXVolume" >

<Language ID="en-es" />

</Product>

</Remove>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Display Level="None" />

</Configuration>

Visio Pro (VL)

XML Configuration File Breakdown:

Component Explanation

Product ID=” VisioProXVolume” SKU of Visio Pro (VL) being removed

Language ID=”en-es” The language being removed from Visio Pro (VL)

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="NONE" No UI when removing Visio Pro (VL)

Enterprise Managed Scenario Page 50

Page 51: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

System Center Configuration Manager Deployment Overview

Enterprise Managed has decided to leverage their existing enterprise software deployment and management tool, System Center Configuration

Manager, to deploy the Office 365 client packages. You will notice that the packages are set to install silently because task sequences are used to

configure and install a stack of products.

Remove all Office 2007 components if found

Remove all Office 2010 components if found

Leave user data in place

Run OffScrub•

Install InfoPath 2013 MSI•

Install Office 365 ProPlus with proper channel, architecture, and languages from System Center Configuration Manager•

The task sequence does the following:

OffScrub

The following table includes the OffScrub Command lines that Enterprise Managed used for the System Center Configuration Manager task

sequence to remove previous versions of Office:

Context for program Command line

Office 2007 Removal Command prompt cscript Offscrub2007.vbs clientall /bypass 1 /log c:\temp /nocancel /q

Office 2010 Removal Command prompt cscript Offscrub2010.vbs clientall /bypass 1 /log c:\temp /nocancel /q

Office 2013 MSI Removal Command prompt cscript OffScrub_O15msi clientall /bypass 1 /log c:\temp /nocancel /q

Office Source Location

The following is an example of the Office source location for Enterprise Managed 32-bit Deferred Channel. The ODT setup.exe sits next to the

downloaded Office 365 client source files and install XML files. This allows for the file paths to always be relative, theref ore a source path is not

needed for the install XML. This is good for System Center Configuration Manager deployments because you don’t need to worry about the names

of the distribution points of local CCMCache, System Center Configuration Manager will handle everything.

The above would be an example of an Office 365 ProPlus System Center Configuration Manager 32 -bit Deferred Channel package: the ODT

setup.exe, all of the install XML files, and all of the Office 365 client bits

Examples of the programs for the package would be as follows:

Context for program Command line

Deferred Channel 32-bit with Shared Computing Activation Setup.exe /configure Install_ProPlus_DC_VDI.xml

Deferred Channel 32-bit for Desktop – North America Setup.exe /configure Install_ProPlus_DC_NA.xml

Deferred Channel 32-bit for Desktop - LATAM Setup.exe /configure Install_ProPlus_DC_LATAM.xml

Deferred Channel 32-bit Project Pro (VL) Setup.exe /configure Install_Project_DC.xml

Individual languages are being added as software programs and placed in the software catalog for users that want additional l anguages to self-

provision. The install XMLs leverage the Product ID=”LanguagePack” element.

Context Command line

Greek Setup.exe /configure Install_Greek_LAP_DC.xml

Spanish Setup.exe /configure Install_Spanish_LAP_DC.xml

Malay Setup.exe /configure Install_Malay_LAP_DC.xml

System Center Configuration Manager Step by Step Configuration

Deploy Office 365 ProPlus by using System Center Configuration Manager

Manage updates with System Center Configuration Manager

The following links should be referenced in order to configure System Center Configuration Manager to deploy and managed Offi ce 365 ProPlus:

System Center Configuration Manager Configuration

Enterprise Managed Scenario Page 51

Page 52: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Initial Deployment

This section explains how Enterprise Managed designed and approached deploying Office 2016 for Mac. They will utilize their existing Mac software

distribution tool to manage the Office 2016 for Mac deployment. Users will be blocked from downloading Office 2016 for Mac fr om the Office 365

portal.

Mac Software Distribution Tool

Since Office 2016 for Mac uses the Apple Installer technology for installation, Enterprise Managed can utilize their existing Mac software distribution

tool such as Apple Remote Desktop or Casper JAMF Software Suite. Administrators control the software deployment and have cent ralized control

over the deployment to monitor the Mac clients to see when they have received the software. In order for Enterprise Managed to deploy via their

Mac software distribution tool, an Office 365 administrator should download the MPKG files from the Office 365 portal and create the deployment

package. It should also be noted that not all third-party Mac software distribution solutions support automatic account configuration.

For more information on deployment options for Office 2016 for Mac, please see: Office 2016 for Mac Clients

Deploy Preferences

For guidance on deploying preferences to end users, please see: Office 2016 for Mac Clients

Note that deployment preferences may overwrite the existing user preference settings. To remove Office for Mac 2011, Troubleshoot Office 2011

for Mac issues by completely uninstalling before you reinstall

Deploy LanguagesAll of the supported languages in Office 2016 for Mac are now included and installed as part of the installer package .pkg file. Since there are no

longer separate installer package files for each language, admins can no longer choose which language to deploy to users and the language will be

chosen during the installation based on the System Preferences settings. If none of the language settings are supported by Of fice, Office will install

in English.

Office 2016 for Mac Client Install

Enterprise Managed Scenario Page 52

Page 53: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Ongoing Management and Future Change Management Scenarios

Enterprise Managed wants to apply GPO management to their Office 365 ProPlus systems, as well as test specific scenarios they are likely to

encounter.

The items are:

Configuration of infrastructure•

Licensing users•

Removal of languages•

Addition of languages•

Adding OneDrive for Business back•

Rolling back builds and switching channels to maintain deployment rings•

Group Policy for desktops•

Additional Group Policy objects for VDI•

Group Policy for OneDrive for Business•

Configure Infrastructure and Maintaining Network, Ports, and Protocols

Office 365 is a cloud service and as such will require Internet access. If you manage by URL, then updates are less frequent and typically only needed

when new products or features are released. However, if managed by IP address range, then changes occur more often. The follo wing page should

be reference and RSS feed subscribed to.

Office 365 URLs and IP address ranges

Licensing Users

Assign licenses to user accounts with Office 365 PowerShell

Addition of Languages

The ProductID="LanguagePack" element allows you to add languages to an existing Office 365 client install without needing to know its previous

existing install configuration settings

<Configuration>

<Add OfficeClientEdition="32">

<Product ID="LanguagePack">

<Language ID="es-es" />

</Product>

</Add>

</Configuration>

Removal of Languages

The remove element allows you to remove a language from an existing Office 365 client install.

<Configuration>

<Remove>

<Product ID="O365ProPlusRetail">

<Language ID="es-es" />

</Product>

</Remove>

</Configuration>

OR

<Configuration>

<Remove>

<Product ID="LanguagePack">

<Language ID="es-es" />

</Product>

</Add>

</Configuration>

Adding OneDrive Back for Users

By removing the application exclude statement from the install XML file, it will include the application when re -run.

<Configuration>

<Add OfficeClientEdition="32" Channel="Current" OfficeMgmtCOM="TRUE">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Product>

</Add>

</Configuration>

Rolling Back a Build

Enterprise Managed can leverage their existing software distribution tool, System Center Configuration Manager, to perform a client rollback. Fo r

step by step guidance on performing a rollback using the OfficeC2RClient.exe update engine, please see the following section: Channel

Management

Switching Channels

In the event that an end user needs alter their channel membership, the following guidance should be used to switch channels: Channel

Management

Configure Policy

It is highly recommended to consistently check for new GPO Templates. As new Office features are rolled out, GPOs may be upda ted and new Office

management GPOs may be released.

Group Policy Reference for Enterprise Managed

EnterrpiseManaged ...

Additional Group Policy for VDI

Additional GPO should be considered around Outlook and Cached Mode for VDI.Enterprise Managed has decided to set the value to 3 days.

Group Policy for OneDrive

Administrative settings for the OneDrive for Business Next Generation Sync Client

Office 2016 Administrative Template files (ADMX/ADML) and Office Customization Tool

Enterprise Managed Mac Client Updates

Similar to Office 365 ProPlus, Microsoft provides new builds that contains application updates meaning that individual securi ty or feature updates

cannot be downloaded or installed. However, with a locally managed deployment, admins can selectively decide which applicatio ns to apply

updates to. Office 2016 for Mac has a program named Microsoft AutoUpdate to automatically check for updates daily. However, t he Microsoft

AutoUpdate can be configured to daily, weekly, monthly, or manually depending on preferences.

Due to Enterprise Managed having an existing Mac software distribution tool, they should configure Microsoft AutoUpdate to manually download

Management - Enterprise Managed

Enterprise Managed Scenario Page 53

Page 54: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Due to Enterprise Managed having an existing Mac software distribution tool, they should configure Microsoft AutoUpdate to manually download

the updates to the local network. They can then use the existing software distribution tool to deploy the updates to the Mac end users.

Enterprise Managed Scenario Page 54

Page 55: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Goal

Locally Managed success criteria is to deploy Office 365 ProPlus in a like-for-like fashion, replacing the previous version of Office. Users should get

the application set they had before, including Visio and Project, and the existing languages. InfoPath -based LOB applications must continue to work,

with minimal user impact and management overhead. Locally Managed only supports 32 -bit Office so all users will remain on 32-bit Office.

Assessment Results

5000 employees•

3 supported languages•

Canada, USA, and Germany•

< 100 travelling users, some who are offsite for extended periods•

Sites are a main office in each country, limited small offices throughout each country•

Size and Distribution

Windows 7 64-bit•

Small group of Mac users, ~25 who users have local administrator rights•

Mac clients are not managed by client management software•

All systems have en-us language pack installed with additional languages in CanAm region or pulled by the user•

Remote Desktop Services and Citrix farm with < 500 users•

Network bandwidth is sufficient for daily business•

Users do not have administrative rights on their machines•

Network is a distributed layout with a small number of high-bandwidth internet interconnection points•

IT Infrastructure

Office 2010 Volume License (MSI) 32-bit•

Groups of users using Project 2010 and Visio 2010 32-bit•

All applications other than Access being deployed•

Due to legacy Line-of-Business (LOB) applications, InfoPath is required•

Application Landscape

Office 365 tenant with Azure AD Connect•

On-Premises Active Directory Federation Services with Single Sign-on (SSO)•

Exchange Online deployed in production•

Self-service including installations are not blocked in the portal•

Cloud Infrastructure

Assessment - Locally Managed

Locally Managed Scenario Page 55

Page 56: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Planning Overview

Creating a deployment plan is a key component when migrating to Office 365 ProPlus. Planning is based on assessment items dis covered including

constraints and how to implement Office 365 ProPlus in order meet the goals of the project.

Planning Source Locations

Office 365 ProPlus can be deployed and updated directly from the Office Content Delivery Network (CDN), System Center Configu ration Manager,

or an internal share such as leveraging a network share or Distributed File System (DFS). Since Locally Managed has a DFS imp lementation, Locally

Managed will leverage it to deploy the initial Office deployment, as well as ongoing build management. The following Planning is focused around

deployment of items via DFS discovered in Assessment.

Channel Membership

Locally Managed understands the Microsoft channel membership guidance is the following:

1% get Current Channel•

10% get First Release for Deferred Channel•

89% get Deferred Channel•

They figure there may be ~20 developer, technology owner, or business lead roles that will self -install and self-manage from CDN with Current

Channel to have the features before anyone one else. These Current Channel users will receive features ahead of FRDC and DC s o they can be

adequately planned for. The existing QA collection of ~500 users will also be utilized to receive First Release for Deferred Channel. These FRDC users

should represent all business groups so each build has been validated throughout the organization.

For more information about channel membership and management, please see the following section: Managing Channels for Office 365 ProPlus

Base Client Packaging

The packaging and deployment team at Locally Managed has a moderate history of deploying MSI -based (MSI) Office leveraging the Office

Customization Tool with Office 2010. Many of the MSI-based files have a large amount of customization in how Office looks and feels. They have

decided to only implement changes that adhere to their security polices to minimize any customizations to look and feel. Offi ce 365 ProPlus will be

configured without Access at deployment time, as it is not required by the organization. There is also a business requirement for the shared

computer scenarios to be covered properly. Office 365 ProPlus distribution will leverage the DFS infrastructure and batch fil es to deploy the Office

365 client with elevated privileges required for installation.

Downloading the Source Files

The Office 2016 Deployment Tool will be used to download the source media required to create an install package and language pack(s) for

customization and distribution. Locally Managed will create a download XML file used by the Office Deployment Tool setup.exe to download the

Office 365 client source files.

For more information about the Office Deployment Tool, please see the following section: Office Deployment Tool

Configuring Deployments

GitHub Office 365 ProPlus - Configuration XML Editor will be used

The install XML files are relatively simple and can be made by hand following the XML properties published at TechNet. However, since Locally

Managed will need to manage multiple download and install XML files, they chose to use a web -based tool to help them get it right and not spend

tedious amounts of time in notepad.

Locally Managed will need install XML files for:

32-bit Office 365 ProPlus Deferred Channel in both regions and appropriate supported regional languages•

32-bit Project Pro Deferred Channel and supported language•

32-bit Visio Pro Deferred Channel and supported language•

32-bit Office 365 ProPlus First Release for Deferred Channel and supported langage•

32-bit Project Pro First Release for Deferred Channel and supported language•

32-bit Visio Pro First Release for Deferred Channel and supported language•

Having multiple install XML files is not difficult to manage as they are less than 4 kilobytes each.

Shared Computing

The shared computing property value needs to be set properly for each of the shared computing scenarios discovered during ass essment.

<Property Name="SharedComputerLicensing" Value="1" />

The following table explains how the setting will be applied to each of the Shared Computer Activation deployment scenarios i dentified during

Assessment:

Client Type XML Value

Standard Desktop 0

RDS 1

Random Access Workstation 1

Languages

Languages will be downloaded and installed using the Office Deployment Tool. Locally Managed has also decided to add a self-service installation

for all three supported languages since they will not be installing the same languages in the CanAm and Germany regions. For the self-service

languages, such as a user in the CanAm region wanting to add German, the plan is to use the Product ID=”LanguagePack” element in the Office

Deployment Tool.

The default language will be the one most commonly used in that region. A table of each region and the corresponding language s and identifiers

are listed below:

Region Languages Geographic area Language ID Map

CanAm English

French

United States

Canada

EN-US

FR-FR

Germany German Germany DE-DE

Planning - Locally Managed

Locally Managed Scenario Page 56

Page 57: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Germany German Germany DE-DE

Remove / Restore of Applications

Access will be excluded from the Office 365 ProPlus suite at time of deployment, but Locally Managed maintains the ability to add it back in later

should business requirements change. They could use AppLocker in GPO to lock the .EXE, but users would still see the icon so they have decided

that the better approach would be to use the ExcludeApp element in the install XML file.

Customizations (GPO)

Locally Managed will leverage the Office 2016 Administrative Template files (ADMX/ADML) and Office Customization Tool for Group Policy. They

have also went through their existing Group Policy settings and identified any preexisting Group Policy settings that will be utilize for Office 365

ProPlus. At this time, OneDrive is a separate GPO template download and should be reviewed in order to determine if any of the Group Policy

settings are required.

A sample set of the Preferred Practices policies and GPO backups can be found here: Group Policy

Side by Side

Locally Managed reviewed their assessment data and decided to avoid running side by side if at all possible. The plan of record is to use the Office

Scrub tool (OffScrub) to remove the previous version of Office 2010 (MSI), but leave the user data intact (dictionary, mail f ile, signature, etc.). If the

user requests Project or Visio back, they will be able to be pre-approved by role (such as project manager) or managed approval in order to be

licensed and allowed to get the Office 365 Project or Visio Pro version installed. If a user runs into macro or add -in issues, then they will attempt to

remediate the issue via the IT helpdesk first. If escalated further, Locally Managed will do side by side for the legacy version of Office. This will be

determined on a case by case basis. However, side by side scenarios will be determined on a case by case basis and will be av oided if possible.

InfoPath

Locally Managed will need to download the 2013 MSI version of InfoPath from the portal or Microsoft download center and distribute it as part of

the payload of office. Locally Managed understands that this product is the last version that will be made, and is working o n removing InfoPath

forms from their environment. It is being deployed with Office in parallel to finding an InfoPath replacement.

Project and Visio

Locally Managed has a moderate number of Project and Visio 2010 installs they do not want to run side by side, and will be transitioning from

machine installs of the software to adding the licenses to their Office 365 tenant to cover Click-to-Run versions of Project and Visio. This way the

license will follow the user and always be the current version of Office, Project, and Visio, which will require less adminis trative effort and

management from the IT team.

Office Scrub Tool (OffScrub)

Locally Managed will use OffScrub to ensure that all previous installations of Office 2010 (MSI), including Project and Visio 2010 installations, are

properly removed with no unwanted artifacts or "couldn’t uninstall" errors before Office 365 ProPlus is installed.

For more information on the OffScrub tool, please see the following section: OffScrub

Architecture

Locally Managed determined that only the 32-bit version of the Office 365 clients will be deployed. Locally Managed has no uses cases for 64-bit

applications.

Office 2016 for Mac

Since Locally Managed has a small population of ~25 existing Office for Mac users, they will leverage a network share for Office 2016 for Mac

deployments. An Office 365 administrator will download the Microsoft_Office_2016_Installer.pkg from the Office 365 portal, and users will install

Office 2016 for Mac from the network location. Users will be prompted for their machine administrator credentials in order to install Office 2016 for

Mac.

Licensing

Locally Managed has already synced all of their users, and the Exchange Online users already using E3 licenses. Locally Managed uses PowerSh ell

and on premises AD DS attributes to determine and assign the Office 365 Licenses. Nearly all users are assigned the E3 licen se SKU. It is important

to note that the licenses are all done with custom PowerShell, and the AD DS is just a reference point for the PowerShell lic ensing script.

Network

Locally Managed has decided to bypass proxy services for all Office 365 ProPlus URLs. As such, the ability to activate or authenticate to Off ice 365

and maintain the subscription will not be blocked. Since they will be relying on users to update from the CDN, all Office 365 ProPlus URLs must be

open.

Name Approximate size Approximate frequency

32-bit Deferred Channel ~1024 MB Monthly

3 Languages 3 *~200MB = ~600 MB Monthly

32-bit First Release Deferred Channel ~1024 MB Every 2 weeks (for estimation purposes)

1 Language ~200 MB Every 2 weeks (for estimation purposes)

Deferred Channel download from Office CDN to DFS each month: ~ 1.6 GB

First Release for Deferred Channel download from Office CDN to DFS each month: ~2.4 GB

Total download from Office CDN to DFS each month: ~4 GB

Staying Current Versus Skipping Builds and Rollbacks

Locally Managed is planning on staying current because they understand that it is the most network optimized solution. However, they have cre ated

a script stored in the DFS that contains the necessary items to perform a rollback to a previously known good version. An adm inistrator would need

to download the appropriate source files to rollback to, and insert the appropriate version number in the script to rollback to.

For more information about performing a rollback, please see the following section: Channel Management

Locally Managed Scenario Page 57

Page 58: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Deployment Activities

Now that Locally Managed has been through Assessment and Planning, it is time to implement the items that they have planned for.

The First Step is to Create a Folder Structure within the Distributed File System

Utilizing the existing Distributed File System (DFS) and scripts allows for users to install from a network share without req uiring administrative

privileges on the local machines. Locally Managed should have a similar folder structure within the DFS to host Office 365 client related content, and

users must have read permissions to the share.

Folder Path Purpose

\\Server\Share\O365 This is the parent folder that will be used for storing all Office 365 ProPlus related items

\\Server\Share\O365\FRDC Use this folder to store the most current Office 365 ProPlus First Release for Deferred Channel build that pre -

production users will receive

\\Server\Share\O365\DC Use this folder to store the most current Office 365 ProPlus Deferred Channel build that production users will

receive. Production channel should be Deferred Channel

\\Server\Share\O365\Archive Use this folder to host N-1 previously known good builds in case a rollback or downgrade is needed

\\Server\Share\O365\OffScrub Use this folder to host the OffScrub scripts to remove previous versions of Office

The below screenshot is an example of the folder structure Locally Managed should create:

The Second Step is to Download the Office 365 ProPlus Files for Redistribution

After downloading the latest version of the Office Deployment Tool (ODT) and placing it in the \\Server\Share\O365 network location, create and

configure the download XML file to download the Office 365 ProPlus source files. Utilize the ODT setup.exe in download mode a nd the download

XML to retrieve the latest Office 365 ProPlus source files. The downloaded source files will need to be for 32 -bit Deferred and First Release for

Deferred Channel builds, Project Pro, Visio Pro, and all supported languages for the Office 365 clients.

The downloads specifically have:

English, French, German

Office 365 ProPlus - Deferred Channel - 32-bit

English

Visio Pro - Deferred Channel - 32-bit

English

Project Pro - Deferred Channel - 32-bit

English

Office 365 ProPlus, Project Pro, and Visio Pro - First Release for Deferred Channel - 32-bit

The Deferred Channel download XML should be placed in the corresponding \\Server\Share\O365\DC network location The First Release for

Deferred Channel download XML should be placed in the corresponding \\Server\Share\O365\FRDC. Both the Deferred Channel and First Release

for Deferred Channel download XMLs should download the source bits into their corresponding channel folders in the DFS create d in step 1 (I.E. –

DC bits should be in DC subfolder, FRDC bits in FRDC subfolder).

The Third Step is to Configure the Deployment Files

The next step is to edit the install XML files for the deployment. Locally Managed made multiple XML files, that along with the Office 365 ProPlus

files previously downloaded, will be used to configure and install Office 365 ProPlus.

GitHub was leveraged to edit the XML files.

The following XML files will need to be made:

English, French

Excluding Access

Office 365 ProPlus - Deferred Channel - Desktops - 32-bit – CanAm Region•

German

Excluding Access

Office 365 ProPlus - Deferred Channel – Desktops - 32-bit - Germany•

Shared Activation

English, French, German

Excluding Access

Office 365 ProPlus - Deferred Channel - VDI - 32-bit - All regions•

English

Project Pro - Deferred Channel - Desktops - 32-bit•

English

Visio Pro - Deferred Channel - Desktops - 32-bit •

English, French, German

Individual languages - Deferred Channel - Desktops 32-bit •

English

Excluding Access

Office 365 ProPlus, Project Pro, and Visio Pro - First Release Deferred Channel - Desktops - 32-bit•

The Deferred Channel install XML should be placed in the corresponding \\Server\Share\O365\DC network location. The First Release for Deferred

Channel install XML should be placed in the corresponding\\Server\Share\O365\FRDC.

The Fourth Step Configure the Office Scrub Tool to Remove all Previous Versions of Office

Locally Managed has only one preexisting version of Office in the environment, Office 2010 (MSI), so only the version of the OffScrub tool th at

removes Office 2007 and 2010 MSI versions needs to be obtained from Premier support. The OffScrub script should be stored in the folder structure

created in step 1 under \\Server\Share\O365\OffScrub. The application will be run via a batch file or script so it will be automated and the user

will not need elevated privilege.

The following sequence will be run:

Office 2010 (MSI) Full Suite Removal

Deployment - Locally Managed

Locally Managed Scenario Page 58

Page 59: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Office 2010 (MSI) Full Suite Removal•

User data will be persisted and all instances of Project and Visio will be removed with the accompanying version of the Offic e suite.

The Fifth Step is to Create the Batch Install Wrapper to Automate the OffScrub and Office 365 ProPlus Install or Removal

Locally Managed should utilize batch files or scripts stored in the folder structure previously created in step 1. The script or batch file w ill run with

elevated privileges so all users need is read permissions to the share hosting the batch file or script, OffScrub script, ODT setup.exe, install XML files,

and Office 365 source files.

A sample Office 365 ProPlus batch file task order would be:

Remove all Office 2010 (MSI) components

Remove Office 2013 Core Suite components (leave Project and Visio 2013)

Leave user data in place

Run OffScrub•

Install InfoPath 2013 (MSI)•

Install Office 365 ProPlus with proper channel, architecture, and languages•

The Project and Visio batch file task orders should be:

Install Project or Visio with proper channel, architecture, and languages•

The following batch files or scripts should be created:

OffScrub + Office 365 ProPlus Deferred Channel install•

Project Pro Deferred Channel install•

Visio Pro Deferred Channel install•

OffScrub + Office 365 ProPlus First Release for Deferred Channel install•

Project Pro First Release for Deferred Channel install•

Visio Pro First Release for Deferred Channel install•

Office 365 ProPlus uninstall•

Individual language installations•

Locally Managed will need to advertise separate batch files for Deferred Chanel and First Release for Deferred Channel users. Users should on ly be

able to perform the script that automates the Office 365 ProPlus configuration that is designed for them, meaning no pre -production or FRDC users

should see the DC or production script. Therefore, the DC automation scripts should be stored in its respective folder locati on \\Server\Share

\O365\DC, and the FRDC automation scripts should be stored in its respective folder location \\Server\Share\O365\FRDC. Locally Managed users

should either be instructed to go to the designated folder and run the appropriate Office script based on their end user role (production or pre-

production), or Group Policy should be utilized to copy down the appropriate batch file on the user’s desktop to run.

Add the below line to a to a batch file (I.E. - Office365_DC_Configuration.cmd). This batch line will dynamically determine the script directory and

find setup.exe and install XML. Note that this does not check if the script is performed with elevated rights or not, so Locally Managed will need to

ensure elevated rights are applied. A similar batch line can be leverage for OffScrub as well.

"%~dp0Setup.exe" /configure "%~dp0install.xml"

An additional batch file (I.E. - Office365_Removal.cmd) to uninstall can be created and leverage the following batch line:

"%~dp0Setup.exe" /configure "%~dp0removal.xml"

The Sixth Step is to Configure Office 2016 for Mac for Distribution

Locally Managed has as small Mac environment and does not have Mac software distribution tools, but still wants to have control over their Ma c

clients. Therefore, it is recommended for them to utilize a network share deployment in order to still have some control over the environment.

Locally Managed Scenario Page 59

Page 60: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Download XML files for Locally Managed

Download Overview

3 languages

Office 365 ProPlus - Deferred Channel - 32-Bit•

1 language

Project Pro – Deferred Channel – 32-bit•

1 language

Visio Pro – Deferred Channel – 32-bit•

1 language

Office 365 ProPlus, Project Pro, and Visio Pro - First Release for Deferred Channel - 32-bit•

Locally Managed needs download XMLs for the following:

Remember that Locally Managed is expecting Current Channel users to self-provision and self-manage, and will be removing the Access application

at time of deployment for all users.

Example Download XML Files

Below are the Locally Managed example download XML files to download Office 365 client source files.

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

<Language ID="fr-fr" />

<Language ID="de-de" />

</Product>

<Product ID="ProjectProRetail">

<Language ID="en-us" />

</Product>

<Product ID=”VisioProRetail">

<Language ID="en-us" />

</Product>

</Add>

</Configuration>

Office 365 ProPlus, Project Pro, and Visio Pro - Deferred Channel - 32-bit

XML Download File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being downloaded

Channel=”Deferred” The channel build of Office 365 ProPlus being downloaded

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being downloaded

Language ID=”ii-cc” The languages being downloaded for Office 365 ProPlus

Product ID=”ProjectProRetail” SKU of Project Pro being downloaded

Language ID=”en-us” The language being downloaded for Project Pro

Product ID=”VisioProRetail” SKU of Visio Pro being downloaded

Language ID=”en-us” The language being downloaded for Visio Pro

<Configuration>

<Add OfficeClientEdition="32" Channel="FirstReleaseDeferred">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Product>

<Product ID="ProjectProRetail">

<Language ID="en-us" />

</Product>

<Product ID=”VisioProRetail">

<Language ID="en-us" />

</Add>

</Product>

</Configuration>

Office 365 ProPlus, Project Pro, and Visio Pro - First Release Deferred Channel - 32-bit

XML Download File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being downloaded

Channel=”First Release Deferred” The channel build of Office 365 ProPlus being downloaded

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being downloaded

Language ID=”en-us” The language being downloaded for Office 365 ProPlus

Product ID=”ProjectProRetail” SKU of Project Pro being downloaded

Language ID=”en-us” The language being downloaded for Project Pro

Product ID=”VisioProRetail” SKU of Visio Pro being downloaded

Language ID=”en-us” The language being downloaded for Visio Pro

Download XML Files for Locally Managed

Locally Managed Scenario Page 60

Page 61: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Install XML files for Locally Managed

Install Overview

2 languages

Office 365 ProPlus - Deferred Channel - Desktops - 32-bit – CanAm Region•

1 language

Office 365 ProPlus - Deferred Channel – Desktops - 32-bit – Germany•

1 language

Project Pro - Deferred Channel - Desktops - 32-bit•

1 language

Visio Pro - Deferred Channel - Desktops - 32-bit•

17 languages

Office 365 ProPlus - Deferred Channel - VDI/Shared Computers - 32-bit - All regions•

3 languages

Individual languages - Deferred Channel - Desktops 32-bit•

1 language

Office 365 ProPlus - First Release Deferred Channel - Desktops - 32-bit•

1 language

Project Pro (VL)- First Release for Deferred Channel - Desktops - 32-bit•

1 language

Visio Pro (VL) - First Release for Deferred Channel - Desktops - 32-bit•

Locally Managed needs install XMLs for:

Remember that Locally Managed is expecting Current Channel users to self-provision and self-manage, and Access will be excluded from the

installation in all cases.

Example Install XML Files

Below are the Locally Managed example install XML files for configuring and installing Office 365 clients.

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

<Language ID="fr-fr" />

<ExcludeApp ID="Access" />

</Product>

</Add>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Logging Level="Standard" />

<Display Level="None" AcceptEULA="TRUE" />

</Configuration>

Office 365 ProPlus - Deferred Channel - Desktops - 32-bit – CanAm Region

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being installed

Language ID=”en-us” The default language being installed for Office 365 ProPlus

Language ID=”fr-fr” The additional language being installed for Office 365 ProPlus

ExcludeApp ID=”Access” Excludes Access from Office 365 ProPlus installation

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="None" Hides the UI when installing Office 365 ProPlus

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="O365ProPlusRetail">

<Language ID="de-de" />

<ExcludeApp ID="Access" />

</Product>

</Add>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Logging Level="Standard" />

<Display Level="None" AcceptEULA="TRUE" />

</Configuration>

Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - Germany

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being installed

Language ID=”de-de” The default language being installed for Office 365 ProPlus

ExcludeApp ID=”Access” Excludes Access from Office 365 ProPlus installation

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="NONE" No UI when installing Office 365 ProPlus

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="ProjectProRetail">

<Language ID="en-us" />

</Product>

</Add>

<Display Level="None" AcceptEULA="TRUE" />

<Logging Level="Standard" />

</Configuration>

Project Pro - Deferred Channel – Desktops - 32-bit

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office 365 Project Pro being installed

Product ID=”ProjectProRetail” SKU of Office 365 Project Pro being installed

Language ID=”en-us” The default language being installed for Office 365 Project Pro

Display Level="NONE" No UI when installing Office 365 Project Pro

AcceptEULA="TRUE" Accept the License Agreement

Install XML Files for Locally Managed

Locally Managed Scenario Page 61

Page 62: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="VisioProRetail">

<Language ID="en-us" />

</Product>

</Add>

<Display Level="None" AcceptEULA="TRUE" />

<Logging Level="Standard" />

</Configuration>

Visio Pro - Deferred Channel - Desktops - 32-bit

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office 365 Visio Pro being installed

Product ID=”VisioProRetail” SKU of Office 365 Visio Pro being installed

Language ID=”en-us” The default language being installed for Office 365 Visio Pro

Display Level="NONE" No UI when installing Office 365 Visio Pro

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

<Language ID="fr-fr" />

<Language ID="de-de" />

<ExcludeApp ID="Access" />

</Product>

</Add>

<Property Name="SharedComputerLicensing" Value="1" />

<Logging Level="Standard" />

<Display Level="None" AcceptEULA="TRUE" />

</Configuration>

Office 365 ProPlus - Deferred Channel - VDI/Shared Computer Activation - 32-bit

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being installed

Language ID=”en-us” The default language being installed for Office 365 ProPlus

Language ID=”ii-cc” The additional languages being installed for Office 365 ProPlus

ExcludeApp ID=”Access” Excludes Access from Office 365 ProPlus installation

SharedComputerLicensing Value=”1” Places Office 365 ProPlus into Shared Computer Activation mode

Display Level="NONE" No UI when installing Office 365 ProPlus

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="LanguagePack">

<Language ID="de-de" />

</Product>

</Add>

</Configuration>

Individual languages - Deferred Channel - Desktops 32-bit

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office language pack being installed

Product ID=”LanguagePack” SKU of language pack being installed

Language ID=”de-de” The language being installed for Office 365 ProPlus

<Configuration>

<Add OfficeClientEdition="32" Channel="FirstReleaseDeferred">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

<ExcludeApp ID="Access" />

</Product>

</Add>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Logging Level="Standard" />

<Display Level="None" AcceptEULA="TRUE" />

</Configuration>

Office 365 ProPlus - First Release for Deferred Channel - Desktops - 32-bit

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being installed

Language ID=”en-us” The default language being installed for Office 365 ProPlus

ExcludeApp ID=”Access” Excludes Access from Office 365 ProPlus installation

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="NONE" No UI when installing Office 365 ProPlus

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add OfficeClientEdition="32" Channel="FirstReleaseDeferred">

<Product ID="ProjectProRetail">

<Language ID="en-us" />

</Product>

</Add>

<Display Level="None" AcceptEULA="TRUE" />

<Logging Level="Standard" />

</Configuration>

Project Pro - First Release for Deferred Channel - Desktops - 32-bit

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office 365 Project Pro being installed

Product ID=”ProjectProRetail” SKU of Office 365 Project Pro being installed

Language ID=”en-us” The default language being installed for Office 365 Project Pro

Display Level="NONE" No UI when installing Office 365 Project Pro

AcceptEULA="TRUE" Accept the License Agreement

Locally Managed Scenario Page 62

Page 63: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add OfficeClientEdition="32" Channel="FirstReleaseDeferred">

<Product ID="VisioProRetail">

<Language ID="en-us" />

</Product>

</Add>

<Display Level="None" AcceptEULA="TRUE" />

<Logging Level="Standard" />

</Configuration>

Visio Pro - First Release for Deferred Channel - Desktops 32-bit

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office 365 Project Pro being installed

Product ID=”VisioProRetail” SKU of Office 365 Project Pro being installed

Language ID=”en-us” The default language being installed for Office 365 Project Pro

Display Level="NONE" No UI when installing Office 365 Project Pro

AcceptEULA="TRUE" Accept the License Agreement

Locally Managed Scenario Page 63

Page 64: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Example Uninstall XML Files for Locally Managed

Below are the Locally Managed example uninstall XML files removing Office 365 clients.

<Configuration>

<Remove>

<Product ID="O365ProPlusRetail" >

<Language ID="en-us" />

<Language ID="fr-fr" />

</Product>

</Remove>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Display Level="None" />

</Configuration>

Office 365 ProPlus – CanAm Region

XML Configuration File Breakdown:

Component Explanation

Product ID=”Office365ProPlusRetail” SKU of Office 365 ProPlus being removed

Language ID=”ii-cc” The languages being removed from Office 365 ProPlus

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="NONE" No UI when removing Office 365 ProPlus

<Configuration>

<Remove>

<Product ID="O365ProPlusRetail" >

<Language ID="de-de" />

</Product>

</Remove>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Display Level="None" />

</Configuration>

Office 365 ProPlus – Germany

XML Configuration File Breakdown:

Component Explanation

Product ID=”Office365ProPlusRetail” SKU of Office 365 ProPlus being removed

Language ID=”de-de” The language being removed from Office 365 ProPlus

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="NONE" No UI when removing Office 365 ProPlus

<Configuration>

<Remove>

<Product ID="ProjectProRetail" >

<Language ID="en-es" />

</Product>

</Remove>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Display Level="None" />

</Configuration>

Project Pro

XML Configuration File Breakdown:

Component Explanation

Product ID=” ProjectProRetail” SKU of Project Pro being removed

Language ID=”en-es” The language being removed from Project Pro

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="NONE" No UI when removing Project Pro

<Configuration>

<Remove>

<Product ID="VisioProRetail" >

<Language ID="en-es" />

</Product>

</Remove>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Display Level="None" />

</Configuration>

Visio Pro

XML Configuration File Breakdown:

Component Explanation

Product ID=” VisioProRetail” SKU of Visio Pro being removed

Language ID=”en-es” The language being removed from Visio Pro

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="NONE" No UI when removing Visio Pro

Uninstall XML Files for Locally Managed

Locally Managed Scenario Page 64

Page 65: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

DFS Overview

Locally Managed has decided to leverage their Distributed File System (DFS) and utilize batch files or scripts to deploy the Office 365 ProPl us

packages. You will notice that the scripts are set to install silently because multiple steps are being performed.

Remove all Office 2010 MSI components if found

Leave user data in place

Run OffScrub•

Install InfoPath 2013 MSI•

Install Office 365 ProPlus with proper channel, architecture, and languages from DFS•

The Office 365 ProPlus configuration script does the following:

OffScrub

The following table includes the OffScrub Command lines that Locally Managed used for the batch file or script sequence to remove the previous

version of Office 2010 (MSI):

Context for program Command line

Office 2010 Removal Command prompt cscript Offscrub2010.vbs clientall /bypass 1 /log c:\temp /nocancel /q

Batch File

Locally Managed will utilize batch files or scripts to complete the Office 365 client configurations. The batch files must run with elevated privileges

since their users are not local admins on their machines. To do so, Locally Managed should do one of the following:

Create a batch file shortcut that runs with elevated privileges, and paste the shortcuts in the appropriate \\Server\Share\O365\DC and

\\Server\Share\O365\FRDC folders

In the batch file or a script include a parameter that will launch command prompt with elevated privileges when an end user without local

administrator rights on the machine performs it

Locally Managed can then either instruct users to the correct batch file or script to run in the DFS network location, or use Group Policy to manually

deploy the appropriate batch file to the user’s desktop.

The following is an example of the Office Source location for Locally Managed 32-bit Deferred Channel. It includes the ODT setup.exe, Office 365

client download and configuration XML files, individual language pack installation XML files, Office 365 client source files, and appropriate batch

files to install or uninstall the Office 365 client software and language packs. A similar example should exist in the FRDC f older as well.

Examples of the batch files or scripts would be as follows:

Context Batch File Performs

Office 365 ProPlus DC

Desktop 32-bit

Office365ProPlus_DC_CanA

m_Configuration

Uninstalls Office 2010 using OffScrub tool, installs Office 365 ProPlus 32-bit Deferred

Channel with CanAm 2 languages

Office 365 ProPlus DC

VDI 32-bit

Office365ProPlus_VDI_DC_C

onfiguration

Uninstalls Office 2010 using OffScrub tool, installs Office 365 ProPlus 32-bit Deferred

Channel with 3 languages and Shared Computer Activation enabled

Visio Pro DC Desktop

32-bit

Visio_DC_Configuration Installs Visio Pro 32-bit Deferred Channel with 1 language

French Language Pack

DC 32-bit

Install_French_LP_DC Installs French language pack 32-bit DC to existing Office 365 clients on machine

Distributed File System (DFS) Configuration

Locally Managed Scenario Page 65

Page 66: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Mac Client Installation

Initial Deployment

This section explains how Locally Managed should design and approach deploying Office 2016 for Mac. Since they do not have a sizeable Mac

population or Mac software distribution tools, it should be managed from a local network share.

Download Office 2016 for Mac to Your Local Network

Administrators can download the MPKG files from the Office 365 Portal Software Page and place the installation image in a net work share. This

strategy is useful for small scaled deployments and allows the user to control the installation of Office. Only users approve d to install Office 2016 for

Mac should have access to the network share.

Sign in to the Office 365 portal as an Office 365 administrator.1.

Go to the Office 365 admin center, and then choose Service Settings > User software.2.

Under Software for Mac, expand Office for Mac, and then choose Download to begin downloading the installer package file. The installer

package file is named Microsoft_Office_2016_Installer.pkg.

3.

Place the Microsoft_Office_2016_Installer.pkg file in the network location4.

Provide Mac end users with installation instructions5.

For more information on deployment options for Office 2016 for Mac, please see: Office 2016 for Mac Clients

Deploy Preferences

For guidance on deploying preferences to end users, please see: Office 2016 for Mac Clients

Note that deployment preferences may overwrite the existing user preference settings. To remove Office for Mac 2011, Troubleshoot Office 2011

for Mac issues by completely uninstalling before you reinstall

Deploy Languages

All of the supported languages in Office 2016 for Mac are now included and installed as part of the installer package .pkg file. Since there are no

longer separate installer package files for each language, admins can no longer choose which language to deploy to users and the language will be

chosen during the installation based on the System Preferences settings. If none of the language settings are supported by Of fice, Office will install

in English.

Office 2016 for Mac Client Install

Locally Managed Scenario Page 66

Page 67: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Ongoing Management and Future Change Management Scenarios

Locally Managed wants to apply some GPO management to their Office 365 ProPlus systems, as well as test specific scenarios they are likely to

encounter.

The items are:

Configuration of infrastructure•

Licensing users•

Removal of languages•

Addition of languages•

Adding Access back•

Rolling back builds and switching channels to maintain deployment rings•

Group Policy for desktops•

Additional Group Policy Objects for VDI•

Group Policy for OneDrive for Business•

Configure Infrastructure

Office 365 is a cloud service and as such will require Internet access. If you manage by URL, then updates are less frequent and typically only needed

when new products or features are released. However, if managed by IP address range, then changes occur more often. The follo wing page should

be reference and RSS feed subscribed to: Office 365 URLs and IP address ranges

Licensing Users

Assign licenses to user accounts with Office 365 PowerShell

Addition of Languages

The ProductID="LanguagePack" element allows you to add languages to an existing Office 365 client install without needing to know its previous

existing install configuration settings

<Configuration>

<Add OfficeClientEdition="32">

<Product ID="LanguagePack">

<Language ID="es-es" />

</Product>

</Add>

</Configuration>

Removal of Languages

The remove element allows you to remove a language from an existing Office 365 client install.

<Configuration>

<Remove>

<Product ID="O365ProPlusRetail">

<Language ID="es-es" />

</Product>

</Remove>

</Configuration>

OR

<Configuration>

<Remove>

<Product ID="LanguagePack">

<Language ID="es-es" />

</Product>

</Add>

</Configuration>

Adding Access Back for Users

By removing the exclude statement from an application, it will include the application when re -run. If the newly run install XML file differs from the

previous file used to install, the latest configuration settings will be applied.

<Configuration>

<Add OfficeClientEdition="32" Channel="Current"

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Product>

</Add>

</Configuration>

Rolling Back a Build

Locally Managed can leverage a batch file or script hosted in their existing DFS structure to perform a client rollback. For step by step gui dance on

performing a rollback using the OfficeC2RClient.exe update engine, please see the following section: Channel Management

Switching Channels

In the event that an end user needs alter their channel membership, the following guidance should be used to switch channels: Channel

Management

Configure Group Policy

It is highly recommended to consistently check for new GPO Templates. As new Office features are rolled out, GPOs may be upda ted and new Office

management GPOs may be released.

Group Policy Reference for Locally Managed

LocallyManaged ...

Additional Group Policy for Shared Computing

Additional GPO should be considered around Outlook and Cached Mode for Shared Computing. Locally Managed has decided to set the value

to 3 days.

Group Policy for OneDrive

Administrative settings for the OneDrive for Business Next Generation Sync Client

Office 2016 Administrative Template files (ADMX/ADML) and Office Customization Tool

Locally Managed Mac Client Updates

Similar to Office 365 ProPlus, Microsoft provides new builds that contains application updates meaning that individual securi ty or feature updates

cannot be downloaded or installed. However, with a locally managed deployment, admins can selectively decide which applicatio ns to apply

updates to. Office 2016 for Mac has a program named Microsoft AutoUpdate to automatically check for updates daily. However, t he Microsoft

AutoUpdate can be configured to daily, weekly, monthly, or manually depending on preferences.

Due to Locally Managed having a small Mac population but no Mac software distribution tool, they should configure Microsoft AutoUpdate to

Management - Locally Managed

Locally Managed Scenario Page 67

Page 68: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Due to Locally Managed having a small Mac population but no Mac software distribution tool, they should configure Microsoft AutoUpdate to

download updates automatically to users’ computers, and then have the users manually install the updates.

Locally Managed Scenario Page 68

Page 69: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Goal

The goal for Cloud Managed is to modernize their existing Office implementation by migrating to Office 365 ProPlus using Offi ce Content Delivery

Network (CDN). Users productivity should not be impacted due to the migration, and 32-Bit Office users will receive Office 365 ProPlus 32-bit.

Assessment Results

500+ employees•

1 supported language•

US based company•

< 25 traveling users, some who are offsite for extended periods•

Sites are small offices•

Size and Distribution

Windows 10 Pro 64-bit•

~5 Mac users whos have local administrator rights•

Mac clients are not managed by client management software•

All systems have EN-US language pack installed with additional languages per region or pulled by the user•

Desktops, notebooks, and shared devices for shift workers•

Network bandwidth is sufficient for daily business•

Windows clients are not managed through client management software•

Office 365 ProPlus will be made available through the Office 365 portal•

Users have local administrative rights on their own machines•

Network is a distributed layout with a small number of high-bandwidth internet interconnection points•

IT Infrastructure

Office 2010 Volume License (MSI) 32-bit•

Some pilot users may have Office Professional Plus 2013 (MSI) 32-bit, as well as Project and Visio 2013 (MSI) 32-bit•

Project 2010 and Visio 2010 (MSI) 32-bit that will be moved to Project and Visio 2013 (MSI) 32-bit•

Application Landscape

Office 365 tenant with Azure AD Connect•

On-Premises Active Directory Federation Services with Single Sign-on (SSO)•

Exchange Online deployed in production•

SharePoint Online deployed in production•

One Drive deployed•

Self-service including installations are not blocked in the portal•

Cloud Infrastructure

Assessment - Cloud Managed

Cloud Managed Scenario Page 69

Page 70: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Planning Overview

Creating a deployment plan is a key component when migrating to Office 365 ProPlus. Planning is based on assessment items dis covered including

constraints and how to implement Office 365 ProPlus in order meet the goals of the project.

Planning Source Locations

Office 365 ProPlus can be deployed and updated directly from the Office Content Delivery Network (CDN), System Center Configu ration Manager,

or an internal share such as leveraging a network share or Distributed File System (DFS). Since Cloud Managed does not use client management

software or have a DFS in place, they will leverage the Office 365 self-service portal to install Office 365 ProPlus for remote users and leverage the

CDN for non-traveling or on premises users. The following Planning is focused around the assets discovered during the assessment phase.

Channel Membership

1% get Current Channel•

10% get First Release for Deferred Channel•

89% get Deferred Channel•

Cloud Managed understands the Microsoft Guidance is the following:

Using existing groups, ~50 users will be on First Release Deferred Channel, and ~440 users will get Deferred Channel. They fi gure there may be ~10

developer, technology owner, or business lead roles that will self-install and self-manage from Office CDN with Current Channel to have the

features before anyone else. These Current Channel users will receive features ahead of FRDC and DC so they can be adequately planned for.

For more information about channel membership and management, please see the following section: Managing Channels for Office 365 ProPlus

Base Client Packaging

The IT department at Cloud Managed has limited history of deploying MSI -based Office using Office Customization Tool, with only one previous

deployment configured. There is a business requirement for shared computers to be covered as part of the deployment. Cloud Ma naged will create

deployment packages consisting of the install XML file and ODT setup.exe and host it internally using UNC shares, and create deployment scripts to

deploy Office 365 ProPlus.

Downloading the Source Files

When using the Office CDN, Cloud Managed is not downloading source files to an on-premises location for redistribution. However, they will still

leverage the Office 2016 Deployment Tool to create an install package and language pack for customization and distribution.

For more information about the Office Deployment Tool, please see the following section: Office Deployment Tool

Configuring Deployments

GitHub Office 365 ProPlus - Configuration XML Editor will be used

The install XML files are relatively simple and can be made by hand following the XML properties published at TechNet. However, since Cloud

Managed will need to manage multiple download and install XML files, they chose to use a web-based tool to help them get it right and not spend

tedious amounts of time in notepad.

Cloud Managed will need install XML files for:

32-bit Office 365 ProPlus Deferred Channel and supported language•

32-bit Office 365 ProPlus First Release for Deferred Channel and supported language•

Having multiple install XML files is not difficult to manage as they are less than 4 kilobytes each.

Shared Computing

<Property Name="SharedComputerLicensing" Value="1" />

The shared computing property value needs to be set properly for each of the shared computing scenarios discovered during Ass essment.

The following table explains how the setting will be applied to each of the Shared Computer Activation deployment scenarios i dentified during

Assessment:

Client Type XML Value

Standard Desktop 0

Shared Workstation 1

Languages

Cloud Managed will utilize the Office CDN and languages will be downloaded directly from the Office CDN and installed using the Office

Deployment Tool. If they decided to allow users to install additional languages, users can leverage a self-service language pack install since they

have local administrator rights on the clients.

Remove / Restore of Applications

Cloud Managed is not planning to exclude any applications during the Office 365 ProPlus deployment.

Customizations (GPO)

Cloud Managed will leverage the Office 2016 Administrative Template files (ADMX/ADML) and Office Customization Tool for Group Policy. They

have also went through their existing Group Policy settings and identified any preexisting Group Policy settings that will be utilize for Office 365

ProPlus. At this time, OneDrive is a separate GPO template download and should be reviewed in order to determine if any of the Group Policy

settings are required.

A sample set of the Preferred Practices policies and GPO backups can be found here: Group Policy

Side by Side

Cloud Managed reviewed their assessment data and decided that they will install Office 365 ProPlus side by side with existing Office instal lations

where Project and Visio are concerned. The plan of record is to remove any previous versions of Office 2010 and 2013 (MSI), P roject 2010 (MSI), and

Visio 2010 (MSI), and to keep user data intact (dictionary, mail file, signature, etc.). If a user already has a 2013 Project or Visio (MSI) install on their

machine, it will be left installed on the machine during the OffScrub process but a quick repair will need to be run after th e Office 365 ProPlus

installation completes in order for the Project and Visio versions to function properly. If a user runs into Macro or Add -in errors, they will then

attempt to remediate the issue by using a side by side scenario.

Project and Visio

Cloud Managed has a small number of 2010 Project and Visio (MSI) deployments within their environment that they will be migrating to 2013

Project and Visio (MSI). 2013 Project and Visio (MSI) will run in side by side with Office 365 ProPlus in a supported N-1 scenario. Cloud Managed

should run a quick repair on any Project and Visio MSI installs once Office 365 ProPlus has been installed.

Office Scrub Tool (OffScrub)

Cloud Managed will use OffScrub to ensure that all previous installations of Office 2010 (MSI), including Project and Visio 2010 installations, and all

previous installations of Office 2013 (MSI), excluding Project and Visio 2013, are properly removed with no unwanted artifacts or "couldn’t

uninstall" errors before Office 365 ProPlus is installed.

For more information on the OffScrub tool, please see the following section: OffScrub

ArchitectureCloud Managed determined that only the 32-bit version of the Office 365 clients will be deployed. Cloud Managed has no uses cases for 64 -bit

applications.

Office 2016 for Mac

Planning - Cloud Managed

Cloud Managed Scenario Page 70

Page 71: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Cloud Managed will not use client management software to deploy Office 2016 for Mac for their ~5 Mac users. They will instead leverage the Office

365 portal for users who need Office 2016 for Mac. Users will be prompted for their machine administrator credentials in order to install Office 2016

for Mac.

Licensing

Cloud Managed has already synced their users and the Exchange Online users already have E3 licenses. Cloud Managed uses PowerShell and on

premises AD DS attributes to determine and assign the Office 365 Licenses, but also does some manual license assignment and m anagement via

the Office 365 admin portal. It is important to note that the licenses are all done with custom PowerShell, and the AD DS is just a reference point for

the PowerShell licensing script.

Network

Cloud Managed has decided to bypass proxy services for all Office 365 ProPlus URLs. As such, the ability to activate or authenticate to Off ice 365

and maintain the subscription will not be blocked. Since they will be relying on users to update from the CDN, all Office 365 ProPlus URLs must be

open.

Staying Current Versus Skipping Builds and Rollbacks

Cloud Managed is planning on staying current because they understand that it is the most network optimized solution. However, they have cre ated

a script stored in a network location that contains the necessary items to perform a rollback to a previously known good vers ion. Administrators

would need to provide the appropriate version number in the script to rollback to, and they will utilize the Office CDN for t he rollback.

For more information about performing a rollback, please see the following section: Channel Management

Cloud Managed Scenario Page 71

Page 72: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Managed Deployment Activities

Now that Cloud Managed has been through Assessment and Planning, it is time to implement Office 365 ProPlus as planned.

The First Step is to Configure the Deployment files for Redistribution

Download the latest version of the Office Deployment Tool (ODT) and create and configure the install XML files to download and install the Office

365 ProPlus source files. Cloud Managed made multiple XML files that will be used to configure and install Office 365 ProPlus.

GitHub was leveraged to edit the XML files.

English

Office 365 ProPlus - Deferred Channel - Desktops - 32-bit•

English

Office 365 ProPlus - Deferred Channel - Desktops - VDI - 32-bit•

English

Office 365 ProPlus - First Release Deferred Channel - Desktops - 32-bit•

The following XML files will need to be made:

The Second Step is to Configure the Office Scrub Tool to Remove all Previous Versions of Office

Since Cloud Managed has multiple versions of Office in the environment, two versions of the Office Scrub tool need to be obtained from Premier

support. The first version removes Office 2007 and 2010 MSI versions, while the second removes Office 2013 MSI, 2013 C2R, and 2016 MSI or C2R

The application will be run via a script, and since there are multiple versions of the tool, each command has to be performed separately.

The following sequence will be run:

Office 2010 Removal•

Office 2013 MSI Core Suite Removal (leave Project and Visio 2013 on machine)•

User data will be persisted and Project and Visio will be left intact. A quick repair on Project and Visio will likely be req uired.

The Third Step is to Create the Batch Install Wrapper to Automate the OffScrub and Office 365 ProPlus Install or Removal

Cloud Managed can utilize a batch file stored in a UNC path to initiate the Office 365 ProPlus installation from the Office CDN, or to unin stall an

existing Office 365 ProPlus installation.

Remove all Office 2010 (MSI) components

Remove Office 2013 (MSI) Core suite applications (leave any 2013 Project and Visio MSI instances intact)

Leave user data in place

Run Office Scrub•

Install Office 365 ProPlus with proper channel, architecture, and languages•

A sample Office 365 ProPlus batch file task order would be:

The following batch files or scripts should be created:

OffScrub + Office 365 ProPlus Deferred Channel install•

OffScrub + Office 365 ProPlus First Release for Deferred Channel Office 365 ProPlus install•

Office 365 ProPlus uninstall•

Add the below line to a to a batch file (I.E. - Office365_DC_Configuration.cmd). This batch line will dynamically determine the script directory and

find setup.exe and install XML. Note that this does not check if the script is performed with elevated rights or not, but Cloud Managed users are

local administrators on their client devices.

"%~dp0Setup.exe" /configure "%~dp0install.xml"

An additional batch file (I.E. - Office365_Removal.cmd) to uninstall can be created and leverage the following batch line:

"%~dp0Setup.exe" /configure "%~dp0removal.xml"

The Fourth Step is to Configure Office 2016 for Mac for Distribution

Cloud Managed has a limited Mac environment and will utilize the Office 365 portal for deployments. Users should be provided instructions o n how

to install Office 2016 for Mac from the Office 365 portal. Users will need to provide their machine administrator credentials in order to install Office

2016 for Mac.

Deployment - Cloud Managed

Cloud Managed Scenario Page 72

Page 73: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Download XML files for Cloud Managed

Cloud Managed deployments will rely on Office CDN as a content source and therefore will not need to create download XML file s. However, in the case that they decide at a

future date to host the content in an on premises source location, the below download XML files could be leveraged.

The Download File

1 language

Office 365 ProPlus Deferred Channel 32-Bit•

1 language

Office 365 ProPlus First Release for Deferred Channel 32-bit•

Cloud Managed would need download XMLs for the following:

Remember that Cloud Managed is expecting Current Channel users to self-provision and self-manage, and all applications will be included during

the install.

Example Download XML Files

Below are the Cloud Managed example download XML files to download Office 365 client source files.

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Product>

</Add>

</Configuration>

Office 365 ProPlus - Deferred Channel - 32-bit

XML Download File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being downloaded

Channel="Deferred" The channel build of Office 365 ProPlus being downloaded

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being downloaded

Language ID="en-us" The languages being downloaded for Office 365 ProPlus

<Configuration>

<Add OfficeClientEdition="32" Channel="FirstReleaseDeferred">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Add>

</Configuration>

Office 365 ProPlus – First Release for Deferred Channel - 32-bit

XML Download File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being downloaded

Channel=”FirstReleaseDeferred” The channel build of Office 365 ProPlus being downloaded

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being downloaded

Language ID=”en-us” The language being downloaded for Office 365 ProPlus

Download XML Files for Cloud Managed

Cloud Managed Scenario Page 73

Page 74: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Install XML files for Cloud Managed

Install Overview

1 language

Office 365 ProPlus - Deferred Channel - Desktops - 32-bit•

1 languages

Office 365 ProPlus - Deferred Channel - Shared Computers - 32-bit•

1 language

Office 365 ProPlus - First Release Deferred Channel - Desktops - 32-bit•

Cloud Managed needs install XMLs for:

Remember that Cloud Managed is expecting Current Channel users to self-provision and self-manage, and all applications will be included in the

install.

Example Install XML Files

Below are the Cloud Managed example install XML files for configuring and installing Office 365 clients.

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Product>

</Add>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Logging Level="Standard" />

<Display Level="None" AcceptEULA="TRUE" />

</Configuration>

Office 365 ProPlus - Deferred Channel - Desktops - 32-bit

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being installed

Language ID=”en-us” The default language being installed for Office 365 ProPlus

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="None" Hides the UI when installing Office 365 ProPlus

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add OfficeClientEdition="32" Channel="Deferred">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Product>

<Property Name="SharedComputerLicensing" Value="1" />

</Add>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Logging Level="Standard" />

<Display Level="None" AcceptEULA="TRUE" />

</Configuration>

Office 365 ProPlus - Deferred Channel - Desktops - Shared Computer Activation - 32-bit

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being installed

Language ID=”en-us” The default language being installed for Office 365 ProPlus

SharedComputerLicensing Value=”1” Places Office 365 ProPlus into Shared Computer Activation mode

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="None" Hides the UI when installing Office 365 ProPlus

AcceptEULA="TRUE" Accept the License Agreement

<Configuration>

<Add OfficeClientEdition="32" Channel="FirstReleaseDeferred">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Product>

</Add>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Logging Level="Standard" />

<Display Level="None" AcceptEULA="TRUE" />

</Configuration>

Office 365 ProPlus - First Release for Deferred Channel - Desktops - 32-bit

XML Configuration File Breakdown:

Component Explanation

OfficeClientEdition=”32” The architecture of Office being installed

Product ID=”O365ProPlusRetail” SKU of Office 365 ProPlus being installed

Language ID=”en-us” The default language being installed for Office 365 ProPlus

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="NONE" No UI when installing Office 365 ProPlus

AcceptEULA="TRUE" Accept the License Agreement

Install XML Files for Cloud Managed

Cloud Managed Scenario Page 74

Page 75: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Example Uninstall XML Files for Cloud Managed

Below is the Cloud Managed example uninstall XML file for removing Office 365 ProPlus.

<Configuration>

<Remove>

<Product ID="O365ProPlusRetail" >

<Language ID="en-us" />

</Product>

</Remove>

<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />

<Display Level="None" />

</Configuration>

Office 365 ProPlus

XML Configuration File Breakdown:

Component Explanation

Product ID=”Office365ProPlusRetail” SKU of Office 365 ProPlus being removed

Language ID=”en-es” The language being removed from Office 365 ProPlus

FORCEAPPSHUTDOWN Value =”True” Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur

Display Level="NONE" No UI when removing Office 365 ProPlus

Uninstall XML Files for Cloud Managed

Cloud Managed Scenario Page 75

Page 76: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

CDN Overview

Cloud Managed has decided to leverage the Office CDN for the source files to deploy the Office 365 ProPlus packages. However, they will uti lize

automation scripts for OffScrub and to initiate the Office 365 ProPlus deployment.

The Office 365 configuration script does the following:

Remove all Office 2010 MSI components if found

Remove Office 2013 MSI core suite if found, but leave 2013 Project and Visio intact if previously installed

Leave user data in place

Run OffScrub•

Install Office 365 ProPlus with proper channel, architecture, and languages from Office CDN•

OffScrub

The following table includes the OffScrub Command lines that Cloud Managed used for the script sequence to remove previous versions of Office:

Context for program Command line

Office 2010 Removal Command prompt cscript Offscrub2010.vbs clientall /bypass 1 /log c:\temp /nocancel /q

Office 2013 MSI Removal Command prompt cscript OffScrub2013.vbs ProPlus /bypass 1 /log c:\temp /nocancel /q

Office Source Location

Cloud Managed will utilize scripts to complete the Office 365 client configurations. The following is an example of the Office Source locat ion for

Cloud Managed 32-bit Deferred Channel. It includes the ODT setup.exe, Office 365 client install XML files, and corresponding batch files.

Example of the batch file for the package would be as follows:

Context for program Command line

Deferred Channel 32-bit Setup.exe /configure Install_ProPlus_DC_.xml

Office Content Delivery Network (CDN) Configuration

Cloud Managed Scenario Page 76

Page 77: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Mac Client Installation for Cloud Managed

Initial Deployment

This section explains how Cloud Managed should design and approach deploying Office 2016 for Mac. Since they have a very limited Mac

population, users should self-manage and self-service from the Office 365 portal.

Office 365 Portal Deployment

In a deployment situation where the user is downloading Office 2016 for Mac from the Office 365 software Portal, the followin g guidance is

recommended: Download and Install Office 2016 for Mac Step by Step Instructions. If Office installation fails, see What to try if you can't install or

activate Office 2016 for Mac using Office 365 for business.

In order for a user to install Office 2016 for Mac from the Office 365 portal, the user must have administrative privileges o n their client device.

Office 2016 for Mac Client Install

Cloud Managed Scenario Page 77

Page 78: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Ongoing Management Future Change Management Scenarios

Cloud Managed wants to apply GPO management to their Office 365 ProPlus systems they want to test specific scenarios they are likely to

encounter.

The items are:

Configuration of infrastructure•

Licensing users•

Rolling back builds and switching channels to maintain deployment rings•

Group Policy for desktops•

Group Policy for OneDrive for Business•

Configure Infrastructure

Office 365 is a cloud service and as such will require Internet access. If you manage by URL, then updates are less frequent and typically only needed

when new products or features are released. However, if managed by IP address range, then changes occur more often. The follo wing page should

be reference and RSS feed subscribed to.

Office 365 URLs and IP address ranges

Licensing Users

Assign licenses to user accounts with Office 365 PowerShell

Rolling Back a Build

Cloud Managed can leverage a script hosted in a network share to perform a client rollback. For step by step guidance on performing a rollb ack

using the OfficeC2RClient.exe update engine, please see the following section: Channel Management

Switching Channels

In the event that an end user needs alter their channel membership, the following guidance should be used to switch channels: Channel

Management

Configure Group Policy

It is highly recommended to consistently check for new GPO Templates. As new Office features are rolled out, GPOs may be upda ted and new Office

management GPOs may be released.

Office 2016 Administrative Template files (ADMX/ADML) and Office Customization Tool

Group Policy Reference for Cloud Managed

CloudManaged ...

Additional Group Policy for Shared Workstations

Additional GPO should be considered around Outlook and Cached Mode for shared workstations. Cloud Managed has decided to set the value

to 3 days.

Group Policy for OneDrive

Administrative settings for the OneDrive for Business Next Generation Sync Client

Cloud Managed Mac Client Updates

Similar to Office 365 ProPlus, Microsoft provides new builds that contains application updates meaning that individual securi ty or feature updates

cannot be downloaded or installed. However, with a locally managed deployment, admins can selectively decide which applicatio ns to apply

updates to. Office 2016 for Mac has a program named Microsoft AutoUpdate to automatically check for updates daily. However, t he Microsoft

AutoUpdate can be configured to daily, weekly, monthly, or manually depending on preferences.

Due to Cloud Managed having a very limited Mac population, they should configure Microsoft AutoUpdate to download updates aut omatically to

users’ computers, and then have the users manually install the update.

Management - Cloud Managed

Cloud Managed Scenario Page 78

Page 79: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Links for Administration Education

Overview

The below table contains helpful videos for Admins new to Office 365 ProPlus:

Product Title Format Location

Office 2013 to Office 2016 Office365 ProPlus Upgrade Video https://mva.microsoft.com/en-US/training-courses/office-365-proplus-upgrade-14776?l=Zo4fEFjzB_6000115881

Office 365 ProPlus Deployment

Deep Dive

Office 365 ProPlus Deep Dive Video https://mva.microsoft.com/en-US/training-courses/office-365-proplus-deployment-deep-dive-14066

What really happens when there

is a Service Outage

What really happens when there is a Service Outage Video https://mva.microsoft.com/en-US/training-courses/what-really-happens-when-there-is-an-office-365-service-incident-and-whats-my-role-14085

Tools and Tips for

Administrating Office 365

Tools and Tips for Administrating Office 365 Video https://mva.microsoft.com/en-US/training-courses/tools-and-tips-for-administering-office-365-14083

Office 365 ProPlus What's New

in 2016 and Beyond

Office 365 ProPlus What's New in 2016 and Beyond Video https://mva.microsoft.com/en-US/training-courses/office-365-proplus-whats-new-in-2016-and-beyond-14065?l=6k9rJAomB_9800115881

Managing Change in Office 365

Rapid Release World

Managing Change in Office 365 Rapid Release World Video https://mva.microsoft.com/en-US/training-courses/managing-change-in-an-office-365-rapid-release-world-14061?l=SaT0W4nmB_1400115881

Deploying Office365 ProPlus Deploying Office365 ProPlus Video https://mva.microsoft.com/en-US/training-courses/deploying-office-365-proplus-9013

Solving Office 365 Client

Deployment Scenarios

Solving Office 365 Client Deployment Scenarios Video https://mva.microsoft.com/en-US/training-courses/solving-office-365-client-deployment-scenarios-9086?l=suttZBf4_2304984382

Reference Materials Page 79

Page 80: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Links for Help Desk and End User Training

Overview

The below table contains helpful videos for end users new to Office 365 ProPlus:

Product Title Format Location

Outlook 2016 on Windows Learn to Setup first Outlook

Account

Video https://support.office.com/en-us/article/Set-up-your-email-

b44563f6-74ca-476d-aa0e-9b9ad0074d82?ui=en-US&rs=en-

US&ad=US

Compose and Send Email Video https://support.office.com/en-us/article/Compose-and-send-email-

ce0669d9-c010-4d59-b5e7-d03e20e2bf8a?ui=en-US&rs=en-

US&ad=US

Stop Sending attachments:

Sharing with email

Video https://support.office.com/en-us/article/Stop-sending-attachments-

Sharing-with-email-234b9758-3fc7-4883-b086-83ddc03cebc8?

ui=en-US&rs=en-US&ad=US

View Unread Emails Video https://support.office.com/en-us/article/View-unread-emails-

ce177123-7e1a-4cfe-aa7c-53789cbda811?ui=en-US&rs=en-

US&ad=US

Reply to an email message Video https://support.office.com/en-us/article/Reply-to-an-email-

message-cb601d69-02bf-4411-bf93-0bec8d814ff1?ui=en-

US&rs=en-US&ad=US

Search and Filter Email Video https://support.office.com/en-us/article/Search-and-filter-email-

d5a7b1b7-ad2a-4ca8-897a-37f637279490?ui=en-US&rs=en-

US&ad=US

`` Create an email signature in

Outlook

Video https://support.office.com/en-us/article/Create-an-email-signature-

in-Outlook-109a41ec-2328-4168-bee8-0824d51c3067?ui=en-

US&rs=en-US&ad=US

Outlook Quick Start Guide PDF http://download.microsoft.com/download/5/E/7/5E7E239F-

B465-4D39-888F-8A5CCEF7A8AD/OUTLOOK%202016%20QUICK%

20START%20GUIDE.PDF

Outlook 2016 on Mac OS Outlook 2016 for Mac Basics PowerPoint https://docs.com/OfficeTraining/6434/outlook-for-mac-2016-basics-

training

Add an Email Account

Attach things to email

Create an email signature

Set up Automatic replies

Add email contacts

Work with your calendar

Work with tasks

Topics:

Office 2016 for Mac Quick

Start Guides

PDF https://support.office.com/en-us/article/Office-2016-for-Mac-Quick-

Start-Guides-5bccb480-0e5b-4b51-b072-66d3793ccad8

Use VoiceOver in Outlook

2106

Article https://support.office.com/en-us/article/Use-VoiceOver-in-

Outlook-2016-for-Mac-13e59ff3-6da3-4d59-88d8-885a5dc9e90d

Where is my Outbox Article https://support.office.com/en-us/article/Where-s-my-Outbox-in-

Outlook-2016-for-Mac-5018fdd3-26b9-4fa0-b111-b656cdb5afae?

ui=en-US&rs=en-US&ad=US

Share your calendar Article https://support.office.com/en-us/article/Share-your-calendar-in-

Outlook-2016-for-Mac-1534a3e9-b6d1-420f-88ae-89abb17ad57e?

ui=en-US&rs=en-US&ad=US

Outlook on the Web General Usage Article https://support.office.com/en-us/article/Welcome-to-Outlook-on-

the-web-28bac523-cc12-4b52-b13c-4436cd181edc

Using email on Outlook on

the web and outlook.com

Article https://support.office.com/en-us/article/Using-email-in-Outlook-on-

the-web-and-Outlook-com-a5806e13-2fdc-4b79-

a7d6-940a54c48121?ui=en-US&rs=en-US&ad=US

Create and send a new message

Spell check an email

Reply, reply all, or forward an email message

Create a new email folder

Search for a piece of mail

Work with draft messages

Archive old email messages

Delete email or recover deleted items

Sign Out of Outlook

Topics:

Outlook on Android Get the app Link https://play.google.com/store/apps/details?

id=com.microsoft.office.outlook

Setup email on an Android

phone or tablet

Article https://support.office.com/en-us/article/Set-up-email-on-an-

Android-phone-or-tablet-886db551-8dfa-4fd5-b835-f8e532091872

Outlook on iOS Get the App Link https://itunes.apple.com/app/id951937596

Setup email on an Android

phone or tablet

Article https://support.office.com/en-us/article/Set-up-email-on-iPhone-

iPad-or-iPod-Touch-b2de2161-cc1d-49ef-9ef9-81acd1c8e234

Outlook on Windows Phone Setup email on Windows

Phone

Article https://support.office.com/en-us/article/Set-up-email-on-Windows-

Phone-181a112a-be92-49ca-ade5-399264b3d417

Word 2016 on Windows Explore the document gallery Video https://support.office.com/en-us/article/Explore-Word-2016-

eb385404-cb97-4b41-b2aa-1c18d05cd383?ui=en-US&rs=en-

US&ad=US

Create a document in Word

2016

Video https://support.office.com/en-us/article/Create-a-document-in-

Word-2016-f01a7977-3942-4daa-b651-23cc06a0054b?ui=en-

US&rs=en-US&ad=US

Format a document in Word

2016

Video https://support.office.com/en-us/article/Format-a-document-in-

Word-2016-780772c6-9506-4081-afd1-aff9aab19f5f?ui=en-

US&rs=en-US&ad=US

Insert Items in a Word 2106

document

Video https://support.office.com/en-us/article/Insert-items-in-a-

Word-2016-document-5c967406-a472-498b-a2e3-cdd5f0d5c50a?

ui=en-US&rs=en-US&ad=US

Add headers and footers and

change page numbers in

Word 2016

Video https://support.office.com/en-us/article/Add-headers-and-footers-

and-change-page-numbers-in-Word-2016-f4875508-bb0c-498d-

a79b-540160a7a85f?ui=en-US&rs=en-US&ad=US

Save a document in Word

2016

Video https://support.office.com/en-us/article/Save-a-document-in-

Word-2016-78c23f64-2791-4137-903d-ab0bb7a9007a?ui=en-

US&rs=en-US&ad=US

Word 2016 Quick Start Guide PDF https://support.office.com/en-us/article/Office-2016-Quick-Start-

Guides-25f909da-3e76-443d-94f4-6cdf7dedc51e

Reference Materials Page 80

Page 81: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Word 2016 on Mac OS Word 2016 for Mac training PowerPoint https://docs.com/OfficeTraining/1025/word-2016-for-mac-basics

Learn your way around

Create a document

Format a document

Save a document

Topics:

Word 2016 for Mac Quick

Start Guide

PDF https://support.office.com/en-us/article/Office-2016-for-Mac-Quick-

Start-Guides-5bccb480-0e5b-4b51-b072-66d3793ccad8

Word 2016 Mac Common

Scenarios

Articles https://support.office.com/en-us/article/Word-2016-for-Mac-Help-

c3292414-89c0-46e5-82a7-d55a1720f3bd

Word on Android Getting Started with Word for

Android Tablet

Video https://support.office.com/en-us/article/Video-Getting-started-with-

Word-for-Android-tablet-1aaaa121-99a7-426d-af6a-ee1611002dca

Android Touch Guide Article https://support.office.com/en-us/article/Word-for-Android-touch-

guide-32b15209-5934-4b0e-a1c4-585cb70ac3fa

Word on iOS Log in to Office for the Ipad Video https://support.office.com/en-us/article/Training-videos-for-Word-

for-iPad-cf2bd27e-e68c-496c-ae81-d4eb6e37b59e

Open Files from the Cloud Video https://support.office.com/en-us/article/Training-videos-for-Word-

for-iPad-cf2bd27e-e68c-496c-ae81-d4eb6e37b59e

Open Email Attachments Video https://support.office.com/en-us/article/Training-videos-for-Word-

for-iPad-cf2bd27e-e68c-496c-ae81-d4eb6e37b59e

How saving work in word for

the iPad

Video https://support.office.com/en-us/article/Training-videos-for-Word-

for-iPad-cf2bd27e-e68c-496c-ae81-d4eb6e37b59e

Type in Word for the IPad Video https://support.office.com/en-us/article/Training-videos-for-Word-

for-iPad-cf2bd27e-e68c-496c-ae81-d4eb6e37b59e

Select stuff in Word for the

iPad

Video https://support.office.com/en-us/article/Training-videos-for-Word-

for-iPad-cf2bd27e-e68c-496c-ae81-d4eb6e37b59e

How to print in Word for iPad Video https://support.office.com/en-us/article/Training-videos-for-Word-

for-iPad-cf2bd27e-e68c-496c-ae81-d4eb6e37b59e

Word for iPhone touch guide Article https://support.office.com/en-us/article/Word-for-iPhone-touch-

guide-0a154e7f-14ee-46f1-a4c2-07c2017151b6

Word on Windows Phone Use Word Mobile for

Windows Phone

Article https://support.office.com/en-us/article/Use-Word-Mobile-for-

Windows-Phone-3fe718ee-e8a6-40b0-8420-b3520c25c411

Excel 2016 on Windows Create your first workbook Video https://support.office.com/en-us/article/Explore-Excel-2016-

c6cd2046-4387-41bf-a874-b03a01ee3c87?ui=en-US&rs=en-

US&ad=US

Create a workbook using a

template

Video https://support.office.com/en-us/article/Create-a-workbook-in-

Excel-2016-01746248-5dbd-429d-8e9a-aa436d5b788b?ui=en-

US&rs=en-US&ad=US

Add data to a workbook by

typing in Excel

Video https://support.office.com/en-us/article/Type-data-in-a-worksheet-

in-Excel-2016-04cbaccf-a606-4b7d-b26a-0edfeed896e2?ui=en-

US&rs=en-US&ad=US

Create a basic chart in Excel Video https://support.office.com/en-us/article/Create-a-basic-chart-in-

Excel-2016-5cbf42ac-c4d1-414c-8e82-f8714cd7043e?ui=en-

US&rs=en-US&ad=US

Save your workbook Article https://support.office.com/en-us/article/Save-your-

workbook-90838b70-f005-4e52-bb45-0ce1f2786821?ui=en-

US&rs=en-US&ad=US

Excel Quick start Guide PDF https://support.office.com/en-us/article/Office-2016-Quick-Start-

Guides-25f909da-3e76-443d-94f4-6cdf7dedc51e

Excel on Mac OS Excel 2016 for Mac Basics Article https://docs.com/OfficeTraining/5255/excel-2016-for-mac-basics

Learn your way around

Create a workbook

Save a workbook

Topics:

What's new in Office 2016 for

Mac?

Video

(Monthly

Updates)

https://support.office.com/en-us/article/What-s-new-and-improved-

in-Office-2016-for-Mac-44d5a464-3051-41b0-b44e-c6cee569f545?

ui=en-US&rs=en-US&ad=US

Excel 2016 Quick Start Guide PDF https://support.office.com/en-us/article/Office-2016-for-Mac-Quick-

Start-Guides-5bccb480-0e5b-4b51-b072-66d3793ccad8

Excel 2016 Mac Common

Scenarios

Article https://support.office.com/en-us/article/Excel-2016-for-Mac-

Help-2010f16b-aec0-4da7-b381-9cc1b9b47745 - Common

Scenarios

Excel on Android (Tablet) Excel 2016 Common

Scenarios

Article https://support.office.com/en-us/article/Excel-for-Android-Tablets-

Help-5f089a58-dfa5-4cdb-b93b-55deb638a469?ui=en-US&rs=en-

US&ad=US

Getting Started with Excel for

Android Tablet

Video https://support.office.com/en-us/article/Video-Getting-started-with-

Excel-for-Android-tablet-c5d5c135-0bc1-4aea-9b54-95a518dd0c11

Log in to Office for Android Video https://support.office.com/en-us/article/Office-for-Android-tablet-

videos-7604a6aa-5148-436d-a58e-01ad331c2774

Get Started with Excel

Spreadsheet for Android

Tablet

Video https://support.office.com/en-us/article/Video-Getting-started-with-

Excel-for-Android-tablet-c5d5c135-0bc1-4aea-9b54-95a518dd0c11

Excel for Android Touch

Guide

Article https://support.office.com/en-us/article/Excel-for-Android-touch-

guide-aef977da-6adf-4724-b054-8ca4bb1d7afb

Excel on iOS Training Videos for Excel on

iPad

Video https://support.office.com/en-us/article/Training-videos-for-Excel-

for-iPad-8c2fb984-de3c-4988-a32d-d549b6c91810

Log in to Office for the iPad

Open Files from the cloud

Open an email attachments

How saving works in Excel for iPad

Type in Excel for the iPad

Select stuff in the Excel for iPad

Print in Excel for the iPad

Topics:

Type in Excel for iPad Video https://support.office.com/en-us/article/Video-Type-in-Excel-for-

iPad-1ebd2af3-40a3-4cfc-bfeb-bc62d9d37a77

Excel for iPhone Common

Scenarios

Article https://support.office.com/en-us/article/Excel-for-iPhone-help-

b367819b-05b4-4a56-ab1c-678da62e1fd3

Excel for iPhone Touch Guide Article https://support.office.com/en-us/article/Excel-for-iPhone-Touch-

Guide-5b175ec6-5cde-48d9-a13f-226680953278

Excel on Windows Phone Use Excel for Windows Phone Article https://support.office.com/en-us/article/Use-Excel-Mobile-for-

Windows-Phone-a39cc086-5230-46c5-bac5-8964bbc453f1

PowerPoint 2016 on Windows Getting Started with

PowerPoint 2016

Video https://support.office.com/en-us/article/Explore-

PowerPoint-2016-74d69873-993c-4618-87c9-98aa3adf11cf?ui=en-

US&rs=en-US&ad=US

Insert Stuff into your

presentation

Video https://support.office.com/en-us/article/Insert-stuff-into-your-

presentation-313b6793-bc76-4f43-bd69-a511dcd83bd3?ui=en-

US&rs=en-US&ad=US

Save and share your Video https://support.office.com/en-us/article/Save-and-share-your-

Reference Materials Page 81

Page 82: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Save and share your

presentation

Video https://support.office.com/en-us/article/Save-and-share-your-

presentation-b40d547f-a07d-48d2-bc60-ef3fb653ac22?ui=en-

US&rs=en-US&ad=US

Presenting with PowerPoint Video https://support.office.com/en-us/article/Presenting-with-

PowerPoint-edb122e7-2ef2-4361-a078-708c3b84022a?ui=en-

US&rs=en-US&ad=US

PowerPoint Quick start Guide PDF https://support.office.com/en-us/article/Office-2016-Quick-Start-

Guides-25f909da-3e76-443d-94f4-6cdf7dedc51e

PowerPoint on Mac OS PowerPoint 2016 for Mac

Basics

PowerPoint https://docs.com/OfficeTraining/2082/powerpoint-2016-for-mac-

basics

Getting Started

Add slides

Add content

Format content

Apply a different theme

Apply a different slide layout

Save your presentation

Topics:

What's new in Office 2016 for

Mac

Video

(Updated

Monthly)

https://support.office.com/en-us/article/What-s-new-and-improved-

in-Office-2016-for-Mac-44d5a464-3051-41b0-b44e-c6cee569f545?

ui=en-US&rs=en-US&ad=US

PowerPoint 2016 Mac Quick

Start Guides

PDF https://support.office.com/en-us/article/Office-2016-for-Mac-Quick-

Start-Guides-5bccb480-0e5b-4b51-b072-66d3793ccad8

PowerPoint Common

Scenarios

Article https://support.office.com/en-us/article/PowerPoint-2016-for-Mac-

Help-89809457-4470-4f79-a4d6-835cd366f7d7

PowerPoint on Android PowerPoint for Android touch

guide

Article https://support.office.com/en-us/article/PowerPoint-for-Android-

touch-guide-7f2b68df-608f-428b-958b-5a165fb109ce

Getting Started with

PowerPoint for Android

Tablet

Video https://support.office.com/en-us/article/Video-Getting-started-with-

PowerPoint-for-Android-tablet-1ca4c589-217b-4762-ae20-

d1877555b8c1

Use an external keyboard

with PowerPoint for Android

Article https://support.office.com/en-us/article/Use-an-external-keyboard-

with-PowerPoint-for-Android-8f4abc4e-afb2-4eb7-

be9f-73b7f928b336

PowerPoint on iOS Training videos for

PowerPoint for the iPad

Video https://support.office.com/en-us/article/Training-videos-for-

PowerPoint-for-iPad-d59b27f6-28cb-47f3-ab85-f3de1e7bbf87

Log in to Office for iPad

Open file from the cloud

Open email attachments

How saving works in PowerPoint for iPad

Type in PowerPoint for iPad

Select stuff in PowerPoint for iPad

How to print in PowerPoint for the iPad

Run a Slideshow in PowerPoint for iPad

Projecting your slideshow to a screen

Topics:

PowerPoint Common

Scenarios for iPhone

Article https://support.office.com/en-us/article/PowerPoint-for-iPhone-

Help-754fcb37-783b-4e8a-afca-edb900221b8b

PowerPoint for iPad touch

Guide

Article https://support.office.com/en-us/article/PowerPoint-for-iPad-touch-

guide-bbc7cfc1-6fb0-4579-a19a-de7b4ff10478

PowerPoint on Windows Phone Use PowerPoint for Windows

Phone

Article https://support.office.com/en-us/article/Use-PowerPoint-Mobile-

for-Windows-Phone-da9ff3b1-0278-454b-8796-e75ce3ce5738

OneNote for Windows What is OneNote Video https://support.office.com/en-us/article/What-is-OneNote-

be6cc6cc-3ca7-4f46-8876-5000f013c563?ui=en-US&rs=en-

US&ad=US

Use OneNote in the Cloud Video https://support.office.com/en-us/article/Use-OneNote-in-the-

cloud-54fcce99-65b6-4501-ab96-27c30a176139?ui=en-US&rs=en-

US&ad=US

Getting Started with OneNote

and notebooks

Video https://support.office.com/en-us/article/Get-started-with-OneNote-

and-notebooks-4beb2128-51d9-4531-a4e0-078f605bbfea?ui=en-

US&rs=en-US&ad=US

Add section and pages Video https://support.office.com/en-us/article/Add-sections-and-pages-

b041747d-f29c-4cd3-a52e-f835ee315660?ui=en-US&rs=en-

US&ad=US

Maximize your pages Video https://support.office.com/en-us/article/Maximize-your-pages-

d57f386d-38de-4bd9-91bc-6820a3988bed?ui=en-US&rs=en-

US&ad=US

Take Notes Article https://support.office.com/en-us/article/Take-

notes-2f9f2dac-57ce-4836-ba8e-fdbf525a52ab?ui=en-US&rs=en-

US&ad=US

Create a Quick Note Article https://support.office.com/en-us/article/Create-a-Quick-Note-

d7c202c5-c8e5-4a47-8645-a7ba29c26baa?ui=en-US&rs=en-

US&ad=US

Clip from the Web Article https://support.office.com/en-us/article/Clip-from-the-Web-

b503dc7e-f320-4d7a-8546-1fb31123c308

Record Audio Article https://support.office.com/en-us/article/Record-audio-

d69dcbfe-1fd7-4930-9564-bbd83099e2c4?ui=en-US&rs=en-

US&ad=US

Capture the screen Article https://support.office.com/en-us/article/Capture-the-screen-

c763fc05-7bd8-4020-aebb-e0b054149d94?ui=en-US&rs=en-

US&ad=US

Insert a picture Article https://support.office.com/en-us/article/Insert-a-picture-56292764-

e25d-4712-91e6-f51c6a22453e?ui=en-US&rs=en-US&ad=US

Copy text from an image Article https://support.office.com/en-us/article/Copy-text-from-an-

image-0ab3ecd7-57e5-4372-a5bd-e684cb52c150?ui=en-

US&rs=en-US&ad=US

Insert a link Article https://support.office.com/en-us/article/Insert-a-link-

c505156d-148f-4160-8b00-27a6cb501d1d?ui=en-US&rs=en-

US&ad=US

Create a table Article https://support.office.com/en-us/article/Create-a-

table-211cf0fe-2116-4af8-92e8-608161494d66?ui=en-US&rs=en-

US&ad=US

Sort a Table Article https://support.office.com/en-us/article/Sort-a-

table-03f6e2c8-6482-470e-9670-343fa18a8d48?ui=en-US&rs=en-

US&ad=US

Convert a table to Excel Article https://support.office.com/en-us/article/Convert-a-table-to-Excel-

a24c39e2-32b6-4366-ad21-537e2a1675e8?ui=en-US&rs=en-

US&ad=US

Quick Start Guide for

OneNote

PDF https://support.office.com/en-us/article/Office-2016-Quick-Start-

Guides-25f909da-3e76-443d-94f4-6cdf7dedc51e

OneNote on Mac OS OneNote 2016 Basics PowerPoint https://docs.com/OfficeTraining/1862/onenote-2016-for-mac-

Reference Materials Page 82

Page 83: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

OneNote on Mac OS OneNote 2016 Basics PowerPoint https://docs.com/OfficeTraining/1862/onenote-2016-for-mac-

basics-training?c=3AM3U6

What is OneNote?

Use OneNote in the cloud

Get started with OneNote and notebooks

Add section and pages

Maximize your pages

Take notes

Record Audio

Capture the screen

Insert pictures

Copy text from images

Insert Links

Create Tables

Topics:

What's new in Office 2016 for

Mac?

Article https://support.office.com/en-us/article/What-s-new-and-improved-

in-Office-2016-for-Mac-44d5a464-3051-41b0-b44e-c6cee569f545?

ui=en-US&rs=en-US&ad=US

OneNote Quick Start Guide PDF https://support.office.com/en-us/article/Office-2016-for-Mac-Quick-

Start-Guides-5bccb480-0e5b-4b51-b072-66d3793ccad8

Get started with OneNote

2016 for Mac

Article https://support.office.com/en-us/article/Get-started-with-

OneNote-2016-for-Mac-d6bec487-285f-426e-be9d-58cb49eb1979

OneNote Quick Start Guide

Watch a video about OneNote

Learn basic tasks in OneNote

Look up OneNote keyboard shortcuts

Check for OneNote updates

Enable Accessibility options in OneNote

Download OneNote for your iPhone and iPad

Topics:

FAQ Article https://support.office.com/en-us/article/Frequently-Asked-

Questions-about-OneNote-2016-for-Mac-bf9bcd6a-b8ce-4d18-

a11f-ed1f596df3ed

OneNote on iOS How does OneNote for iPad

work?

Article https://support.office.com/en-us/article/How-does-OneNote-for-

iPad-work-808e6fc6-5ee8-4095-ae4c-b6ca8b9451a9

Common Scenarios Article https://support.office.com/en-us/article/Microsoft-OneNote-Help-

f44e5bcd-5203-4553-9de4-0c56e6500825?ui=en-US&rs=en-

US&ad=US

How do I sync the notebooks

on my computer with my

iPhone

Article https://support.office.com/en-us/article/How-do-I-sync-the-

notebooks-on-my-computer-with-my-

iPhone-74d823b2-1398-44b3-aba2-2cf74f4a494c

Share content from other

apps with OneNote for

iPhone

Article https://support.office.com/en-us/article/Share-content-from-other-

apps-with-OneNote-for-iPhone-or-iPad-f21123c3-2b5f-4fc6-

bc75-62fecd284824?ui=en-US&rs=en-US&ad=US

OneNote on Windows Phone Use OneNote Mobile for

Windows Phone

Article https://support.office.com/en-us/article/Use-OneNote-on-a-

Windows-Phone-203dd6b0-240b-46bf-b65c-1f0834bc697a?ui=en-

US&rs=en-US&ad=US

OneDrive Business for Windows What is OneDrive for Business Video https://support.office.com/en-us/article/What-is-OneDrive-for-

Business-187f90af-056f-47c0-9656-cc0ddca7fdc2

Store, Share and sync files for

OneDrive for Business

Article https://support.office.com/en-us/article/Store-sync-and-share-your-

work-files-OneDrive-for-Business-301817f6-9705-4525-

ba3d-79082029b195

Dragging and dropping files to OneDrive for Business

https://support.office.com/en-us/article/Dragging-and-

dropping-files-to-OneDrive-for-Business-

e2e0c53e-8707-4b9d-aa0d-d3cfcb792b72

Seeing your files from other devices

https://support.office.com/en-us/article/Seeing-your-files-

from-other-devices-fe48cf1e-d23c-4bb5-b274-f04e3d46539a

Saving and opening files https://support.office.com/en-

us/article/Saving-and-opening-files-f3c50490-e402-44cd-81f1-

d559fdc715fb

Syncing your files with your computer

https://support.office.com/en-us/article/Syncing-your-files-

with-your-computer-31e11d42-c3e4-443a-a5dd-9186bb6fdf3c

Managing your files in OneDrive for Business

https://support.office.com/en-us/article/Managing-your-files-

in-OneDrive-for-Business-1c53e2c1-950e-46fa-8611-

e07efcfb0565

Sharing files with others https://support.office.com/en-

us/article/Sharing-files-with-others-1441ccff-7d1d-4105-

bf62-84b720149a28

Topics Covered

OneDrive Business on Android

phone or tablet

Install and setup OneDrive on

an Android phone or tablet

Article https://support.office.com/en-us/article/Install-and-set-up-

OneDrive-on-an-Android-phone-or-tablet-b8ed509b-

c068-4ec8-8e69-60ffe8af23ce?ui=en-US&rs=en-US&ad=US

OneDrive Business for IPhone or

iPad

Working with your files on

your iPhone or iPad

Article https://support.office.com/en-us/article/Install-and-set-up-

OneDrive-on-your-iPhone-or-iPad-

c535c845-91ae-4f6a-81fd-5247cb7da0a4?ui=en-US&rs=en-

US&ad=US

OneDrive Business for Windows

Phone

Working with your files on

your Windows Phone

Article https://support.office.com/en-us/article/Set-up-OneDrive-for-

Business-on-your-Windows-Phone-519fa7ee-

a842-4f7e-9269-0f26d701505c?ui=en-US&rs=en-US&ad=US

Skype for Business for Windows Getting started with Skype Video https://support.office.com/en-us/article/Introducing-Skype-for-

Business-e705627e-8e94-4bae-ac8b-4ccea5a9c4c0?ui=en-

US&rs=en-US&ad=US

Explore Skype for Business Video https://support.office.com/en-us/article/Explore-Skype-for-

Business-8b7aecb2-bdf0-436b-894f-31af502e912b?ui=en-

US&rs=en-US&ad=US

Add a contact Video https://support.office.com/en-us/article/Add-a-contact-

f3f993dd-3cd8-49cb-a68c-6764ba23db4a?ui=en-US&rs=en-

US&ad=US

Check a contact's presence

and IM them

Video https://support.office.com/en-us/article/Check-a-contact-s-

presence-and-IM-them-9d0b09c3-8e5e-4db3-8077-263a2b120fe8?

ui=en-US&rs=en-US&ad=US

Change your picture Article https://support.office.com/en-us/article/Change-your-

picture-772fcd80-55a7-4196-bff7-1e3f172c8eb2?ui=en-US&rs=en-

US&ad=US

Lync is now Skype for

Business see What's new

Article https://support.office.com/en-us/article/Lync-is-now-Skype-for-

Business-%e2%80%94-see-what-s-new-aba02d7e-c801-4a82-bccd-

e7207240f612?ui=en-US&rs=en-US&ad=US

What's Skype for Business Video https://support.office.com/en-us/article/What-s-Skype-for-

Business-3a21eca4-434d-41f1-ab06-3d4a268573b7?ui=en-

Reference Materials Page 83

Page 84: Preferred Practices for Office 365 ProPlus Deployment...Deploying Office 365 ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the

Business-3a21eca4-434d-41f1-ab06-3d4a268573b7?ui=en-

US&rs=en-US&ad=US

Make and Receive a Skype for

Business video code

Article https://support.office.com/en-us/article/Make-and-receive-a-Skype-

for-Business-video-call-abf62493-670f-4b0d-b2cf-fe03b49caf42?

ui=en-US&rs=en-US&ad=US

Make a Skype for Business

call but use your PBX desk

phone for audio

Article https://support.office.com/en-us/article/Make-a-Skype-for-

Business-call-but-use-your-PBX-desk-phone-for-audio-6a316c11-

a05e-460c-b969-32ff0ad848e6?ui=en-US&rs=en-US&ad=US

Set up a Skype for Business

meeting in Outlook

Video https://support.office.com/en-us/article/Set-up-a-Skype-for-

Business-meeting-in-Outlook-b8305620-

d16e-4667-989d-4a977aad6556

Join a Skype for Business

Meeting

Video https://support.office.com/en-us/article/Join-a-Skype-for-Business-

meeting-3862be6d-758a-4064-a016-67c0febf3cd5

Calling into a meeting on

your mobile or other phone

Article https://support.office.com/en-us/article/Call-into-a-Skype-for-

Business-meeting-on-your-mobile-or-other-phone-9fc51fc3-

f201-49b1-b2d3-97fe6f9da238?ui=en-US&rs=en-US&ad=US

Setup an audio device for

Skype for Business

Video https://support.office.com/en-us/article/Set-up-an-audio-device-

for-Skype-for-Business-2533d929-9814-4349-8ae4-fca29246e2ff?

ui=en-US&rs=en-US&ad=US

Skype for Business on Windows

Phone

Skype for Business on

Windows Phone

Article https://support.office.com/en-us/article/Skype-for-Business-is-now-

on-Windows-Phone-6f48a22d-b064-4f2f-beab-25b4744af5c4

Quick Start Guides for Skype for

Business

Quick Start Guides for Skype

for Business

Article https://support.office.com/en-us/article/Quick-Start-Guides-about-

Skype-for-Business-bbb1dd15-3858-4081-9c28-8379020af66d?

ui=en-US&rs=en-US&ad=US

Audio setup and making calls

Contacts, presence and IM

Meetings

Video

Sharing and collaboration

Topics Covered

Skype for Business is now on

iOS

Skype for Business is now on

iOS

Article https://support.office.com/en-us/article/Skype-for-Business-is-now-

on-iOS-1a2cf653-955b-4329-b289-db7a67d32bfd

Skype for Business is now on

Android

Skype for Business in now on

Android

Article https://support.office.com/en-us/article/Skype-for-Business-is-now-

on-Android-59aacea2-cf3c-44c8-976a-9fd9353ba770

Skype Meeting Broadcast What is Skype Meeting

Broadcast

Article https://support.office.com/en-us/article/What-is-a-Skype-Meeting-

Broadcast-c472c76b-21f1-4e4b-ab58-329a6c33757d?ui=en-

US&rs=en-US&ad=US

Schedule a Skype Meeting

Broadcast Event

Article https://support.office.com/en-us/article/Schedule-a-Skype-Meeting-

Broadcast-c3995bc9-4d32-4f75-a004-3bc5c477e553?ui=en-

US&rs=en-US&ad=US

Manage a Skype Meeting

Broadcast Event

Article https://support.office.com/en-us/article/Manage-a-Skype-Meeting-

Broadcast-event-c7b98cbe-d168-4cf4-b87f-867707b25811

Publisher 2016 (Same material

as 2013) for Windows

Basic Tasks in Publisher Article https://support.office.com/en-us/article/Basic-tasks-in-

Publisher-0e5ed249-1927-433f-a35c-63beb8216fcf?ui=en-

US&rs=en-US&ad=US

Make the Switch to Publisher Article https://support.office.com/en-us/article/Make-the-switch-to-

Publisher-2013-bb151ab4-fc6f-48a7-932e-778da48aa7a4

Publisher Quick Start Guide PDF https://support.office.com/en-us/article/Publisher-2013-Quick-Start-

Guide-ea8023fe-5d0c-48e2-9401-b9d9b386dad8

Access 2016 (Same material as

2013)

Basic Tasks for an Access

desktop database

Article https://support.office.com/en-us/article/Basic-tasks-for-an-Access-

desktop-database-5ddb8595-497c-4366-8327-ae79d2abdc9c?

ui=en-US&rs=en-US&ad=US

Choose a template

Create a database from scratch

Add a table

Copy and paste data

Import or link to data

Organize data with the Table Analyzer

Topics Covered

Introduction to tables Article https://support.office.com/en-us/article/Introduction-to-

tables-78ff21ea-2f76-4fb0-8af6-c318d1ee0ea7

Introduction to queries Article https://support.office.com/en-us/article/Introduction-to-

tables-78ff21ea-2f76-4fb0-8af6-c318d1ee0ea7

Create an Access form Article https://support.office.com/en-us/article/Create-a-form-in-

Access-5d550a3d-92e1-4f38-9772-7e7e21e80c6b?ui=en-

US&rs=en-US&ad=US

Introduction to reports in

Access

Article https://support.office.com/en-us/article/Introduction-to-reports-in-

Access-e0869f59-7536-4d19-8e05-7158dcd3681c

Protect your data with backup

and restore process

Article https://support.office.com/en-us/article/Protect-your-data-with-

backup-and-restore-processes-96539a81-5984-4d56-99ca-

ee81f8d6356c

Access Quick Start Guide PDF https://support.office.com/en-us/article/Access-2013-Quick-Start-

Guide-aa404d26-ce42-4dd2-ac5e-51f9f39f7275

Visio - Nothing

Office Mobile Quick Start

Guides

Office Mobile Quick Start

Guides

PDF https://support.office.com/en-us/article/Office-Mobile-Quick-Start-

Guides-c957c048-00fa-4793-8b40-4f564f9d58c6?ui=en-US&rs=en-

US&ad=US

Word Mobile

Excel Mobile

PowerPoint Mobile

OneNote Mobile

Topics Covered

Reference Materials Page 84