When managing a Workspace Environment Management (WEM) Configuration set, it is crucial to understand how Active Directory (AD) objects are integrated. First, for efficiency, the WEM administration console allows administrators to add multiple user accounts in a single operation by separating their names with semicolons. Second, computer objects can be added either individually by name or by importing an entire Organizational Unit (OU) containing multiple machines. Finally, the fundamental workflow in WEM requires that an AD object (such as a user, group, or OU) must first be added to the configuration set before any specific actions, filters, or assignments can be applied to it.

B. WEM fully supports adding AD security groups. Disallowing groups would severely limit its administrative scalability and functionality, which is contrary to its design.

E. Item Priority is a core feature in WEM used for conflict resolution and can be applied to objects in both the "Users" and "Machines" sections, including OUs.

1. Citrix Workspace Environment Management Documentation, "Active Directory Objects." This section details the process for adding users, groups, and OUs. It explicitly states, "Type the names of the users you want to add, separated by semicolons (;)" when adding users, confirming option A. It also shows distinct options for adding Users, Groups, and OUs, invalidating option B.

2. Citrix Workspace Environment Management Documentation, "Machines." This documentation outlines the methods for adding computer objects to a configuration set. It describes the functionality of both the "Add OU" and "Add Object" buttons, which allows for the addition of OUs containing computers or individual computer accounts, respectively. This supports option C.

3. Citrix Workspace Environment Management Documentation, "Assignments." This section explains the WEM workflow. It clarifies that administrators must first select a user, group, or OU from the list (which presupposes it has already been added) and then add actions to the "Assigned" pane for that object. This confirms the procedural requirement in option D. The same section also discusses the use of priority for assigned actions, which applies to all object types, making option E incorrect.