How I Stopped Worrying And Learned To Love Our .Local Active Directory Domain

kenshoberlin
New Contributor

Hello,

our organisation currently runs about sixty percent of our desktop and mobile clients on OS X - ranging from Snow Leopard to Mountain Lion. Our clients are bound to an Active Directory domain with the .local domain name suffix. This, as everyone will tell you, is in conjunction with Macs a rather terrible idea.

Contrary to my attention - grabbing headline we may always run into problems integrating new OS X releases into our AD. Which is why during the course of a project to integrate our clients more efficiently with our Windows backend we have suggested a migration towards a recommended fully qualified domain name space.

What I am looking for with this post are fellow sufferers - admins who are integrating the clients into .local environments. How do you manage to accommodate your clients into this challenging setup? Has your organisation perhaps made the move towards an AD migration? If so I would very much like to be in touch.

1 REPLY 1

dolivieri
New Contributor

Mapping SMB file shares has been a big challenge for us.