Mysterious Drive Connection

  • Thread starter Thread starter Michiel Lange
  • Start date Start date
M

Michiel Lange

Recently we have installed a new server and put it in our (AD) domain.
We also created a new user. While we use scripts to connect to drives
and this user should not get any network connections this user got one
(q:) which according to the scripts he should NOT have gotten.

Opened NTUSER.DAT on the domain controller's 'Default User'
(C:\Documents and Settings\Default User) and attempted to find this
drive. (no luck here) The normal profile path is D:\profiles (which is
shared as <server>\profiles) there is no "Default User" in this path,
so I assumed these settings would come from the Default User on the
C-disk (?)

Anyone any idea where this mysterious Q: drive comes from and how we
can remove it from being connected by default?
 
Michiel Lange said:
Recently we have installed a new server and put it in our (AD) domain.
We also created a new user. While we use scripts to connect to drives
and this user should not get any network connections this user got one
(q:) which according to the scripts he should NOT have gotten.

Opened NTUSER.DAT on the domain controller's 'Default User'
(C:\Documents and Settings\Default User) and attempted to find this
drive. (no luck here) The normal profile path is D:\profiles (which is
shared as <server>\profiles) there is no "Default User" in this path,
so I assumed these settings would come from the Default User on the
C-disk (?)

Anyone any idea where this mysterious Q: drive comes from and how we
can remove it from being connected by default?
Click to expand...

- Log on as the problem user.
- Disconnect drive Q:.
- Start a Command Prompt.
- Type this command: net use /persistent:no
 
Back
Top