/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


Questions about users, departments, and locations

06/02/2017 1371 views
Questions pertaining to k1000 v7:
  1. Is there a way to batch import locations for Users?
  2. Is there a way to assign users to departments? Apparently not but I can't fathom why not.
Answer Summary:
0 Comments   [ + ] Show comments

Comments


Answer Chosen by the Author

1
Information like location and department for users is typically imported from within AD, by setting additional or custom fields to import data when the users are imported or updated. If that information is not readily available in your AD and you wish to add it in then you would be best to look at either manually updating the records or otherwise creating some sort of ticket rule that updates the data within the user table.
Answered 06/05/2017 by: Hobbsy
Red Belt

  • The department info is in AD. Locations are not, though could be. But from what I've seen in documentation and on this forum, LDAP can only write such info to a label, it can't actually connect a user to a department or location asset.

    Similarly, it appears that a ticket rule CAN do this, but only after a given user logs in to trigger an action. I need a solution that works for users who never have reason to log into the k1000.
    • When users are imported via the LDAP import their location is pulled from one of the attributes in AD, for us that is physicalDeliveryOfficeName. If the value being imported is not already a location asset in the K1000 that asset it created and then associated with the user being imported. I am not sure why there isn't similar functionality for department.
      • Could you point me at where you configured that? Is it in the LDAP import setting? How do you tell the k1000 that physicalDeliveryOfficeName equals a location asset?
      • In the scheduled LDAP import (Settings, User Authentication) add the AD attribute to the list of attributes to receive. On the next page set location to the attribute that contains the location. The appliance does the rest.
      • Is there not similar functionality for other asset types, too, such as cost center? Since locations seem to be "special" asset types in v7, maybe that's why it's different?
      • Locations have acted like this since at least version 5 when we got our appliance, so it isn't because they have changed in v7. It would certainly make sense if it worked for other assets, but I can't tell you why it doesn't.

All Answers

1
Locations are actually assets, so they can be imported through the regular asset import tool. You may have to use one of the custom fields for the user as the department, that is what we do.
Answered 06/05/2017 by: chucksteel
Red Belt

  • Yes, we've used that tool to populate the location table. But linking users to those location (or department) assets is another matter, and is what I'm asking about.

    By custom field, I assume you mean you've created a field named Department that takes either free text or a defined list. I recognize I could do it that way, but I don't understand why I can't accomplish it in what seems to be a superior way for maintainability, consistency, and reporting, which is to use a department table.

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