Today's modern IT environment is filled with Mac ® endpoints. Some stores now only use macOS ® systems. The problem that many IT administrators face is just to handle all of these Mac systems. Because most IT networks used to be on-prem and Windows ® based, there are many IT administrators who are quick to wonder if using Active Directory ® [1
An Active Directory Past
Perhaps because of the dominance that Microsoft ® has had with its Active Directory Platform AD standard directory that sysadmins thinks of. And that makes a lot of sense. When Microsoft Active Directory was developed over two decades ago, the IT infrastructure it was intended to control was largely Windows based and on-prem. We must remember that the vast majority of systems twenty-two years ago were desktop-sized beige desktops.
Due to this early event, the view was that Microsoft could lock its customers into high-margin solutions such as Windows ® and Office ™ and associate it all through Active Directory. With all this context, it is easy to understand that AD is optimized for Windows. Microsoft has never had an incentive to introduce support to competing endpoints. They want their customers to remain cuffed for Microsoft solutions .
MacOS Intrer Fray
The problem with IT admins though is that in the last decade Apple's Mac platform has made great input for businesses. People just want to use them. A recent survey indicates that 72% of the company's employees would choose a Mac system when they were given . The problem is, Microsoft does not care much about meeting these requests. Perhaps that's why only about half of businesses allow their employees to make that choice. Nevertheless, IT organizations and administrators turn to managing the Mac platform. Those with Active Directory in place have usually been left with two options for managing macOS environments: invest in additional resolutions as an identity bridge or leave Mac systems unmanaged. Both options are far from ideal.
The problem with identity bridges is that (Read more …)