Attention: The forums will be placed on read only mode this Saturday (Oct. 20, 2018)

During this outage (6:30 AM to 8 PM PDT) the forums will be placed on read only mode. We apologize for this inconvenience. Click here to read details

Windows Legacy OS forum

General discussion

trouble with xp registry

by pdumond / March 10, 2008 4:43 AM PDT

I administrate a small windows peer to peer network. I want to stop users from changing static ip address computers to dhcp. Because of our accounting software the users have to be local administrators on the workstation. I tried making a registry change, that I read about at I added a new key "Network Connections" under [HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\ then added the new DWORD value. After reboot no change. Any help or other ideas would be appreciated.
thanks, pete (

Discussion is locked
You are posting a reply to: trouble with xp registry
The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our CNET Forums policies for details. All submitted content is subject to our Terms of Use.
Track this discussion and email me when there are updates

If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.

You are reporting the following post: trouble with xp registry
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
Collapse -
Why not...
by R. Proffitt Forum moderator / March 10, 2008 4:47 AM PDT

Just issue a policy statement about this? It beats battling the users.

Collapse -
What do you mean
by pdumond / March 10, 2008 4:51 AM PDT
In reply to: Why not...

You wrote:
"Just issue a policy statement about this? It beats battling the users."

What do you mean?

Collapse -
Just a guess
by Jimmy Greystone / March 10, 2008 5:17 AM PDT
In reply to: What do you mean

Just a guess, but I imagine Bob meant putting out a memo telling employees not to mess with that, and threatening some kind of reprisal should it happen.

You could also use the "Run As" function to run just the accounting program as an administrator, and the users themselves would be regular users. This would require the users to enter in a password every time they want to run the program, but that shouldn't be more than 1-2 times a day. There's the added headache of having to make a new account on each system that needs to run this program, so you'll need to make a decision about whether or not it's worth it.

Personally, I'd just start by putting out a memo asking people not to change those settings. If that doesn't work, put out a memo that has some consequences for anyone who does change those settings. If those consequences aren't enough, you can use the "Run As" or alternate credentials method I talked about above on a user by user basis. Just prohibit this special admin level account from being able to log in, so they don't try and end run you.

Popular Forums

Computer Newbies 10,686 discussions
Computer Help 54,365 discussions
Laptops 21,181 discussions
Networking & Wireless 16,313 discussions
Phones 17,137 discussions
Security 31,287 discussions
TVs & Home Theaters 22,101 discussions
Windows 7 8,164 discussions
Windows 10 2,657 discussions


Your favorite shows are back!

Don’t miss your dramas, sitcoms and reality shows. Find out when and where they’re airing!