Skip to main content

Failed to perform redirection of folder My Documents

 Dear All,

I want to share this case with you.
When you planned to migrating your infrastructure you may need to change users roaming folders and their mapped drive.
Accually you may face some issues while changing their new redirection target.
If you find an error at event viewer as below:
The event ID: 112 and 1085.



"Failed to perform redirection of folder My Documents. The files for the redirected folder could not be moved to the new location. The folder is configured to be redirected to <\\Server2\home\%USERNAME%\My Documents>. Files were being moved from \\server1\home\user to <\\server2\home\user\My Documents>. The following error occurred while copying <\\server1\home\user\Ashraf\MUM\GLOBAL\2009\AR\revi wed\Copy of file.xls> to <\\server2\home\user\My Documents\Ashraf\MUM\GLOBAL\2009\AR\reviwed\Copy of file.xls>:

The specified network name is no longer available. "

You may need to do some troubleshooting as below:
1.May be two GPOs were being applied, one at the domain level and the second at the OU level. Both handled folder redirection. The Group Policy Results Wizard showed that neither of the GPOs were actually being applied. If the user having trouble logged on to another computer, the GPOs and folder redirection worked properly. If any other user logged on to the problematic computer, folder redirection worked properly. The solution was to rename the local copy of the user's profile and have the system recreate it by using a "fresh" copy of the user's roaming profile.

2.When using basic folder redirection directing “C:\documents and settings\(name)\my documents” to “\\share\(name)\my documents”. The problem was the user’s permissions on their user-name folder (\\share\name), where not giving access to the user. Correcting permissions fixed this error.

Our case solution was to rename current profile "profile1" and made a new profile "profile2" with copy all data from "profile1" to the new profile "profile2".

Comments

Post a comment

Popular posts from this blog

ما هى ال FSMO Roles

  بأختصار ال FSMO Roles هى اختصار ل Flexible Single Operation Master و هى عباره عن 5 Roles فى ال Active Directory و هما بينقسموا لقسمين A - Forest Roles 1- Schema Master Role و هى ال Role اللى بتتحكم فى ال schema و بيكون فى Schema Master Role واحد فى ال Forest بيكون موجود على Domain Controller و بيتم التحكم فيها من خلال ال Active Directory Schema Snap in in MMC بس بعد ما يتعمل Schema Register بواسطه الامر التالى من ال Cmd regsvr32 schmmgmt.dll 2-Domin Naming Master و هى ال Role المسئوله عن تسميه ال Domains و بتتأكد ان مفيش 2 Domain ليهم نفس الاسم فى ال Forest و بيتم التحكم فيها من خلال ال Active Directory Domains & Trusts B- Domain Roles 1-PDC Emulator و هى ال Role اللى بتتحكم فى ال Password change فى ال domain و بتتحكم فى ال time synchronization و هى تعتبر المكان الافتراضى لل GPO's و هى تعتبر Domain Role مش زى الاتنين الاولانيين و بيتم التحكم فيها من خلال ال Active directory Users & Computers عن طريق عمل كليك يمين على اسم الدومين و نختار operations master فى تاب ال PDC Emu
Post a comment
Read more

Question كيفية عمل share للـ outlook conntact لكل الـ Domain Users

  الحل بسيط جدا عايز الكونتاكت تتحدث دايما بحيث انك لما تضيف يوزر جديد يسمع في الكونتاكت اول حاجه بتدخل علي in office 2003 tools --- email account ---- add address book --- internet directory service (LDAP) type your server name then login info . mark this server require me to logon type any user on active directory and its password then save and close outlook and open it again now you will find all your active directory users in address book
Post a comment
Read more

Recreating a missing VMFS datastore partition in VMware vSphere 5.x and 6.x

    Symptoms A datastore has become inaccessible. A VMFS partition table is missing.   Purpose The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the last rescan. The partition table is physically located on the LUN, so all vSphere hosts that have access to this LUN can see the change has taken place. However, only the hosts that do a rescan will be affected.   This article provides information on: Determining whether this is the same problem Resolving the problem   Cause This issue occurs because the VMFS partition can be deleted by deleting the datastore from the vSphere Client. This is prevented by the software, if the datastore is in use. It can also happen if a physical server has access to the LUN on the SAN and does an install, for example.   Resolution To resolve this issue: Run the  partedUtil  command on the host with the issues and verify if your output
Post a comment
Read more