The application and updates in the Office 365 Client Updater package will need to be stored on a local file server. On that file server, you should create 2 shares, one which will store the updates (in this example we’ll call it Updates) and another which will store the log files (in this example we’ll call it Logs).
You should give Everyone Read Access to the Updates share and Full Access to the Logs share (with the logs centrally stored, you’ll be better able to track the install progress).
After downloading the Office 365 Client Updater package, you should extract the contents to the Updates share. There should be 18 files in total and directory called Lync Install.
When you download files from the Internet, they maybe blocked by Windows. To unblock the files, you must go to the properties of each file, and if there is an Unblock button, click it to allow the file to execute. You should do this on each of the files in the Updates share.
The zip file contains 2 installers. The default installupdates-1.0.exe, which is in the root directory when you extract the files, does not install Lync. If you want to install Lync with the updates, then you need to replace the default installupdates-1.0.exe in the root directory with the installupdates-1.0.exe contained in the Lync Install directory.
In addition to changing the installupdates-1.0.exe, you need to download the 32 and 64 bit versions of the Lync install program to the share which contains the other updates. Since both the 32 and 64 bit versions of the installer have the same file name, you must rename them after they are downloaded.
The 32 bit installer must be renamed LyncSetup32.exe
The 64 bit installer must be renamed LyncSetup64.exe
The installer will automatically download the appropriate version to the client system and run the Lync install without user interaction.
If you are on BPOS and using Communicator, installing Lync will uninstall Communicator.
By default the installupdates.bat file looks like:
\\fileserver\updates\installupdates-1.0.exe /VERYSILENT /SUPPRESSMSGBOXES /LOG=\\fileserver\logs\%computername%-setup.log /BASEPATH=\\fileserver\updates
You need to replace FileServer with the name of your actual file server and save the .bat file.
There are a couple things you need configure on the Group Policy Object. We want to create a policy which applies to the computer at startup. Since the script will run as the local system, it runs silently in the background and does not require that the user have administrator rights on the PC.
First you need to call the installupdates.bat file through a Computer Startup Script
Second on the Security Filtering, you need to add the end user workstations. At first we recommend adding a single workstation so you can test the process.
The final step is to link the GPO to your domain.
Once everything is in place, reboot the client PC and check the \\fileserver\logs share for a log file from the client. The first time the updater runs it should download and install the updates on the PC. If the computer is rebooted and application runs again, it should detect the necessary updates are already installed and not download and install them again.
If you need to deploy the updates with minimal user interaction, you should download the O365Update.exe application. This version of the installer can be run directly on the end user workstation, but it does require the user have admin rights to execute it. It installs the same updates and writes a log file, O365setup.log, to the desktop.