Follow by Email

Monday, 21 November 2016

How to Deploy Office 365 via SCCM 2012/1511/1606

Kindly take note before you start the Office 365 deployment.

· You can't mix 64-bit and 32-bit versions of Office and will have to choose one or the other.

· You can mix versions such as Office 2010 and either Office 2013 or Office 2016 as long as both are either 32-bit or 64-bit.

· To switch from 32-bit to 64-bit, you'll have to uninstall the 32-bit version and then install the 64-bit version. Likewise, to switch from 64-bit to 32-bit, you’ll need to uninstall the 64-bit version and then install the 32-bit version.

Sources from :- https://support.office.com/en-US/client/results?Shownav=true&lcid=1033&ns=OCSAC2RClickToRun&version=16&omkt=en-US&ver=16&helpid=%225-BOOTSTRAPPER_PREREQ-SxS_32_over_64%22&app=webviewABE27C04-8E33-42CC-861A-F0F694C830B6

Version and build numbers of update channel releases for Office 365 clients

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

Understanding of O365 Updates

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

Update channel

Primary purpose

How often updated with new features

Default update channel for the following products

Current Channel

Provide users with the newest features of Office as soon as they're available.

Monthly

Visio Pro for Office 365

Project Online Desktop Client

Office 365 Business, which is the version of Office that comes with some Office 365 plans, such as Business Premium.

Deferred Channel

Provide users with new features of Office only a few times a year.

Every four months

Office 365 ProPlus

First Release for Deferred Channel

Provide pilot users and application compatibility testers the opportunity to test the next Deferred Channel.

Every four months

None

Update channel

Feature updates

Security updates

Non-security updates

Current Channel

Monthly

Monthly

Monthly

Deferred Channel

Every four months

Monthly

Every four months

First Release for Deferred Channel

Every four months

Monthly

Monthly

Configure the update channel to be used by Office 365 ProPlus

Deferred Channel is the default update channel for Office 365 ProPlus. But you can configure an Office 365 ProPlus installation to use Current Channel or First Release for Deferred Channel. Also, not all users in your organization have to be configured the same. For example, you might do the following:

  • Provide a group of pilot users with Current Channel, so they can try out the new features of Office as they become available.
  • Provide your finance department, which has several key line-of-business applications, with Deferred Channel.
  • Provide your application compatibility testers with First Release for Deferred Channel so that they can test that the finance applications will work with the next Deferred Channel release.

To configure the update channel for an Office 365 ProPlus installation, you can use the latest version of the Office Deployment Tool or use the Group Policy Administrative Templates files (ADMX/ADML) for Office 2016.

Enable Office 365 Client Management via Group Policy

If you use the Office Deployment Tool, you can use the Channel attribute in the configuration.xml file. The Channel attribute can be specified in the Add element or the Update element. The relevant values are Current, Deferred, and FirstReleaseDeferred. For example, if you want to download and install the Current Channel of Office 365 ProPlus, your configuration.xml file would look like the following example.

<Configuration>

<Add SourcePath="\\server01\office" OfficeClientEdition="32" Channel="Current">

<Product ID="O365ProPlusRetail" >

<Language ID="en-us" />

</Product>

</Add>

</Configuration>

The name of the Group Policy setting is Update Channel. You can find this policy setting under Computer Configuration\Administrative Templates\Microsoft Office 2016 (Machine)\Updates. The relevant choices when you enable the Group Policy setting are Current, Deferred, and FirstReleaseDeferred.

You can also provide users with First Release for Deferred Channel by selecting them for the First Release program for Office 365. If you do this, those users can install First Release for Deferred Channel directly from the Software page in the Office 365 portal.

Downloads O365 Installers from Cloud

Requirement

1.Download.xml ( To Download Office 365)

2.Configuration.xml (To Install Office 365 with customization configuration files)

3.Uninstall.xml (To Uninstall Office 365)

4.Setup.exe (To Execute the xml file either download or install)

Create two folders at below :-

1) O365x86

2) O365x64

Download the Office 2016 Deployment Tool and extract to two folders.

Office 2016 Deployment Tools url :-

https://www.microsoft.com/en-us/download/details.aspx?id=49117

Creating Download.xml files for download office 365

Copy and paste to notepad and save as DownO365x86.xml for download the office 365 32 bits version. Save it to the o365x86 folders.

For 32bit Office

<Configuration>

<Add OfficeClientEdition="32">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Product>

</Add>

</Configuration>

Copy and paste to notepad and save as DownO365x64.xml for download the office 365 64 bits version. Save it to the o365x64 folders.

For 64bit Office

<Configuration>

<Add OfficeClientEdition="64">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Product>

</Add>

</Configuration>

Copy and Paste to notepad and save as Updatesource0365.bat to run for download the Latest O365 installer

For 32 bit and save it to o365x86 folders

@Echo OFF

Set here=%~dp0%

 

ECHO Creating Dumming Files before running Setup for Office 2016 ...

Pushd %here%

if not exist " Office" md "Office" >nul

if not exist "Office\Data" md "Office\Data" >nul

echo This file will be replaced automatically during first download.>Office\Data\v32.cab

echo This file will be replcaed automatically during first download.>Office\Data\v64.cab

 

ECHO Starting Download of Office 2016 Setup files now....

setup.exe /download downO365x86.xml

popd

For 64 bit and save it to o365x64 folders

@Echo OFF

Set here=%~dp0%

 

ECHO Creating Dumming Files before running Setup for Office 2016 ...

Pushd %here%

if not exist " Office" md "Office" >nul

if not exist "Office\Data" md "Office\Data" >nul

echo This file will be replaced automatically during first download.>Office\Data\v32.cab

echo This file will be replcaed automatically during first download.>Office\Data\v64.cab

 

ECHO Starting Download of Office 2016 Setup files now....

setup.exe /download downO365x64.xml

popd

You can execute the Updatesource0365.bat from O365x86 and O365x64 folders.It will download the O365 Installers.

Optional step :- you can also use Office 365 XML Editor to generate the xml files.

Url:- https://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.html

Preparing the Configuration.xml

Office 365 64BitsConfiguration.xml

Copy and paste to notepad and save as Configuration.xml for install office 365 64 bits version. Save it to the o365x64 folders.

Change those highlighted word accordingly

<Configuration>

<Add OfficeClientEdition="64" Version="16.0.7466.2038">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Product>

</Add>

<Logging Level="Standard" Path="C:\Windows\Temp" />

<Updates Enabled="True" Branch="Current" UpdatePath="\\SCCM2016\O365Updates"/>

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

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

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

</Configuration>

Office 365 32BitsConfiguration.xml

Copy and paste to notepad and save as Configuration.xml for install office 365 32 bits version. Save it to the o365x86 folders.

Change those highlighted word accordingly

<Configuration>

<Add OfficeClientEdition="32" Version="16.0.7466.2038">

<Product ID="O365ProPlusRetail">

<Language ID="en-us" />

</Product>

</Add>

<Logging Level="Standard" Path="C:\Windows\Temp" />

<Updates Enabled="True" Branch="Current" UpdatePath="\\SCCM2016\O365Updates"/>

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

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

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

</Configuration>

Command line to run setup.exe /configure configuration.xml

Preparing the Uninstall.xml

Office 365 64BitsUninstall.xml

Copy and paste to notepad and save as Uninstall.xml for Uninstall office 365 64 bits version. Save it to the o365x64 folders.

<Configuration>

<Remove All="TRUE" />

<Logging Level="Standard" Path="C:\Windows\Temp" />

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

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

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

</Configuration>

 

Office 365 32BitsUninstall.xml

Copy and paste to notepad and save as Uninstall.xml for Uninstall the office 365 32 bits version. Save it to the o365x86 folders.

<Configuration>

  <Remove All="TRUE" />

  <Logging Level="Standard" Path="C:\Windows\Temp" />

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

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

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

</Configuration>

Command line to run setup.exe /configure uninstall.xml

Creating O365 Packages for X86 and X64 version

Navigate to Software Library\Overview\Application Management\Applications,

Right Click and Click on Create Application.

Under General tab, Select Manually specify the application information and click on Next.

Under General information tab, Key in the Name Publisher and Version and click on Next.

Click on Browse and point to Setup.exe to getting the office icons and click on Next.

Under Deployment Types tab, Click on Add button and Click on Next.

Under General tab, Select Script Installer and manually and click on Next.

Under General Information tab, Key in the Name and Click on Next.

Under Content tab, Key in the content location Path, Install and Uninstall as below :-

Content location = Office 365 location path.

Installlation Program = setup.exe /configure configuration.xml

Uninstall program = Setup.exe /configure uninstall.xml

Under Detection Method tab and Detection Rule configure as below :-
Setting Type :- File System

For Office 365 x86

Type:- File
Path:- %ProgramFiles (x86)%\Microsoft Office\root\Office16\
File or Folder name : winword.exe
Select the file system setting must satisfy the following rule
Property = Version
Operator = Greater than or equal to (Not using equal because allowing office to be updated)
Value = The version number you downloaded (by the time I’m using 16.0.7466.2038)

For Office 365 x64

Type:- File
Path:- %ProgramFiles%\Microsoft Office\root\Office16\
File or Folder name : winword.exe
Select the file system setting must satisfy the following rule
Property = Version
Operator = Greater than or equal to (Not using equal because allowing office to be updated)
Value = The version number you downloaded (by the time I’m using 16.0.7466.2038)

Under Detection Method tab, click on Next.

Under User Experience tab, follow the setting above and click on Next.

Under Requirements tab, Choose Operating System that support this installers and click on Next.

You are successfully created Office 365 Packages for 32 bits version , please repeat the same steps to create Office 365 packages for 64 bits version.

Distribute content

Don’t Forget to distribute content to the distribution point after finish created the packages.

Deployment

You can create Office 365 collections and target to deploy to those machines.

Scenario :-

I have Windows 7 64 bits system with running on Microsoft Office 2013 x86 version.

For Office 2013 x86 version you must use Office 365 32 bit version .

For office 2013 x64 version , you must use Office 365 64 bits version.

Below are the computers that with office 2013 x86 version installed.

Troubleshooting

You can always check on c:\Windows\Temp , there is the log files that return , why the office fail to install.

Uninstall Office

You can refer to below blogs to uninstall those office version.

http://www.deploymentmadscientist.com/2016/02/08/deploying-microsoft-office-2016-removing-old-versions/

No comments:

Post a Comment