Control Modifying Proxy Settings Using Registry Editor

You don't mention what made you decide to make that change to that Key. I assume that it was identified in some online article.

I suggest that you use something like RegShot to check what happens when you disable it normally, in group policy.
regshot - SourceForgeNet
regshot Discussion - SourceForgeNet
How to Use Regshot To Monitor Your Registry - HTG

You'll first need to delete that new entry before starting with RegShot so that you have a good foundation for the experiment.
- Export it first to a .reg file as a form of backup.


Best of luck,
Denis

Wolfy7 said:

I don't have problem identifying my registry changes.

I assume from that remark that RegShot confirms that it is that Registry change that takes place when you change the setting in Group policy.

Wolfy7 said:

I can disable and re-enable the proxy easily from group policy it works fine but the problem occurs when I try to apply that in the Registry. It works only one way, that is (disabling). I want to do it in two ways (enable & disable) through registry.

I have also found Registry changes that do not have the effect of the change made through the user interface. And some that do have the effect but are not shown as such in the user interface.
You might also experiment by, say, creating the Key Value you to want to disable the feature then deleting it again to enable the feature [instead of changing its Data entry to 0].



Best of luck,
Denis

Wolfy7 said:

So the scenario is like this, once the admin login they double click the .reg file created in their desktop and it directly enables proxy through registry, they can also disable it using a different .reg file.

And my creating / deleting idea, if it works, could also be managed the same way - one .reg file for enable, another .reg file for deletion.

Many people prefer batch files using reg commands as an alternative to .reg files.
The batch files can run without interruptions [without confirmation dialogs etc].
You can set them up so that even the Admin prompt is bypassed - that's a bit fiddly and only applies to the specific batch file you set it up for. It also ought only to be used for batch files held within folders that you have applied protective permissions to so you can be reasonably confident that malware is not going to creep in behind your back.
I can elaborate on these statements if they are of interest to you.
You'd want to start with seeing if the creating / deleting idea works using .reg files first because there's no point trying to make something more convenient if it does not work anyway.

All the best,
Denis

If you can prove that the idea of managing your Registry entries using .reg files works then it's worth looking at using reg commands instead.
Please remember that it was just an idea. I do not know if it will work or not.

To use reg commands instead of .reg files, see these guides
Reg - SS64
reg - MSLearn
And there are several examples of reg commands in
Reg examples - TenForums
As you'll see from those guides & examples, you'll essentially be cutting & pasting bits of your .reg files into the batch files.

By all means post back for further guidance but do make sure that the .reg file solution works first.
reg commands cannot solve the problem if those .reg files cannot.
reg commands would just be a more convenient method [in my opinion] not a more effective one.

Best of luck,
Denis