Solved Mapped drive server change / reverting back to old server

Dell / Latitude e6420
January 17, 2014 at 07:39:17
Specs: Win 7 Pro x64, I7 Sandy Bridge 2.201 GHz / 8072 MB
Hello All,
I had a mapped drive set up on our company network. Recently I changed the server where the mapped folder resides.I use a logon script in Active Directory to automatically map drives whenever a user logs in. I modified the logonscript to the new server and for most clients it is working. A few clients are still being reverted back to the old server when they log in. The drive letter is the same (F:). I was thinking maybe something on the local clients is causing this I.E. a registry setting. Any ideas why this is happening? Solutions?

~winipcfg

ASCII Question, Get an ANSI


See More: Mapped drive server change / reverting back to old server

Report •

✔ Best Answer
January 17, 2014 at 09:42:55
The former share they were previously mapped to should be unshared. This will automatically make the mapping error out. Then it should be just a matter of disconnecting the drive on the client.

The mapped drive letter exists in a number of locations in the registry. I don't know off hand which is the one associated with reconnect at logon.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's



#1
January 17, 2014 at 08:12:58
Two easy things that come to my mind are 1) Are these clients logging on to the mapped drive using another log-in name and password? and 2) is the box for "reconnect at log-on" checked? Probably neither one but it's worth a check.

Report •

#2
January 17, 2014 at 08:29:29
Chrisgraf2,
Thanks for the suggestions. Unfortunately is is not either of those things. When a user logs in they will have drives mapped automatically because of the logonscript in AD. It has to be something local, just not sure what.

~winipcfg

ASCII Question, Get an ANSI


Report •

#3
January 17, 2014 at 08:54:19
Did you review/update the DNS server entries concerning the servers?
Are you perhaps mapping by ip address instead of host name?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

Related Solutions

#4
January 17, 2014 at 09:04:05
Hi Wanderer,
Should be no need to update the DNS. The script is set to map by name, not IP address. This is only happening to very few users maybe only 5% of clients. Myself included. I'm certain at this point that the problem is local, as I tested a theory. I had a spare laptop that I wiped out and reformatted. With a new Windows installation the drives mapped correctly, where they wouldn't before the reformat. Do you happen to know where the mapped drives are stored in the registry? I looked around but didn't have much luck. I still think something's sticking in the registry that shouldn't.

~winipcfg

ASCII Question, Get an ANSI


Report •

#5
January 17, 2014 at 09:19:44
I have never used the feature I'm going to ask you to check, so I'm not sure if it's related to your issue.

Right-Click on the mapped drive and see if there is a checkmark on the "Always available offline".


Report •

#6
January 17, 2014 at 09:36:18
There is not a checkmark next to Always Available Offline. Won't that just index the shared folder?

~winipcfg

ASCII Question, Get an ANSI


Report •

#7
January 17, 2014 at 09:42:55
✔ Best Answer
The former share they were previously mapped to should be unshared. This will automatically make the mapping error out. Then it should be just a matter of disconnecting the drive on the client.

The mapped drive letter exists in a number of locations in the registry. I don't know off hand which is the one associated with reconnect at logon.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#8
January 17, 2014 at 10:05:30
Thanks Wanderer,
I didn't think of unsharing the original location.

~winipcfg

ASCII Question, Get an ANSI


Report •

Ask Question