Registry Keys & Values with Group Policy

  • Thread starter Thread starter joh
  • Start date Start date
J

joh

Hi All,

I need some help; I read somewhere that one can
deploy/modify registry keys on remote clients using Group
Policy. Is this available with a W2K domain? If so, how is
it done?

Thanks,

joh
 
Joh,

What is it that you want to deploy? Most of the Registry settings can be
configured in ADM templates, which are very easy to create and deploy.
 
Thanks for you reply. We are using VNC and we want to use
some advanced features, such as users being prompted to
accept incoming connections. These configurations require
registry changes, such as adding a key, and modifing a
couple of values. If you could give me an example of how
to do this, that would be great.

Thanks.
joh
 
this ADM template code modifies the Registry to perform an auto logon:


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
CLASS MACHINE ;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

CATEGORY BCN_Custom_ADMs
POLICY Auto_Logon
KEYNAME "SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon"
part "What is the name of the user?" EDITTEXT
VALUENAME "autoadminlogon"
end part
part "What is the user's password?" EDITTEXT
valuename "defaultpassword"
END PART
END POLICY
END CATEGORY
 
I find it easy to export the reg key(s) you want and the make a batch file
to run on logon. and use the format.

c:\winnt\regedit.exe /s YourChanges.reg
exit

real simple.
 
joh,

Policy Maker include a *free* registry extension to Group Policy. Within
the GPOE, you can browse to any setting(s) and make it a policy. It's fully
compliant with the GP specification. You also get 25 categories of
filtering on each setting, user and computer policy, RSoP reporting,
tracing, policy event logging, etc. You can control whether settings are
enforced, automatically removed, tatooed, or are just one-time preferences,
and you can set all types of values. You can't do these things with ADM
template customization, which is not well suited for setting non-policy
values, and of course performing configuration in scripts prevents your
settings from being and acting as policy settings.

Regards,

Eric Voskuil
Policy Maker
http://www.autoprof.com/policy
 
Back
Top