Re: Terminal Services SUBST mapping by default

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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@xxxxxxxxxxxxxx> 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...@xxxxxxxxx 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?
.

Relevant Pages

  • Re: Terminal Services SUBST mapping by default
    ... There you can define a "normal" home directory ... During logon to a terminal server Windows checks for a TS ... nothing happens (unless you use logon scripts to map drives). ...
    (microsoft.public.windows.terminal_services)
  • VPN Logon script problem
    ... scripts to map network drives, ... drives except for the users' Home Drives. ...
    (microsoft.public.windows.server.networking)
  • Re: Mapped Network Drives Problem
    ... facilities to your logon script made it immediately obvious! ... > I went back to the login scripts and realised that the logon scripts were ... >> which run login scripts to map network drives depending on the section ...
    (microsoft.public.win2000.networking)
  • Re: Logon Scripts
    ... scripts to map my users network drives and I just need some pointers to get started. ... I am trying to map a drive to my personal folder on the server. ... When the .bat file runs, it fails to map the drive. ...
    (microsoft.public.windows.server.networking)
  • Re: Map a network drive based on group policy
    ... I use scripts on my network to map drives. ... applied the batch files in the logon scripts in user configuration. ...
    (microsoft.public.win2000.group_policy)