Mapping network drive, disconnecting.

[Dazzo]

After a recent server upgrade our shared location moved from B to A. I remapped all the computers network drives however a number of them are reconnecting the old drive. I slightly remember a cmd for it about making the old one stop connecting at start up and the new one to do so. I already checked the connect at startup box but ti still happens.

Is there a command for it or am I off the mark?

Darren

[danielno8]

"net use X: /delete" may work

another option may be to remap the old drive map, but this time take out the checkmark in the box, this may override the previous mapping where reconnect at logon was selected.

[Dazzo]

Thank you daniel, i will try both methods.

[Qs]

Originally Posted by Dazzo

Thank you daniel, i will try both methods.

Also make sure you don't have a login script set up, otherwise the old drive will continue to map.

Qs

[danielno8]

yeh i made the assumption there were no login scripts as he mentioned he remapped all the computers network drives

[Qs]

Originally Posted by danielno8

yeh i made the assumption there were no login scripts as he mentioned he remapped all the computers network drives

You can still re-map network drives with or without a login script.

Better to cover all bases.

Qs

[danielno8]

Originally Posted by Qs

You can still re-map network drives with or without a login script.

Better to cover all bases.

Qs

yeh that being the reason for the thread in first place lol?

[Qs]

Originally Posted by danielno8

yeh that being the reason for the thread in first place lol?

Originally Posted by Dazzo

I remapped all the computers network drives however a number of them are reconnecting the old drive. I slightly remember a cmd for it about making the old one stop connecting at start up and the new one to do so. I already checked the connect at startup box but ti still happens.

The OP is manually mapping drives (hence the 'startup checkbox' comment above). He's not editing login scripts himself.

Therefore, if a login script is in place which the OP doesn't know about then this could be the sole cause of the problem.

Geddit?

Qs

[danielno8]

not really.....I know he is mapping manually....My first comment to you was merely stating I ASSUMED he wasn't using login scripts, wasn't trying to say you shouldn't have asked him to clarify whether there were login scripts in use.

Geddit?

[Qs]

Originally Posted by danielno8

not really.....I know he is mapping manually....My first comment to you was merely stating I ASSUMED he wasn't using login scripts, wasn't trying to say you shouldn't have asked him to clarify whether there were login scripts in use.

Geddit?

Assuming the lack of script use isn't going to help rectify the problem. As stated previously, it's better to ask the question than assume incorrectly.

Qs

[danielno8]

lmao i know this hence my post to you sayin i made the mistake of assuming there were no login scripts

/the end

[dazza786]

handbags down!

i'm sure i posted on here, but yeah what has been pointed out multiple times:

- "net use X: /delete" may work
- make sure there's no script which maps the drives via gpo
- another option may be to remap the old drive map, but this time take out the checkmark in the box, this may override the previous mapping where reconnect at logon was selected.

[Dazzo]

I've tried both suggestions however none seem to work.

I've looked for the scripts also but cannot find any and spoke to previous person in my role who said he never made any logon scripts.

My thought after pondering the computers in question is maybe it's a batch file of some sort (probably made via the people who supply us with this program) so i logged the error with themselves. Or maybe it's a batch file made via some-one else so i'm looking into it and found one common batch file at the moment.

I'm still waiting to hear back from them and still looking into the problem myself as i have to remap pcs daily, easy to do but annoying doing it each morning.

Thank you for continuing to help me solve this problem.

[Dazzo]

After extensive searching over lunch i found the problem. Was a batch file on a select group of PC's that remapped the drive. Was stored in all users start up so it was happening to whomever logged onto the station and was stored on the old server. The old server is not in use anymore which is why it only seemed to happen to individuals and when deleted from the all users start up folder it works fine.

First time I've came accross the batch files used in this way.

Thanks again for helping steer me in the right direction, without the login script comment i would never have thought to look for a batch file..... funny how the mind works.

Regards

Darren

[Qs]

Originally Posted by Dazzo

without the login script comment i would never have thought to look for a batch file..... funny how the mind works.

Regards

Darren

No problem, glad it's sorted.

Qs