This is about doing a mass update of the OS. I have followed all the guides and document under Remote Commands - Update OS version and built in apps - Target version - latest version based on device eligibility - download and install the update, and restart computers after installation.
On a side note, JAMF really needs to update that training video. That is 5 years out of date now. Any information for using the softwareupdate binary, or any policies for OS updates is no longer relevant. The SoftwareUpdate Binary wont work on Apple Silicon Macs, you also cant use custom OS update servers anymore.
Download And Install The Update And Restart Devices After Installation Jamf
Download 🔥 https://shoxet.com/2yGaAs 🔥
I've just recently went down a Rabbit Hole on this very issue. If your on M1 computers and they haven't had the MDM boot strap escrowed to them, the MDM command to silently install updates flat out won't work.
To fix this going forward, I have my very first policy that runs at enrollment create a new local admin account, delete the admin account that was created by the pre-stage enrollment, and then run a script to escrow the bootstrap token. For better or worse, this assures that every account that logs into the machine gets the secure token on login (hopefully this doesn't bite me in the ass later). I am not finding an easy way to fix the 500 or so m1 machines in my org that don't have a boot strap token because I'm not sure who has the secure token unless I research on a case-by-case basis.
I'm running into the same exact issue - but it's also affecting our Intel Macs. After waiting a good 24 to 48 hours after having executed the remote update command from with Jamf, I manually log into the affected machines, and from within the Software Update interface it shows the download process as having stuck (usually pretty early like < 5%). I click on the "X" to stop the download, manually tell it to check for updates again, select the update, it then prompts me with the EULA which I select "agree", and everything proceeds fine after that. This behavior did not start for me until the Ventura 13.4 update back in mid-May. Again these are all Intel Macs.
Once I send the remote update command, I checked the computers the following day. The update download progress bar in System Settings-->General-->Software Update was only at approximately 5% completed, where it remained. At that point, I simply clicked on the little "X" to stop the download. I then rechecked for updates, the 13.4.1 update reappeared as available, I selected download, was presented with the EULA pop-up which I accepted, and the downloaded started and completed fairly quickly, resulting the computer rebooting and successfully installing the update.
Jamf's purpose is to simplify work by helping organizations manage and secure an Apple experience that end users love and organizations trust. Jamf is the only company in the world that provides a complete management and security solution for an Apple-first environment that is enterprise secure, consumer simple and protects personal privacy. Learn about Jamf.
This site contains User Content submitted by Jamf Nation community members. Jamf does not review User Content submitted by members or other third parties before it is posted. All content on Jamf Nation is for informational purposes only. Information and posts may be out of date when you view them. Jamf is not responsible for, nor assumes any liability for any User Content or other third-party content appearing on Jamf Nation.
We already defer updates by 45 days, but some of the devices fall WAY behind (some are still iOS 12) and it's hard to try to enforce updates on the devices when
A) kids have them at home
and B) kids don't want to update or don't know how to
I try to force out Update / Restart via the Action command to all devices in a smart group from time to time, but for some reason we only get about 60% completion and the others will just continue to check in but never update themselves.
If the devices have a passcode on them, the "download and install the update, and restart devices after installation" will not work. You will first need to clear all the passcodes. With the passcode set, the student has to input their passcode for the update to install.
Is there no way to force the deployment of the latest iOS version to the phones without having to either clear the password first-- which will make the employees using the phones panic-- or to wait for the employee to enter their code, select "install now" instead of "ignore" and then enter their code again?
We struggle keeping our student 1:1 iPads up to date too. I agree the requirement to clear the passcode is terrible for security. I contacted Apple about this and they told me JAMF should be able to implement an easier process for the updating. With security holes constantly popping up, this really needs to be automatic or at least easier to do. (we use JAMF school)
One of our teams is seeing this in a different enrollment scenario. When they enroll a new Mini using automated setup, as soon as enrollment completes and Apple Setup shows "Applying Settings" it shuts down. This interrupts the agent install. I haven't seen it in our environment (different server entirely) so I wonder if it's a config profile thing. It works as expected on earlier OS versions and only behaves this way on Monterey.
Edit: I just took a look and they are applying Energy Saver settings to wake on network and also restart after power failure, and those sound perfect for an OS bug. What payloads are you installing when this happens?
Any other ideas on this one? I have attempted to uncheck all config profiles and run into the same issue. When enrollment reaches "Applying Settings" it either shuts down or reboots. Both on intel and m1.
I found I could setup a smart group that identified if an extension attribute was empty, that I could add that smart group as an exclusion to all my config. profiles, was enough to resolve the issue. Essentially any attribute that requires the Jamf agent to perform a recon to fill is enough, i.e. push notification inventory update can not be enough. I'm sure there are some standard Jamf Pro computer attributes that would work, I just happened to have a simple extension attribute that meets the requirements (boot drive free space in Gigs instead go Megs).
In a PreStage Enrolment, the setting "Automatically advance through Setup Assistant" is not compatible with the "Setup Assistant Options" below it, leave them turned off, otherwise the advancing process will trigger a shutdown or restart when it expects a missing window to appear. i.e.
I followed your instructions, so I left all the options below "Setup Assistant Options" unchecked. Now it doesn't shutdown, but it does a restart. So this seems not to be the only reason for this unexpected restart/shutdown.
To supplement my previous post: When also unchecking all of the configuration profiles, the machines finishes the DEP enrollment. Only an Office 365 package which is added to 'enrollment packages' is not installed after DEP enrollment. You would expect this one to be installed during the DEP enrollment.
When reinstalling MacOS I run into issues in the Remote Management section during installation. After establishing a network connection, I proceed to the Remote Management section of the installation and the setup is failing with an error "Unable to connect to the MDM server for your organisation.". Is there any way how I can resolve this issue manually? Because there is no way how to bypass this step in the setup.
I would start with ensuring that your MDM server can access all the necessary ports it's looking for. These should be listed in the server documentation. The big ones are 443, 2195, 2197, and 5223. These are the ports Apple communicates with the MDM server over. Any of these being inaccessible is usually the cause of your error. 152ee80cbc
how to download data in jotform
everyone it 39;s my birthday reel song download