Hi All,

I'm not sure if this is the right group, but if it's not then please
let me know which group is more appropriate!

I changed a logon script on the sysvol of the DC to remove a drive
mapping from a file server that we took offline. The problem that we
are having is that 2k and XP clients still attempt to map to that drive
even though we removed it in the logon script. I'm pretty sure the
script is cached somewhere locally but I don't know where and I don't
know the proper way to force the machines to load the modified logon
script.

I know it's the right script because when I log into a fresh machine it
maps all the drives correctly. BTW, we are using static profiles!

Thanks for any help or suggestions!

The drives are probably persistent (equivelant of "reconnect at logon" check
box in a static mapping). Try adding the line:

net use O: /delete

where O: is the id of the phantom drive.
After it's gone forever, you can remove the line.

.....kurt

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi All,
>
> I'm not sure if this is the right group, but if it's not then please
> let me know which group is more appropriate!
>
> I changed a logon script on the sysvol of the DC to remove a drive
> mapping from a file server that we took offline. The problem that we
> are having is that 2k and XP clients still attempt to map to that drive
> even though we removed it in the logon script. I'm pretty sure the
> script is cached somewhere locally but I don't know where and I don't
> know the proper way to force the machines to load the modified logon
> script.
>
> I know it's the right script because when I log into a fresh machine it
> maps all the drives correctly. BTW, we are using static profiles!
>
> Thanks for any help or suggestions!
>