Redirected Documents to User's HomeShare Issue!

[MYK-IT]

Hi,

 

Recently configured folder redirection for 'Documents' (and 'Pictures' using Setting: Follow the Documents folder) to user's Path: %HOMESHARE%%HOMEPATH%.

 

All worked, until we realised that all the folders on the file server have been renamed to 'Documents'!

 

I have found this document, https://docs.microsoft.com/en-us/troubleshoot/windows-server/networking/redirected-documents-folder-name-not-user-name and despite referring to Windows 7/Vista it does appear to cover the same issue (Windows 10 / Server 2019).

 

In fairness, we had redirected to the root of the file share. for example \\fileserver\usershare would direct to C:\Users\User1 - whereas the Microsoft article suggests C:\Users\User1\Documents - meaning I would have to create a 'Documents' subfolder within every user area location. And that's in addition to attempting to rename all the many 'Documents' folders back to the original name!

 

Extra workload that we didn't need...

[Davit2005]

In file explorer you can add an additional column or used to be able to, right click on the column header to add a more helpful column, It's that peskey desktop.ini file from memory. Edited July 8, 2022 by Davit2005

[TechMonkey]

I was always told to keep the folders under a sub folder so \\SHARENAME$\USERNAME\Documents. I'm pretty sure you don't need to create them, first login will create them. But it has been a while since I did it.

 

If I recall deleting the desktop.ini will clear all the folders being Documents. Again, my memory is a bit fuzzy but making your own desktop.ini and setting the security to not allow any changes shouldn't have any adverse affects.

[3s-gtech]

Add the filename column in Explorer,move it to the left, and you can forget about it entirely then.

[CrootUK]

You can do a GPO to edit the desktop.ini to fix this. Will dig it out later n post.

[msi_school]

I had a logon script that changed the attributes on the desktop ini so the administers did not have read permission which resolved this.

[CrootUK]

Apologies for this being late, this is how we resolve this issue. *UserGPO