Loading
Active Directory Discovery

Hi All ,

We have Active Directory Discovery in our environment and all the Assets are getting discovered from all the OU.

But we have servers and clusters  in the OU named *servers* (cluster being logical entity only i.e just the name of clusters  eg : CLUxxyyzz).

So ,we are getting these Clusters in the list of devices not getting inventoried. (Since we cannot install agent on the cluster name ).

Is their any way to  remove or restrict snow to recognize cluster names as a asset  ?

or can Snow tag the cluster name to their respective nodes ?

Regards // Shahbaz


  • Hi Marcel , Thank for the comments !! , i was just checking if we could stop these CI's appearing on the report at the first place to reduce the validation tasks . Also if i delete it from the Inventory Smacc , will it reappear again on the next discovery (Just curious) ? Regards // Shahbaz
    • Community Manager (Flexera Software)

      Hi ‌, clearing out the discovery results via SMACC or even the database will result in all items reappearing with the next discovery run. An effective solution would be to restrict the AD discovery user if possible. Another solution could be to write a small sql script to clear out the information from the database on a regular basis. However this is not update proof and out of any support. Please do not edit anything in the database if you don't feel comfortable with it. You might call your Account Manager or Certified Snow Partner to request Professional Services for this. /marcel Customer Success Manager Did someone answer your question? Make sure to mark it as answered! Welcome to Snow! Discover more here: 
      Expand Post
      • Thanks Marcel , I'll probably try to tweak the LDAP query in the device discovery to filter out the Data in SMACC . Regards // Shahbaz
  • Community Manager (Flexera Software)

    Hi ‌, please be aware that Active Directory Discovery is not an inventory solution and it will not create datasets as active machines. It will just populate the report "Computers that are not inventoried" and make you aware of open tasks to complete. It's on the license management team to validate this information and filter out irrelevant information.   /marcel Customer Success Manager Did someone answer your question? Make sure to mark it as answered! Welcome to Snow! Discover more here: 
    Expand Post
  • I think this would be a great add to the idea board as well. The ability within the Master Server AD Discovery to include/exclude certain OU's would be a good one to limit the scope for both computers and users. I think it would also be good to have additional options there like "Don't bring in disabled objects, objects over 90 days, etc." to reduce time and data storage. Pretty sure some of this is done already in the LDAP query Snow uses, but not sure we know what that query is today.
    Expand Post
  • Hi all,

    Did anyone got it sorted by any chance? I'm quite new and looking at the same issue where cluster names apearing in the discovered assets not inventoried.

    Thanks.

Loading
Active Directory Discovery