Morning everybody,

Still planning my O365 deployment, so the following is so far has only been applied to a small number of test machines.

When updating O365 on my endpoints, the source of those updates is set by the configuration.xml I use when running the initial install. As the updates are not likely to amount to a huge amount of data, the updatepath is set to a network share.

In the same config.xml, the sourcepath is set as a local path on the machine, because rather than having 4000 machines all try to pull over a gig of source files down over the network (half of which will be on via VPN), it made sense to stage them locally via SCCM for the sake of that initial setup.

My questions are as follows:

1. When updating, does the sourcepath set in the config.xml need to still exist on the local machine, or do the updates go straight into the Program Files folder?
2. Once that initial setup is complete, is there any reason those source files which I've stored locally shouldn't be deleted?

Many thanks,

AP

• Edited by Arterion86 Friday, January 30, 2015 11:34 AM

Hi,

As per your description, I understand that you've deployed Office 365 with a customized configuration.xml file. In the XML file, the SourcePath attribute was set to a local path, and the UpdatePath was set to a network share.

With this configuration, your Office 365 will check the update path for updates instead of using the cloud as the update source. The difference or delta between the new build and the existing one will be installed directly when Office apps/processes arent running.

The build/source in your sourcepath is not involved during the whole update process, you can delete it after the initial installation.

Hope this helps.

Regards,

Ethan Hua
TechNet Community Support