-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Script fails to update after recent update to MAU and/or Office 365 apps #10
Comments
It looks like the script (lines 223-259) needs to be updated to include new Application IDs for Office 2019.
|
I updated the ids and still having the same issue. If add an override for one of the apps with the build number and don't use the default "latest" it will find the updates. |
@dash4385 for clarification, if you use the build numbers as listed at https://macadmins.software/msupdate then the update works. But, if you don't specify the build number, then no updates are found? What about from the command-line directly (rather than the script)? |
As of last night when I entered in 16.29.1 as the override for word and ran the script the msupdate tool itself would run and show me the list of updates. When I came back to this in the morning this seems to no longer be the case. when the script is run with blank or with override (tried 16.29.1 and 16.29.19091700) I see flashes of an app opening on the dock but nothing happens. Logs will say there are no updates. when i run |
This morning I tried using the v1.5 listed as a pending pull request but netted the same results. Here is the debug out but from Jamf
Here are the updates that
|
Same exact issue, this script is not finding any updates when manually running the msupdate -l shows multiple updates pending and I can run them succesfully with msupdate -i manually. |
We are seeing the same behavior too. As well as the issue I describe in #11 |
running a stand alone one liner in terminal does work. For example I just ran
and it found and updated without issue. Still can't figure out what it causing it not find update when run from the script itself. |
@dash4385 does the 'one-liner' also run properly when implemented as a Jamf script? Also, one other thought - do you have the correct PPPC profile in place that allows the Jamf Agent to send events to MAU? It's at https://github.com/pbowden-msft/MobileConfigs/tree/master/Jamf-MSUpdate |
I do have that config profile in place already. I have not tested the one liner above. |
Can confirm the one-liner works via Jamf policy just fine. Going to start using that as a work around until this is sorted. |
@hkabik Odd Tried running the one liner and returned no results when trigger through jamf. |
Scratch that... the one-liner SOMETIMES works in Jamf. yesterday it worked fine, today it reported back "Detecting and downloading updates... No result returned from Update Assistant" on a Machine that did need updates. I was able to run them by SSHing and running the one-liner manually. |
@hkabik Seems more like a bug with Jamf or MAU then the script if even a single line command run consistently. Guess We will have to wait for an update to MAU and test it again. |
I am seeing the same issue trying to run MSUpdate from Jamf - both with the simple one line script or with pbowden's script, returns no updates found every time. If I run the command or script locally it pulls and installs the updates just fine. I also have the PPPC profile in place. Hopefully this can be addressed somehow. |
Installed the MAU 4.16 (19101301) Hopping issues would resolve this but getting that same results. Running msupdate --list shows there are updates available but they are not found by the script |
Update on a method I used to get it to work for anyone having the same issue, had to add a variable to pull the current user and then ran the command as su currentuser. Script I used below worked great!
|
@SurgEm Do the users need to have admin rights for this to work? |
I should have mentioned that yes in our environment mac users have admin rights. and just to expand on my reply - it worked on MOST of them but a handful still returned no updates found for whatever reason. I ended up doing these ones manually. Frustrating :\ |
We limit most of our user to not have admin so this was great to allow them to update through self-service was great. May just have to scrap this script an go back to using the GUI seem to be the only reliable tool. |
Looks like the command line updater does not work at all. Running version 4.17 (19111002) and the command line finds "No result returned from Update Assistant" but if I run the GUI it finds 6 updates available. At this point, I don't think it is an issue with the script but rather a poorly implemented command-line tool from Microsoft. At this point, I am giving up on it and will revert back to using the GUI |
I am still having partial success with it - I think there is some sort of timing issue? as it seems to work "eventually" if you run it enough times. The way I have it set up now is working well enough for me - running the currentuser based script I posted above set to run once per day in the jamf policy on Smart group of any machine with office out of date. |
When run as a script executed from Self Service msu-date runs through too quickly (movement in dock indicating activity) to actually be doing anything and nothing gets updated. But running msupdate manually from the command line shows updates available, and actually updates them.
Nothing has changed in my setup except new versions of O365 where it worked previously. Issue has also been reported on #microsoft_autoupdate on MacAdmins Slack group.
autoupdate.log
The text was updated successfully, but these errors were encountered: