Chat now with support
Chat with Support

KACE as a Service 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

About the patch testing environment

About the patch testing environment

About assessment testing
About deployment testing

Built-in Lumension security uses VMware® ESX®, VMware® vCenter™ Lab Manager™, and custom hardware bench testing.

Testing methods include:

•
Verification that patch-naming conventions comply with Lumension policy.
•
Verification that patch content supports the replication process. Each patch created by the content team is validated with the Symantec Ghost™ Solution Suite distribution and Update Server products.
About assessment testing

Assessment testing verifies that the Patch Management component is performing properly.

The testing verifies that:

•
An applicable non-patched device shows as applicable and not patched.
•
A patched device shows as installed and not applicable.
•
No false positives exist in the detection of the digital fingerprint.
•
Patch content is compliant with mandatory baselines.
•
Vulnerability is correctly displayed in the Update Server.
•
All Smart Label, sorting, and other visual features are functioning properly.
About deployment testing

Deployment testing verifies that patches are being deployed appropriately.

The testing verifies that:

•
The package is deployable.
•
The suppress-reboot functionality works.
•
The uninstallation functionality works.
•
On-demand package caching works.
•
Automatic deployment scheduling works.
•
Agent package download works.
•
CRC checksum ensures package integrity.
•
The Agent automatically runs assessment after patch deployment.
•
The Agent restarts automatically after reboot.

About assessment testing

About the patch testing environment

About assessment testing
About deployment testing

Built-in Lumension security uses VMware® ESX®, VMware® vCenter™ Lab Manager™, and custom hardware bench testing.

Testing methods include:

•
Verification that patch-naming conventions comply with Lumension policy.
•
Verification that patch content supports the replication process. Each patch created by the content team is validated with the Symantec Ghost™ Solution Suite distribution and Update Server products.
About assessment testing

Assessment testing verifies that the Patch Management component is performing properly.

The testing verifies that:

•
An applicable non-patched device shows as applicable and not patched.
•
A patched device shows as installed and not applicable.
•
No false positives exist in the detection of the digital fingerprint.
•
Patch content is compliant with mandatory baselines.
•
Vulnerability is correctly displayed in the Update Server.
•
All Smart Label, sorting, and other visual features are functioning properly.
About deployment testing

Deployment testing verifies that patches are being deployed appropriately.

The testing verifies that:

•
The package is deployable.
•
The suppress-reboot functionality works.
•
The uninstallation functionality works.
•
On-demand package caching works.
•
Automatic deployment scheduling works.
•
Agent package download works.
•
CRC checksum ensures package integrity.
•
The Agent automatically runs assessment after patch deployment.
•
The Agent restarts automatically after reboot.

About deployment testing

About the patch testing environment

About assessment testing
About deployment testing

Built-in Lumension security uses VMware® ESX®, VMware® vCenter™ Lab Manager™, and custom hardware bench testing.

Testing methods include:

•
Verification that patch-naming conventions comply with Lumension policy.
•
Verification that patch content supports the replication process. Each patch created by the content team is validated with the Symantec Ghost™ Solution Suite distribution and Update Server products.
About assessment testing

Assessment testing verifies that the Patch Management component is performing properly.

The testing verifies that:

•
An applicable non-patched device shows as applicable and not patched.
•
A patched device shows as installed and not applicable.
•
No false positives exist in the detection of the digital fingerprint.
•
Patch content is compliant with mandatory baselines.
•
Vulnerability is correctly displayed in the Update Server.
•
All Smart Label, sorting, and other visual features are functioning properly.
About deployment testing

Deployment testing verifies that patches are being deployed appropriately.

The testing verifies that:

•
The package is deployable.
•
The suppress-reboot functionality works.
•
The uninstallation functionality works.
•
On-demand package caching works.
•
Automatic deployment scheduling works.
•
Agent package download works.
•
CRC checksum ensures package integrity.
•
The Agent automatically runs assessment after patch deployment.
•
The Agent restarts automatically after reboot.

About the patch quality assurance process

About the patch quality assurance process

Quest partners with HEAT Software to provide Patch Management customers more value through the content development and quality assurance processes. The quality assurance teams verify the patch install and uninstall processes as well as the patch metadata produced by the content development team. Providing quality content to our customers is a high priority. To ensure successful delivery of content, HEAT Software executes test cases covering the following test components.

Testing environment

HEAT Software invests heavily in testing infrastructure. The content development and quality assurance teams have access to a virtual enterprise environment representing more than 1,500 nodes of various configurations. HEAT Software uses a mix of virtual desktops and servers in addition to custom physical bench testing to ensure that our testing infrastructure is state of the art.

Application testing

HEAT Software tests with various applications as necessary to ensure the requirements of the patch are satisfied.

Testing strategy

HEAT Software uses the following types of testing:

•
General testingverifies the following:
◦
Patch-naming convention complies with the HEAT Software policy.
◦
The content supports the replication process: each patch created by the content team is validated with the Global Subscription Service (GSS) distribution and Patch Server products.
•
Assessment testingverifies the following:
◦
An applicable non-patched system shows applicable and not patched.
◦
An patched system shows installed and not applicable.
◦
False positives in the detection of digital fingerprint.
◦
The content complies with mandatory baselines.
◦
The patch is correctly displayed in Patch Server, including all filtering, sorting and other visual functionality.
•
Deployment testingverifies the following:
◦
The package can be successfully deployed.
◦
The suppress reboot functionality works correctly.
◦
The uninstall functionality works correctly.
◦
On-demand package caching works correctly.
◦
Automatic deployment scheduling works correctly.
◦
Agent package downloads.
◦
The package hash ensures the package integrity.
◦
The agent automatically runs assessment after each patch deployment.
◦
The agent restarts automatically after a reboot.

Trusted delivery and flexibility

The HEAT Software GSS is designed and implemented to maximize global availability through a secure content distribution network. All communications with the HEAT Software GSS are conducted through encrypted, secure channels to ensure the integrity of security content.

Using a best practice approach, critical security patches are automatically downloaded to customer locations, based on their subscription options. Additional security patches may be downloaded, as necessary, to create a customized version of the KACE Patch Content Repository within the customer’s own secure enterprise environment.

The patches (.pls) and its associated packages (.plp) are encrypted with a key. This key is part of our product (kace.plk). Hence these files cannot be opened and modified without the key and also a Lumension-specific library.

SCR is a Java-based tool used to download patches. It employs checksum verification during the download process.

Related Documents