Posted on 09-18-2024 12:32 AM
Hello everyone,
At the beginning of the year, we started our journey from leaving Novell in favor of Active Directory and MS Cloud.
Now it's time to make adjustments for our Apple environment. We have chosen not to use Jamf Connect (initially) but rely on our supplier that they can do it well without (though not as well as with). But there are some important points for us to get across.
- Not binding the units to ADs
- Enable access to network volumes, own storage volume and shared
Is there anyone in the community who is in such an environment and what have you done to solve it? Or is there any specific way to go to solve it, recommendations?
Then another little thing. We will (sadly) move part of our Apple environment to Intune for financial reasons. As I don't know much about Intune, I take the opportunity to ask the question if anyone here knows. Can we run Macs in Intune without binding them or is it a must on that side?
Posted on 09-18-2024 08:22 AM
Accessing network shares would be identity based, not domain registration based. Users can still access share drives on nondomain bound devices, they would just need to authenticate manually or have a tool like Apples SSO extensions installed and enabled (Kerberos Single Sign-on extension with Apple devices - Apple Support).
For your Intune question. Intune does not require domain binding, but it does require azure registration which is its own thing entirely.