Discussion Locked

Remote registry change

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I need to make a registry change to over 300 NT workstation's, I cannot put a call to a .reg file in the logon script because almost none of the user's have admin right's. Does anybody know how to do this without going to all the machine's because it has to be done in the course of one weekend and that is just a pain to do on over 300 machine's. No we don't have SMS and no third party software because the company is cheap. I am pretty sure there is no way but I thought I would ask anyway.

3 replies

by joseph moore

Calling a .REG file from a user logon script runs under the Local System account context. Local System is a default NT account, and it is a member of the Local Administrators group on every NT workstation.
So, you should be able to call the Registry file in the users logon scripts, and it will work.
For example, I use a central file server to distribute virus software definition files. All user workstations are configured to scan \\VSERVER\DAT every day for the latest updated definition file.
A few weeks ago, the machine name of this server was changed to FSERVER.
As you can then guess, this change broke the virus definition updates for everyone. They were looking for \\VSERVER, and it was no longer on the network.
So, I configureda workstation to look for \\FSERVER\DAT, then I exported this piece of REgistry out into a file (VIRUS.REG).
I then copied this REG file to the Netlogon share on my PDC and BDC, and made this entry into every user logon script:
CALL REGEDIT /S VIRUS.REG

It will work for you. Set this up, then let your users log in on Monday. Users don't need admin access for a REG file import from a logon script to work.

Hope this helps.

This discussion is closed to new replies.