Chat now with support
Chat with Support

KACE Systems Management Appliance 7.1 - Administrator Guide

About the KACE Systems Management Appliance (K1000) Getting started
Configuring the appliance
Requirements and specifications Power-on the appliance and log in to the Administrator Console Access the Command Line Console Tracking configuration changes Configuring System-level and Admin-level General Settings Configure appliance date and time settings Verifying port settings, NTP service, and website access Configuring network and security settings Configuring Agent settings Configuring session timeout and auto-refresh settings Configuring locale settings Configure data sharing preferences About DIACAP compliance requirements Configuring Mobile Device Access Enable fast switching for organizations and linked appliances Linking Quest KACE appliances Configuring history settings
Setting up and using labels to manage groups of items Configuring user accounts, LDAP authentication, and SSO Using Replication Shares Managing credentials Configuring assets
About the Asset Management component About managing assets Adding and customizing Asset Types and maintaining asset information Managing Software assets Managing physical and logical assets Maintaining and using manual asset information Managing locations
Setting up License Compliance Managing License Compliance Setting up Service Desk Creating and managing organizations Importing and exporting appliance resources
Managing inventory
Using Device Discovery Managing device inventory
About managing devices Features available for each device management method About inventory information Tracking changes to inventory settings Managing inventory information Finding and managing devices Provisioning the K1000 Agent Manually deploying the K1000 Agent Using Agentless management Adding devices manually in the Administrator Console or by using the API Forcing inventory updates Managing MIA devices Obtaining Dell warranty information
Managing applications on the Software page Managing Software Catalog inventory
About the Software Catalog Viewing Software Catalog information Adding applications to the Software Catalog Managing License assets for Software Catalog applications Using software metering Using Application Control Update or reinstall the Software Catalog
Managing process, startup program, and service inventory Writing custom inventory rules
Deploying packages to managed devices
Distributing software and using Wake-on-LAN Broadcasting alerts to managed devices Running scripts on managed devices Managing Mac profiles
Patching devices and maintaining security
About patch management Subscribing to and downloading patches Creating and managing patch schedules Managing patch inventory Managing Dell devices and updates Maintaining device and appliance security
Using reports and scheduling notifications Monitoring servers
Getting started with server monitoring Working with monitoring profiles Managing monitoring for devices Working with alerts
Using the Service Desk
Configuring Service Desk Managing Service Desk tickets, processes, and reports
Overview of Service Desk ticket lifecycle Creating tickets from the Administrator Console and User Console Creating and managing tickets by email Viewing tickets and managing comments, work, and attachments Using the ticket escalation process Using Service Desk processes Using Ticket Rules Run Service Desk reports Archiving, restoring, and deleting tickets Managing ticket deletion
Managing Service Desk ticket queues About User Downloads and Knowledge Base articles Customizing Service Desk ticket settings Configuring SMTP email servers
Maintenance and troubleshooting
Maintaining the appliance Troubleshooting the K1000
Appendixes Glossary About us Legal notices

Importing users from an LDAP server

Importing users from an LDAP server

You can import user information from LDAP servers to create user accounts on the K1000 appliance. This provides administrators, such as Service Desk staff, with a richer set of data to use when working with users.

There are two ways to import user information:

Import user information manually

Import user information manually

You can import user information manually by specifying criteria to identify the users you want to import.

1.
Go to the Users page:
a.
Log in to the K1000 Administrator Console, http://K1000_hostname/admin. Or, if the Show organization menu in admin header option is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information.
b.
On the left navigation bar, click Settings, then click Users.
c.
Select Choose Action > Import Users.
NOTE: Use the LDAP Browser to specify the Search Base DN and Search Filter. See Use the LDAP Browser.

Option

Description

Server

The IP address or the hostname of the LDAP server. If the IP address is not valid, the appliance waits to timeout, resulting in login delays during LDAP authentication.

If you have a non-standard SSL certificate installed on your LDAP server, such as an internally-signed certificate or a chain certificate that is not from a major certificate provider such as VeriSign, contact Quest Support at https://support.quest.com/contact-support for assistance.

Port

The LDAP port number, which is usually 389 (LDAP) or 636 (secure LDAP).

Base DN

The criteria used to search for accounts.

This criteria specifies a location or container in the LDAP or Active Directory structure, and the criteria should include all the users that you want to authenticate. Enter the most specific combination of OUs, DCs, or CNs that match your criteria, ranging from left (most specific) to right (most general). For example, this path leads to the container with users that you need to authenticate:

OU=end_users,DC=company,DC=com.

Advanced Search

The search filter. For example:

(&(sAMAccountName=KBOX_USERNAME)(memberOf=CN=financial,DC=example,DC=com))

Login

The credentials of the account the K1000 uses to log in to the LDAP server to read accounts. For example:

LDAP Login:CN=service_account,CN=Users,

DC=company,DC=com.

If no username is provided, an anonymous bind is attempted. Each LDAP Label can connect to a different LDAP or Active Directory server.

Password

The password of the account the K1000 uses to log in to the LDAP server.

Option

Description

Attributes to retrieve

Specify the LDAP attributes to retrieve. For example:

sAMAccountName, objectguid, mail, memberof, displayname, sn, cn, userPrincipalName, name, description, manager

The LDAP attributes specified in this field can be mapped to K1000 User attributes on the next page. If this field is blank, the appliance retrieves all LDAP attributes. Leaving this field blank increases the time required to import attributes and is not recommended.

IMPORTANT: To retrieve the manager object associated with the user, you must add the manager attribute to the list, and to specify this mapping in a later step.

Label Attribute

Enter a label attribute. For example: memberof.

This setting returns a list of groups this user is a member of. The union of all the label attributes forms the list of labels you can import. If the search filter contains both the label names and user names, the label attribute is not required.

Label Prefix

Enter the label prefix. For example: ldap_

The label prefix is a string that is added to the beginning of all the labels.

Binary Attributes

Enter the binary attributes. For example: objectsid.

Binary attributes indicates which attributes should be treated as binary for purposes of storage.

Maximum Number of Rows

Enter the maximum number of rows to retrieve. This limits the result set that is returned in the next step.

Debug Output

Select the check box to view the debug output.

4.
Click Next.
The Define mapping between User attributes and LDAP attributes page appears.

Option

Description

Ldap Uid

The identifier for the user. Recommended value: objectguid.

User Name

The name of the user. Recommended value: name.

Email

The email address for the user. Recommended value: mail.

Manager

The manager of the user. This mapping is mandatory only if you want to retrieve the manager information. Recommended value: manager.

IMPORTANT: To retrieve the manager object associated with the user, you must also add the manager attribute to the Attributes to retrieve box.

Option

Description

Api Enabled

Whether users are enabled to access the K1000 using the KACE GO app. Access is enabled if the field contains a numerical value. Access is disabled if the field contains no value. Therefore, to enable access, select an attribute that returns a numerical value. To disable access, select No Value.

Ams Id

Not used in the K1000 6.4 release. Recommended value: No Value.

6.
Optional: In the Role drop-down list, select the role for the imported users. See Add or edit User Roles.
7.
Optional: In the Labels drop-down list, select the label to apply to imported users. See About labels.
8.
In the Search Results section below the attribute mapping drop-down lists, verify that the list of users to import is correct, and the information listed for each user is what you expect. To refine your search, click the Back button and revise the search parameters and attributes.
For example, to change the number of Search Results, change the Maximum Number of Rows on the Choose attributes to import page.
9.
Click Next to display the Import Data into the K1000 Management Appliance page.
Only users with values for the required attributes, Ldap Uid, User Name, Email, and Manager are imported. Records that do not have these values are listed in the Users with invalid data section.
11.
Click Import Now to start the import.

The Users page appears, and the imported users appear on the list. The imported users can access the features of the Administrator Console, User Console based on the role to which they are assigned.

Import user information according to a schedule

Import user information according to a schedule

To keep user data current, schedule regular user data imports from your LDAP server.

1.
Go to the Admin-level Authentication Settings page:
a.
Log in to the K1000 Administrator Console, http://K1000_hostname/admin. Or, if the Show organization menu in admin header option is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information.
c.
On the Control Panel, click User Authentication.
2.
Select LDAP Authentication, then click the Schedule button next to the server name in the list of servers to schedule a user import: .
The User Import: Schedule – Choose attributes to import page appears.

The following Read Only Administrator Server Details are displayed:

Option

Description

Server

The IP address or the hostname of the LDAP server. If the IP address is not valid, the appliance waits to timeout, resulting in login delays during LDAP authentication.

If you have a non-standard SSL certificate installed on your LDAP server, such as an internally-signed certificate or a chain certificate that is not from a major certificate provider such as VeriSign, contact Quest Support at https://support.quest.com/contact-support for assistance.

Port

The LDAP port number, which is usually 389 (LDAP) or 636 (secure LDAP).

Base DN

The criteria used to search for accounts.

This criteria specifies a location or container in the LDAP or Active Directory structure, and the criteria should include all the users that you want to authenticate. Enter the most specific combination of OUs, DCs, or CNs that match your criteria, ranging from left (most specific) to right (most general). For example, this path leads to the container with users that you need to authenticate:

OU=end_users,DC=company,DC=com.

Advanced Search

The search filter. For example:

(&(sAMAccountName=KBOX_USERNAME)(memberOf=CN=financial,DC=example,DC=com))

Login

The credentials of the account the K1000 uses to log in to the LDAP server to read accounts. For example:

LDAP Login:CN=service_account,CN=Users,

DC=company,DC=com.

If no username is provided, an anonymous bind is attempted. Each LDAP Label can connect to a different LDAP or Active Directory server.

Password

The password of the account the K1000 uses to log in to the LDAP server.

Option

Description

Attributes to retrieve

Specify the LDAP attributes to retrieve. For example:

sAMAccountName, objectguid, mail, memberof, displayname, sn, cn, userPrincipalName, name, description, manager

The LDAP attributes specified in this field can be mapped to K1000 User attributes on the next page. If this field is blank, the appliance retrieves all LDAP attributes. Leaving this field blank increases the time required to import attributes and is not recommended.

IMPORTANT: To retrieve the manager object associated with the user, you must add the manager attribute to the list, and to specify this mapping in a later step.

Label Attribute

Enter a label attribute. For example: memberof.

This setting returns a list of groups this user is a member of. The union of all the label attributes forms the list of labels you can import. If the search filter contains both the label names and user names, the label attribute is not required.

Label Prefix

Enter the label prefix. For example: ldap_

The label prefix is a string that is added to the beginning of all the labels.

Binary Attributes

Enter the binary attributes. For example: objectsid.

Binary attributes indicates which attributes should be treated as binary for purposes of storage.

Maximum Number of Rows

Enter the maximum number of rows to retrieve. This limits the result set that is returned in the next step.

Debug Output

Select the check box to view the debug output.

4.
In the Email Recipients section, click the Edit button to enter the recipient’s email address .
5.
Select users in the Recipients drop-down list.
6.
In the Scheduling section, specify schedule options:

Option

Description

Don’t Run on a Schedule

Run in combination with an event rather than on a specific date or at a specific time.

Run Every day/specific day at HH:MM

Run daily at a specified time, or run on a designated day of the week at a specified time.

Run on the nth of every month/specific month at HH:MM

Run on the same day every month, or a specific month, at the specified time.

7.
Click Next to display the User Import: Schedule - Define mapping between User attributes and LDAP Attributes page.

Option

Description

Ldap Uid

The identifier for the user. Recommended value: objectguid.

User Name

The name of the user. Recommended value: name.

Email

The email address for the user. Recommended value: mail.

Manager

The manager of the user. This mapping is mandatory only if you want to retrieve the manager information. Recommended value: manager.

IMPORTANT: To retrieve the manager object associated with the user, you must also add the manager attribute to the Attributes to retrieve box.

Option

Description

Api Enabled

Whether users are enabled to access the K1000 using the KACE GO app. Access is enabled if the field contains a numerical value. Access is disabled if the field contains no value. Therefore, to enable access, select an attribute that returns a numerical value. To disable access, select No Value.

Ams Id

Not used in the K1000 6.4 release. Recommended value: No Value.

9.
Optional: In the Role drop-down list, select the role for the imported users. See Add or edit User Roles.
11.
Optional: In the Labels drop-down list, select the label to apply to imported users. See About labels.
12.
In the Search Results section below the attribute mapping drop-down lists, verify that the list of users to import is correct, and the information listed for each user is what you expect. To refine your search, click the Back button and revise the search parameters and attributes.
For example, to change the number of Search Results, change the Maximum Number of Rows on the Choose attributes to import page.
13.
Click Next to display the Import Data into the K1000 Management Appliance page.
Only users with values for the required attributes, Ldap Uid, User Name, Email, and Manager, are imported. Records that do not have these values are listed in the Users with invalid data section.
Click Back to change settings.
Click Import to save the schedule and import user information immediately. The import begins, and the schedule is set to run according to the options selected in Scheduling section.
Click Finish to save the schedule without importing user information. The schedule is set to run according to the options selected in the Scheduling section.

About single sign on (SSO)

About single sign on (SSO)

Single sign on enables users who are logged on to the domain, or authenticated through a third-party, to access the K1000 Administrator Console and User Console without having to re-enter their credentials on the K1000 login page.

You can use either Active Directory or Quest Identity Brokerfor single sign on. You cannot enable both single sign on methods simultaneously on the same appliance.

Single sign on is available for:

One domain only: If you have multiple domains, only one can be enabled for single sign on. This is true even if the Organization component is enabled on the K1000 appliance, and you have multiple organizations that are on different domains. Single sign on is a System-level configuration, and organizations cannot be configured independently for single sign on.
Microsoft Active Directory servers: You can enable single sign on using Microsoft Active Directory servers with 2003 R2 or higher schema versions. Earlier schema versions cannot be used. If the Organization component is enabled on your appliance, the Active Directory single sign on method can be used with multiple organizations.
Quest Identity Broker: Quest Identity Broker (QIB) is a cloud-based single sign on solution that enables users to request access to the K1000 Administrator Console or User Console using identity providers, such as your organization's Identity Provider. If the Organization component is enabled on your appliance, QIB can be enabled for the default organization only.
NOTE: Quest recommends that you access the Administrator Console using the web server name rather than the IP address. The web server name can be found on the Network Settings page. See Changing appliance network settings.
Related Documents