At 26:04 the setup and install of Intune and configuration. I am not finding a doc on how to set that up. I was playing around just installed Intune Comapny portal but error stating there can only be one MDM.
At 14:11, what is the required action? Delete this Enterprise App? Cool story about the chocolate, but can't understand what the action is we need to take.
I'm assuming what's missing is: 1. Remove the existing app with the App ID from your Jamf Conditional Access page. 2. Then create a new App for the new Device Compliance to be setup in JAMF But I'm unsure
@@Weapuhx are you in need of help? Because I can help maybe. I don't want to watch the whole darn video. The old app can coexist with the new one, so deleting it isn't mandatory. Also, be aware. Around June Jamf updated the instruction of the migration. Users now need to start a script from the Self Service app. That's changed and was something we weren't expecting unfortunately lol.
@@MisterGolda Luckily I caught that script from the learn.jamf site. The one question mark I had was surrounding the Enterprise App portion. I think, to correct what I wrote above, a new Enterprise Application will it be created by virtue of accepting the Consent URL from Jamf.
@@MisterGolda luckily I fumbled around on enough links in the knowledge articles I was able to find that script and throw it in to Jamf. Thanks for the heads up, I think I'm good to go.Not really much of a choice now, it being Aug 26th :D
Do you have the link to the microsoft talk that were mentioned in this video regarding jamf, microsoft and conditional access policies?
At 26:04 the setup and install of Intune and configuration. I am not finding a doc on how to set that up. I was playing around just installed Intune Comapny portal but error stating there can only be one MDM.
At 14:11, what is the required action? Delete this Enterprise App? Cool story about the chocolate, but can't understand what the action is we need to take.
I'm assuming what's missing is:
1. Remove the existing app with the App ID from your Jamf Conditional Access page.
2. Then create a new App for the new Device Compliance to be setup in JAMF
But I'm unsure
@@Weapuhx are you in need of help? Because I can help maybe. I don't want to watch the whole darn video. The old app can coexist with the new one, so deleting it isn't mandatory. Also, be aware. Around June Jamf updated the instruction of the migration. Users now need to start a script from the Self Service app. That's changed and was something we weren't expecting unfortunately lol.
@@MisterGolda Luckily I caught that script from the learn.jamf site. The one question mark I had was surrounding the Enterprise App portion. I think, to correct what I wrote above, a new Enterprise Application will it be created by virtue of accepting the Consent URL from Jamf.
@@MisterGolda luckily I fumbled around on enough links in the knowledge articles I was able to find that script and throw it in to Jamf. Thanks for the heads up, I think I'm good to go.Not really much of a choice now, it being Aug 26th :D
@@Weapuhx Haha that's true. For us, it was not a big deal after all. But overall a little bit disappointing to bother the end-users.
Azure, I refuse to say the new name.
21:10 it's funny how Jamf is telling us NOT to nest smart groups as it uses more server resources and can cause outages.