Software Deployment Question

Office365 Install Failing

04/23/2020 312 views


I have an offline version of Office 365 and it installs on machines where Office Applications are not in use it seems. Which I appreciate makes sense but when I got mine to go direct to Microsoft it did the install in the background and updated after a reboot while I had multiple applications open. 

Does anyone know how I can get this to happen in my environment as we have old versions of Office 365 kicking around and I am changing the location of the install to as it was previously done badly. 

I am running the following command in a batch file via the scripting method: "\\Server\Share\setup.exe" /configure "\\Server\Share\Config.xml"

I have looked through the config file using the Office customisation Wizard but I cant seem to find anything which would do what I need it to do, unless I am missing something. 

Would a simple registry update to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration and the UpdateChannel and UpdateUrl be enough? 

Any help would be appreciated.



4 Comments   [ + ] Show comments


  • How are you triggering the install? And in what user context is your installer running?
  • I am triggering the install with a batch file on a server share containing the above string. using an online Kscript.

    As for the user it is running as a service account as it requires to connect to a server share. The account has admin privileges over the machine.
  • So that I understand your question clearly, are you trying to change the location (updatepath) of existing office 365 installation to a different location so the device can install feature/security updates from a new location such as your network share or from Microsoft CDN?
  • Yes thats correct I want to ensure that the following are updated:


    Out of curiosity how often does office check in for updates by default?

All Answers


I think Audience and Update Channel should be only touched if you are changing channel (e.g. from Monthly to Semi-Annual), which is not common and should be left alone.

To change the update location, the only property that should be changed or added is the UpdateUrl registry key, which can be done via office setup and UpdatePath attribute in configuration xml. Updates Enabled can be FALSE, if you want to manage updates via SMA.

Check your config file to make sure its correctly created. Test your script on one machine locally via cmd line before executing on multiple machines via sma scripting. This will help verify that config xml and script are correct.

A sample config xml can look like this ->

<Configuration>  <Updates Enabled="FALSE" UpdatePath="\\yourserver\sharepath\o365" /> </Configuration>

As for how often office check in for updates by default, check Task Scheduler on the device.

Task Schedule Library -> \Microsoft\Office. there should be a list of tasks associated with Office updates. Triggers for each task will give you information on when and how frequently it checks for updates.

Answered 04/24/2020 by: mehulpatel2012
Senior White Belt

  • For testing use psexec.exe to run as system. use the cmd to start a interactive SYSTEM console. psexec.exe -i -s cmd.exe.

    If you are having issues installing as SYSTEM and its killing the process = unhappy users, have a look into PSDeployToolkit. It has a GUI function prompt users, and allows the user to defer - will take about 90 mins to read up on it and get your head around it, its quite powerful.

    If you're having problems updating, ie the installer it borking when trying to update the office, or borking at uninstrall. Check out (what I call the office nuke, or) office official uninstall scripts.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ