Registry tatooing

In another thread I referred to problems getting the home drive mapped
in the user's profile to a subdirectory of a share, in that the drive
letter would often be mapped to the root of the share instead of the
subfolder.

This morning I found a policy setting in User
Configuration\Administrative Templates\System\User Profiles that
directly controls this behaviour and after I disabled this policy, the
home drives are being mapped properly.

It seems this could be an example of registry tatooing because these
computers were connecting to a Windows NT type domain (Samba) using the
System Policies before.

Is there much documentation about the problems of registry tatooing? Is
there some means to reset all the old NT4 policy settings?

.

Relevant Pages

  • 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)
  • 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
    ... Why on earth would you want users to have 2 different home drives, ... a non-TS and a TS home drive??? ... > HOMEPATH to the user's local profile, ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)