- #RANDOM MICROSOFT AUTOUPDATE MAC UPDATE#
- #RANDOM MICROSOFT AUTOUPDATE MAC PATCH#
- #RANDOM MICROSOFT AUTOUPDATE MAC LICENSE#
You could also try Paul Bowden’s SignInHelper script and set the above values using a plist instead, or script it yourself using the Jamf API. The address can be populated from AD on enrollment or in production, but that is beyond the scope of this article.
![random microsoft autoupdate mac random microsoft autoupdate mac](https://3nlm2c1gjj0z2ju16293909h-wpengine.netdna-ssl.com/wp-content/uploads/2015/03/office-2016-mac-review-office-2016-update.jpg)
Provided the email is correct in Jamf, this will work. Jamf will fill in the email address from Jamf on a per-user-basis before distributing the profile. In Jamf, you can use $EMAIL instead of the actual address in a configuration profile.
#RANDOM MICROSOFT AUTOUPDATE MAC UPDATE#
When you are ready to update a client, set the following preferences, using a configuration profile:Ĭom.microsoft.office OfficeAutoSignIn TRUEĬom.microsoft.office OfficeActivationEmailAddress DefaultEmailAddressOrDomain with the correct Office 365 account. mobileconfig can be uploaded directly into a new Jamf configuration profile, Jamf will sign it before distribution. This can be done using a smart group containing all clients running 10.14, and can also be done ahead of time without conflicting with the current installation. Then register Microsoft AutoUpdate afterwards by running a script running the two lsregister commands below (see Paul Bowden’s RegMAU tool) as the logged in user on clients, to pre-approve the popup asking users to approve the first run of Microsoft’s update daemon when it starts along with an app.ĭistributing Microsoft AutoUpdate this way will not conflict with the installations of users who have not yet been upgraded from Office 2016, so both of these steps can be done ahead of time.ĭistribute Paul Bowden’s Jamf Controller for Microsoft AutoUpdate configuration profile to clients that are running Mojave (so Jamf has the right permissions to control msupdate in a script).
![random microsoft autoupdate mac random microsoft autoupdate mac](https://167974-484938-raikfcquaxqncofqfm.stackpathdns.com/storage/posts/April2020/autoupdate-app2.jpg)
#RANDOM MICROSOFT AUTOUPDATE MAC PATCH#
These are the steps you need to achieve a silent upgrade using Jamf:įirst, distribute the most recent version of the Microsoft AutoUpdate package from macadmins.software to all clients using a policy or Patch Management. Also it will be Microsoft’s own AutoUpdate system that quits the app, which is the most graceful way to do it. Users may be asked for permission to quit an app to perform an upgrade, but it can be postponed. With this method it is not necessary to uninstall the previous version first or have users approve a non-graceful application quit either.
#RANDOM MICROSOFT AUTOUPDATE MAC LICENSE#
Unlicensing Office 2016 before upgrading is unnecessary, as the new license is backwards compatible. If users try to start an app while it is being updated, they will get a user friendly message telling them the app will start after the update is complete.
![random microsoft autoupdate mac random microsoft autoupdate mac](https://167974-484938-raikfcquaxqncofqfm.stackpathdns.com/storage/1544/microsoft-autoupdate-mac-virus.png)
The upgrade will happen in the background and the user can keep using the machine while it is being performed. The only thing your users will see, is a window informing them Office is being activated the first time they start one of the Office applications after the upgrade. It is entirely possible to silently upgrade users from Office 2016 VL to Office 365/2019 without user interaction, provided they are already using Outlook with an Office email account.