Re: Preventing resolution changes



Here is the other link I forgot to add.

Steve

http://technet.microsoft.com/en-us/library/bb457006.aspx

"Steven L Umbach" <n9rou@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OIQRtWLGIHA.3360@xxxxxxxxxxxxxxxxxxxxxxx
Below is a helpful link on SRP. When you start out create a test
Organizational Unit with a test Group Policy linked to it and experiment
with it that way with a couple test users/computers that can be moved in
or out of that OU as needed. Also check the application log on any
computer that has SRP applied to it or a user that logs onto it can be
helpful in troubleshooting.

Steve


http://www.windowsnetworking.com/articles_tutorials/Software-Restriction-Policies.html

"Sam" <Sam@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:53333D45-3494-4D4B-9357-AD8EAC837F7A@xxxxxxxxxxxxxxxx
I looked at where the registry was being modified. Most of the 20 or so
changes occur in HKLM\System\ControSet001 where the normal user only has
read
access anyway. So I guess I will try and setup a software restriction
policy. New territory for me but I will give it a shot.

"Steven L Umbach" wrote:

Try setting a Software Restriction Policy that prevents that program
from
running using a hash rule or hash rules if there are various versions.

Another thing to try is to force Group Policy registry settings to be
reapplied even if Group Policy settings have not changed. Do that in the
appropriate Group Policy under computer configuration/administrative
templates/system/group policy - registry policy processing set to
enabled
and with process even if Group Policy objects have not changed. Then by
default every 90 minutes [default interval] or so the registry settings
should be set back to what Group Policy specifies.

To track down actual registry keys involved you could try running the
program using a registry snapshot program like the free Regshot to see
before and after changes after doing so. Then you could try changing
permissions to the registry keys involved to no allow users change
permission which also could be implemented via Group Policy or computer
startup script if needed.

http://www.softpedia.com/get/Tweak/Registry-Tweak/Reg-Shot.shtml --
Regshot

Steve


"Sam" <Sam@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:73C771EB-F3F6-4526-9E7D-F38565FA43FD@xxxxxxxxxxxxxxxx
I have group policies in place to prevent users from changing the
screen
resolutions of their desktops. Occasionally, I still find a few
screens
that
have been changed. Upon investigation, I find that the user is using
a
program (reschange.exe) downloaded from the Internet that obviously
bypasses
the gp setting. Other than software Restriction Policies, which I am
a
bit
leary of and find difficult to setup and manage, is there any other
way to
prevent resolution changes (registry permissions, etc)? I would think
that
there is a registry entry that I could harden the permissions on.







.



Relevant Pages

  • Re: Admin / Domain Admin rights problem
    ... As far as Group Policy - registry you will not see that in Local ... >> Key and SubKey - Type of Access: ... >> Detailed Access Flags: ...
    (microsoft.public.win2000.security)
  • RE: GPEDIT + Workstation Registry
    ... registry key permissions via Group Policy. ... Click OK twice to complete the settings and exit the Group Policy ...
    (microsoft.public.windows.server.sbs)
  • Re: Applying zone settings on Pop-up Blocker
    ... I checked the registry and the settings is there! ... > Troubleshooting Group Policy in Microsoft? ...
    (microsoft.public.windows.group_policy)
  • Re: Apply registry setting.
    ... registry setting to the editor in Group Policy and allow you to manage it. ... GPOE and then managed on the GPO itself. ... diagnostic value called 'Replication Events' that can be turned on the ...
    (microsoft.public.win2000.group_policy)
  • Re: Location of local policies
    ... The registry is one location. ... The Group Policy template folder contains subfolders, including, but not ...
    (microsoft.public.windowsxp.security_admin)