For a customer, we're running Windows Server 2012 R2 and a mix of Windows 7, Windows 8.1 and Windows 10 clients. We have an issue regarding home folders being mapped when a user first boots up. This occurs when users are online and when they attempt to use offline folders.
We use the home folder settings on the user account's profile tab in ADUC to map their H: drive to their home folder. Prior to us managing this network, the IT person manually mapped the users' P: drive to a "public" share on their servers. We haven't changed that as it's a small company and there's not a huge amount of turnover, so it's not creating too much administrative overhead.
Scenario 1:
User A has a computer which is in the office and is always using a wired connection to the LAN. That user turns on or reboots their computer. Upon logon, there is no H: drive mapping. The user does, however, have their P: drive. The
user logs off and logs back on and they have an H: drive as well as their P: drive.
Scenario 2:
User B has a laptop which is sometimes in the office connected via wireless or wired connection to the LAN. Other times, User B uses their laptop out of the office. User B sometimes connects to the office LAN via VPN and other times the user doesn't.
The user has configured their H: drive to "Always Available Offline". When the user works offline, the H: drive doesn't appear, however the P: drive is there and available offline. User B connects to the office LAN via VPN and manually
maps H: drive and it maps correctly. User B disconnects from the VPN and the H: drive is available to use offline.
This behavior is consistent and easily replicated.
Does anyone have any ideas as to what could be the problem? I have some ideas on both issues, but I don't want to lead the conversation and would appreciate some fresh input.
Thanks!!