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
84
Embed
Preferred Practices for Office 365 ProPlus Deployment · PDF fileThe Preferred Practices for Office ... Determine the deployment method to use for Office 365 ProPlus Deployment options
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
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
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.
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•
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?
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
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.
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
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?
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
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
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
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:
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.
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
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
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
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
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
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
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?
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:
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
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:
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
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
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.
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:
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
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
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
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
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.
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
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:
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:
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
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
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
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
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
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.
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
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
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