You expect the folder name to be the user name. This behavior may create many Documents folders on the network share. If you try to rename one Documents folder, all the other Documents folders change to that name.
This is due to file permissions on the Desktop. This how-to provides a PowerShell script that adjusts file permissions on the desktop. To keep things simple, consider creating a folder on the data drive your user's folders are stored called "docfix" or something similar. Then unzip and rename the script as well. PowerShell doesn't allow just anything to run right out of the box, so you'll need to allow downloaded scripts to run, so type:.
If you have users that use XP, the script will generate a large number of error messages in red at first. This is to be expected, as these folders do not contain a desktop. The script will soon begin finding and adjusting the desktop. Unless you feel comfortable leaving the execution policy set as is it IS a security risk you know , you should set it back to restricted.
Type this in PowerShell:. Open an explorer window to your redirected users folder on the Windows R2 server via UNC on a remote computer and scroll to the M's. It's important that you do this from a workstation, and not on the server itself. Verify that you do not see any folders listed as "My Documents". This "feature" can range from a minor administration annoyance to a full-on headache when trying to track down the right user's files, especially when you have a large number of Windows 7 users that have folders that are all showing up as "My Documents".
Hopefully this will save you some headaches like it has done for me. Glad you guys are getting some mileage out of this. I'll see if I can find the technet posting but MS responded to a couple of users about this problem and it doesn't sound like it's going to be corrected any time soon, so this seems like the best fix in town to me. I have one question - if this is not the appropriate spot please let me know and I can re-post elsewhere. I am new to Spice. I ran the script and everything went smoothly.
On the file server R2 all of the folder names were changed from "My Documents" to the appropriate username. I was able to log into my workstation Windows 7 as a domain admin and browse to users' folders and the names were still correct.
However, when logging in as any other user the folders still showed up as "My Documents". So, at the server things are good; and logged into a workstation as a domain admin, things are also good; but when I log in as a non domain admin user the My Documents folders still appear when viewing a share.
Did anyone else have this issue? Thanks in advance. With a little script-fu I'm sure you'd be able to adjust the script to your liking or needs, but I guess my question is That should not be something that the end users have access to browse or read In the Settings pane, right-click the Document folder and select Properties. On the Target tab, click the Setting drop-down list arrow, and select Basic - Redirect Everyone's Folder to the Same Location, which reveals additional options.
There is another option to configure folder redirection to different locations based on group membership, but for this example, select the basic redirection option. In the Target Folder Location section, there are several options to choose from and each should be reviewed for functionality; for this example, select Create a Folder for Each User Under the Root Path. This is very important if multiple folders will be redirected; more details are explained in the following steps.
Notice how the end-user name and Document folder will be created beneath the root share folder. This requires that the end users have at least Change rights on the share permissions and they must also have the Create Folder and Create File NTFS permissions on the root folder that is shared.
If necessary, check the check box to also apply redirection to Windows , Windows XP, and Windows Server operating systems. Click OK to complete the folder redirection configuration. A warning pop-up opens that states that this policy will not display the Folder Redirection node if an administrator or user attempts to configure or view this group policy using policy management tools from Windows , Windows XP, or Windows Server Click Yes to accept this warning and configure the folder redirection.
After the profile completes loading, click the Start button, and locate and right-click the Documents folder. Anyone experienced this one? Do the solutions provided also address that problem? Using Windows Standard R2. Trying to get all users "My Documents" folder to the server, without going to each PC. Method 3 has a bad link on the KB that MS wants you to use.
I know, that isn't a Spiceworks problem, but still frustrating. To continue this discussion, please ask a new question. Laplink Software, Inc. Neil Laplink. Which of the following retains the information it's storing when the system power is turned off? Submit ». Get answers from your peers along with millions of IT pros who visit Spiceworks.
0コメント