Mapped network drive won't reconnect at logon
Posted on 2006-11-30
I have a Windows 2003 Server box that I am using as a terminal server. Because of a "unique" licensing scheme a particular piece of software uses, I need different users to see different drives. The "keys" that allow the software to work reside in the root directory of the drive. Different keys unlock different features so each user needs to be able to only "see" his own key and none of the others. I tried to solve this by creating diffent folders with different shares and permissions on the local C: drive. I then map network drives for each user to the different shares. I put the "key" for each user in his own mapped network drive - no keys will go in the root of the C: drive. This works fine for the Administrator account, but certain other accounts won't keep the drive mapping. I can map the network drive, making sure to check the "Reconnect at logon" box and use it. I can copy files into and out of it. However, when I log off and back on, the network drive is gone. Any files I put in the shared folder are still there, but the drive mapping is gone. This problem occurs with accounts that I have "locked down" as much as possible. I assume I turned off some kind of permission that was needed, but I have no idea which one it was.