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

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...
Post a Comment
Read more

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.
Post a Comment
Read more

Device expanded/shrank messages are reported in the VMkernel log for VMFS-5

    Symptoms A VMFS-5 datastore is no longer visible in vSphere 5 datastores view. A VMFS-5 datastore is no longer mounted in the vSphere 5 datastores view. In the  /var/log/vmkernel.log  file, you see an entry similar to: .. cpu1:44722)WARNING: LVM: 2884: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device shrank (actual size 18424453 blocks, stored size 18424507 blocks) A VMFS-5 datastore is mounted in the vSphere 5 datastores view, but in the  /var/log/vmkernel.log  file you see an entry similar to: .. cpu0:44828)LVM: 2891: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device expanded (actual size 18424506 blocks, stored size 18422953 blocks)   Purpose This article provides steps to correct the VMFS-5 partition table entry using  partedUtil . For more information see  Using the partedUtil command line utility on ESX and ESXi (1036609) .   Cause The device size discrepancy is caused by an incorrect ending sector for the VMFS-5 partition on the ...
Post a Comment
Read more