지금 지원 담당자와 채팅
지원 담당자와 채팅

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

Subscribing to and downloading patches

Subscribing to and downloading patches

About patch subscription and downloads
Websites that must be accessible to the appliance
Overview of first-time patch-subscription workflow
View details about operating systems and applications
Subscribing to patches and configuring download settings
Viewing available patches and download status
Best practices for resolving patch subscription issues

To enable patching, you need to subscribe to patches and schedule patch downloads to the appliance.

About patch subscription and downloads

About patch subscription and downloads

Patch subscription is the process of selecting the operating systems and applications for which you want to receive patches.

If the Organization component is enabled on your appliance, you select subscription settings for each organization separately.

After you subscribe to patches, the appliance downloads them according to the schedule you set. When patches are downloaded, you can test and deploy them. You can choose to automatically deploy patches as well, but such deployment is recommended for low-risk or time-important patches only. See:

•
Select patch and feature update download settings
•
Using Smart Labels for patching

Applications that the appliance can patch

For a list of applications that the appliance can patch, go to https://support.quest.com/kb/112030, and open the attachment.

NTP service requirement

When downloading patches using HTTPS, the NTP (Network Time Protocol) service must be running on the appliance. The NTP service is required because the secure protocol uses the current date stamps from the appliance to ensure certificate validity. If the NTP service is not running, patch download failures, suggesting invalid certificates, might result.

Websites that must be accessible to the appliance

Websites that must be accessible to the appliance

To complete patch downloads, access product information, and interact with Quest Support, the firewall, DNS server, and proxy server settings must allow the appliance to access specific domains on both port 80 and port 443.

Refer to the link for the websites that must be accessible to the appliance:

https://go.kace.com/to/k1000-network-ports-url-whitelist

Overview of first-time patch-subscription workflow

Overview of first-time patch-subscription workflow

Patch detection signatures and patch packages are not downloaded to the appliance by default. You must subscribe to the patches you want and then schedule a time to download them.

To save network bandwidth and disk space, Quest recommends that you download patch definition signatures first, because they are much smaller in size than patch packages. Then you can detect the patches that you need, and select the download settings that work best for your network.

The following workflow is for first-time patch-subscription.

1.
Gather information: Identify the operating systems, language packages, and applications installed on managed devices so that you know what you need to subscribe to. You can find this information on the appliance Dashboard page as well as by running reports. See View details about operating systems and applications.
2.
Select initial patch subscription settings: Subscribe to the operating systems and languages required by managed devices. See Subscribing to patches and configuring download settings.
3.
Download patch detection signatures: Patch detection signatures are smaller files that can be downloaded quickly and do not require much disk space. Download the patch detection signatures of the patches you subscribe to. Downloading these signatures enables you to view available patches and identify the patch packages you want to download later. See Select patch and feature update download settings.
4.
Run a detect-only patching job: Schedule a Detect-only patching job to identify the patches required by managed devices. A detect-only patching job is a one-time operation that shows how large the first patching job is going to be. Also, it indicates how to allocate resources based on device availability for patch installations and reboots. To run a detect-only patching job, create a patching schedule that detects patches on all devices. See Configuring patch schedules.
5.
Select patch package download settings: After you have identified the patch packages that you need, set a time for package downloads to occur. See Select patch and feature update download settings.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택