Re: Registry tatooing
- From: "Erik Cheizoo" <echeizoo.XenD.nl@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 8 Jan 2007 17:51:59 +0100
Unfortunately, there is no such thing as registry reset (if you don't count setup.exe as an viable solution ;-) )
The only way to revert tattooed settings is creating a reverse policy (with the opposite setting), leave it for a few weeks (till all workstations/users have logged on at least once) and then set the setting to not defined.
--
Kind regards,
Erik Cheizoo
eXcellence & Difference - we keep your business running
============================================
Always test in a non-production environment before implementing
Guidelines for posting: http://support.microsoft.com/?id=555375
============================================
"NZSchoolTech" <nzschooltech@xxxxxxxxxx> wrote in message news:1168202323.107958.299240@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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?
.
- Follow-Ups:
- Re: Registry tatooing
- From: Ace Fekay [MVP]
- Re: Registry tatooing
- References:
- Registry tatooing
- From: NZSchoolTech
- Registry tatooing
- Prev by Date: Cannot create/copy accounts in active directory
- Next by Date: Re: Setting default logon hour for new users
- Previous by thread: Registry tatooing
- Next by thread: Re: Registry tatooing
- Index(es):
Relevant Pages
|
Loading