Can't remove unwanted network drives

[WinNSun]

I am having an issue with a network drive trying to reconnect when users try to launce applications via Citrix. I have disconnected this drive, removed the drive letter mapping from the network entry in the registry, remapped the drive letter in question, deleted all profiles except All users, Administrator, and Default user. I launched a Citrix desktop after with out issue. Then I launched Word still no problem. Then Excel, at this point the system tries to connedt to the network drive in question, even though it has nothing to with it. After this anytime a user logs in the drive tries to map. Any Ideas?

 

[xs4citrix]

Could you check the HKEY_Users key for the mapping on that server?

http://www.printingsupport.com

Free citrixprinting support

 

[WinNSun]

Yep, I deleted the drive letter from within that key, then remapped to a different drive using the same drive letter, selected reconnect at login. Next login, the old drive mapping reappears. I tried via command line with net use, making the mapping persistent, still no luck.

 

[maximumbit]

did you customize your "default profile"? you should log in as a local administrator with admin powers and see if it tries to map network drives. If it does, your default profile has the setting in there. You need to correct it on the default profile if that is the case.

 

[geek2d]

Could be the usrlogon.cmd file under the system32 folder. Try editing it to see if net use is set to map these drives.

 

[bran2235]

I think/bet geek2k is right... BUT, try the (in a script or at a cmd line) net use x: /delete with the drive that you want to get rid of. Then follow the same line with the net use x: >destination<

Maybe this will help...

Brandon

 

[WinNSun]

When I log in as local admin, it does not try to map the drive.
Now only certain users have the problem. I delete their profile from the farm servers, when they try to access it again they (except for one) are fine.
1) I had to uninstall the application & the pervasive client it runs on
2) run a search for s:\ (the drive in question)and delete all entries
3) delete all profiles that accessed apps on that server
4) reinstall pervasive and the application using unc pathing
5) set the s:\ mapping in the usrlogon.cmd specifying user and password.

The previous admin had set the drivemapping up via map network drive with the reconnect at logon option checked. After that any access to the server tried to map that drive.
I think the first install of the Pervasive client was the culprit.

Thanks for all you help.