I have a reg file that I'd like to have imported to several windows XP PCs on my WAN. I'd like to know if there's a quick and easy way to do it. The users of the PCs are not administrators so I need this to be done even if the users doesn't have rights to modify the registry. What is the quickest and sure way of doing this?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
The easiest way (to my mind) is to create a startup (or logon) script (depending on what part of the registry you are altering) using a batch file with reg add /f in it.
http://www.petri.co.il/reg
(syntax is easy - given on the site above)
The quickest way (if there are only a few machines) is to find the computer names/ip addresses, and connect to them from your computer.
Open regedit from the run menu. Go to file --> connect network registry. Enter the name of the computer you want to connect to and connect to it. After a successful connection, go to file--> import and select your registry file. That's it!
We do it all the time with non-admin users.
I would use a GPO and a batch file. put the reg file in a share on the server, create a gpo to run the batch file on logon and it should run the reg file, or you could have the batch file run the reg file from the local workstation. Connect to the admin share of the C drive (\\wkstnand\c$) place the file there and set the batch to run the file on the local computer instead of getting it from the remote server. (need admin rights/account of local machine or domain admin to connect to admin share of remote wkstn.)
Good luck
Can you term serv or remote desktop to the users in question? If you setup a shared drive, you can copy the the .reg file locally to their desktop and start > run > regedit and import the file to the registry.
There is no automated way of doing this to all users in one time that I'm aware of except for SMS.
Because of the amount of machines, you want to use a vbs login script. You can assign each user to load XYZ.vbs script under the AD profile section. If you already have a login script, you can then have it call your registry script. Just put the scripts in your domain controllers netlogon share. Here are some samples. The sections are described in the notes of each.
----------------------
Dim WSHNetwork, objNetwork, objShell, WshShell, regkey, SRegMarkerValue, clDrives, boolPersistent
Set objNetwork = WScript.CreateObject("WScr
Set objShell = WScript.CreateObject("WScr
Set WSHNetwork = WScript.CreateObject("WScr
boolPersistent = True ' True = Persistent ; False = Not Persistent
On Error Resume Next
'Disconnect ALL mapped drives
Set clDrives = WshNetwork.EnumNetworkDriv
For i = 0 to clDrives.Count -1 Step 2
WSHNetwork.RemoveNetworkDr
Next
'Map all drives BoolPersistent forces it to remain when disconnected
objNetwork.MapNetworkDrive
objNetwork.MapNetworkDrive
On Error Goto 0
'This is to call other scripts
objShell.Run "sample.vbs"
'This is to set the autodisconnect for drive mapping to "Never"
Set WshShell = WScript.CreateObject("WScr
regkey = "HKLM\SYSTEM\CurrentContro
On Error Resume Next
readreg = WshShell.RegRead(regkey, -1, "REG_DWORD")
If Err Then
Err.Clear
RegRead = Null
End If
'Adds autodisconnect registry key if not found or if different
If regkey <> readreg Then
WshShell.RegWrite "HKLM\SYSTEM\CurrentContro
End If
Wscript.Quit
By using the script approach, you can add/remove scripts and have them call other scripts (nested) as the environment/business needs change. I add call scripts to the main script all the time. This way all I have to do is change one vbs script and I can leave the individual users alone.
By using a login script, you eliminate the admin rights need. I have 3 registry files checked and deleted/added as needed per user login. I basically prevent users from changing certain settings each time them login.
A gpo is nice, but I have found that some registry entries have problems when being applied via gpo (plus, if you plan to change to vista/win 2008 server, you may have problems. We had some with registry and certificates).
If you are using batch files vs. vbs, then you may want to consider changing over to vbs. Vbs allows for much greater flexibility, though accomplishing some of the same tasks is more difficult to add (e.g. Adding network shares). Vbs improves login speed if the script is larger than 4-6 lines or calls other scripts. We noticed a significant improvement in our international environment.
Business Accounts
Answer for Membership
by: mwecomputersPosted on 2007-11-06 at 12:49:13ID: 20227472
It might be possible to do it via this solution:
http://searchwincomputing.
You might also be able to do it via Microsoft Software Update Services:
http://www.petri.co.il/sus
http://www.wsus.info/forum
http://www.experts-exchang
Even though this link is for creating GPOs for MSI Installation, it could perhaps be modified for registry changes...
http://home.fnal.gov/~jkle