I am back with my query regarding patching O365. I would like to use the built in OfficeC2rclient.exe with a version control in place. The download files will be retrieved from a DFS share whose unc path will pre populated on the workstations registry path
I am trying to replicate an action similar to the one given below:
Has anybody in the community had luck in updating O365 using thus method. Is this achievable using BigFix? I don’t see a reason why it wouldn’t work, however like to see some real world examples if any.
It sounds like if you aren’t bandwidth constrained, then you don’t need to distribute anything, you can just do the following:
waithidden "C:\Program Files\Microsoft Office 15\ClientX64\OfficeC2RClient.exe" /update user updatetoversion=15.0.4631.1004
Even if you do decide to do it through distributing a file, there shouldn’t be any need to use DFS. You can download the file using BigFix, and then just run the command pointing to the file that was downloaded.
What is the command that you would use to update O365 from a file?
We are actully bandwidth constraint and cannot download the updates from the internet for all sites, as we have no local internet breakouts. Thus we need to use DFS shares where we are going to place the update files. The reason we would prefer to use click2run is because in this mode the end users can use office till the updates are being downloaded, it is only while applying the updates that office needs to be shut down. Thereby reducing the long downtime, i am using the same action as you specified and it is invoking the c2r client however fails with an ugly message.