Trying to use an Active Directory Path to define a group.
What syntax does BigFix use?
I've tried a few things, but nothing seems to work.
This topic has been locked.
Pinned topic Active Directory Paths
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Lee Wei 270003U2EX76 Posts
Re: Active Directory Paths2008-11-24T21:11:16ZThis is the accepted answer. This is the accepted answer.Hi,
There is an inspector for Active Directory that looks like the following:
Q: distinguished name of local computer of active directory
If you use the predefined property "Active Directory Path", it will return a format similar to the one above.
Maybe if you describe your AD structure and what/how you would like to filter the computers, someone might be able to help.
Re: Active Directory Paths2008-11-25T13:59:26ZThis is the accepted answer. This is the accepted answer.Thanks. I tried running that in QnA (after finding it within the Active Directory Path property), but I get "Singular expression refers to nonexistent object". Any reason why that would be? Looking at the summary for workstations, it's clear that BigFix is getting the AD path.
Re: Active Directory Paths2008-11-25T14:06:38ZThis is the accepted answer. This is the accepted answer.Additionally, am I even going about this the right way?
What I want to do, ultimately, is create automatic groups based on which OU a device is in. So far, I'm not having much success setting Active Directory Path "equals" the path to the specific OU. If I use "contains" and a word contained within the OU, it's successful. The problem is that I would like to be as specific as possible, to eliminate the possibility of grouping items from another OU.
Lee Wei 270003U2EX76 Posts
Re: Active Directory Paths2008-11-25T17:25:33ZThis is the accepted answer. This is the accepted answer.Hi,
Maybe you can give us some specific scenarios, so we can see where the problem might be.
Re: Active Directory Paths2008-11-25T17:46:14ZThis is the accepted answer. This is the accepted answer.Let's say that I have an OU named "Special". That OU is within another OU named "Town".
AD path would be CN=Special,CN=Town,DC=MyCompany,DC=COM
I want to create an automatic group that will include every device within "Special".
When I create my automatic group, if I use Active Directory Path "equals" CN=Special,CN=Town,DC=MyCompany,DC=COM, no devices populate the group.
If i create the automatic group using Active Directory Path "contains" Special, then many devices populate the group.
The problem being that the word "Special" is used for several OUs throughout AD. I specifically want machines that are located in CN=Special,CN=Town,DC=MyCompany,DC=COM.
pmullins91 060001TQQ78 Posts
Re: Active Directory Paths2008-11-25T18:02:50ZThis is the accepted answer. This is the accepted answer.CN= likely references the name of your box only. Try "equals" CN=<name of PC>,OU=Special,OU=Town,DC=MyCompany,DC=COM instead.
contains "OU=Special,OU=Town" might do the trick for the group.
Re: Active Directory Paths2008-11-25T18:12:03ZThis is the accepted answer. This is the accepted answer.I'll give that a shot and let you know how it goes. Thanks.
Re: Active Directory Paths2008-11-25T20:09:42ZThis is the accepted answer. This is the accepted answer.Contains OU appears to be doing the trick. Thanks again.