A read only file share containing the Office 2016 click to run files.Therefore you need to run the installation by way of a startup script that first checks if Office 365 ProPlus click to run has already been installed or not. But this is not simple either as startup scripts run each time the computer starts up (obviously!) but will run regardless of whether the software is already installed. Therefore you need to deploy the software via a computer startup script. An existing installation installed before the “2019” release in October 2018 will seamlessly move to this version at the next applicable update. This is not the case with the “2019” release. You cannot just drop the latest versions of the files in an existing 2013 deployment folder and expect the clients to update automatically – you must install 2016 to upgrade it and install it for the first time.You cannot run software with elevated installation rights, as the setup.exe shells out to other processes to run the installation (the officeclick2run.exe service).You cannot use the “Software Installation” features of GPO’s to deploy the installer click to run software as this is an exe file, and “Software Installation” runs MSI files.Microsoft 365 Apps for enterprise (aka Office 365 ProPlus) Click To Run (which comes with Office 365 subscriptions) can be deployed via Group Policy, but there are a few things that you need to know and do first. Note: Article updated April 20 to support the new Channel names and XML updates and the new name for the product (Microsoft 365 Apps for enterprise). Note: Article updated October 2018 to remove references to “Office 2016” and replace it with “Office 365 ProPlus” as the rollover to the 2019 release is seamless and does not change this products name.
0 kommentar(er)
