Tchater maintenant avec le support
Tchattez avec un ingénieur du support

KACE Systems Management Appliance 14.1 Common Documents - KACE Service Desk Administrator Guide

About the KACE Service Desk 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 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 Configuring Content Security Policy
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 About Remote Control 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 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 Manage quarantined file attachments
Using reports and scheduling notifications Monitoring devices
Getting started with 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

Configure email preferences

Configure email preferences

You can create and configure preferences for the email sent to and from the Service Desk users and staff.

By default, the Service Desk is configured to use an internal SMTP server for sending ticket-related emails. You have an option to use an external SMTP server, however, you must configure it in the appliance network settings. For more information, see Change appliance network settings.

1.
Go to the Service Desk Email Preferences 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, in the Email Configuration section, click Configure Email Preferences.
2.
On the Service Desk Email Preferences page that appears, in the Outbound Email tab, select the Include "Reply above this line" text on outbound email communications check box.
It is recommended to use this feature to prevent the entire email chain from being added to each comment.
3.
Specify the text that you want to detect in the email subject. When the Service Desk receives a ticket-related email with the specified subject, it will stop processing that email.
a.
In the Inbound Email tab, in the Ignore emails with following text in the subject field, type the words that you want to detect. You can specify multiple entries, using a semi-colon as a separator. For example: Out of Office;Mail Delivery Failure.
4.
Configure the thresholds for all inbound email notifications during a specific period. When these levels are reached, the Service Desk will stop sending email notifications.
* 
NOTE: When the overall threshold is reached, notifications will pause for all tickets. If a per-ticket threshold is reached, notifications will be paused only for the affected ticket. When the number of email updates in the given period becomes lower than the configured threshold, the notifications will resume.

Option

Description

Total Emails per Ticket

The maximum number of all emails the Service Desk receives and responds with email notifications. The default value is 100 emails.

Received within the interval of x minutes

The time interval in minutes during which the specified number of emails are received. The default value is one minute.

To disable this restriction, you can set to a high number such as 99999.

5.
Configure the thresholds for inbound email notifications per ticket, during a specific period. When these levels are reached, the Service Desk will stop sending email notifications.

Option

Description

Total Emails per Ticket

The maximum number of all emails the Service Desk receives for each ticket, and responds with email notifications. The default value is 5 emails per ticket.

Received within the interval of x minutes

Specify the time interval in minutes during which the specified number of emails for each ticket are received. The default value is one minute. To disable this restriction, set this option to a high number such as 99999.

6.
Click Save.

Next, you can configure POP3 email accounts for specific Service Desk queues. For more information, see Configure queue-specific email settings.

Configuring email triggers and email templates

Configuring email triggers and email templates

Configure email triggers
Configure email templates

You can set up triggers that automatically send email from the appliance and use templates to set the content of those email messages.

The Email on Events section determines which actions trigger an email to the various appliance users. Email templates determine the content of the messages.

Timing of email messages

The following email events trigger the appliance to send email immediately:

•
Comment: The system sends email notifications for comments when users add comments and click Submit on the ticket form. When users add comments and click Save on the ticket form, however, only the Any Change notification is sent.
•
Ticket Closed: If the Satisfaction Survey is enabled, an email that describes the Satisfaction Survey is sent immediately when tickets are closed.

The following email events trigger the appliance to send email every few minutes to prevent email overload:

•
Any Change
•
Owner Change
•
Status Change
•
Approval Change
•
Resolution Change
•
Escalation
•
SLA Violation
•
New Ticket Via Email
Configure email triggers

You can configure email triggers for a queue. If you have multiple queues, you can configure the email triggers for each queue separately.

1.
Go to the Service Desk Queue 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, in the Email Configuration section, click Setup email on events.
d.
Display the Queue Detail page by doing one of the following:
▪
Click the name of a queue.
▪
Select Choose Action > New.
2.
On the Queue Detail page, under Email Address, click [edit] link to display the Service Desk Queue Email Settings page.
3.
On the Service Desk Queue Email Settings page, in the Email on Events tab, select the options for sending email when the specified events occur. Each column represents a type of Service Desk user (role) and each row represents a ticket event.

Service Desk user (role)

Description

Owner

The person who is expected to resolve the ticket.

Submitter

The person whose issue is being resolved.

Approver

The person who can approve or reject the ticket for processing.

Ticket CC

One or more email addresses that are stored in the CC field of the ticket.

Category CC

One or more email addresses that are stored in the CC List of the Category Value of the ticket. See Configure CC lists for ticket categories.

Queue Owners

One or more owners of the ticket queue, as specified by the Owner label. This only applies to the New Ticket Via Email and New Ticket via Portal events.

When a ticket event occurs, email is sent to the selected roles or users. For example, if you select the Any Change box in the Owner column, email is sent to the ticket owner whenever the ticket is changed. For the Comment and Ticket Closed triggers, email is sent immediately. For other ticket changes, however, email is sent every few minutes to prevent email overload.

* 
NOTE: If users have the KACE GO mobile app installed on their smart phone or tablet, the system sends push notifications for the selected Service Desk ticket events.

Option

Description

Any Change

Any information on the ticket is changed.

Owner Change

The ticket's Owner field is changed.

Status Change

The ticket's Status field is changed.

Comment

Information, attachments, or screen shots are added to the ticket's Comments section. The system sends email notifications for comments when users add comments and click Submit on the ticket form. When users add comments and click Save on the ticket form, however, only the Any Change notification is sent.

Approval Change

The ticket's approval status has changed.

Resolution Change

The ticket's resolution has changed.

Response SLA Escalation

The ticket has not been updated to a stalled or closed status within the escalation time defined by the ticket priority.

Resolution SLA Violation

The ticket has not been resolved by its due date.

Ticket Closed

The ticket's Status field is changed to Closed. This event is used to present a Satisfaction Survey to submitters. See Using the Satisfaction Survey.

New Ticket Via Email

A user sends an email message to the Service Desk and a ticket is created.

New Ticket Via Portal

A ticket is created through the User Console.

4.
Click Save.
Configure email templates

You can configure the email templates that Service Desk uses to generate email messages for a queue. If you have multiple queues, you customize the email templates for each queue separately.

1.
Go to the Service Desk Queue 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 Create and manage queues in Queue section.
d.
Display the Queue Detail page by doing one of the following:
▪
Click the name of a queue.
▪
Select Choose Action > New.
2.
On the Queue Detail page, under Email Address, click Configure Queue Email Settings link to display the Service Desk Queue Email Settings page.
3.
On the Service Desk Queue Email Settings page, complete one of the following steps.
◦
To edit all email templates, click Customize All Emails.
◦
To edit a specific email template, in the Events area, in the row containing the email template you want to edit, in the Customize Email column, click .
4.
On the page that appears, change one or more of the selected email templates, as required.
* 
NOTE: If the default text for any of the templates is changed, the email messages will not be translated into different languages.

The following email template are available:

Ticket-related template

Description

Default recipients

Response SLA Escalated

Used to send periodic notifications according to the Escalation Time configured for the ticket priority in the queue. For example, if tickets with the priority of High have an Escalation Time of 30 minutes, this email is sent every 30 minutes for High priority tickets until the ticket priority changes or until the ticket is closed.

Owners, the ticket CC list, and ticket Category CC list

Ticket Created from Email(Queue Owners)

Used to acknowledge that a ticket has been created through email.

Owners, Submitters

Ticket Created from Portal

Used to acknowledge that a ticket has been created through the User Portal.

Owners, submitters

Ticket Modified

Used to notify recipients when ticket information is changed or added.

Owners and the ticket CC list

Comment Submitted

Used to notify recipients that comments are added to tickets.

Owners, submitters, approvers, the ticket CC list, and the ticket Category CC list

Ticket Closed

Used to present a Satisfaction Survey to submitters when tickets are closed. See Using the Satisfaction Survey.

Submitters

Email Ticket Manually

Used to for messages that are forwarded using the Email Ticket action on Ticket Detail pages.

Tip:
 
TIP: If you use HTML/Markdown, the $ticket_fields_visible token must be enclosed in the <pre> tag to prevent formatting, such as line breaks, from being discarded. For example:

<pre>$ticket_fields_visible</pre>

Manually entered by the sender

Resolution SLA Violated

Used to notify recipients that a ticket has remained open past the due date calculated using the SLA (Service Level Agreement) settings and the ticket priority.

None. Configurable on the Queue Detail page

Error-related template

Description

Recipients

Error Creating Ticket from Email

Used to notify senders that the ticket could not be created for reasons other than unknown email address.

Submitters

Unknown Email Address Response

Used to notify senders that the ticket could not be created because the submitter's email address is unknown.

Submitters

Table 6. Tokens used in all email templates

Token

Description

$helpdesk_email

The email address associated with the Service Desk queue. This address is configured on the Queue Detail page.

$helpdesk_name

The name of the Service Desk queue. This name is configured on the Queue Detail page.

$userui_url

A link to the User Console. Access to the User Console requires login credentials.

Table 7. Tokens used in ticket-related email templates

Token

Description

$change_desc

A formatted representation of the changes that were made the last time the ticket was saved, including both field changes and comments.

$last_attachment

The most recent attachment added to the ticket.

$last_comment

The most recent comment added to the ticket.

$mobile_ticket_url

A link to the ticket KACE GO mobile app. When displayed in an email on an Android or iOS mobile device, this links opens the associated ticket in the KACE GO mobile app.

$process_description

The process description. It can include important pre-requisites that the users need to complete before proceeding to create a ticket based on a process template.

$process_name

The name of the process template.

$process_status

The status of the process template such as Approval Required, Approval Timed Out, Approval Received, Approval Rejected, Process Cancelled, and Process Complete.

$process_type

The type of the process. In a default installation, only the Service Desk process type is included. You can create new process types, as required. For example, you can create a process type for accessing a specific application, or a group of applications. For more information, see Define process types.

$summary

The current summary of the ticket.

$ticket_approver_email

The email address of the ticket approver. Having this address is especially useful for Comments email notifications.

$ticket_approver_name

The name of the ticket approver.

* 
NOTE: The approver name and contact information is derived from the USER record associated with the fields on the ticket.

$ticket_approver_phone_home

Contact information for the ticket approver.

$ticket_approver_phone_mobile

Contact information for the ticket approver.

$ticket_approver_phone_pager

Contact information for the ticket approver.

$ticket_approver_phone_work

Contact information for the ticket approver.

$ticket_custom_X_label

$ticket_custom_X_value

The label and value used for a custom field, where X represents the index number of the custom field.

For example, if a queue has a ticket field labeled, CUSTOM_5, and that field is configured with the label Location Name, the system replaces $ticket_custom_5_label with the text, Location Name. The token, $ticket_custom_5_value is replaced with the ticket value that was saved for the Location Name field, such as, Topeka or Albuquerque.

By default, all ticket queues are configured with 15 custom fields, but this number can be increased as needed.

* 
NOTE: Each queue can have different custom fields and different email template configurations.

$ticket_due_date

The due date as saved on the ticket. Administrators can override automatic due dates with manual due dates if necessary.

$ticket_escalation_minutes

The time, in minutes, between periodic notifications. This time is determined by the Escalation Time configured for the ticket priority in the queue. For example, if tickets with the priority of High have an Escalation Time of 30 minutes, this email is sent every 30 minutes for High priority tickets until the ticket priority changes or until the ticket is closed. This token is typically used in the Ticket Escalated email template, to inform recipients of the frequency of email notifications.

$ticket_fields_visible

Include all the ticket fields that are visible for the user who is forwarding the ticket by email.

Tip:
 
TIP: If you use HTML/Markdown, the $ticket_fields_visible token must be enclosed in the <pre> tag to prevent formatting, such as line breaks, from being discarded. For example:

<pre>$ticket_fields_visible</pre>

$ticket_history

The complete history of the ticket.

* 
NOTE: For some tickets, the history information can become very detailed and too large to send through email. If the complete history is not needed, use $ticket_history_X to limit the number of records to include.

$ticket_history_X

A specified number of records in the ticket history. X indicates the number of records to include, beginning with the most recent.

$ticket_id

A unique identifier assigned to the ticket, also called the ticket number. Using this identifier is the primary method for users to identify tickets.

$ticket_number

A formatted version of the ticket ID. This version begins with TICK followed by a minimum of five digits. For example, a ticket with ID 4321 is displayed as TICK:04321. This format is especially useful in email Subject lines to make sure that email replies link to the correct tickets.

$ticket_owner_email

The email address of the Service Desk administrator assigned to the ticket.

$ticket_owner_name

The name of the Service Desk administrator assigned to the ticket.

* 
NOTE: The owner name and contact information is derived from the USER record associated with the fields on the ticket.

$ticket_owner_phone_home

Contact information for the Service Desk administrator assigned to the ticket.

$ticket_owner_phone_mobile

Contact information for the Service Desk administrator assigned to the ticket.

$ticket_owner_phone_pager

Contact information for the Service Desk administrator assigned to the ticket.

$ticket_owner_phone_work

Contact information for the Service Desk administrator assigned to the ticket.

$ticket_priority

The priority assigned to the ticket. Default values include High, Medium, and Low.

$ticket_resolution

Information about what was done to resolve the ticket as described in the ticket’s Resolution field.

$ticket_status

The status of the ticket. Defaults include New, Opened, Closed, Need More Info, Reopened, Waiting Overdue, Waiting on Customer, and Waiting on Third Party.

$ticket_submitter_email

The email address of the submitter.

$ticket_submitter_name

The name of the submitter.

* 
NOTE: The submitter name and contact information is derived from the USER record associated with the fields on the ticket.

$ticket_submitter_phone_home

Contact information for the submitter.

$ticket_submitter_phone_mobile

Contact information for the submitter.

$ticket_submitter_phone_pager

Contact information for the submitter.

$ticket_submitter_phone_work

Contact information for the submitter.

$ticket_title

The title of the ticket as it appears on the Ticket Detail page.

$ticket_url

A link to the ticket in the User Console. Access to the User Console requires login credentials.

$ticket_http_url

A link to the ticket in the User Console. This format is used for backward compatibility on older systems. Access to the User Console requires login credentials.

$ticket_https_url

A secure link to the ticket in the User Console. Use this token if SSL is enabled on your appliance. This ensures that links sent through email work correctly.

$userui_url

A link to the home page of the User Console. Access to the User Console requires login credentials.

Table 8. Tokens used in merged ticket email templates

Token

Description

$ticket_merged_number

The number of the merged ticket.

$ticket_merged_title

The title of the merged ticket as it appears on the Ticket Detail page.

$ticket_merged_changer_name

The name of the user who merged the tickets.

$ticket_merged_url

A link to the merged ticket in the User Console. Access to the User Console requires login credentials.

Table 9. Tokens used in error-related email templates

Token

Description

$error_text

Used to identify a problem processing the submitted tokens. This error appears when:

•
The system does not recognize a variable
•
A variable is recognized, but the user does not have permission to change the field
•
The variable attempts to change the approval status of the ticket but the user is not the approver

$quoted_mail

The content of the original email message.

$subject

The subject of the original email message.

* 
NOTE: Tokens that are invalid are ignored and they are not replaced in email messages. For example, if you add an unknown token such as $today, it is ignored, and it appears in the email message as $today.
5.
Optional: For each email template, create HTML-based content instead of using plain text.
a.
Select Send as HTML to use a HTML-based email instead of plain text.
An HTML editor appears, with a full range of text editing options for formatting your content, such as buttons for bold text, hyperlinks, lists, or text color.
b.
Use the controls in the editor to format the template content. 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 .
c.
To quickly add a token, click , and from the list that appears, select the applicable token.
See step 4 for more information about each token.
6.
For each template, indicate how you want to handle email file attachments.
◦
To allow Service Desk to send file attachments, select Include attachments. Then, indicate which attachments you want to send:
▪
Most recent change (if applicable): Include only the file attachments that are added with the most recent ticket update.
▪
Last uploaded: Include the last uploaded file attachments.
▪
All: Include all file attachments.
◦
To prevent Service Desk from sending file attachments with ticket-related email, clear the Include attachments check box.
7.
Click Save.

For instructions on how to configure the appliance to use SMTP email, see Configuring SMTP email servers.

Configure email triggers

Configuring email triggers and email templates

Configure email triggers
Configure email templates

You can set up triggers that automatically send email from the appliance and use templates to set the content of those email messages.

The Email on Events section determines which actions trigger an email to the various appliance users. Email templates determine the content of the messages.

Timing of email messages

The following email events trigger the appliance to send email immediately:

•
Comment: The system sends email notifications for comments when users add comments and click Submit on the ticket form. When users add comments and click Save on the ticket form, however, only the Any Change notification is sent.
•
Ticket Closed: If the Satisfaction Survey is enabled, an email that describes the Satisfaction Survey is sent immediately when tickets are closed.

The following email events trigger the appliance to send email every few minutes to prevent email overload:

•
Any Change
•
Owner Change
•
Status Change
•
Approval Change
•
Resolution Change
•
Escalation
•
SLA Violation
•
New Ticket Via Email
Configure email triggers

You can configure email triggers for a queue. If you have multiple queues, you can configure the email triggers for each queue separately.

1.
Go to the Service Desk Queue 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, in the Email Configuration section, click Setup email on events.
d.
Display the Queue Detail page by doing one of the following:
▪
Click the name of a queue.
▪
Select Choose Action > New.
2.
On the Queue Detail page, under Email Address, click [edit] link to display the Service Desk Queue Email Settings page.
3.
On the Service Desk Queue Email Settings page, in the Email on Events tab, select the options for sending email when the specified events occur. Each column represents a type of Service Desk user (role) and each row represents a ticket event.

Service Desk user (role)

Description

Owner

The person who is expected to resolve the ticket.

Submitter

The person whose issue is being resolved.

Approver

The person who can approve or reject the ticket for processing.

Ticket CC

One or more email addresses that are stored in the CC field of the ticket.

Category CC

One or more email addresses that are stored in the CC List of the Category Value of the ticket. See Configure CC lists for ticket categories.

Queue Owners

One or more owners of the ticket queue, as specified by the Owner label. This only applies to the New Ticket Via Email and New Ticket via Portal events.

When a ticket event occurs, email is sent to the selected roles or users. For example, if you select the Any Change box in the Owner column, email is sent to the ticket owner whenever the ticket is changed. For the Comment and Ticket Closed triggers, email is sent immediately. For other ticket changes, however, email is sent every few minutes to prevent email overload.

* 
NOTE: If users have the KACE GO mobile app installed on their smart phone or tablet, the system sends push notifications for the selected Service Desk ticket events.

Option

Description

Any Change

Any information on the ticket is changed.

Owner Change

The ticket's Owner field is changed.

Status Change

The ticket's Status field is changed.

Comment

Information, attachments, or screen shots are added to the ticket's Comments section. The system sends email notifications for comments when users add comments and click Submit on the ticket form. When users add comments and click Save on the ticket form, however, only the Any Change notification is sent.

Approval Change

The ticket's approval status has changed.

Resolution Change

The ticket's resolution has changed.

Response SLA Escalation

The ticket has not been updated to a stalled or closed status within the escalation time defined by the ticket priority.

Resolution SLA Violation

The ticket has not been resolved by its due date.

Ticket Closed

The ticket's Status field is changed to Closed. This event is used to present a Satisfaction Survey to submitters. See Using the Satisfaction Survey.

New Ticket Via Email

A user sends an email message to the Service Desk and a ticket is created.

New Ticket Via Portal

A ticket is created through the User Console.

4.
Click Save.
Configure email templates

You can configure the email templates that Service Desk uses to generate email messages for a queue. If you have multiple queues, you customize the email templates for each queue separately.

1.
Go to the Service Desk Queue 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 Create and manage queues in Queue section.
d.
Display the Queue Detail page by doing one of the following:
▪
Click the name of a queue.
▪
Select Choose Action > New.
2.
On the Queue Detail page, under Email Address, click Configure Queue Email Settings link to display the Service Desk Queue Email Settings page.
3.
On the Service Desk Queue Email Settings page, complete one of the following steps.
◦
To edit all email templates, click Customize All Emails.
◦
To edit a specific email template, in the Events area, in the row containing the email template you want to edit, in the Customize Email column, click .
4.
On the page that appears, change one or more of the selected email templates, as required.
* 
NOTE: If the default text for any of the templates is changed, the email messages will not be translated into different languages.

The following email template are available:

Ticket-related template

Description

Default recipients

Response SLA Escalated

Used to send periodic notifications according to the Escalation Time configured for the ticket priority in the queue. For example, if tickets with the priority of High have an Escalation Time of 30 minutes, this email is sent every 30 minutes for High priority tickets until the ticket priority changes or until the ticket is closed.

Owners, the ticket CC list, and ticket Category CC list

Ticket Created from Email(Queue Owners)

Used to acknowledge that a ticket has been created through email.

Owners, Submitters

Ticket Created from Portal

Used to acknowledge that a ticket has been created through the User Portal.

Owners, submitters

Ticket Modified

Used to notify recipients when ticket information is changed or added.

Owners and the ticket CC list

Comment Submitted

Used to notify recipients that comments are added to tickets.

Owners, submitters, approvers, the ticket CC list, and the ticket Category CC list

Ticket Closed

Used to present a Satisfaction Survey to submitters when tickets are closed. See Using the Satisfaction Survey.

Submitters

Email Ticket Manually

Used to for messages that are forwarded using the Email Ticket action on Ticket Detail pages.

Tip:
 
TIP: If you use HTML/Markdown, the $ticket_fields_visible token must be enclosed in the <pre> tag to prevent formatting, such as line breaks, from being discarded. For example:

<pre>$ticket_fields_visible</pre>

Manually entered by the sender

Resolution SLA Violated

Used to notify recipients that a ticket has remained open past the due date calculated using the SLA (Service Level Agreement) settings and the ticket priority.

None. Configurable on the Queue Detail page

Error-related template

Description

Recipients

Error Creating Ticket from Email

Used to notify senders that the ticket could not be created for reasons other than unknown email address.

Submitters

Unknown Email Address Response

Used to notify senders that the ticket could not be created because the submitter's email address is unknown.

Submitters

Table 6. Tokens used in all email templates

Token

Description

$helpdesk_email

The email address associated with the Service Desk queue. This address is configured on the Queue Detail page.

$helpdesk_name

The name of the Service Desk queue. This name is configured on the Queue Detail page.

$userui_url

A link to the User Console. Access to the User Console requires login credentials.

Table 7. Tokens used in ticket-related email templates

Token

Description

$change_desc

A formatted representation of the changes that were made the last time the ticket was saved, including both field changes and comments.

$last_attachment

The most recent attachment added to the ticket.

$last_comment

The most recent comment added to the ticket.

$mobile_ticket_url

A link to the ticket KACE GO mobile app. When displayed in an email on an Android or iOS mobile device, this links opens the associated ticket in the KACE GO mobile app.

$process_description

The process description. It can include important pre-requisites that the users need to complete before proceeding to create a ticket based on a process template.

$process_name

The name of the process template.

$process_status

The status of the process template such as Approval Required, Approval Timed Out, Approval Received, Approval Rejected, Process Cancelled, and Process Complete.

$process_type

The type of the process. In a default installation, only the Service Desk process type is included. You can create new process types, as required. For example, you can create a process type for accessing a specific application, or a group of applications. For more information, see Define process types.

$summary

The current summary of the ticket.

$ticket_approver_email

The email address of the ticket approver. Having this address is especially useful for Comments email notifications.

$ticket_approver_name

The name of the ticket approver.

* 
NOTE: The approver name and contact information is derived from the USER record associated with the fields on the ticket.

$ticket_approver_phone_home

Contact information for the ticket approver.

$ticket_approver_phone_mobile

Contact information for the ticket approver.

$ticket_approver_phone_pager

Contact information for the ticket approver.

$ticket_approver_phone_work

Contact information for the ticket approver.

$ticket_custom_X_label

$ticket_custom_X_value

The label and value used for a custom field, where X represents the index number of the custom field.

For example, if a queue has a ticket field labeled, CUSTOM_5, and that field is configured with the label Location Name, the system replaces $ticket_custom_5_label with the text, Location Name. The token, $ticket_custom_5_value is replaced with the ticket value that was saved for the Location Name field, such as, Topeka or Albuquerque.

By default, all ticket queues are configured with 15 custom fields, but this number can be increased as needed.

* 
NOTE: Each queue can have different custom fields and different email template configurations.

$ticket_due_date

The due date as saved on the ticket. Administrators can override automatic due dates with manual due dates if necessary.

$ticket_escalation_minutes

The time, in minutes, between periodic notifications. This time is determined by the Escalation Time configured for the ticket priority in the queue. For example, if tickets with the priority of High have an Escalation Time of 30 minutes, this email is sent every 30 minutes for High priority tickets until the ticket priority changes or until the ticket is closed. This token is typically used in the Ticket Escalated email template, to inform recipients of the frequency of email notifications.

$ticket_fields_visible

Include all the ticket fields that are visible for the user who is forwarding the ticket by email.

Tip:
 
TIP: If you use HTML/Markdown, the $ticket_fields_visible token must be enclosed in the <pre> tag to prevent formatting, such as line breaks, from being discarded. For example:

<pre>$ticket_fields_visible</pre>

$ticket_history

The complete history of the ticket.

* 
NOTE: For some tickets, the history information can become very detailed and too large to send through email. If the complete history is not needed, use $ticket_history_X to limit the number of records to include.

$ticket_history_X

A specified number of records in the ticket history. X indicates the number of records to include, beginning with the most recent.

$ticket_id

A unique identifier assigned to the ticket, also called the ticket number. Using this identifier is the primary method for users to identify tickets.

$ticket_number

A formatted version of the ticket ID. This version begins with TICK followed by a minimum of five digits. For example, a ticket with ID 4321 is displayed as TICK:04321. This format is especially useful in email Subject lines to make sure that email replies link to the correct tickets.

$ticket_owner_email

The email address of the Service Desk administrator assigned to the ticket.

$ticket_owner_name

The name of the Service Desk administrator assigned to the ticket.

* 
NOTE: The owner name and contact information is derived from the USER record associated with the fields on the ticket.

$ticket_owner_phone_home

Contact information for the Service Desk administrator assigned to the ticket.

$ticket_owner_phone_mobile

Contact information for the Service Desk administrator assigned to the ticket.

$ticket_owner_phone_pager

Contact information for the Service Desk administrator assigned to the ticket.

$ticket_owner_phone_work

Contact information for the Service Desk administrator assigned to the ticket.

$ticket_priority

The priority assigned to the ticket. Default values include High, Medium, and Low.

$ticket_resolution

Information about what was done to resolve the ticket as described in the ticket’s Resolution field.

$ticket_status

The status of the ticket. Defaults include New, Opened, Closed, Need More Info, Reopened, Waiting Overdue, Waiting on Customer, and Waiting on Third Party.

$ticket_submitter_email

The email address of the submitter.

$ticket_submitter_name

The name of the submitter.

* 
NOTE: The submitter name and contact information is derived from the USER record associated with the fields on the ticket.

$ticket_submitter_phone_home

Contact information for the submitter.

$ticket_submitter_phone_mobile

Contact information for the submitter.

$ticket_submitter_phone_pager

Contact information for the submitter.

$ticket_submitter_phone_work

Contact information for the submitter.

$ticket_title

The title of the ticket as it appears on the Ticket Detail page.

$ticket_url

A link to the ticket in the User Console. Access to the User Console requires login credentials.

$ticket_http_url

A link to the ticket in the User Console. This format is used for backward compatibility on older systems. Access to the User Console requires login credentials.

$ticket_https_url

A secure link to the ticket in the User Console. Use this token if SSL is enabled on your appliance. This ensures that links sent through email work correctly.

$userui_url

A link to the home page of the User Console. Access to the User Console requires login credentials.

Table 8. Tokens used in merged ticket email templates

Token

Description

$ticket_merged_number

The number of the merged ticket.

$ticket_merged_title

The title of the merged ticket as it appears on the Ticket Detail page.

$ticket_merged_changer_name

The name of the user who merged the tickets.

$ticket_merged_url

A link to the merged ticket in the User Console. Access to the User Console requires login credentials.

Table 9. Tokens used in error-related email templates

Token

Description

$error_text

Used to identify a problem processing the submitted tokens. This error appears when:

•
The system does not recognize a variable
•
A variable is recognized, but the user does not have permission to change the field
•
The variable attempts to change the approval status of the ticket but the user is not the approver

$quoted_mail

The content of the original email message.

$subject

The subject of the original email message.

* 
NOTE: Tokens that are invalid are ignored and they are not replaced in email messages. For example, if you add an unknown token such as $today, it is ignored, and it appears in the email message as $today.
5.
Optional: For each email template, create HTML-based content instead of using plain text.
a.
Select Send as HTML to use a HTML-based email instead of plain text.
An HTML editor appears, with a full range of text editing options for formatting your content, such as buttons for bold text, hyperlinks, lists, or text color.
b.
Use the controls in the editor to format the template content. 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 .
c.
To quickly add a token, click , and from the list that appears, select the applicable token.
See step 4 for more information about each token.
6.
For each template, indicate how you want to handle email file attachments.
◦
To allow Service Desk to send file attachments, select Include attachments. Then, indicate which attachments you want to send:
▪
Most recent change (if applicable): Include only the file attachments that are added with the most recent ticket update.
▪
Last uploaded: Include the last uploaded file attachments.
▪
All: Include all file attachments.
◦
To prevent Service Desk from sending file attachments with ticket-related email, clear the Include attachments check box.
7.
Click Save.

For instructions on how to configure the appliance to use SMTP email, see Configuring SMTP email servers.

Configure email templates

Configuring email triggers and email templates

Configure email triggers
Configure email templates

You can set up triggers that automatically send email from the appliance and use templates to set the content of those email messages.

The Email on Events section determines which actions trigger an email to the various appliance users. Email templates determine the content of the messages.

Timing of email messages

The following email events trigger the appliance to send email immediately:

•
Comment: The system sends email notifications for comments when users add comments and click Submit on the ticket form. When users add comments and click Save on the ticket form, however, only the Any Change notification is sent.
•
Ticket Closed: If the Satisfaction Survey is enabled, an email that describes the Satisfaction Survey is sent immediately when tickets are closed.

The following email events trigger the appliance to send email every few minutes to prevent email overload:

•
Any Change
•
Owner Change
•
Status Change
•
Approval Change
•
Resolution Change
•
Escalation
•
SLA Violation
•
New Ticket Via Email
Configure email triggers

You can configure email triggers for a queue. If you have multiple queues, you can configure the email triggers for each queue separately.

1.
Go to the Service Desk Queue 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, in the Email Configuration section, click Setup email on events.
d.
Display the Queue Detail page by doing one of the following:
▪
Click the name of a queue.
▪
Select Choose Action > New.
2.
On the Queue Detail page, under Email Address, click [edit] link to display the Service Desk Queue Email Settings page.
3.
On the Service Desk Queue Email Settings page, in the Email on Events tab, select the options for sending email when the specified events occur. Each column represents a type of Service Desk user (role) and each row represents a ticket event.

Service Desk user (role)

Description

Owner

The person who is expected to resolve the ticket.

Submitter

The person whose issue is being resolved.

Approver

The person who can approve or reject the ticket for processing.

Ticket CC

One or more email addresses that are stored in the CC field of the ticket.

Category CC

One or more email addresses that are stored in the CC List of the Category Value of the ticket. See Configure CC lists for ticket categories.

Queue Owners

One or more owners of the ticket queue, as specified by the Owner label. This only applies to the New Ticket Via Email and New Ticket via Portal events.

When a ticket event occurs, email is sent to the selected roles or users. For example, if you select the Any Change box in the Owner column, email is sent to the ticket owner whenever the ticket is changed. For the Comment and Ticket Closed triggers, email is sent immediately. For other ticket changes, however, email is sent every few minutes to prevent email overload.

* 
NOTE: If users have the KACE GO mobile app installed on their smart phone or tablet, the system sends push notifications for the selected Service Desk ticket events.

Option

Description

Any Change

Any information on the ticket is changed.

Owner Change

The ticket's Owner field is changed.

Status Change

The ticket's Status field is changed.

Comment

Information, attachments, or screen shots are added to the ticket's Comments section. The system sends email notifications for comments when users add comments and click Submit on the ticket form. When users add comments and click Save on the ticket form, however, only the Any Change notification is sent.

Approval Change

The ticket's approval status has changed.

Resolution Change

The ticket's resolution has changed.

Response SLA Escalation

The ticket has not been updated to a stalled or closed status within the escalation time defined by the ticket priority.

Resolution SLA Violation

The ticket has not been resolved by its due date.

Ticket Closed

The ticket's Status field is changed to Closed. This event is used to present a Satisfaction Survey to submitters. See Using the Satisfaction Survey.

New Ticket Via Email

A user sends an email message to the Service Desk and a ticket is created.

New Ticket Via Portal

A ticket is created through the User Console.

4.
Click Save.
Configure email templates

You can configure the email templates that Service Desk uses to generate email messages for a queue. If you have multiple queues, you customize the email templates for each queue separately.

1.
Go to the Service Desk Queue 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 Create and manage queues in Queue section.
d.
Display the Queue Detail page by doing one of the following:
▪
Click the name of a queue.
▪
Select Choose Action > New.
2.
On the Queue Detail page, under Email Address, click Configure Queue Email Settings link to display the Service Desk Queue Email Settings page.
3.
On the Service Desk Queue Email Settings page, complete one of the following steps.
◦
To edit all email templates, click Customize All Emails.
◦
To edit a specific email template, in the Events area, in the row containing the email template you want to edit, in the Customize Email column, click .
4.
On the page that appears, change one or more of the selected email templates, as required.
* 
NOTE: If the default text for any of the templates is changed, the email messages will not be translated into different languages.

The following email template are available:

Ticket-related template

Description

Default recipients

Response SLA Escalated

Used to send periodic notifications according to the Escalation Time configured for the ticket priority in the queue. For example, if tickets with the priority of High have an Escalation Time of 30 minutes, this email is sent every 30 minutes for High priority tickets until the ticket priority changes or until the ticket is closed.

Owners, the ticket CC list, and ticket Category CC list

Ticket Created from Email(Queue Owners)

Used to acknowledge that a ticket has been created through email.

Owners, Submitters

Ticket Created from Portal

Used to acknowledge that a ticket has been created through the User Portal.

Owners, submitters

Ticket Modified

Used to notify recipients when ticket information is changed or added.

Owners and the ticket CC list

Comment Submitted

Used to notify recipients that comments are added to tickets.

Owners, submitters, approvers, the ticket CC list, and the ticket Category CC list

Ticket Closed

Used to present a Satisfaction Survey to submitters when tickets are closed. See Using the Satisfaction Survey.

Submitters

Email Ticket Manually

Used to for messages that are forwarded using the Email Ticket action on Ticket Detail pages.

Tip:
 
TIP: If you use HTML/Markdown, the $ticket_fields_visible token must be enclosed in the <pre> tag to prevent formatting, such as line breaks, from being discarded. For example:

<pre>$ticket_fields_visible</pre>

Manually entered by the sender

Resolution SLA Violated

Used to notify recipients that a ticket has remained open past the due date calculated using the SLA (Service Level Agreement) settings and the ticket priority.

None. Configurable on the Queue Detail page

Error-related template

Description

Recipients

Error Creating Ticket from Email

Used to notify senders that the ticket could not be created for reasons other than unknown email address.

Submitters

Unknown Email Address Response

Used to notify senders that the ticket could not be created because the submitter's email address is unknown.

Submitters

Table 6. Tokens used in all email templates

Token

Description

$helpdesk_email

The email address associated with the Service Desk queue. This address is configured on the Queue Detail page.

$helpdesk_name

The name of the Service Desk queue. This name is configured on the Queue Detail page.

$userui_url

A link to the User Console. Access to the User Console requires login credentials.

Table 7. Tokens used in ticket-related email templates

Token

Description

$change_desc

A formatted representation of the changes that were made the last time the ticket was saved, including both field changes and comments.

$last_attachment

The most recent attachment added to the ticket.

$last_comment

The most recent comment added to the ticket.

$mobile_ticket_url

A link to the ticket KACE GO mobile app. When displayed in an email on an Android or iOS mobile device, this links opens the associated ticket in the KACE GO mobile app.

$process_description

The process description. It can include important pre-requisites that the users need to complete before proceeding to create a ticket based on a process template.

$process_name

The name of the process template.

$process_status

The status of the process template such as Approval Required, Approval Timed Out, Approval Received, Approval Rejected, Process Cancelled, and Process Complete.

$process_type

The type of the process. In a default installation, only the Service Desk process type is included. You can create new process types, as required. For example, you can create a process type for accessing a specific application, or a group of applications. For more information, see Define process types.

$summary

The current summary of the ticket.

$ticket_approver_email

The email address of the ticket approver. Having this address is especially useful for Comments email notifications.

$ticket_approver_name

The name of the ticket approver.

* 
NOTE: The approver name and contact information is derived from the USER record associated with the fields on the ticket.

$ticket_approver_phone_home

Contact information for the ticket approver.

$ticket_approver_phone_mobile

Contact information for the ticket approver.

$ticket_approver_phone_pager

Contact information for the ticket approver.

$ticket_approver_phone_work

Contact information for the ticket approver.

$ticket_custom_X_label

$ticket_custom_X_value

The label and value used for a custom field, where X represents the index number of the custom field.

For example, if a queue has a ticket field labeled, CUSTOM_5, and that field is configured with the label Location Name, the system replaces $ticket_custom_5_label with the text, Location Name. The token, $ticket_custom_5_value is replaced with the ticket value that was saved for the Location Name field, such as, Topeka or Albuquerque.

By default, all ticket queues are configured with 15 custom fields, but this number can be increased as needed.

* 
NOTE: Each queue can have different custom fields and different email template configurations.

$ticket_due_date

The due date as saved on the ticket. Administrators can override automatic due dates with manual due dates if necessary.

$ticket_escalation_minutes

The time, in minutes, between periodic notifications. This time is determined by the Escalation Time configured for the ticket priority in the queue. For example, if tickets with the priority of High have an Escalation Time of 30 minutes, this email is sent every 30 minutes for High priority tickets until the ticket priority changes or until the ticket is closed. This token is typically used in the Ticket Escalated email template, to inform recipients of the frequency of email notifications.

$ticket_fields_visible

Include all the ticket fields that are visible for the user who is forwarding the ticket by email.

Tip:
 
TIP: If you use HTML/Markdown, the $ticket_fields_visible token must be enclosed in the <pre> tag to prevent formatting, such as line breaks, from being discarded. For example:

<pre>$ticket_fields_visible</pre>

$ticket_history

The complete history of the ticket.

* 
NOTE: For some tickets, the history information can become very detailed and too large to send through email. If the complete history is not needed, use $ticket_history_X to limit the number of records to include.

$ticket_history_X

A specified number of records in the ticket history. X indicates the number of records to include, beginning with the most recent.

$ticket_id

A unique identifier assigned to the ticket, also called the ticket number. Using this identifier is the primary method for users to identify tickets.

$ticket_number

A formatted version of the ticket ID. This version begins with TICK followed by a minimum of five digits. For example, a ticket with ID 4321 is displayed as TICK:04321. This format is especially useful in email Subject lines to make sure that email replies link to the correct tickets.

$ticket_owner_email

The email address of the Service Desk administrator assigned to the ticket.

$ticket_owner_name

The name of the Service Desk administrator assigned to the ticket.

* 
NOTE: The owner name and contact information is derived from the USER record associated with the fields on the ticket.

$ticket_owner_phone_home

Contact information for the Service Desk administrator assigned to the ticket.

$ticket_owner_phone_mobile

Contact information for the Service Desk administrator assigned to the ticket.

$ticket_owner_phone_pager

Contact information for the Service Desk administrator assigned to the ticket.

$ticket_owner_phone_work

Contact information for the Service Desk administrator assigned to the ticket.

$ticket_priority

The priority assigned to the ticket. Default values include High, Medium, and Low.

$ticket_resolution

Information about what was done to resolve the ticket as described in the ticket’s Resolution field.

$ticket_status

The status of the ticket. Defaults include New, Opened, Closed, Need More Info, Reopened, Waiting Overdue, Waiting on Customer, and Waiting on Third Party.

$ticket_submitter_email

The email address of the submitter.

$ticket_submitter_name

The name of the submitter.

* 
NOTE: The submitter name and contact information is derived from the USER record associated with the fields on the ticket.

$ticket_submitter_phone_home

Contact information for the submitter.

$ticket_submitter_phone_mobile

Contact information for the submitter.

$ticket_submitter_phone_pager

Contact information for the submitter.

$ticket_submitter_phone_work

Contact information for the submitter.

$ticket_title

The title of the ticket as it appears on the Ticket Detail page.

$ticket_url

A link to the ticket in the User Console. Access to the User Console requires login credentials.

$ticket_http_url

A link to the ticket in the User Console. This format is used for backward compatibility on older systems. Access to the User Console requires login credentials.

$ticket_https_url

A secure link to the ticket in the User Console. Use this token if SSL is enabled on your appliance. This ensures that links sent through email work correctly.

$userui_url

A link to the home page of the User Console. Access to the User Console requires login credentials.

Table 8. Tokens used in merged ticket email templates

Token

Description

$ticket_merged_number

The number of the merged ticket.

$ticket_merged_title

The title of the merged ticket as it appears on the Ticket Detail page.

$ticket_merged_changer_name

The name of the user who merged the tickets.

$ticket_merged_url

A link to the merged ticket in the User Console. Access to the User Console requires login credentials.

Table 9. Tokens used in error-related email templates

Token

Description

$error_text

Used to identify a problem processing the submitted tokens. This error appears when:

•
The system does not recognize a variable
•
A variable is recognized, but the user does not have permission to change the field
•
The variable attempts to change the approval status of the ticket but the user is not the approver

$quoted_mail

The content of the original email message.

$subject

The subject of the original email message.

* 
NOTE: Tokens that are invalid are ignored and they are not replaced in email messages. For example, if you add an unknown token such as $today, it is ignored, and it appears in the email message as $today.
5.
Optional: For each email template, create HTML-based content instead of using plain text.
a.
Select Send as HTML to use a HTML-based email instead of plain text.
An HTML editor appears, with a full range of text editing options for formatting your content, such as buttons for bold text, hyperlinks, lists, or text color.
b.
Use the controls in the editor to format the template content. 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 .
c.
To quickly add a token, click , and from the list that appears, select the applicable token.
See step 4 for more information about each token.
6.
For each template, indicate how you want to handle email file attachments.
◦
To allow Service Desk to send file attachments, select Include attachments. Then, indicate which attachments you want to send:
▪
Most recent change (if applicable): Include only the file attachments that are added with the most recent ticket update.
▪
Last uploaded: Include the last uploaded file attachments.
▪
All: Include all file attachments.
◦
To prevent Service Desk from sending file attachments with ticket-related email, clear the Include attachments check box.
7.
Click Save.

For instructions on how to configure the appliance to use SMTP email, see Configuring SMTP email servers.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation