Re: Prevent home drive mapping from appearing in terminal server

Tech-Archive recommends: Fix windows errors by optimizing your registry

Why on earth would you want users to have 2 different home drives,
a non-TS and a TS home drive???
There is *no* setting in an AD account for a TS-specific home
drive, only for a TS-specific profile!

> In all the above scenarios I've tried redirecting HOMEDRIVE and
> HOMEPATH to the user's local profile, with no luck.

Maybe you mean profile in stead of home drive? Profiles and home
drives are two *very* different things, and users *should* have a
TS-specific profile, as well as one single home driver, which they
can access at all times.

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

=?Utf-8?B?VGhlIEJpZyBB?= <The Big A@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 12 jan 2006 in
microsoft.public.windows.terminal_services:

> Hi everyone,
>
> Hope you are all well. Just a small query:
>
> If a terminal server user does not have a terminal server home
> drive within active directory, the user's normal non-TS home
> drive (also from active directory) is mapped instead.
> One of the apps running on the terminal server doesn't just look
> for the drive letter, it follows environment variable paths. Can
> I suppress this non-TS home drive mapping so that it doesn't
> map, and also ensure the environment variables don't point to
> the non-TS home drive?
>
> I have done a lot of investigation and haven't found a reliable
> way to do this yet. Anyone who knows anything useful would be
> greatly appreciated.
>
> If you want to know what I've done already... below are tools I
> have tried:
>
> Net use H: /d /y (worked a treat). Deleting the drive mapping is
> easy.
>
> SET HOMEDRIVE=..... but once you've logged on and launch cmd,
> when you type in SET you see that HOMEDRIVE=H:
>
> Modified registry HKCU\Volatile Environment\HOMEDRIVE.... but
> when you launch cmd you find HOMEDRIVE=H:
>
> Tried vbscript - used WshShell.Environment object (all of
> SYSTEM, USER, PROCESS) and set HOMEDRIVE in there. No luck.
> after running you still find HOMEDRIVE=H:
>
> In all the above scenarios I've tried redirecting HOMEDRIVE and
> HOMEPATH to the user's local profile, with no luck.
>
> Previously on windows 2000 terminal server the home drive
> mapping has not taken place. I haven't changed anything
> significant to make it happen.
>
> Anyone have any clues what to do next?
.

Relevant Pages

  • Re: Prevent home drive mapping from appearing in terminal server
    ... > Why on earth would you want users to have 2 different home drives, ... We're setting up special software to run on terminal server from head ... This software requires a both a TS users home drive and a TS profile ... know how to suppress the non-TS home drive. ...
    (microsoft.public.windows.terminal_services)
  • Re: Prevent home drive mapping from appearing in terminal server
    ... If you are using Windows 2003 TS server, you can use GPO to specifiy a TS home directory. ... software to run on terminal server from head office. ... home drives are two *very* different things, and users *should* have a TS-specific profile, as well as one single home driver, which they can access at all times. ...
    (microsoft.public.windows.terminal_services)
  • Re: GPO Not Setting TS Home
    ... Are the settings for the TS profile and TS home drive in AD ... conflicting with the settings in your GPO? ... user account have TS Profile and TS Home drives set in AD. ...
    (microsoft.public.windows.terminal_services)
  • Registry tatooing
    ... in the user's profile to a subdirectory of a share, ... This morning I found a policy setting in User ... home drives are being mapped properly. ... It seems this could be an example of registry tatooing because these ...
    (microsoft.public.windows.server.active_directory)