There are two options for where the updates can be installed from, which is defined using UpdatePath attribute in config.xml. This depends on the configuration of office 365 on client computers.
Not helpful for updating deployed machines obviously, but might be a factor in your deployment plans. And if the Office 365 patches on the appliance still need access to Microsoft in order to apply updates, they will fail.įYI, as you may know if you "setup.exe /download" it'll always grab the latest version of the binaries. This is problematic in my environment because our firewall blocks certain Microsoft sites - we don't want our machines being able to patch directly from Microsoft, we want the K1000 to be our sole patching mechanism. Our K1000 is subscribed to Office 365 updates and I see those patches being downloaded, but they are very small (1MB or smaller) and appear to be bootstrap files that still need to go out to Microsoft to apply each patch. I have the same question as you regarding updates. "setup.exe /configure" does the actual installation while pulling from that share. I made the xml config files and ran the deployment tool with "setup.exe /download", which then saves the binaries locally (about 2GB of files) which I then put on a network share. James, I'm in the same situation as yourself.
0 kommentar(er)
