When configuring AD, what can be added as exceptions?

Study for the ePolicy Orchestrator (ePO) Certification Exam. Enhance your knowledge with flashcards and multiple-choice questions, each providing hints and explanations. Prepare to excel on your certification journey!

Multiple Choice

When configuring AD, what can be added as exceptions?

Explanation:
In AD configurations that involve filtering or scoping, an exception is typically a boundary you want to exclude from processing. Organizational units are the containers used to structure the directory and define administrative boundaries. Because you often want to exclude entire branches of AD from a sync or policy application, specifying an OU as an exception makes the most sense and is the most practical way to scope exclusions. Users, groups, and computers are individual objects within those containers. Excluding them one by one is rarely desirable or feasible, whereas targeting at the OU level allows you to exclude large sections of AD with a single exception entry.

In AD configurations that involve filtering or scoping, an exception is typically a boundary you want to exclude from processing. Organizational units are the containers used to structure the directory and define administrative boundaries. Because you often want to exclude entire branches of AD from a sync or policy application, specifying an OU as an exception makes the most sense and is the most practical way to scope exclusions.

Users, groups, and computers are individual objects within those containers. Excluding them one by one is rarely desirable or feasible, whereas targeting at the OU level allows you to exclude large sections of AD with a single exception entry.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy