![]() I've got an apple care enterprise support ticket open for this so I'll keep you updated if I get a fix. This test was done on an intel Mac with FileVault turned off so there shouldn't be any conflicts with secure tokens or ownership etc. So it seems like the issue only occurs when a standard user is logged in even though the script is running from Jamf as root. When a standard user is logged into the Mac and this command is run by jamf, root or a localadmin in terminal the command doesn’t download anything and also never ends and this is what is breaking out workflow.īut just like the “softwareupdate -list” command, if I log into the mac as a local administrator and run “softwareupdate -download -all” in terminal it immediately starts the download of the available updates. The main issue is the command in the script which follows this which is run in a Jamf script: “softwareupdate -download -all” The error lines in the output of “softwareupdate -list” don’t actually cause us an issue. So it seems like the issue is triggered when the command/script runs as a local admin or root when a standard user is the logged in user. If I then log out as the standard user and back in as a local admin and run the command again there are no errors. If I then log out as a local admin, log into the mac as a standard user, open terminal and change user to a localadmin and then run the “softwareupdate -list” command in terminal, the errors do appear. If I log in as a local administrator first and then run the “softwareupdate -list” command in terminal as a local administrator I don’t see the errors. I did another test today where I excluded all policies from my computer so that all that happens during the DEP stage is that Jamf connect is installed and then no other policies are applied. If I come up with anything on that front I'll share it here. There are a lot of mentions of Secure Tokens being an issue, and while I didn't think of that at first, that seems as good a place as any to start. It seems like the connection between and Software Updates are the notifications presented to the user when the sequence is started and/or ready to restart. ![]() In one example someone was trying to load a Launch Daemon to have software updates install, but it also encountered a hung state that reads (to me) similarly to the symptoms mentioned in the MunkiTools thread. What I'm noticing is some discussion about secure tokens from the Apple Developer Forum threads. And this is another submitted by someone not working with an MDM, but is functionally in the same space trying to use commands to run updates.This is open thread that is right in line with our discussion here:.Someone there suggested that macOS 12.3 resolves this issue: This is the one I posted earlier from the MunkiTools GitHub.I've only started looking today, but I've found several open threads concerning this problem: macOS 11 appears to behave as expected when using softwareupdate) Seeing issues across both platforms on macOS 12 releases. (As a note I work with both Intel and Silicon based endpoints in my environment. Might also suggest updating to that beta on a test device and seeing if this behavior persists. The most recent posts in that thread indicate the bug is being worked out in the 12.3 release so we may see a fix here soon. Like Jamf, Munki simply tries to use the softwareupdate binary to run OS updates, so it doesn't appear to be something specific to Munki deployments. As a result updates aren't being downloaded or devices that have updates are showing up as clean until an admin or technician actually goes to an endpoint and invokes softwareupdate manually. Recent posts here: , suggest that there's an issue with softwareupdate where it's hanging waiting for a response it never receives. ![]() On a thread from the Munki GitHub, I don't think this issue is related to you working in a vm.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |