We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
Real talk, real tools and real-time support from people who get it.
Real answers from Apple Admins like you
Find your way around
Share your thoughts
Submit your idea
I manage several dozen iPads using Jamf Pro. I have a restriction set to only allow OS updates after they are 30 days old. Once the 30 days are up, I manually push out the update using the “Download and schedule to install” option, setting the “Force install date” one week in the future and selecting the specific version I want installed. What I am seeing is that when the “Force install date” comes around, the update is not forced, but the user is allowed to continue using the iPad without updating the OS. I expected them to be “forced” to update when this date happens. Does “force” have a different meaning here? What am I missing? Also, if I choose “Download and install” it does not force the user to update the OS either. Thanks for any insight. I’m new to this world.
Hello All, We’ve just started to implement Jamf Pro in our company. Nearly all configurations are completed except sending compliant information to Microsoft Intune. We have to do this because we’re using Azure (Entra) Conditional Access rules in our company. If a macOS device is not compliant it cannot reach internal company resources. Just a simple rule. Steps Completed Jamf <> Intune compliance partner connector connected successfully. Microsoft Device Compliance configuration policy prepared in Jamf Policies -https://learn.microsoft.com/en-us/intune/intune-service/protect/jamf-managed-device-compliance-with-entra-id Problem Summary After enrolling to jamf, we are trying to sign in to Company portal and jamf compliance popup appears. Then we are entering our user account details again but somehow Microsoft login page shows that “get app”. It behaves like Company Portal is not installed. Briefly some of our computers are being Compliant without any problem, but some of others cannot
Been having a lot of problems with Filevault over the years. Now I’ve just discovered that you can no longer use the Filevault recovery keys in macOS 15.5. Instead, you are expected to boot to recovery, which is more of a pain. This removal is insane. Like many we use the stored key from Jamf to unlock devices in the event of account passwords not working. Now we have to use Recovery mode. I’d love to know Apple’s reasoning for this. Anyone else aware of this and have any comment?
Hi, I noticed that rather many of my Mac clients are not FileVault encrypted even though I have configured a configuration that should take care of that. Now I wanted to ask what is the best practice to enable FileVault on all my Macs. As far as I know there is an option to enable it via Policy and one via Configuration Profiles. What is the difference there and what is recommended?
I need to force install a Chrome Extension. I have looked in Jamf Nation for solution but latest ones were in 2017 and they currently do not work (from my testing). Has anyone got them to work with Monterey?
Hi there, Has anyone managed to successfully get the Jamf Pro Custom API action call card working in Okta? I get a 401 Unauthorized error even though the bearer token is brand new and passed directly to the auth field of the custom API action card. I even tried with API endpoint reference curl command and compared an invalid bearer token to a valid freshly generated one: curl --request POST \ --url https://sandbox.jamfcloud.com/api/v1/ddm/18/sync \ --header 'accept: application/json' \ --header 'authorization: Bearer invalid_token'{ "httpStatus" : 401, "errors" : [ { "code" : "INVALID_TOKEN", "description" : "Unauthorized", "id" : "0", "field" : null } ]}% curl --request POST \ --url https://sandbox.jamfcloud.com/api/v1/ddm/24/sync \ --header 'accept: application/json' \ --header 'authorization: Bearer working_token'{ "httpStatus" : 500, "errors" : [ ]}%
Hi All, Windows admin here, thrust into a mixed environment consisting mainly of Mac’s. I’ve worked with Intune for a few years now, but Jamf/managing macOS is totally new to me. Looking forward to learning a lot, but I was wondering what everyone wishes they knew at the beginning of their Jamf journey?
Since moving to JAMF Cloud, we’ve noticed that some time appears to be off. For example, I ran an Inventory Update manually on a computer, and the record in JAMF console shows that it was run 1 hour earlier than it actually was. Also, with Apple TVs we have records that say that the Inventory Update occurred up to an hour in the future. I’m not sure that this is causing an actual problem yet, but concerned that it could. Are there time zone settings we should see or anything? All of our client devices are in the same time zone (unless a client goes on a temproary trip or something).
I blocked the extension installation on chrome, with that un approved extension are blcoked but now I want to remove the un approved extension which is installed previously. Is there any way to removed it? I tried to remove the extension ID with script but in Chrome browser it shows corrupted not removing completely.
Hello, I need to create a script to simply turn on the Teamviewer in Security & Privacy > Screen recording. Right now it's a manual process and we're trying to deploy Teamviewer host via Jamf. However the configuration policy that comes with Teamviewer host does not allow us to allow screen sharing. It gives the user the option to allow screen sharing and since we don't want the user to interact with anything, I'm looking for a script that can turn on Teamviewer in Screen recording in Security & privacy:
Hello everyone, i wanted to roll out our new custom TeamViewer Host and everything works except that our custom design with the company logo is not displayed. I did it exactly as in the instructions: https://hcsonline.com/images/PDFs/Jamf_Teamviewer_Host.pdf After the custom logo didn't show up, I kept searching and came across these instructions: https://community.teamviewer.com/English/kb/articles/50739-mass-deployment-on-macos#perform-an-assignment The groups and the membership works but unfortunately our custom layout does not. Am I missing something or have I done something wrong?
Does the JIM use Apache Tomcat at all?
We got Defender working on our Macs about a year ago - deployed via JAMF Pro and with configuration profiles. We are not bound to the domain and do not use JAMF Connect. I am trying to follow along with Microsofts documentation (Onboard and offboard macOS devices into Microsoft Purview solutions using JAMF Pro | Microsoft Learn) which seems to be written for setting this up from scratch rather than adding it in to an existing setup. It seems to be doing something as we are getting better feedback under Device Onboarding, but still not making much progress. Here is an example of the details in Device Onboarding in Microsoft Purview with the error messages before and the more informative messages after I have created the configuration profiles in JAMF from the above guide: View under Device Onboarding: Before the configuration profiles were updated: After the configuration profile was updated: In the documentation that I linked to near the top, there is a "Before You Begin section which
Earn a cool badge and Jamf Nation Reward Bytes for your published articles. We’re looking forward to your submissions!
1 Question Answered
216 Questions Answered
30 Questions Answered
17 Questions Answered
15 Questions Answered
16 likes
15 likes
10 likes
Learn about our customer advocacy program that celebrates our most passionate customers.
Join the community to receive product updates, and share feedback.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
