Chat now with support
Chat with Support

KACE Asset 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

Add Desktop Wallpaper scripts

Add Desktop Wallpaper scripts

Use this template to build scripts that control the desktop wallpaper settings of Windows devices.

The recommended format for wallpaper files is bitmap (BMP). The specified wallpaper file is distributed to devices when the script runs.

1.
Go to the Desktop Wallpaper 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 Scripting, then click Configuration Policies.
c.
On the Configuration Policies panel, in the Windows section, click Desktop Wallpaper.

Option

Description

Name

A name that identifies the script. This name appears on the Scripts page.

Use wallpaper

Display the wallpaper file on the desktop of target devices.

Wallpaper bitmap file

Click Browse or Choose File to select and upload the file to use for the wallpaper. The file must be in BMP or JPG format.

Position

Select an option in the Position drop-down list:

Stretch: Stretch the image so that it covers the entire screen.
Center: Display the image in the center of the screen.
Tile: Repeat the image over the entire screen.
3.
Click Save to display the Script Detail page.
5.
To edit the raw XML used in the script, click Edit XML below the Schedule section.
6.
Click Save.

Add Desktop Shortcuts scripts

Add Desktop Shortcuts scripts

Use this template to create scripts that add Internet shortcuts to the Desktop or Start menu of Windows devices.

For example, you could use this script to add a shortcut to a company website or any other URL.

1.
Go to the Windows Desktop Shortcuts 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 Scripting, then click Configuration Policies.
c.
On the Configuration Policies panel, in the Windows section, click Desktop Shortcuts.

Option

Description

Name

A name that identifies the script. This name appears on the Scripts page.

3.
Click Add Shortcut.

Option

Description

Name

The text label that appears below or next to the shortcut.

Target

The full path to the application, file, or URL to be launched when the shortcut is selected. For example:

To create shortcut for explorer.exe, use this format: C:\WINDOWS\explorer.exe

To create a shortcut from the UNC share for explorer.exe, use this format:

\\192.168.1.1\WINDOWS\explorer.exe

or

\\HostName\WINDOWS\explorer.exe

Parameters

The command line parameters required for the shortcut. For example:

/S /IP=123.4

Working Directory

The changes to the current working directory. For example: C:\Windows\Temp

Location

The location where you want the shortcut to appear. Options include: Desktop and Start Menu.

5.
Click Save Changes to save the shortcut.
6.
Click Add Shortcut to add more shortcuts. To edit or delete a shortcut, hover over a shortcut and click the Edit button or the Delete button: .
7.
Click Save to display the Script Detail page.
9.
To edit the raw XML used in the script, click Edit XML below the Schedule section.
10.
Click Save.

Add Event Log Reporter scripts

Add Event Log Reporter scripts

Use this template to create scripts that query the Windows Event Log and upload the results to the appliance.

1.
Go to the Windows Event Log Reporter 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 Scripting, then click Configuration Policies.
c.
On the Configuration Policies panel, in the Windows section, click Event Log Reporter.

Option

Description

Name

A name that identifies the script. This name appears on the Scripts page.

Output File Name

The name of the log file created by the script.

Log File

The type of log you want to query: Software, System, or Security.

Event Type

The type of event you want to query: Information, Warning, or Error.

Source Name

(Optional) The names of sources to which the query is restricted.

3.
Click Save to display the Script Detail page.
5.
To edit the raw XML used in the script, click Edit XML below the Schedule section.
6.
Click Save.
7.
To view the event log of a device, click Inventory, then click a device name.
8.
In Scripting Logs, under Currently Deployed Jobs and Policies, click the View logs link next to Event Log.

Add MSI Installer scripts

Add MSI Installer scripts

Use this template to create scripts that set the basic command-line arguments for running MSI-based installers on Windows devices.

For command-line options, go to the Microsoft MSI Command-Line documentation: http://msdn.microsoft.com/en-us/library/windows/desktop/aa367988%28v=vs.85%29.aspx.

1.
Go to the Windows MIS Installer 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 Scripting, then click Configuration Policies.
c.
On the Configuration Policies panel, in the Windows section, click MSI Installer.

Option

Description

Name

A name that identifies the script. This name appears on the Scripts page.

Action

The task to be performed. Tasks include Install, Uninstall, Repair missing files, and Reinstall all files.

Software

The application to use for the script. To search for an application, begin typing in the field.

MSI Filename

The MSI filename (required if the file is a ZIP archive).

User Interaction

How the installation appears to users. Options include: Default, Silent, Basic UI, Reduced UI, and Full UI.

Install Directory

The directory on the target device where the application is to be installed.

Additional Switches

Any additional installer switches. Additional switches are inserted between the msiexe.exe and the /i foo.msi arguments.

Additional Properties

Any additional properties. These properties are inserted at the end of the command line. For example:

msiexec.exe /s1 /switch2 /i patch123.msi TARGETDIR=C:\patcher PROP=A PROP2=B

Feature List

The features to install. Use commas to separate features.

Store Config per device

Whether to store configuration information for individual devices.

After install

The action to be performed after installation.

Restart Options

The action to be performed after the device restarts.

Logging

The information to record in the installation log. Use Ctrl-click or Command-click to select multiple items.

Log File Name

The name of the log file.

3.
Click Save to display the Script Detail page.
5.
To edit the raw XML used in the script, click Edit XML below the Schedule section.
6.
Click Save.
Related Documents