Hello is there a way to make the request for manual UAMDM Approval within a DepNotify workflow, pretty much the same way Selfservice does once open for the first time warning an poiting to system prefences with non-DEP machines?
Ideal would be stopping the DepNotify workflow until UAMDM is approved but if think it takes a little effort/logic with extension attributes and recon Just the reminder a-la self service would be enough to begin with Any help will be much appreciated Ciao
As a frequent hacker of DEPNotify workflows, I'm glad to see what you are thinking here. So here's my off-the-top-of-my-head idea that I have not tested, so take it with a grain of salt.
This article by @rtrouton will show you how to detect if it's approved in your loop. If my process requires any additional clarity (it's the end of the week and my brain is fried) let me know and I'll try to expound.
@chadlawson thank you for the hint and sorry for the late reply, I was OOO
I could swear I saw a DEPNotify presentation somewhere and also shared on GitHub (I can't find it anymore) and there was the same picture SelfService app shows
I mean the very same picture asking the user to go to System prefs to approve MDM was within the DEPNotify window and so it seemed to be part of that DEPNotify workflow
@Nix4Life that's very interesting indeed, thank you
@chadlawson Many thanks again! when I first started wondering about how to ease UAMDM with DEPNotify I was still focusing on quickadd.pkg enrollment, which looks like to be soon deprecated, therefore the way to go is DEP (or User-Initiated Enrollment from https://your.awesome.JSS.com:8443/enroll/) which both solve the problem of UAMDM...