How should the Active Directory support in Software Distribution be used?
Beginning with TEM 8.1, Active Directory Security Group and Organizational Unit membership can be used in the Software Distribution tool to create applicable Relevancy statements.
Resolving the problem
Beginning with TEM 8.1, Active Directory Security Group and Organizational Unit membership can be seen for users and computers. To help administrators take advantage of these functions, the Software Distribution tool can build Relevance statements referring to Security Group and OU membership. This capability is in the Task wizard in the Manage Software Distribution Packages dashboard under the Systems Lifecycle domain.
Click "New Task" or the Pencil icon on an existing Task.
Select or check the files and installation command for your Task.
To use Active Directory attributes for targeting, begin by selecting the phrase and match operator that matches what the attribute you want to target with, then enter a string in the text box describing the group or OU you want to target. For instance, you might select "Exists user who is a member of this AD Security Group", select "Exactly Matches", and then type in "Developers".
Note that it is possible to enable auto-fill for these text fields, which will make suggestions based on observed attributes. To enable this feature, activate the optional "Active Directory Security Groups and Organizational Units" Analysis in the Software Distribution site.
Additional clauses can be added by clicking the Plus icon on the right side, or deleted by clicking the Minus icon. For instance, you might create a second clause, select "Exists computer which is a member of this AD OU", select "Contains", and then type in "Servers".
The relationships between clauses are managed in a text bar at the bottom of the wizard using standard logical grouping tools such as parentheses, AND, OR, and NOT keywords. For instance, after adding the two clauses described above, this bar will contain "1 AND 2".
Note that all clauses are positive in nature, detecting a condition instead of the absence of that condition. To negate a condition, add NOT in front of it in the logical grouping bar. For instance, "1 AND NOT 2" would be used to install a package on any system used by a member of the Developers security group unless that system is a member of an OU with "Servers" in the name.
More support for:
IBM BigFix family
Software version: All Versions
Operating system(s): Platform Independent
Software edition: All Editions
Reference #: 1506247
Modified date: 03 October 2011
Translate this page: