Back them up - and if you really don't like them, you can revert these to their default state.Īlso I don't need to be demeaned on this site from someone who can't even formulate proper sentences. Click Site Settings to wipe cookies and reset site permissions for example, or. Don't Delete the Default Domain Policy or the Default Domain Controllers Policy. If Opera is your web browser of choice, then you can go to Advanced in Settings to access a variety of reset options.Once all have been replaced or countered, and the environment is to your liking, that would be the appropriate time to remove old GPOs. It would be recommended (if you "dislike" the GPOs in place) to create new ones - with higher precedence - that supplant the existing GPOs.At the very least, you should keep the "old" GPOs around and not linked to anything so that you have a reference if ever needed for troubleshooting. It is possible that a) you do not recognize what some settings are doing, or b) you have overlooked the importance of some others. It would probably benefit you more to not "nuke and pave" if you do not fully understand Group Policy anyway (only assumed because you're apparent unfamiliarity with tattooing).It would be much easier to reverse any settings applied by these GPOs by using the very GPOs you "dislike" Honestly - well a few things come to mind: This is what I remember reading at some point and why I asked about removal from registry as opposed to the GPMC. Unmanaged policy- Settings remain even if the machine or user falls out of scope. Managed Policy- These settings are changed when policy is applied and should change back to what they were if the user or computer falls out of the scope of a GPO. The problem is the previous user did not create unique GPO's, he did most editing in the default domain and controller policies.