AD Bind on macOS is dead - long live Jamf Connect
Use Cases and Deployment Scope
With Jamf Connect, we are able to register users via Azure AD when a new user gets a new MacBook. In addition, password sync is possible with it and the Macs no longer have to be AD bind. So we don't have trouble with asynchronous local und AD-passwords. We can also activate Filevault when creating the account.
Pros
- password sync works very well
- regular updates to Jamf Connect with improvements
- small and simple tool
- Account creation is now on next level after we don't need AD Bind
Cons
- the Jamf configuration app for the config profiles looks not really Jamf-like
- Why are under "Jamf Connect Deployment and Update Settings" in Jamf Pro all possible configuration profiles listed? We have some and I don't think there had to list every!?
- how the Jamf Connect updates work under "Jamf Connect Deployment and Update Settings" is very unclear. i.e. for troubleshooting
Most Important Features
- account creation
- password sync
- Filevault activation
Return on Investment
- we need more time to understand how Jamf Connect and the configuration "really" works
Other Software Used
Jamf Pro, Jamf Protect, Matrix