Group Policy Objects
Group Policy Objects
Every user who uses the system is impacted when Group Policy is created at the local level.
However, once you take action and use Active Directory, you may have virtually unlimited
Group Policy objects and choose just which users and computers will receive which settings.
When a GPO is created, two things happen: Some brand-new entries within Active Directory
occur, and automatically some brand-new files are created on our domain controllers. These
collectively make up one GPO.
In order to establish a group policy object, follow these steps, but bear in mind that you must be
logged in as a user account that has permission to do so:
Go to Start -> Administrative tools -> and select Group policy management
Ensure you expand your Active directory forest to domains in order to find the Group
Policy objects node linked to your domain in the dropdown
Right-click on Group Policy Objects, click on New, choose a name and then press Ok
In the left pan, expand the container of Group Policy Objects, right-click on the GPO you
created, and then choose Edit in order to open the Group Policy Management
Editor window and set up the required settings you need.
In order to link a GPO with a setting you’ve configured, go to the organization unit
named Domain controllers, right-click, then select Domains, then choose the
option, Link a GPO
A GPO can only be utilized within the domain in which it was formed after being created.
To apply a GPO’s settings, you link it to one or more sites, domains, or OUs:
No matter which domain or OU a particular account is in, if a GPO is linked at the site
level, its settings apply to all user accounts and computer accounts in that particular site.
This is configured using Active Directory Sites and Services and is based on the IP subnet
that the user’s PC belongs to.
When a GPO is linked at the domain level, all users and computers in the domain, across
all OUs below it, are affected.
When a GPO is linked at the OU level, it has an impact on every user or machine in that
OU as well as all OUs below it (which are called child OUs or sub-OUs).
You can however step in and manage how GPOs are applied to a specific domain, site, or OU by
doing any of the following:
Changing the link order: In the event of a conflict, the setting in the GPO with the
lowest link order will take precedence because it is processed last and has the highest
priority.
Blocking inheritance: All GPOs are automatically inherited by child OUs from the
parent, however, you can prevent this inheritance.
Enforcing a GPO link: By default, any conflicting settings in GPOs linked to child OUs
take precedence over the settings for parent OUs, but you may reverse this behavior by
setting a GPO link to Enforced.
Disabling a GPO link: For all GPO links, the processing is by default turned on.
However, by turning off the GPO link for a specific container, you can stop a GPO from
being applied to that container.
Incase you want to link a GPO to more than one domain, then you must:
Create exactly the same GPO in each domain using the GPMC (group policy
management console).
Using the GPMC or a third-party tool, create the GPO in one domain and duplicate it in
the other domains.
Utilize policy linking between domains. However, it is well acknowledged that this is a
harmful practice.