System Collection based on Directory Group

[Nat Taylor]

I would be grateful if anyone can advise where I am going wrong. I have configured and tested Directory Service. The directory group specified is ou=servers, ou=app_ldn_ewi, ou=app_ldn, ou=app_gb, ou=app, DC=eur, DC=nsroot, DC=net. The Directory Service task looks like it completes correctly, but when I create a system collection for Directory Group starting with "app", no servers are listed.

[Aravindh Rajaram]

Did you make sure that after running the directory services tool, the systems that you are trying to make part of the collection are all have the right AD related attributes set? You can do that by using the following command:

mxnode -lf

See if you can view the AD related attributes in the XML format output that you get. If not, there is some problem with the DN that you supply to configure the Directory service.

[Nat Taylor]

Thanks AMicSys
I have checked the Directory Service configuration and think it is correct.
When I output the details of every server using mxnode -lf, every server has the distinguised name listed eg:

My team's server OU:
sw-attribute name="distinguishedName">CN=EURDCLN003,OU=Servers,OU=app_ldn_ewi,OU=app_ldn,OU=app_gb,OU=app,DC=eur,DC=nsroot,DC=net

or

Our domain controllers
CN=EURDCLN003,OU=Servers,OU=app_ldn_ewi,OU=app_ldn,OU=app_gb,OU=app,DC=eur,DC=nsroot,DC=net

However when I try to create a custom collection based on Directory Group or OU no servers are listed. If I choose OU contains APP all the servers are returned. However because I am trying to set this up for multiple teams I need to drill down to the dept code level eg EWI

I wonder if the _ in the OU path is causing any issues? Any advice would be appreciated as this is driving me mad!!!