Home Drive F Mapping Issue

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We have a Windows 2003 Active Directory domain setup. When a user logs on to
the network from a Windows XP computer with SP2 installed, the home drive
sometimes maps as it is supposed to, but not all the time. The home folder is
set in the user properties of AD to map F:\ to \\sancluster\Users$\%USERNAME%
and sometimes the F Drive is mapped to \\sancluster\Users$ instead. We also
have this mapping to get set in user login scripts, but if the F drive is
already mapped it skips this portion. I have tried changing the login scripts
to delete the mapping, but it does not correct the group policy update
problem. One other thing I have noticed is that when group policy updates
according to Application Event Log with ID 1704, then the drive is sometimes
disconnected and reconnected to \\sancluster\Users$ instead of the
\\sancluster\Users$\%USERNAME%
 
We have a Windows 2003 Active Directory domain setup. When a user logs on to
the network from a Windows XP computer with SP2 installed, the home drive
sometimes maps as it is supposed to, but not all the time. The home folder is
set in the user properties of AD to map F:\ to \\sancluster\Users$\%USERNAME%
and sometimes the F Drive is mapped to \\sancluster\Users$ instead. We also
have this mapping to get set in user login scripts, but if the F drive is
already mapped it skips this portion. I have tried changing the login scripts
to delete the mapping, but it does not correct the group policy update
problem. One other thing I have noticed is that when group policy updates
according to Application Event Log with ID 1704, then the drive is sometimes
disconnected and reconnected to \\sancluster\Users$ instead of the
\\sancluster\Users$\%USERNAME%
Click to expand...

Gabriel,

Why do you setup your user share as "\\sancluster\Users$"? This makes it an
administrative share, which by definition, the users lack access to. What is
the other mapping to drive F, that is, the mapping which sometimes prevents the
proper mapping?
 
The share is followed with a $ so that it is hidden from the network
neighborhood browsing capability. Users have the appropriate share
permissions for accessing the hidden share. All of our drive F mappings are
set to map to \\sancluster\Users$\%USERNAME%. When group policy updates
occurr, then the drive appears to be disconnected and remapped to
\\sancluster\Users$ instead of \\sancluster\Users$\%USERNAME% which is where
user files point to and My Documents folder is redirected.
 
Back
Top