Mapped drive preventing logon to Active Directory

New Contributor

We are in the process of migrating users and computer from one domain (Windows 2008 domain and forest functional level) to Windows 2012 R2. Users are migrated with their SID History as well as groups. Users, also, have their home drive mapped to H: in their AD profile. We have seen where users with such a mapping in their user object's profile tab are prevented from logon to the new Active Directory Forest. Once that H: mapping is removed from their profile, they can logon just fine. What is causing this and what is the best approach towards allow drive mapping in their AD profile?


New Contributor III

Maybe in the macOS Active Directory plug-in (inside Directory Utility), specify the new domain server? This will force it to use the new Windows 2012 R2 server you've setup. (see screenshot attached). Just something to try.


Not sure how many Macs are involved here but you could try to rejoin one to the domain and see if this fixes the issue as well. Perhaps something get messed up during the migration.

When that same user logs into a Windows PC do they have the same issue?

New Contributor

The user does NOT have the same issue when logging into a windows machine. It seems to be tied to having a home directory defined in their Active Directory Object under the profile tab. Once that setting is cleared, they can logon to Active Directory with their Mac.