/build/static/layout/Breadcrumb_cap_w.png

KACE Inventory pulls the users full name in devices. Is it based on AD ?

KACE Inventory  pulls the users full name in devices.  Is it based on AD  ? 



2 Comments   [ + ] Show comments
  • thanks a lot great... - rahimpal 4 years ago
  • Do you have Authentication set up to use your AD? - JasonEgg 4 years ago

Answers (1)

Answer Summary:
Posted by: akmagnum 4 years ago
Red Belt
1

Top Answer

By default, this is from the last logged on user.....

not from active directory.

Of course, you could make it from AD if you wanted

by creating a custom inventory rule......


Comments:
  • Thanks akmagnum,

    can you please give me simple example how to fetch from AD, CIR rule pls


    any idea how does it fetch these details?
    Full name and Domain, we use LN LDAP

    User Logged: KACE\ALEX
    User Full name: ALEX M
    User Name: Alexm
    User Domain: KACE - rahimpal 4 years ago
    • The info you posted seems like it's coming from the inventoried computer, not any AD source. There needs to be some type of mapping between the "logged user" detail in inventory and the KACE users in Settings > Users. In our environment, Windows users log in to the domain so what links user records to computers is their network username - JasonEgg 4 years ago
  • yes we have both AD and lotus notes LDAP - rahimpal 4 years ago
    • How do you import and/or authenticate users? (I.E. What are you settings in Settings > User Authentication and do you have any scheduled imports?) - JasonEgg 4 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ