This deserves its own blog post, but here’s what I do.
First, here’s the script that I use:
@ECHO OFF
IF /I NOT "%PROCESSOR_ARCHITECTURE%"=="amd64" (
IF /I NOT "%PROCESSOR_ARCHITEW6432%" == "amd64" GOTO 32BIT )
:64BIT
reg add "HKLM\Software\Microsoft\Office\15.0\ClickToRun\Configuration" /v
"updateurl" /t REG_SZ /d "%~dp0O365" /f /reg:64
"%PROGRAMFILES%\Microsoft Office 15\ClientX64\OfficeC2RClient.exe" /update user
updatetoversion=15.0.4631.1004
GOTO END
:32BIT
reg add "HKLM\Software\Microsoft\Office\15.0\ClickToRun\Configuration" /v
"updateurl" /t REG_SZ /d "%~dp0O365" /f
"%PROGRAMW6432%\Microsoft Office 15\ClientX64\OfficeC2RClient.exe" /update user
updatetoversion=15.0.4631.1004
GOTO END
:END
This should be placed in a source directory and the updated O365 C2R files
placed in a sub-directory called O365 (or whatever you want if you change the
script). Create a package for this directory and a program with this batch file
as the command-line. Set the package to run from DP (since you most likely
don’t want this to get cached down but you certainly could do that if you
wanted to). Deploy. Done.
J
From: [email protected] [mailto:[email protected]] On
Behalf Of Brian McDonald
Sent: Wednesday, November 18, 2015 7:49 AM
To: [email protected]
Subject: [mssms] Patching 0365
I have SCCM, and deploying Office 365. However each Office 365 client by
default reaches out to the internet to update, causing a lot of traffic. I have
found that Microsoft has an .admx file that will disable the automatic updating
of Office 365, and the following blog post of how to use SCCM to update clients
with Office 365.
http://blogs.technet.com/b/ouc1too/archive/2014/09/05/patching-office-365-with-configuration-manager-2012-or-how-i-learned-to-stop-worrying-and-love-the-click2rclient.aspx
. By reading the comments, this looks like it might be more hit and miss than
anything. I have also seen where you can use that .admx template to have
clients update from a UNC path, but that becomes a manual updating of that
path, and also the configuration of multiple GPOs and shares for all their
sites. None of these solutions seems good for a client with 500 machines.
Has anyone implemented a patch management solution for Office 365 for clients?
If so, can you share the details on how you did it?
Thanks,
Brian
