Chatta subito con l'assistenza
Chat con il supporto

KACE Systems Management Appliance 13.2 Common Documents - Administrator Guide

About the KACE Systems Management Appliance 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 Managing user notifications Enable Two-Factor Authentication for all users 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 Configuring the default theme 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 Deploying the KACE Agent to managed devices Using Replication Shares Managing credentials Configuring assets
About the Asset Management component Using the Asset Management Dashboard 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 Managing contracts Managing licenses Managing purchase records
Setting up License Compliance Managing License Compliance Setting up Service Desk Configure the Cache Lifetime for Service Desk widgets Creating and managing organizations Importing and exporting appliance resources
Managing inventory
Using the Inventory Dashboard 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 Registering KACE Agent with the appliance Provisioning the KACE Agent Manually deploying the KACE 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 Associate Managed Installations with Cataloged Software 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 Using Task Chains
Patching devices and maintaining security
Using the Security Dashboard About patch management Subscribing to and downloading patches Creating and managing patch schedules Managing patch inventory Managing Windows Feature Updates Managing Dell devices and updates Managing Linux package upgrades Maintaining device and appliance security Manage quarantined file attachments
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 Using the Service Desk Dashboard 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 Merging tickets 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 appliance
Appendixes Glossary About us Legal notices

Create a Service Desk ticket from an alert

Create a Service Desk ticket from an alert

You can create a Service Desk ticket from a server monitoring alert, with information from the alert automatically populating fields in the ticket form.

1.
Go to the Monitoring Alerts list in one of the following ways:
◦
If you have the Monitoring Alerts widget installed on your open Dashboard, click Monitoring Alerts.
◦
In the left navigation bar, select Monitoring > Alerts.
2.
Select the check box for the row that contains the alert message, then select Choose Action > New Ticket.
◦
If you want to create a ticket based on a queue, if there are multiple ticket queues in the organization, select a queue from the Ticket drop-down list.
◦
If you want to create a ticket based on a process template, select the process from the Process drop-down list.
The Title, Summary, Submitter, and Device fields contain information from the alert.
3.
Optional: Change the Title and Summary to conform to your corporate procedures.
4.
Provide the rest of the information needed to complete the form, then click Save to save the ticket and leave the Ticket Detail page, or Apply Changes to save the ticket and continue editing it.

Option

Description

Title

(Required) A brief description of the issue. You can replace the monitoring-provided title with one of your choosing.

Summary

A more detailed description of the issue.

This field includes a full range of text editing options for formatting your content, such as buttons for bold text, hyperlinks, lists, or text color.

For example:

•
To apply bold text to a text string, select it in the editor, and click .
•
To add images, click , and provide the URL to the image file, a local file path, or simply drop the image into the indicated area.
◦
You can also copy and paste screen shots directly into the text field.
◦
Any images you include this way are added as file attachments to the ticket. They are also included in email communication, as applicable.
◦
Deleting an image from the text field does not remove the associated file attachment. You can manage file attachments in the Attachments section of the ticket page. For more information, see Add or delete screen shots and attachments from Service Desk tickets.
•
To add external links, click .
•
To embed externally hosted videos, click .

Submitter

The login name of the user submitting the ticket. The submitter can be changed by selecting a different login name in the drop-down list. Click to view the submitter contact information.

Asset

The asset that the information in the ticket is about. Select an asset in the drop-down list. Click to view the asset details.

Filter on submitter assigned assets

Filter the asset list based on the assets that are assigned to the submitter.

Device

The device that the information in the ticket is about. Monitoring provides this information. Click to view the device details.

Filter on submitter assigned devices

Filter the asset list based on the devices that are assigned to the submitter.

Impact

The number of people that are inconvenienced or cannot work.

Category

A classification of the issue.

Status

The current state of the ticket. This field does not appear if you are creating or editing a ticket from a process template.

Priority

The importance of priority of the ticket.

Owner

The user responsible for managing the ticket through its lifecycle.

Due

Date and time the ticket is scheduled to be completed.

If Service Level Agreements are not enabled, the due date is set to None, by default.

If Service Level Agreements are enabled, the due date is automatically calculated according to the SLA settings. The due date is calculated based on the priority set when the ticket is submitted. If the priority is changed after the ticket is initially submitted, the due date will be recalculated according to the new priority, but based on the original submitted date and time. If the SLA resolution time configuration is changed, it is only applicable on new tickets. Old tickets are not affected. See Configuring Service Level Agreements.

Select Manual Date to manually set the due date and time. In this case, if Service Level Agreements are enabled, the due date and time is calculated and displayed as an option, but not selected.

CC List

A list of users who receive a notification email when a ticket event occurs. The CC List is emailed based on the ticket event and Ticket CC being configured for the queue Email on Events configuration.

Resolution

The resolution of the issue associated with the ticket.

This field includes a full range of text editing options for formatting your content, such as buttons for bold text, hyperlinks, lists, or text color.

For example:

•
To apply bold text to a text string, select it in the editor, and click .
•
To add images, click , and provide the URL to the image file, a local file path, or simply drop the image into the indicated area.
◦
You can also copy and paste screen shots directly into the text field.
◦
Any images you include this way are added as file attachments to the ticket. They are also included in email communication, as applicable.
◦
Deleting an image from the text field does not remove the associated file attachment. You can manage file attachments in the Attachments section of the ticket page. For more information, see Add or delete screen shots and attachments from Service Desk tickets.
•
To add external links, click .
•
To embed externally hosted videos, click .

Related Ticket Information

This section does not appear if you are creating a ticket from a process template.

Add Ticket

Click to add an additional ticket to this ticket's related information.

Referrers

The Referrer is a read-only field that holds a ticket reference to any ticket that references this ticket by way of the See also section.

Merged Tickets

This section allows you to edit the list of tickets merged with this ticket, as applicable. Any tickets that you want to merge must belong to the same queue. When you merge tickets using the Ticket Detail page, the open ticket becomes the primary ticket. All other merged tickets are archived when you merge them. For more details, see Merging tickets.

To add a merged ticket, click Add Tickets to Merge/Edit Merged Tickets, and select a ticket from the list that appears.

Process Information

This section only appears if you are creating a ticket from a process template. All of the settings appearing in this section are read-only. For complete information about creating and configuring process templates, see Add, edit, and enable process templates

Process

The name of the process template associated with this ticket.

Process Type

The type of the process.

Process Status

The status of the workflow associated with this process template. For example, Pending Approval.

Parent

The name of the parent ticket, as defined in the process template associated with this ticket.

Process Approvals

A list of users that are assigned as approvers for this ticket, if applicable. The approvers are listed in stages, as defined in the process template. Each stage can have one or more approvers, as needed. The settings related to each approver and stage are also listed in this section, such as approval timeouts and notifications. When you create a process ticket, the timeout period starts for the first approver. When that user approves the ticket, the timeout starts for the next one, and so on.

Process Activities

A list of process activities, each representing a child ticket, and listed in stages, as defined in the process template. Multiple tickets can be assigned to the same stage, if needed. For example, if the first stage is to obtain equipment and supplies for a new-hire, you can have several separate child tickets for ordering devices, office equipment, and supplies, all assigned to stage 1. When you create a process ticket, all child tickets assigned to stage 1 are created automatically. Stage 2 tickets are created when all stage 1 tickets are closed, stage 3 tickets are created when all stage 2 tickets are closed, and so on.

Add Ticket

Click to add an additional ticket to this ticket's related information.

Referrers

The Referrer is a read-only field that holds a ticket reference to any ticket that references this ticket by way of the See also section.

Comments

Comments that you want to add to the ticket. You can also add file attachments, screenshots, provide automatic responses or Knowledge Base article contents as ticket comments. For more information see:

•
Add comments to tickets
•
Add or delete screen shots and attachments from Service Desk tickets

If you want to add an automatic response as a resolution to this ticket, click Predefined Response and select a response template.

The selected response template appears in the Resolution field. You can add multiple response templates as resolution entries. They appear in the order you selected them.

* 
TIP: To create or edit a response template, save your changes and click Manage. This will take you to the Response Templates page. For more information about response templates, see View and edit response templates.

Knowledge Base Article

Look up a Knowledge Base article and append its contents to the ticket comments. For more information about Knowledge Base articles, see Managing Knowledge Base articles.

Creating and managing tickets by email

Creating and managing tickets by email

About attachments to tickets created through email
Enable email ticket creation
Create a ticket by email
Modifying ticket attributes using email
Clearing a ticket field using email
Changing ticket fields using email
Changing ticket approval fields using email

You can enable users to create and manage tickets by email. This is useful for users who do not have access to the appliance Administrator Console or User Console.

About attachments to tickets created through email

About attachments to tickets created through email

Users can attach files to Service Desk tickets submitted through email, and those attached files can be up to 8 MB in size.

If attachments exceed 8 MB in size, email messages are rejected. No error messages are displayed to users.

If the appliance detects any threats in a file attachment included with Service Desk tickets, access to the file is blocked and can be managed on the Antivirus Quarantine page. For details, see Manage quarantined file attachments.

Enable email ticket creation

Enable email ticket creation

You can enable users to create and manage Service Desk tickets using email.

1.
Go to the Service Desk Ticket Detail page:
a.
Log in to the appliance Administrator Console, https://appliance_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 Service Desk, then click Configuration.
c.
On the Configuration panel, click Queues.
d.
Click the name of a queue.
2.
Set up a valid email account, such as Support@mydomain.com, where users can send email to create tickets.
3.
Add the email address to the Alternate Email Address field.
4.
Select the Allow all users as submitters check box.
5.
Select the Accept email from unknown users check box.

If Accept email from unknown users is enabled in the queue configuration, any email sent to the Service Desk queue to create a ticket is allowed to set the Submitter field. In this case the username must be passed in the @submitter token and is that of an existing user, or is the current email address if it is an unknown user.

If Accept email from unknown users is disabled, the preceding process works only when the email address of the sender is already associated with a Service Desk user account.

6.
Click Save.

Tickets created from email messages receive the default values for Impact, Category, and Priority as configured on the Queue Detail page. The body of the email message is added as a comment. The Submitter field is derived from the sender’s email address.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione