Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've got a 2k3 functional level domain environment. I'd like to use group policy to deploy a few registry settings.

I know that this can be done through GP Preferences client side extentions (which means deploying and validating the deployment of that CSE installer, which I'd prefer to avoid) and through a GP deployed start-up script (which feels a little clugey, and will take forever to apply). I'd much rather create a central admx or adm template that I can use to manage the settings I need.

Group policy in a lot of cases is just a happy interface for a lot of different registry settings. Can I just take a random admx file and modify it for my needs? What are the syntax pitfalls I should be concerned with? Is there a reference guide that I'm just missing?

share|improve this question
up vote 1 down vote accepted

GP Preferences are so ridiculously useful that I'd hesitate to work around them. Plenty of work has been done in deploying the CSE easily. If you have WSUS already, you can download Feature Packs and then approve the updates for the Client Side Extensions.

The above link also includes a GPO startup script to install it if you don't have WSUS, but I agree that it's a kludge. Below is another example script.

Example through computer startup script:

share|improve this answer

Try using NUTS. It has a REG to ADM utility.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.