Does it require maintaining a corresponding collection in PDQ Inventory? - yes.Does the package include silent parameters to install for all users (machine-wide installation)? - yes. Are we able to automate checking the Software publisher's site for when new versions are released? - Update history for Microsoft 365 Apps (listed by date) - Office release notes | Microsoft Learn.Is this software deployed to the majority of an organization's endpoints/servers or is only used as a utility for a handful of admins? We are interested in software that maximizes the time savings for SysAdmins - Used by majority of users.Does the Package End-User License Agreement (EULA) allow us to redistribute the software? - unknown.Is this commercial software that requires a license or is this free for business customers to use? - Free for customers with valid MSFT licensing.For example, if we are patching and it rolls into a new Microsoft patching window, this command will install the latest version that has not been properly tested. We currently have a workaround to run the command to ""C:\Program Files\Common Files\Microsoft Shared\ClickToRun\OfficeC2RClient.exe" /update user updatepromptuser=true forceappshutdown=true displaylevel=true", but it does not take into account what patch we are trying to install. We are looking to patch Office 365 Apps as part of our monthly patching cycle and would like this to be packaged in PDQ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |