Registry editing via startup script

[BigFinn]

How do you roll out a .reg patch to the workstations via GPO or startup script? Has anyone successfully done this?



I'm trying to roll out a patch that allows Exchange 2000/Outlook 2003 to allow the mailing of URLs via Send As, I've created the new Outlook Security Settings public folder with it's altered template.

I find that unless the user has local admin rights, no registry editing is possible.

-regini won't run
-regedit won't run
-reg won't run.

I'm up against NTFS permissions to the registry files, I assume.

Clients are XP, server is 2000.

I've had a look at .ADM template files, but don't know the syntax to write these or even if they work.

Can anyone advise how they overcame this?

Kind Regards

BF

 

[BigFinn]

I've found a halfway house:

'Multi-Remote Registry Change v4'

by Eytcheson Software.

Even the demo of this allows the importing/changing of keys into remote PC registries, regardless of who is logged on at the receiving end. You can change stuff live, 'under' the user logged in.

I've not worked out how to run it from a login script, but 'command-detonating' a reg change to multiple PCs is almost as good. It's a stand-alone tool, not GPO/AD linked at all.

If you pay the license, you can upload changes to more than 10 machines at a time.

BF