Has anyone used this successfully? I have a fleet of mostly M1 Macbooks, FileVault enabled on all of them. I've tried using a test group to deploy software updates, but none of the computers seem to respond no matter what I select. No prompts, no updates downloading. I've tried on three different machines on Ventura. Jamf pro version is 10.48. Do I need to be on 10.49?
Page 1 / 1
its very much.. 'beta' and im sure I read somewhere on here was not working as expected re deferrals not deferring and rebooting.. one for testing only and not production
its very much.. 'beta' and im sure I read somewhere on here was not working as expected re deferrals not deferring and rebooting.. one for testing only and not production
Yep, happened for me in my test this morning on an M1 - pushed an update from 13.4.1 to 13.5 with 2 deferrals, and didnt receive any notice, the machine just rebooted and updated.
its very much.. 'beta' and im sure I read somewhere on here was not working as expected re deferrals not deferring and rebooting.. one for testing only and not production
Yeah, that's what I was kind of afraid of. I'll keep working on it and see if Jamf support can offer any options for running updates to machines in the meantime. I definitely need to look into that more as I primarily manage the Jamf environment for my company.
There is a case open with jamf CASE#CS0998447.
There is actually a product issue now open for this - PI112338
Had to read up on the mass action commands. These still aren't great. They keep getting stuck pending and seem to run at a random time a few hours later. Can't figure out why.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.