Home Folder Doesn't map

Question

Hi Everyone,

I know this has been covered by some but it seems to be for 2003 and older.

Environment: Server 2012r2, Win10 all up to date

Home Folder Connect U: \FQDN\User$\%username%, the share is using Access Based Enumeration,

Some user's it maps the drive, others it doesn't. There aren't any thumb drives devices that are taking the U:\, GPOs or other items for the affected users. Went Through DNS, dcdiag shows replications to second DNS server is fine. NTFS permissions are ok, and affected users can drop the filepath in, and access the folder

Created New User, fresh PC, doesn't work for some, and others it works just fine. I'm stumped.

Answer 1

Hello,

Thank you so much for posting here.

Here we did a test about Home Folder mapping, below are the steps.

Step 1: Create a folder in one of your hard disk drives

Step 2: Right-click the folder you created in above step and scroll the menu. Click Properties

Step 3: Click Advanced Sharing.

Step 4: Check the text box Share this folder. Click Permissions

Step 5: Allow full control from permissions for Everyone

 
 
Step 6: Open server manager dashboard and click Tools. Scroll down the menu and click Active Directory Users and Computers. Select all the users you would like to set them up a home folder and right-click and scroll down the menu. Click Properties

Step 7: Open Profile tab and check the home folder. Provide a path in the format \<MachineName>\<FolderName>\%username% and click Apply. Click OK

Check the contents of the shared folder; a folder that matches the user’s name should exist in this folder.

 

When a user logins to any domain joined machine will get a home folder.

If the Home Folder could be configured successfully through user profile, it is not necessary to do drive map via GPO. Since now some users' Home Folder could not be mapped, we could try the GPO to check whether it works.

For any question, please feel free to contact us.

Best regards,
Hannah Xiong

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

I ended up assigning the drive through GPO, to get it working successfully.
Traced all of DNS, and doesn't appear to be the culprit, its concerning that AD can't get this done.