Registry changes made via ADM file disappear after a reboot
- From: RabidVermin <RabidVermin@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 22 Jan 2009 12:11:03 -0800
I am having a problem with a registry setting that I am updating via an ADM I
have imported into the GPO and I have been tearing my hairout trying to
figure this out.
Basically, I need to make the ShowLogonOptions
(HKLM/Software/Microsoft/Windows NT/Winlogon) setting from 1 to 0 and set the
default domain. We are being told by auditors that we cannot display the
"Log on to:" box on any of our terminal servers. I created a custom ADM that
I found here:
http://www.tomshardware.com/forum/223570-46-remove-domain-drop-list
I am able to add the ADM without any trouble. I then run a gpudate and I
check the registry and I see the registry value change from a 1 to a 0. I
reboot the server and the registry value reverts back to 1.
I run rsop.msc and gpresult and it shows that I am updating the correct
policy. Just for good measure I applied the policy to every GPO that I have
in my domain. I don't have any special log out scripts, this is a pretty
vanilla server.
There are a couple of things that might have bearing on any answers to my
forthcoming questions. First, I am testing these settings on a development
domain controller at my house. Second, I have to unapply (uncheck) the
filter "Only show policy settings that can be fully managed" otherwise I
cannot see the settings in the Administrative Template that I created and
imported as described above.
My question is how do I get these settings to apply to the registry via the
GPO and then have them stick after a reboot? I am fairly new to GPO's and
ADMs. Am I missing something fundamentally easy here?
Thanks and I look forward to the reply.
.
- Follow-Ups:
- Prev by Date: Re: Domain Controller restore question
- Next by Date: Re: Domain Controller restore question
- Previous by thread: AD Query Attribute
- Next by thread: Re: Registry changes made via ADM file disappear after a reboot
- Index(es):
Relevant Pages
|