upgrade to office 365 proplus by sccm › office › step-by-step...page 5 upgrade to office 365...

Upgrade to Office 365 ProPlus by SCCM

Upgrade to Office 365 ProPlus


Index

1 Purpose of this document .................................................................................................... 3

2 Assumptions .............................................................................................................................. 3

3 Create and Distribute Office 365 ProPlus 2016 ............................................................ 5

3.1 Prepare the Office 365 ProPlus installation files to be deployed by Configuration Manager ........................... 5

3.2 Create an application for Office 365 ProPlus in Configuration Manager ............................................................. 7

3.3 Create a deployment type for the Office 365 ProPlus application in Configuration Manager .......................... 8

3.4 Distribute the Office 365 ProPlus application to distribution points in Configuration Manager .................... 11

4 Create and Distribute Office Scrubs ................................................................................ 12

4.1 Create Office Scrubs as a package .......................................................................................................................... 12

4.2 Distribute Office Scrub ............................................................................................................................................. 15

5 Create and Configure Custom Task Sequence ............................................................ 18

5.1 Create Task Sequence ............................................................................................................................................... 18

5.2 Configure Task Sequence ......................................................................................................................................... 21

5.3 Add Command Line .................................................................................................................................................. 22

5.4 Add Office 365 ProPlus 2016 to task Sequence .................................................................................................... 25

5.5 Deploy task sequence to a Device collection ........................................................................................................ 27

6 Deploy the Task Sequence to the client ........................................................................ 30

7 Managing Updates for Office 365 ProPlus ................................................................... 32

7.1 Managing Updates for SCCM 1602 or later ........................................................................................................... 32

7.1.1 Restart behaviour and client notifications for Office 365 updates ....................................................................................... 36

7.1.2 Add languages for Office 365 update downloads ................................................................................................................. 37

7.1.3 Change the update channel after you enable Office 365 clients to receive updates from Configuration Manager ...... 42

7.2 Managing Updates for SCCM 2012 R2 or without SCCM. ................................................................................... 43

7.2.1 High-level steps for a fully automated testing and deployment process............................................................................ 43

7.2.2 How to deploy updates for SCCM 2012 R2 ............................................................................................................................ 44


1 Purpose of this document

The main goal of this document to quickly Deploy Microsoft Office 365 ProPlus by System Center

Configuration Manager using the task sequence to remove the earlier version of office and deploy

the latest version of office 365 ProPlus 2016.

2 Assumptions

This document assumes that you already have a tenant on Microsoft online services, synchronized

to your on-premises Active Directory forest and a configured Office 365 ProPlus 2016 Application

at the existing System Center Configuration Manager.

In addition, you need to check the following concepts available:

Assumption Description

SCCM Server Version Applies to System Center 2012 R2 Configuration Manager or

Configuration Manager version 1602 or later.

SCCM Collections Collections in System Center 2012 Configuration Manager

provide you with the means to organize resources into

manageable units, which then enable you to create an

organized structure that logically represents the kinds of

tasks that you want to perform. Collections are also used to

perform Configuration Manager operations on multiple

resources at one time. The following table shows some

examples of how you might use collections in Configuration

Manager.

Available Here

Overview of the Office 2016

Deployment Tool

The Office 2016 Deployment Tool (ODT) is a command-line

tool that you can use to download and deploy Office 365

ProPlus to your client computers. The ODT gives you more

control over an Office installation: you can define which

products and languages are installed, how those products

should be updated, and whether or not to display the install

experience to your users.

Available Here

Deploying O365 ProPlus with SCCM you can also use that existing Configuration Manager

environment to deploy Office 365 ProPlus. By using

Configuration Manager, you can control which users and

computers get Office 365 ProPlus, where they get the

https://technet.microsoft.com/en-us/library/gg682177.aspx

https://support.office.com/en-us/article/Overview-of-the-Office-2016-Deployment-Tool-bb5b62d9-1168-47e9-9d54-15a958acfcca?ui=en-US&rs=en-US&ad=US#bkmk_downloadinstallationfiles


installation files from, and when the Office 365 ProPlus

installation occurs

Available Here

Task Sequence Task sequences in SCCM 2012 are used for applying images,

configuring windows, installing drivers, installing applications

and installing application packages.

Available Here

Office Scrubs A collection of useful PowerShell scripts to make deploying

Office 2016 and Office 365 ProPlus easier for IT Pros and

administrators Available Here

Automatic Deployment Rules You can automatically deploy software updates by adding

new software updates to an update group associated with an

active deployment or you can use an automatic deployment

rule (ADR). Typically, you will use ADRs to deploy monthly

software updates (generally known as Patch Tuesday

updates) and for managing definition updates. Available

Here.

https://support.office.com/en-us/article/Deploy-Office-365-ProPlus-with-System-Center-Configuration-Manager-4dd6a023-0a5d-4dc9-9bad-ff70e01840b8?ui=en-US&rs=en-US&ad=US

https://technet.microsoft.com/en-us/library/hh273490.aspx

https://github.com/OfficeDev/Office-IT-Pro-Deployment-Scripts/tree/master/Office-ProPlus-Deployment/Remove-PreviousOfficeInstalls

https://docs.microsoft.com/en-us/sccm/sum/deploy-use/automatically-deploy-software-updates


3 Create and Distribute Office 365 ProPlus 2016

3.1 Prepare the Office 365 ProPlus installation files to be

deployed by Configuration Manager

To get started, download the Office 2016 version of the Office Deployment Tool from the

Microsoft Download Center to a shared folder on your organization's network. Then, use the

Office Deployment Tool to download the Office 365 ProPlus installation files from the Internet to

the same shared folder.

Next, edit the configuration.xml, and specify the settings for how you want to install Office 365

ProPlus. The following example shows a configuration.xml that you can use to install the 32-bit,

English version of Office 365 ProPlus.

• Notes:

If the Customer Config Manager build id 1602 or later kindly keep the

OfficeMgmtCom= true, if the config Manager is 2012 or 2012 R2 remove the

OfficeMgmt value.

• we excluded the Groove app for one Drive for business to make the package updated

with the latest version of one drive for business sync client.

• We've made some slight changes to the names for Semi-Annual Channel. We've

changed "(Pilot)" to "(Targeted)" and we've removed the "(Broad)" designation from the

new name for Deferred Channel. These names will be aligned across Windows 10 and

Office 365 ProPlus feature update releases.

<Configuration>

<Add Channel=" Semi-Annual Channel" OfficeClientEdition="32"

OfficeMgmtCOM="True" >

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

<ExcludeApp ID="Groove"/>

</Product>

</Add>

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

</Configuration>

http://go.microsoft.com/fwlink/p/?LinkID=626065

https://support.office.com/en-us/article/download-the-Office-365-ProPlus-installation-files-bb5b62d9-1168-47e9-9d54-15a958acfcca#bkmk_downloadinstallationfiles

https://support.office.com/en-us/article/specify-the-settings-d3879f0d-766c-469c-9440-0a9a2a905ca8


It's important that you don't include the SourcePath attribute in the Add section of your

configuration.xml file. That's because Configuration Manager copies the installation files for an

application into a folder under the Configuration Manager client cache folder, and the name of

that subfolder is different for each computer. Because the folder name is different for each

computer, you can't specify a SourcePath that will work for every computer that you're deploying

Office 365 ProPlus to. Instead, leave out the SourcePath attribute. When a SourcePath isn't

specified, the Office Deployment Tool automatically looks for the Office 365 ProPlus installation

files in the same folder that the Office Deployment Tool is located. That's why we're including the

Office Deployment Tool, the configuration.xml, and the Office 365 ProPlus installation files

together in the same shared folder.

New name Old name

Monthly Channel Current Channel

Semi-Annual Channel (Targeted) First Release for Deferred Channel

Semi-Annual Channel Deferred Channel


3.2 Create an application for Office 365 ProPlus in Configuration

Manager

The next step is to create an application in Configuration Manager. An application contains the

files and information that Configuration Manager needs to deploy software to a user's

computer.

To create an application

1. In the Configuration Manager console, choose Software Library > Application

Management > Applications.

2. On the Home tab, in the Create group, choose Create Application.

3. On the General page of the Create Application Wizard, select Manually specify the

application information, and then choose Next.

4. On the General information page, enter a name for the application, enter any optional

information, and then choose Next.

5. On the Application Catalog page, provide the information that's appropriate for your

environment, and then choose Next.

6. On the Deployment Types page, choose Next. We'll add a deployment type later.

7. On the Summary page, review the settings you've chosen, and then choose Next to create

the application.

8. After the application is created, on the Completion page, choose Close.

https://go.microsoft.com/fwlink/p/?LinkId=535035


3.3 Create a deployment type for the Office 365 ProPlus

application in Configuration Manager

An application in Configuration Manager must contain at least one deployment type. The

deployment type contains the installation files for a software package as well as rules that

specify when and how the software is deployed.

For the Office 365 ProPlus application, the deployment type includes the following:

• The path of the shared folder that contains the Office Deployment Tool, your

configuration.xml file, and the Office 365 ProPlus installation files that you

downloaded from the Internet. For example, \\server1\share1.

• The command line that gets the Office Deployment Tool to start the installation of

Office 365 ProPlus.

• A detection method, which Configuration Manager uses to determine if Office 365

ProPlus is already installed on the user's computer.

To create a deployment type



2. Select the Office 365 ProPlus application, and then on the Home tab, in the

Application group, choose Create Deployment Type.

3. On the General page of the Create Deployment Type Wizard, in the Type list, select

Script Installer, and then choose Next.

4. On the General Information page, enter a name for the deployment type, enter any

optional information, and then choose Next.

5. On the Content page, do the following:

o In the Content-location box, enter the network share where you put the

Office Deployment Tool, your configuration.xml file, and the Office 365

ProPlus installation files that you downloaded from the Internet.

o In the Installation program box, enter the following text: setup.exe

/configure configuration.xml

After you enter this information, choose Next.

6. On the Detection Method page, choose Add Clause.




7. There are 2 methods for the detection rules Method 1 to use the Registry type or to

use the File system type.

8. In the Detection Rule 1 dialogue box, do the following:

o In the Setting Type list, select Registry.

o In the Hive list, select HKEY_LOCAL_MACHINE.

o In the Key box, enter the following text:

Software\Microsoft\Windows\CurrentVersion\Uninstall\O365ProPlusRet

ail - en-us

o Select the Use (Default) registry key value for detection check box.

9. In the Detection Rule 2 Dialog box, do the following in case method 1 didn’t work

with you.

o In the Setting Type list, select File System.

o In the Type list, select File.

o In the Path box, enter the following text: C:\Program Files (x86)\Microsoft

Office\root\Office16

o In the File or Folder Name box, type: WINWORD.EXE.


10. After you enter this information, choose OK, and then on the Detection Method

page, choose Next.

11. On the User Experience page, in the Installation behavior list, select Install for

system, and then choose Next.

12. If you want to specify any requirements or dependencies for the deployment type,

choose Next to go through those pages in the wizard. Otherwise, choose Summary.

13. On the Summary page, review the settings you've chosen, choose Next, and then

choose Close.


3.4 Distribute the Office 365 ProPlus application to distribution

points in Configuration Manager

After you create the Office 365 ProPlus application and configure its deployment type, the

next step is to copy all the files needed by the application to the appropriate distribution

points in your Configuration Manager environment.

To distribute the application to distribution points



2. Select the Office 365 ProPlus application, and then on the Home tab, in the

Deployment group, choose Distribute Content.

3. On the General page of the Distribute Content Wizard, choose Next, and then on

the Content page, choose Next.

4. On the Content Destination page, choose Add > Distribution Point, select the

appropriate distribution points, and then choose OK. Then, select Next.

5. On the Summary page, review the settings you've chosen, and then choose Next.

6. On the Confirmation page, check that the content was successfully assigned to the

distribution points, and then choose Close.

7. To monitor the distribution, go to Monitoring > Distribution Status > Content

Status.

8. Select the application, and then view the Completion Statistics.




4 Create and Distribute Office Scrubs

The Offscrub vbs scripts can be used to automate the removal of Office products. The scripts will

uninstall the existing Office products regardless of the current health of the installation. The

Remove-PreviousOfficeInstalls.ps1 script will determine which version of Office is currently

installed and will call the appropriate Offscrub vbs script to remove the Office products

installations.

The Offscrub vbs files included are:

• OffScrub03.vbs - Used to remove Office 2003 products.



• OffScrub_O15msi.vbs - Used to remove Office 2013 MSI products.

• OffScrub_O16msi.vbs - Used to remove Office 2016 MSI products.

• OffScrubc2r.vbs - Used to remove Click-To-Run products.

4.1 Create Office Scrubs as a package

1 In the Configuration Manager console, click Software Library.

2 In the Software Library workspace, expand Application Management, and then click

Packages.

3 In the Home tab, in the Create group, click Create Package.

4 On the Package page of the Create Package and Program Wizard, specify the following

information:

• Name: Specify a name for the package with a maximum of 50 characters.

• Description: Optionally specify a description for this package with a maximum of

128 characters.

• Manufacturer: Optionally specify a manufacturer name to help you identify the

package in the Configuration Manager console. This name can be a maximum of 32

characters.

• Language: Optionally specify the language version of the package with a maximum

of 32 characters.

• Version: Optionally specify a version number for the package with a maximum of 32

characters.

• This package contains source files - This setting indicates whether the package

requires source files to be present on client devices. By default, this check box is

cleared, and Configuration Manager does not use distribution points for the

package. When this check box is selected, distribution points are used.

• Source folder: If the package contains source files, click Browse to open the Set

Source Folder dialog box and specify the location of the source files for the package.


5 On the Program Type page of the Create Package and Program Wizard, select Standard

Program, and then click Next.

6 On the Standard Program page of the Wizard, specify the following information like the

below Picture:


7 On the Requirements page of the Create Package and Program Wizard, leave it to the

default.

8 On the Summary page of the Wizard, review the actions that will be taken, then complete

the Wizard.

9 Optionally, verify that the new package and program is displayed in the Packages node of

the Software Library workspace.


4.2 Distribute Office Scrub

1 In the Configuration Manager console, click Software Library.

2 In the Software Library workspace, select one of the following steps for the type of content

that you want to distribute:

3 Packages: Expand Application Management, click Packages, and then select the packages

that you want to distribute

4 On the Home tab, in the Deployment group, click Distribute Content. The Distribute

Content Wizard opens.

5 On the General page, verify that the content listed is the content that you want to

distribute, choose whether you want Configuration Manager to detect content

dependencies that are associated with the selected content and add the dependencies to

the distribution, and then click Next.


6 On the Content Destination page, click Add, Distribution Point: Select an existing

distribution point, and then click OK.

7 On the Summary page, review the settings for the distribution before you continue. To

distribute the content to the selected destinations, click Next.

8 The Progress page displays the progress of the distribution.


9 The Completion page displays whether the content was successfully assigned to the points.

10 Make sure that the content status is a success.


5 Create and Configure Custom Task Sequence

5.1 Create Task Sequence

1 In the Configuration Manager console, navigate to System Center Configuration Manager

/ Software Library / Operating System Deployment / Task Sequences.


2 To start the New Task Sequence Wizard, right-click the Task Sequences node, and then

click New/Task Sequence, On the Create a New Task Sequence page, select Create a

new custom task sequence, and then click Next.


3 On the Task Sequence Information page, specify descriptive information about the

custom task sequence, type the Task sequence name, Version, and a Description in the

spaces provided.


4 Don’t specify the boot image.

5 To complete the creation of the new custom task sequence, on the Summary page, click

Next.

6 To confirm that the new task sequence created using the properties specified, review the

confirmation on the Confirmation page.

5.2 Configure Task Sequence

1 To edit or add or remove steps to the custom task sequence, right-click the task sequence,

and then click Edit.


5.3 Add Command Line

1 To add a new task sequence step, click Add, Select General, Select Run Command Line.


2 Fill the data in the below table.

At the command line: Cscript.exe .\OffScrub10.vbs ALL /Q /NoCancel

Check the Disable 64-bit file system redirection.

Select package and then Browse and select the Office scrub from the list of packages.


3 Select options tab, select continue error.


5.4 Add Office 365 ProPlus 2016 to task Sequence

1 To add a new task sequence step, click Add, Software, Install Application.


2 Browse and select Office 365 ProPlus 2016 application.


5.5 Deploy task sequence to a Device collection

1 From the Home page, select the Created task sequence and click deploy.

2 Under Select collection, change the view to be Device Collections, select the test device

collection.


3 At Deployment Setting, make sure that choice is available not required this to avoid any

issues to the rest of the devices in the collection in the worst case. After the success of the

pilot devices, you can change the deployment from available to required.


4 Complete the wizard until the completion page.


6 Deploy the Task Sequence to the client

1 Open client Program and features from the control panel to make sure that the Office

Professional Plus 2010.

2 Open Software Center to check the task sequence availability. If it didn’t appear open the

configuration manager application from the control panel, select action and run the

application deployment cycle.

3 Select the task sequence click Install.


4 Monitor the task sequence it will do the uninstallation of the previous version office which is

Office ProPlus 2010 in our case.

5 After the installation is successful check the program and features again, you will find the

latest version of Office is installed.


7 Managing Updates for Office 365 ProPlus

7.1 Managing Updates for SCCM 1602 or later

1. Requirements for using Configuration Manager to manage Office 365 client updates: -

To enable Configuration Manager to manage Office 365 client updates, you need the following:

• System Center Configuration Manager, update 1602 or later.

• An Office 365 client – Office 365 ProPlus, Visio Pro for Office 365, Project Online Desktop

Client, or Office 365 Business.

• Supported channel version for Office 365 client. For more details, see Version and build

numbers of update channel releases for Office 365 clients

• Windows Server Update Services (WSUS) 4.0.

You can't use WSUS by itself to deploy these updates. You need to use WSUS in

conjunction with Configuration Manager.

• On the computers that have the Office 365 client installed, the Office COM object is

enabled.

2. Enable Configuration Manager to receive Office 365 client package notifications: -

To start, you need to configure Configuration Manager to receive notifications when Office 365

client update packages are available. To do that, use the following steps:

• In the Configuration Manager console, choose Site Configuration > Sites, and then

select your site server.

• On the Home tab, in the Settings group, choose Configure Site Components, and then

choose Software Update Point.

• In the Software Update Point Component Properties dialogue box, do the following:

o On the Products tab, under Office, select Office 365 Client.

o On the Classifications tab, select Updates.

o You can have other check boxes selected in the Products and Classifications

tabs. But, Office 365 Client and Updates need to be selected for Configuration

Manager to receive notifications when Office 365 client update packages are

available.

• Next, synchronize software updates. If you don't do that, you won't see the updates in

the console and the updates won't be available to deploy. For more information about

https://support.office.com/en-us/article/Version-and-build-numbers-of-update-channel-releases-for-Office-365-clients-ae942449-1fca-4484-898b-a933ea23def7

https://support.office.com/en-us/article/Version-and-build-numbers-of-update-channel-releases-for-Office-365-clients-ae942449-1fca-4484-898b-a933ea23def7

https://support.office.com/en-us/article/Manage-updates-to-Office-365-ProPlus-with-System-Center-Configuration-Manager-b4a17328-fcfe-40bf-9202-58d7cbf1cede#bkmk_enableclient

https://support.office.com/en-us/article/Manage-updates-to-Office-365-ProPlus-with-System-Center-Configuration-Manager-b4a17328-fcfe-40bf-9202-58d7cbf1cede#bkmk_enableclient


how to synchronize software updates, see Introduction to software updates in System

Center Configuration Manager.

3. Enable Office 365 clients to receive updates from Configuration Manager

For Configuration Manager to be able to manage Office 365 client updates, an Office COM

object needs to be enabled on the computer where Office is installed. The Office COM

object takes commands from Configuration Manager to download and install client updates.

You can enable the Office COM object by using either of the following methods: the Office

Deployment Tool or Group Policy.

Method 1: Use Office Deployment Tool to enable Office 365 clients to receive updates

from Configuration Manager

You can use the latest version of the Office Deployment Tool to configure Office 365 clients

to receive updates from Configuration Manager.

To configure this capability, use a text editor, such as Notepad, to modify the

configuration.xml file for the Office Deployment Tool. In the Add element, include the

OfficeMgmtCOM attribute and set its value to True, as seen in the following example.

<Configuration>

<Add Channel=" Semi-Annual Channel " OfficeClientEdition="32"

OfficeMgmtCOM="True" >

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

<ExcludeApp ID="Groove"/>

</Product>

</Add>

<Updates Enabled="True" />

</Configuration>

https://docs.microsoft.com/en-us/sccm/sum/understand/software-updates-introduction

https://docs.microsoft.com/en-us/sccm/sum/understand/software-updates-introduction

http://go.microsoft.com/fwlink/p/?LinkID=626065


Also, we recommend that you set the value of the Enabled attribute to True in the Updates

element. If you set the value of the Enabled attribute to False, Office 365 clients can still

receive updates from Configuration Manager. But, users won't see any notifications when

updates are pending.

Then, use the Office Deployment Tool and the configuration.xml file to install, for example,

Office 365 ProPlus. If you've already installed Office 365 clients to your users, you can run

the Office Deployment Tool with the configuration.xml on those computers to update the

configuration. But, a better choice to configure computers that are already deployed might

be Group Policy.

Method 2: Use Group Policy to enable Office 365 clients to receive updates from

Configuration Manager

You can enable Configuration Manager to manage Office 365 client updates on specific

computers by using Group Policy. This does the same thing as setting the OfficeMgmtCOM

attribute to True in the configuration.xml file used by the Office Deployment Tool. But, with

Group Policy, you can apply this setting to multiple computers, an organizational unit (OU), or

a domain.

To use Group Policy to enable this capability, you do the following:

• Download and install the Office 2016 Administrative Template files (ADMX/ADML) from

the Microsoft Download Center.

• Enable the Office 365 Client Management policy setting. You can find this policy setting

under Computer Configuration\Policies\Administrative Templates\Microsoft Office 2016

(Machine)\Updates.

• After you deploy Office 365 apps, you can create automatic deployment rules to maintain

the apps. To create an automatic deployment rule for Office 365 apps, click Create an ADR

from the Office 365 Client Management dashboard, and select Office 365 Client when you

choose the product. For more information, see Automatically deploy software updates

https://www.microsoft.com/download/details.aspx?id=49030

https://docs.microsoft.com/en-us/sccm/sum/deploy-use/automatically-deploy-software-updates


Contents of the Office 365 client update package for WSUS

The update package that Microsoft publishes to WSUS only appears in the WSUS catalogue.

It doesn't contain a copy of the updated version of Office that's on the Office CDN. Instead, it

contains information that Configuration Manager needs to be able to download and distribute

the updated version of Office.

The package contains a file named noop.exe. But, that file doesn't contain any code and

shouldn't be downloaded or run.

For each update release there are different packages for each architecture and for each update

channel. For example, for the May update release, there is a package for the 32-bit edition of

the Monthly Channel and a package for the 64-bit edition of the Monthly Channel. In June,

there will be two new packages for Monthly Channel, one for each architecture. The packages

contain information so that Configuration Manager knows which packages are more recent

than other packages. For example, that the June package supersedes the May package.

There aren't separate packages for the different Office 365 clients. For example, an update

package for the 32-bit edition of the Monthly Channel has information about the Office 365

ProPlus, Visio Pro for Office 365, Project Online Desktop Client, and Office 365 Business clients.


7.1.1 Restart behaviour and client notifications for Office 365 updates

When you deploy an update to an Office 365 client, the restart behaviour and client notifications

are different depending on which version of Configuration Manager you have. The following table

gives information about the end user experience when the client receives an Office 365 update:

Configuration

Manager version End-user experience

Prior to 1610 A restart flag is set and the update is installed after the computer

restarts.

1610 Office 365 apps are shut down without warning before installing

the update

1610 with update

1702

A restart flag is set and the update is installed after the computer

restarts.

1706 The client receives pop-up and in-app notifications, as well as a

countdown dialogue, prior to installing the update.


7.1.2 Add languages for Office 365 update downloads

Beginning in Configuration Manager version 1610, you can add support for Configuration

Manager to download updates for any languages supported by Office 365, regardless of whether

they are supported in Configuration Manager.

Important

Configuring additional Office 365 update languages is a site-wide setting. After you add the

languages using the following procedure, all Office 365 updates are downloaded in those

languages, as well as the languages that you select on the Language Selection page in the

Download Software Updates or Deploy Software Updates wizards.

Use the following procedure on the software update point at the central administration site or

stand-alone primary site.

1. From a command prompt, type wbemtest as an administrative user to open the Windows

Management Instrumentation Tester.

2. Click Connect, and then type root\sms\site_<siteCode>.

3. Click Query, and then run the following query: select * from SMS_SCI_Component where

componentname ="SMS_WSUS_CONFIGURATION_MANAGER"


4. In the results pane, double-click the object with the site code for the central administration

site or stand-alone primary site.

5. Select the Props property, click Edit Property, and then click View Embedded.


7.1.3 Change the update channel after you enable Office 365 clients to

receive updates from Configuration Manager

To change the update channel after you enable Office 365 clients to receive updates from

Configuration Manager, use group policy to distribute a registry key value change to Office 365

clients. Change the

KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration\CDNBase

Url registry key to use one of the following values:

Monthly Channel:

CDNBaseUrl = http://officecdn.microsoft.com/pr/492350f6-3a01-4f97-b9c0-c7c6ddf67d60

Semi-Annual Channel:

CDNBaseUrl = http://officecdn.microsoft.com/pr/7ffbc6bf-bc32-4f92-8982-f9dd17fd3114

Monthly Channel (Targeted):

CDNBaseUrl = http://officecdn.microsoft.com/pr/64256afe-f5d9-4f86-8936-8840a6a4f5be

Semi-Annual Channel (Targeted):

CDNBaseUrl = http://officecdn.microsoft.com/pr/b8f9b850-328d-4355-9145-c59439a0c4cf


7.2 Managing Updates for SCCM 2012 R2 or without SCCM.

In case you do have an earlier version of SCCM or you don’t have SCCM and you need to Manage

updates let us follow the below Major Steps.

The benefit of this approach is that regardless of what changes implemented in an Office build,

the steps you are taking to mitigate the risk of introducing those changes are consistent. This will

enable your organization to quickly (and cheaply!) adopt changes including typical monthly

builds, newer Service Packs, or even major versions of Office 365 ProPlus. This positions you to

adopt change at a faster pace, increasing your company’s agility while ensuring your cost and risk

minimized and process quality is consistent.

7.2.1 High-level steps for a fully automated testing and deployment

process

Testing and Update Process Overview: -

Here are the high-level steps for a fully automated testing and deployment process:

1. Find a “testing” group.

2. Configure testing group to get their updates from an internal source.

3. Configure all others to get their updates from a different internal source.

4. Update the testing source after every Patch Tuesday.

5. Have your testing group use Office.

6. Update the production testing source 2-3 weeks later.

7. Enable a back out strategy.

Testing results: -

The above sample testing and update process provide the outcomes:

• A zero-touch approach which uses automation.

• Reduced administrative and manual testing effort.

• A consistent process which can lead to higher quality of the process’s result.

• A 2-3-week window for testing.

• Automatic deployment into production if no issues arise.

• An “Opt-out” mechanism.


7.2.2 How to deploy updates for SCCM 2012 R2

In the below hyperlinks, you will be able to find the step by step guide on how to manage your

updates with the correct sequence.

Reference Articles: -

1. Choose how to manage updates to Office 365 ProPlus

2. Configure update settings for Office 365 ProPlus

3. Managing Updates for Office 365 ProPlus – Part 1

4. Managing Updates for Office 365 ProPlus – Part 2

https://support.office.com/en-us/article/Choose-how-to-manage-updates-to-Office-365-ProPlus-e486afce-ad31-4889-87a4-28796751bb86?ui=en-US&rs=en-US&ad=US

https://support.office.com/en-us/article/Configure-update-settings-for-Office-365-ProPlus-a073ea21-62ed-40ef-8405-fd287f7d0b11?ui=en-US&rs=en-US&ad=US

https://blogs.technet.microsoft.com/office_resource_kit/2014/01/21/managing-updates-for-office-365-proplus-part-1/

https://blogs.technet.microsoft.com/office_resource_kit/2014/01/28/managing-updates-for-office-365-proplus-part-2/

upgrade to office 365 proplus by sccm › office › step-by-step...page 5 upgrade to office 365...

Documents