Terminal Services SUBST mapping by default

[prosbloom@gmail.com]

Hello, I have a terminal server with around 25 users connecting. The
problem we are having is windows is mapping the W: drive by default
for every user to the users home directory. It is not a net use
mapping, but rather a subst map. We have to map the W: drive to a
different place because some of our software is hardcoded to use the
W: drive. There is no group policy in place and no login scripts
running that would be forcing this drive map. Any ideas where or why
windows would be mapping this drive?

 

[Helge Klein]

Windows probably uses the settings in the Active Directory user
objects in your case. There you can define a "normal" home directory
(and drive) and a TS home directory. Please check both entries.

Remarks: During logon to a terminal server Windows checks for a TS
home directory entry in the user object first. If it finds none, it
uses the "normal" home directory instead. If none are configured,
nothing happens (unless you use logon scripts to map drives). A home
directory defined in a GPO overrides the settings from the user
object.

I hope this helps.

Helge

==================
Please visit my blog:
http://it-from-inside.blogspot.com
==================

On 8 Aug., 20:35, prosbl...@gmail.com wrote:
> Hello, I have a terminal server with around 25 users connecting. The
> problem we are having is windows is mapping the W: drive by default
> for every user to the users home directory. It is not a net use
> mapping, but rather a subst map. We have to map the W: drive to a
> different place because some of our software is hardcoded to use the
> W: drive. There is no group policy in place and no login scripts
> running that would be forcing this drive map. Any ideas where or why
> windows would be mapping this drive?

 

[Vera Noest [MVP]]

My guess is that it is defined in UsrLogon.Cmd

W: is the default letter assigned to the %RootDrive% variable, when
you run an application compatibility script.

195950 - How and why ROOTDRIVE is used on Windows Terminal Server
http://support.microsoft.com/?kbid=195950

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Helge Klein <Helge.Klein@googlemail.com> wrote on 08 aug 2007 in
microsoft.public.windows.terminal_services:

> Windows probably uses the settings in the Active Directory user
> objects in your case. There you can define a "normal" home
> directory (and drive) and a TS home directory. Please check both
> entries.
>
> Remarks: During logon to a terminal server Windows checks for a
> TS home directory entry in the user object first. If it finds
> none, it uses the "normal" home directory instead. If none are
> configured, nothing happens (unless you use logon scripts to map
> drives). A home directory defined in a GPO overrides the
> settings from the user object.
>
> I hope this helps.
>
> Helge
>
> ==================
> Please visit my blog:
> http://it-from-inside.blogspot.com
> ==================
>
> On 8 Aug., 20:35, prosbl...@gmail.com wrote:
>> Hello, I have a terminal server with around 25 users
>> connecting. The problem we are having is windows is mapping
>> the W: drive by default for every user to the users home
>> directory. It is not a net use mapping, but rather a subst
>> map. We have to map the W: drive to a different place because
>> some of our software is hardcoded to use the W: drive. There
>> is no group policy in place and no login scripts running that
>> would be forcing this drive map. Any ideas where or why
>> windows would be mapping this drive?