05.03.2013 Views

MCSA/MCSE Self-Paced Training Kit (Exam 70-270): Installing ...

MCSA/MCSE Self-Paced Training Kit (Exam 70-270): Installing ...

MCSA/MCSE Self-Paced Training Kit (Exam 70-270): Installing ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

!<br />

Lesson 1 Overview of Security Policy<br />

16-11<br />

<strong>Exam</strong> Tip An easy way to remember the order in which GPOs are processed is that first the<br />

local GPO is processed, and then Active Directory GPOs are processed. Active Directory GPOs<br />

are processed starting with the farthest structure from the user (the site), then the next<br />

closer structure to the user (the domain), and finally the closest structure (the OU). You can<br />

also use the acronym LSDOU (local, site, domain, organizational unit) to help you remember.<br />

Note Administrators can configure the order in which GPOs are applied if multiple GPOs<br />

exist for a site, domain, or OU. In addition, administrators can control whether GPOs from<br />

higher levels are overridden or not, which might affect how GPOs are processed.<br />

How Group Policy Is Applied<br />

Obviously, processing policies when a user logs on is a pretty complicated endeavor.<br />

After all, a large number of GPOs might be linked (either directly or through inheritance)<br />

to the computer that a user is logging on to and to the user account being logged<br />

on with. The following steps describe how Group Policy is applied when a computer<br />

that is part of Active Directory starts and a user logs on.<br />

1. During startup, the computer obtains an ordered list of GPOs, based on whether<br />

the computer is a member of Active Directory or not. If not, only the local GPO is<br />

processed. If the computer is a member of Active Directory, the list of GPOs to<br />

process is based on the Active Directory structure and inheritance, as discussed in<br />

the preceding sections.<br />

2. If the GPOs linked to the computer have not changed since the last time the computer<br />

started, no processing is done. If the GPOs have changed, they are all processed<br />

again.<br />

3. The computer applies any Computer Configuration settings, which occurs in the<br />

familiar order: local, site, domain, OU.<br />

4. Startup scripts specified by any GPOs now run. Each script must complete or time<br />

out before the next script begins.<br />

5. The logon screen is displayed to the user. The user presses CTRL+ALT+DEL and<br />

enters credentials to log on to the network.<br />

6. Once the user is authenticated, the computer loads the user profile (which is governed<br />

by the GPOs in effect).<br />

7. The computer receives an ordered list of GPOs that are linked to the user. Again,<br />

if no GPOs have changed since the last time the user logged on, no processing is<br />

done. If the GPOs have changed, they are all processed again.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!