During our deployment we utilize jamf connect for account creation and for password sync thereafter. We don't use connect for login AFTER deployment (we have a policy in DEPnotify that resets authchanger). All is well and good until a macOS update comes along and machines revert authchanger to jamf connect. We have contacted jamf and were told it's a product issue.
Now, to fix the issue so it doesn't keep happening. The idea is to place a dummy file on machines DURING enrollment with an extension attribute to verify the file's existence (report a value of true or false) and pull the configuration profile for jamf connect login (excluding a smart group with membership based on extension attribute data). The file/policy is done. The extension attribute is done and reporting correctly. The issue is I can't figure out how to scope a smart group based on the given data.
Has anyone done this? Is it possible? Is there a better way to do it?
