• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 921
  • Last Modified:

Import registry to XP workstation from 2000 server

I have Windows 2000 Server and 25 XP workstations

Trying to remove all "My Network Places" Icons from START and Explorer.

I have a .Reg file that works great (that is, when I logon as administrator).

But if I logon as a user with limited rights I get an error
"not all data was sucessfully written to the registry. Some keys are open by the system or other processes."

I have tried a batch file that calls my .reg file and used regini.exe but still only work if I'm administrator.

What I want to do is have a user (with limited rights) logon and at startup import these keys in the registry?
1 Solution
You can use gpedit.msc on the workstations to make these changes - click start>run>gpedit.msc

Hope this helps.
Seelan NaidooMicrosoft Systems AdminCommented:
From your reg file, you know what keys to edit..
Therefore you need to grant the users logging on full control of the specific registry key

1. Open Registry Editor.
2. Click the key to which you want to grant full control.
3. On the Edit menu, click Permissions.
4. Under Group or user names, click the user to whom you want to grant full control of your registry key.
5. Under Permissions for name, where name represents the name of the user to whom you are granting full control of the key, select the Allow check box for Full Control.


You could also make the changes via a GPO, [since you are aware of the registry keys] which apply to the users configuration of the GPO, and results in the spefic key modifications as needed.

This would be my preferred method, since its the easiest to configure and deploy.

mchaney69Author Commented:
I want to change the reg keys of the WS without having to manually go to every pc and log on and change the registry permissions as admin

if that was the case, i'd just log on as admin and ad run the reg file...

What Security Threats Are We Predicting for 2018?

Cryptocurrency, IoT botnets, MFA, and more! Hackers are already planning their next big attacks for 2018. Learn what you might face, and how to defend against it with our 2018 security predictions.

Seelan NaidooMicrosoft Systems AdminCommented:
Try a using a Startup script..

Any changes to HKLM can be done in a Startup script, using Group Policy.

Startup scripts run with System privileges on the local machine, so you can modify just about anything.
You could use the "runas" command to execute the .reg file or script with administrator credentials:


Or you can use a .vbs script so the admin password is not required / and or visible to the user.

Hope this helps.
Rich RumbleSecurity SamuraiCommented:
in addition to runas i have a VB script that allows you to automatically enter the password for the higher priv account see here:

The Active Directory sugestion (above) should also work, you can assign the changes to machines automatically that way.

Featured Post

Cyber Threats to Small Businesses (Part 1)

This past May, Webroot surveyed more than 600 IT decision-makers at medium-sized companies to see how these small businesses perceived new threats facing their organizations.  Read what Webroot CISO, Gary Hayslip, has to say about the survey in part 1 of this 2-part blog series.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now