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%

Gabriel Simmons wrote:
> 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%

Are any of the computers hooked up to printers with card readers installed?
This often causes problems with mapping drives to the lower letters of the
alphabet.

Kerry

No, we do not use card readers.

"Kerry Brown" wrote:

> Gabriel Simmons wrote:
> > 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%
>
> Are any of the computers hooked up to printers with card readers installed?
> This often causes problems with mapping drives to the lower letters of the
> alphabet.
>
> Kerry
>
>
>

Gabriel Simmons wrote:
> No, we do not use card readers.

Many current HP printers have them and even setup access over the network
for all pc's running their software. A lot of new pc's HP/Compaq, Dell,
Gateway, and many others come with card readers installed. Usually the
readers take up two or three drive letters depending on how many different
card types they support. Users using USB flash drives can also cause
problems with lower letters. It was just a thought. Since I started seeing
this I have changed all drive mappings to start at Z: and work down.

Kerry

>
> "Kerry Brown" wrote:
>
>> Gabriel Simmons wrote:
>>> 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%
>>
>> Are any of the computers hooked up to printers with card readers
>> installed? This often causes problems with mapping drives to the
>> lower letters of the alphabet.
>>
>> Kerry

Thanks for the info. Do you have any other ideas?

"Kerry Brown" wrote:

> Gabriel Simmons wrote:
> > No, we do not use card readers.
>
> Many current HP printers have them and even setup access over the network
> for all pc's running their software. A lot of new pc's HP/Compaq, Dell,
> Gateway, and many others come with card readers installed. Usually the
> readers take up two or three drive letters depending on how many different
> card types they support. Users using USB flash drives can also cause
> problems with lower letters. It was just a thought. Since I started seeing
> this I have changed all drive mappings to start at Z: and work down.
>
> Kerry
>
> >
> > "Kerry Brown" wrote:
> >
> >> Gabriel Simmons wrote:
> >>> 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%
> >>
> >> Are any of the computers hooked up to printers with card readers
> >> installed? This often causes problems with mapping drives to the
> >> lower letters of the alphabet.
> >>
> >> Kerry
>
>
>
>

Gabriel Simmons wrote:
> Thanks for the info. Do you have any other ideas?

Try posting the question in microsoft.public.windows.group_policy or
microsoft.windows.server.networking

Although I use and administer networks with AD I'm by no means an expert :-)

Kerry

>
> "Kerry Brown" wrote:
>
>> Gabriel Simmons wrote:
>>> No, we do not use card readers.
>>
>> Many current HP printers have them and even setup access over the
>> network for all pc's running their software. A lot of new pc's
>> HP/Compaq, Dell, Gateway, and many others come with card readers
>> installed. Usually the readers take up two or three drive letters
>> depending on how many different card types they support. Users using
>> USB flash drives can also cause problems with lower letters. It was
>> just a thought. Since I started seeing this I have changed all drive
>> mappings to start at Z: and work down.
>>
>> Kerry
>>
>>>
>>> "Kerry Brown" wrote:
>>>
>>>> Gabriel Simmons wrote:
>>>>> 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%
>>>>
>>>> Are any of the computers hooked up to printers with card readers
>>>> installed? This often causes problems with mapping drives to the
>>>> lower letters of the alphabet.
>>>>
>>>> Kerry