Loading
Active Directory Discovery - Forests, Domains and Sub-Domains

Anyone else seeing this in Inventory.

 

When configuring the Active Directory discovery module either in the SMACC as per the documentation or via the admin tool now on gateway servers the LDAP lookup will only do the following:

 

a) Lookup the domain first in the list to discover - any additional domains added just get ignored and no errors logged in the logs to say why.

 

b) If a root domain is the first and only one in the list the LDAP lookup fails to take in to account any sub-domains off the root domain. Suggesting the LDAP looking is not talking to the Global Catalog for it's information.

 

Are people getting around these easily resolved in 'app code' LDAP issues by having to put gateway servers in any and all sub domains where discovery is needed?

 

I've got an open ticket with Support but it's been open for months with no progress. Even with it affect Atlas Extenders too.

 

 


  • Detlev Eufinger (Flexera Software)

    hey Joseph,

     

    which version are you using?

     

    In our latest Snow Inventory Server Version 6.9.2 we have some updates for AD Discovery

    Expand Post
    • I had hoped 6.9.2 and the mentions of AD Discovery changes would resolve this long standing issue.

      Sadly they don't address it and we had hoped with it sharing the same code as the Atlas extender this would add more focus on getting it working.

      Case number 04761155 if you wanted to get more information.

      Expand Post

Loading
Active Directory Discovery - Forests, Domains and Sub-Domains