Yes, absolutely, this is the very foundation of Group Policy hierarchy. Group Policies are applied in the following order:
- Local Group Policy (Based on the client machine - this is not connected to your AD Group Policy)
- Site Level Policies
- Domain Level Policies
- OU Level Policies
Within each of the latter 3, each 'level' can have multiple GPO's and their order is decided by the system administrator. This is called the "link order" and the lowest number is processed last, which means that policy has the final say.
OU policies are applied starting at the "root", and then downwards, if that makes sense.
Here is some good reading on the subject:
With regards as to what to actually do with the individual GPO, well that kind of depends on the policy itself, but generally, they have the following three options:
- Not Configured
And all that happens is that the very last policy to execute will have the final 'say' on what the final setting with. With the exception of 'Not Configured' where no changes are made. 'Not configured' is the default for all options within Group Policy when you create a new GPO.
So, if your current policy has a setting that is "Enabled", you need to create a GPO with the same setting "Disabled".