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

KACE Systems Management Appliance 13.2 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 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

About Dell Data Protection | Encryption (DDP|E) and encryption information in device details

About Dell Data Protection ||E) and encryption information in device details

If devices in the network have the DDP|E client installed, the appliance can collect status and configuration information and display it on the Device Detail page.

Registry key needed to be set on Windows DDP|E client

A requirement for the appliance being able to collect detailed inventory from Windows DDP|E clients is to set the DumpXmlInventory key in the client.

Key: HKLM\SYSTEM\CurrentControlSet\services\DellMgmtAgent\Parameters
DWORD Value: DumpXmlInventory
Data: 0x1

This registry value causes DDP|E to write an inventory.xml file to the target device, which is then parsed by inventory. See Add a Dump Inventory registry key to permit inventory collection on Windows DDP|E client devices.

This requirement applies only to Windows.

Dell Data Protection ||E)

DDP|E consists of applications that enable a user to:

•
Detect data security risks on desktops, laptops, and external media.
•
Protect data on these devices by enforcing access control policies, authentication, and encryption of sensitive data.
•
Manage data centrally with policies using collaborative tools that integrate into existing user directories.
•
Support key and data recovery, automatic updates, and tracking for protected devices.

Table 11. Supported OSs for DDP|E

Operating system

Versions

Windows

7, 8, 8.1

Mac OS X

10.7.5, 10.8.3–10.8.5, 10.9.2–10.9.3

Table 12. DDP|E information displayed on the Device Detail page

 

Item

 

Description

MACHINE_DDPE

Database field

Unique ID

An identification of the DDP|E client used by the DDP|E server.

MCID

Agent Version

Version of DDP|E client installed.

AGENT_VERSION

Server Hostname

Hostname of the DDP|E server managing this DDP|E client.

SERVER_HOSTNAME

Protection Status

Example values are Protected and Unprotected. Values of Locked or Unknown might indicate a problem.

PROTECTION_STATUS

Last Inventory Generated

Timestamp of when the last DDP|E client inventory occurred. Not to be confused with K1 inventory.

PROTECTION_STATUS_UPDATED

Table 13. DDP|E Volume information displayed on the Device Detail page

 

Item

 

Description

MACHINE_DDPE_VOLUME

Database field

Device

Name of the device/volume as reported by the operating system.

DEVICE_ID

Protection Status

Indication of the current level/status of DDP|E protection on the DDP|E client.

PROTECTION_STATUS

Protection Reason

Manner of protection used on the DDP|E client. The option is typically VendorProtected, which indicates DDP|E or BitLocker.

PROTECTION_REASON

BitLocker

BitLocker is a full disk encryption feature included with Windows.

Table 14. Supported OSs for BitLocker

Operating system

Versions

Windows

Vista, 7 (Enterprise and Ultimate)

Windows

8, 8.1 (Pro and Enterprise)

Windows server

2008, 2008 R2, 2012, 2012 R2

Table 15. BitLocker information displayed on the Device Detail page

 

Item

 

Description

MACHINE_BITLOCKER_VOLUME

Database field

Device ID

Unique identifier for the volume on the system.

DEVICE_ID

Persistent Volume ID

A persistent identifier for the volume on the system.

PERSISTENT_VOLUME_ID

Protection status

Denotes whether BitLocker is protecting the volume.

•
Protection Off
•
Protection On
•
Protection Unknown

PROTECTION_STATUS

Metadata Version

Possible values:

•
0
•
1
•
2

VERSION

Encryption Method

Type of encryption used. For example, AES-128. Possible values:

•
None
•
AES-128 with Diffuser
•
AES-256 with Diffuser
•
AES-128
•
AES-256
•
Encrypted
•
Unknown

SELF_ENCRYPTION_DRIVE

_ENCRYPTION_METHOD (self-encrypting drives only)

ENCRYPTION_METHOD (software-based encryption only)

Hardware Encryption Status
* 
NOTE: The Hardware Encryption Status property is supported on Windows 8 and higher systems.

Possible values:

•
Unknown
•
Not Supported
•
No Protection
•
Uses Software
•
Uses Hardware

HARDWARE_ENCRYPTION_STATUS

Lock Status

Possible values:

•
Unknown
•
Unlocked
•
Locked

LOCK_STATUS

Conversion Status

Status of the conversion. Possible values:

•
Unknown
•
Fully Decrypted
•
Fully Encrypted
•
Encryption In Progress
•
Decryption In Progress
•
Encryption Paused
•
Decryption Paused

CONVERSION_STATUS

Encryption Percentage

The extent of conversion, shown as a percentage.

ENCRYPTION_PERCENTAGE

Wiping Status

Status of any wiping of free space. Possible values:

•
Unknown
•
Free Space Not Wiped
•
Free Space Wiped
•
Free Space Wiping In Progress
•
Free Space Wiping Paused

WIPING_STATUS

Wiping Percentage

The extent of free space wiping, shown as a percentage.

WIPING_PERCENTAGE

Key Protectors

Key protectors in place. Possible values:

•
Unknown
•
Trusted Platform Module (TPM)
•
External Key
•
Numerical Password
•
TPM and PIN
•
TPM and Startup Key
•
TPM and PIN and Startup Key
•
Public Key
•
Passphrase
•
TPM Certificate
•
CryptoAPI Next Generation (CNG) Protector

KEY_PROTECTORS

FileVault 2

FileVault 2 is a full disk encryption feature included with Mac OS X.

Table 16. Supported OSs for FileVault 2

Operating system

Versions

Mac OS X

10.8, 10.9, 10.10

Table 17. FileVault 2 information displayed on the Device Detail page

 

Item

 

Description

MACHINE_FILEVAULT_VOLUME

Database field

Enabled

Indicates if FileVault is enabled.

IS_ENABLED

Personal Recovery Key

Indicates the existence of a Personal Recovery Key.

HAS_PERSONAL_RECOVERY_KEY

Institutional Recovery Key

Indicates the existence of a corporate-provisioned X.509-based asymmetric key pair.

HAS_INSTITUTIONAL_RECOVERY

_KEY

Authorized Users

A list of accounts that can unlock the drive in EFI.

AUTHORIZED_USERS

Conversion Status

The status of the encryption process. Examples include Pending Conversion, Converting, Encryption Paused, and Complete.

CONVERSION_STATUS

Conversion Percentage

The extent of conversion, shown as a percentage.

CONVERSION_PERCENTAGE

Encryption Status

Status of the encryption. For example, Locked or Unlocked.

ENCRYPTION_STATUS

Encryption Type

Type of encryption used. For example, AES-XTS.

ENCRYPTION_TYPE

Device

Unique identifier for the volume on the system.

DEVICE_ID

Version

VERSION

Trusted Platform Module (TPM)

TPM is a dedicated microprocessor that secures hardware by integrating cryptographic keys into devices.

Table 18. Supported OSs for TPM

Operating system

Versions

Windows

Vista, 7, 8, 8.1

Windows Server

2008, 2008 R2, 2012, 2012 R2

Table 19. TPM information displayed on the Device Detail page

 

Item

 

Description

MACHINE_TPM

Database field

Manufacturer

Manufacturer of the TPM chip.

MANUFACTURER_ID_TEXT

Manufacturer Version

Version of the TPM chip.

MANUFACTURER_VERSION

Manufacturer Version Info

Additional version information that is specific to the manufacturer.

MANUFACTURER_VERSION_INFO

Specification Version

The version of the Trusted Computing Group (TCG) specification that the TPM supports.

SPECIFICATION_VERSION

Physical Presence Version

The version of the Physical Presence Interface that the device supports. The Physical Presence Interface is a communication mechanism that runs device operations that require physical presence.

PHYSICAL_PRESENCE_VERSION

_INFO

TPM Enabled

Step 1 of TPM initialization.

IS_TPM_ENABLED

TPM Activated

Step 2 of TPM initialization.

IS_TPM_ACTIVATED

TPM Owned

Step 3 of TPM initialization.

IS_TPM_OWNED

Add a Dump Inventory registry key to permit inventory collection on Windows DDP|E client devices

Add a Dump Inventory registry key to permit inventory collection on Windows DDP|E client devices

Add the DumpXmlInventory registry key to an Agent-managed Windows device
Add the DumpXmlInventory registry key to an Agentless-managed Windows device

If DumpXmlInventory is absent on a Windows DDP|E client, the appliance cannot get access to the inventory .xml file in order to collect the relevant field information.

Dell Data Protection | Encryption is installed on the Windows device. Go to http://www.dell.com/support/home/us/en/19/product-support/product/dell-data-protection-encryption/drivers.

The procedure for adding the key is different for Agent-managed devices and Agentless-managed devices.

Add the DumpXmlInventory registry key to an Agent-managed Windows device

You must add DumpXmlInventory to a Windows DDP|E client before the appliance can collect field information from that client's inventory.xml file.

For Agent-managed Windows devices, you can use a default offline KScript from the appliance scripting feature to set the "dump inventory" registry key. This key is necessary for the DDP|E agent to write the detailed inventory XML data to the appliance file system.

* 
NOTE: After you set the registry key, the DDP|E service requires a full policy update schedule before the appliance is able to collect inventory.
1.
Go to the Script Detail page for the K1000 Enable Detailed DDPE Inventory (Windows) script.
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 Scripting, then click Scripts.
c.
From the list, select K1000 Enable Detailed DDPE Inventory (Windows).
2.
In the Configure section, specify script settings:

Option

Description

Name

K1000 Enable Detailed DDPE Inventory (Windows), the name of this default script.

Enabled

Select this check box to run the script on the target devices. Do not enable a script until you are finished testing it and are ready to run it. Enable the script on a test label before you enable it on all devices.

Type

The script type is Offline KScripts.

Status

Indicates the readiness of the script to be rolled out to the network. Set the status to Production.

Description

Contains the brief description of the actions the default script performs.

Notes

Any additional information you want to provide.

3.
In the Deploy section specify deployment options:

Option

Description

All Devices

Deploy to all devices. Clear the check box to limit the deployment to specific labels or devices.

Labels

Limit deployment to devices that belong to specified labels. To select labels, click Edit, drag labels to the Limit Deployment to window, then click Save.

If you select a label that has a Replication Share or an alternate download location, the appliance copies digital assets from that Replication Share or alternate download location instead of downloading them directly from the appliance.

* 
NOTE: The appliance uses a Replication Share before it uses the KACE Alt Location.

Devices

Limit deployment to one or more devices. To find devices, begin typing in the field.

Operating Systems

The operating systems on which the application runs. Applications are deployed only to devices with the selected operating systems.

1.
Click Manage Operating Systems.
2.
In the Operating Systems dialog box that appears, select the OS versions in the navigation tree, as applicable.

You have an option to select OS versions by their family, product, architecture, release ID, or build version. You can choose a specific build version, or a parent node, as needed. Selecting a parent node in the tree automatically selects the associated child nodes. This behavior allows you to select any future OS versions, as devices are added or upgraded in your managed environment. For example, to select all build current and future versions associated with the Windows 10 x64 architecture, under All > Windows > Windows 10, select x64.

4.
In the Schedule section, specify run options:

Option

Description

None

Run in combination with an event rather than on a specific date or at a specific time.

Every n hours

Run at a specified interval.

Every day/specific day at HH:MM

Run daily at a specified time, or run on a designated day of the week at a specified time.

Run on the nth of every month/specific month at HH:MM

Run on the same day every month, or a specific month, at the specified time.

Run on the nth weekday of every month/specific month at HH:MM

Run on the specific weekday of every month, or a specific month, at the specified time.

Custom

Run according to a custom schedule.

Use standard 5-field cron format (extended cron format is not supported):

* * * * *
| | | | +────────day of week (0-6)(Sun=0)
| | | +────────month (1-12)
| | +────────day of month (1-31)
| +────────hour (0-23)
+────────minute (0-59)

Use the following when specifying values:

•
Spaces ( ): Separate each field with a space.
•
Asterisks (*): Include the entire range of values in a field with an asterisk. For example, an asterisk in the hour field indicates every hour.
•
Commas (,): Separate multiple values in a field with a comma. For example, 0,6 in the day of the week field indicates Sunday and Saturday.
•
Hyphens (-): Indicate a range of values in a field with a hyphen. For example, 1-5 in the day of the week field is equivalent to 1,2,3,4,5, which indicates Monday through Friday.
•
Slashes (/): Specify the intervals at which to repeat an action with a slash. For example, */3 in the hour field is equivalent to 0,3,6,9,12,15,18,21. The asterisk (*) specifies every hour, but /3 restricts this to hours divisible by 3.

Examples:

•
15 * * * * Run 15 minutes after every hour every day
•
0 22 * * * Run at 22:00 every day
•
0 0 1 1,6 * Run at 00:00 on January 1 and June 1
•
30 8,12 * * 1-5 Run weekdays at 08:30 and 12:30
•
0 2 */2 * * Run every other day at 02:00

View Task Schedule

Click to view the task schedule. The Task Schedule dialog box displays a list of scheduled tasks. Click a task to review the task details. For more information, see View task schedules.

5.
Skip the Dependencies and Tasks sections.
6.
Do one of the following:
◦
Click Run Now to immediately push the script to all devices.

Use this option with caution. See Using the Run and Run Now commands.

◦
Click Save.
Add the DumpXmlInventory registry key to an Agentless-managed Windows device

You must add DumpXmlInventory to a Windows DDP|E client before the appliance can collect field information from that client's inventory.xml file.

For an Agentless-managed Windows device, the process requires that you create a new Group Policy Object on a Windows Server 2008 or 2012 device so that you can deploy the registry setting to multiple devices in a domain.

1.
On a Windows Server 2008 or 2012 device, open the Group Policy Management Console.
2.
Right-click Group Policy Objects and click New.
3.
Provide a description name for the new GPO (for instance, Dell Data Protection | Encryption: Inventory Registry Setting) and click OK.
4.
Right-click the new GPO and click Edit.
5.
Browse to Computer Configuration > Preferences > Windows Settings > Registry.
6.
Right-click Registry and select New > Registry Item.
7.
On the General tab, select Update in the Action drop-down menu.
8.
Select HKEY_LOCAL_MACHINE in the Hive drop-down list.
9.
Specify a Key Path of SYSTEM\CurrentControlSet\services\DellMgmtAgent\Parameters.
10.
Specify a Value name of DumpXmlInventory.
11.
Select REG_DWORD in the Value type drop-down list.
12.
Specify 1 in the Value data field.
13.
Select the Hexadecimal option in the Base group, and click OK.
14.
Close the Group Policy Management Editor.

You can now link this new group policy object to a specific domain, Organizational Unit, and so on.

Important:
 
IMPORTANT: You should test the GPO on a specific computer or set of computers before deploying it to all systems.

Add the DumpXmlInventory registry key to an Agent-managed Windows device

Add a Dump Inventory registry key to permit inventory collection on Windows DDP|E client devices

Add the DumpXmlInventory registry key to an Agent-managed Windows device
Add the DumpXmlInventory registry key to an Agentless-managed Windows device

If DumpXmlInventory is absent on a Windows DDP|E client, the appliance cannot get access to the inventory .xml file in order to collect the relevant field information.

Dell Data Protection | Encryption is installed on the Windows device. Go to http://www.dell.com/support/home/us/en/19/product-support/product/dell-data-protection-encryption/drivers.

The procedure for adding the key is different for Agent-managed devices and Agentless-managed devices.

Add the DumpXmlInventory registry key to an Agent-managed Windows device

You must add DumpXmlInventory to a Windows DDP|E client before the appliance can collect field information from that client's inventory.xml file.

For Agent-managed Windows devices, you can use a default offline KScript from the appliance scripting feature to set the "dump inventory" registry key. This key is necessary for the DDP|E agent to write the detailed inventory XML data to the appliance file system.

* 
NOTE: After you set the registry key, the DDP|E service requires a full policy update schedule before the appliance is able to collect inventory.
1.
Go to the Script Detail page for the K1000 Enable Detailed DDPE Inventory (Windows) script.
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 Scripting, then click Scripts.
c.
From the list, select K1000 Enable Detailed DDPE Inventory (Windows).
2.
In the Configure section, specify script settings:

Option

Description

Name

K1000 Enable Detailed DDPE Inventory (Windows), the name of this default script.

Enabled

Select this check box to run the script on the target devices. Do not enable a script until you are finished testing it and are ready to run it. Enable the script on a test label before you enable it on all devices.

Type

The script type is Offline KScripts.

Status

Indicates the readiness of the script to be rolled out to the network. Set the status to Production.

Description

Contains the brief description of the actions the default script performs.

Notes

Any additional information you want to provide.

3.
In the Deploy section specify deployment options:

Option

Description

All Devices

Deploy to all devices. Clear the check box to limit the deployment to specific labels or devices.

Labels

Limit deployment to devices that belong to specified labels. To select labels, click Edit, drag labels to the Limit Deployment to window, then click Save.

If you select a label that has a Replication Share or an alternate download location, the appliance copies digital assets from that Replication Share or alternate download location instead of downloading them directly from the appliance.

* 
NOTE: The appliance uses a Replication Share before it uses the KACE Alt Location.

Devices

Limit deployment to one or more devices. To find devices, begin typing in the field.

Operating Systems

The operating systems on which the application runs. Applications are deployed only to devices with the selected operating systems.

1.
Click Manage Operating Systems.
2.
In the Operating Systems dialog box that appears, select the OS versions in the navigation tree, as applicable.

You have an option to select OS versions by their family, product, architecture, release ID, or build version. You can choose a specific build version, or a parent node, as needed. Selecting a parent node in the tree automatically selects the associated child nodes. This behavior allows you to select any future OS versions, as devices are added or upgraded in your managed environment. For example, to select all build current and future versions associated with the Windows 10 x64 architecture, under All > Windows > Windows 10, select x64.

4.
In the Schedule section, specify run options:

Option

Description

None

Run in combination with an event rather than on a specific date or at a specific time.

Every n hours

Run at a specified interval.

Every day/specific day at HH:MM

Run daily at a specified time, or run on a designated day of the week at a specified time.

Run on the nth of every month/specific month at HH:MM

Run on the same day every month, or a specific month, at the specified time.

Run on the nth weekday of every month/specific month at HH:MM

Run on the specific weekday of every month, or a specific month, at the specified time.

Custom

Run according to a custom schedule.

Use standard 5-field cron format (extended cron format is not supported):

* * * * *
| | | | +────────day of week (0-6)(Sun=0)
| | | +────────month (1-12)
| | +────────day of month (1-31)
| +────────hour (0-23)
+────────minute (0-59)

Use the following when specifying values:

•
Spaces ( ): Separate each field with a space.
•
Asterisks (*): Include the entire range of values in a field with an asterisk. For example, an asterisk in the hour field indicates every hour.
•
Commas (,): Separate multiple values in a field with a comma. For example, 0,6 in the day of the week field indicates Sunday and Saturday.
•
Hyphens (-): Indicate a range of values in a field with a hyphen. For example, 1-5 in the day of the week field is equivalent to 1,2,3,4,5, which indicates Monday through Friday.
•
Slashes (/): Specify the intervals at which to repeat an action with a slash. For example, */3 in the hour field is equivalent to 0,3,6,9,12,15,18,21. The asterisk (*) specifies every hour, but /3 restricts this to hours divisible by 3.

Examples:

•
15 * * * * Run 15 minutes after every hour every day
•
0 22 * * * Run at 22:00 every day
•
0 0 1 1,6 * Run at 00:00 on January 1 and June 1
•
30 8,12 * * 1-5 Run weekdays at 08:30 and 12:30
•
0 2 */2 * * Run every other day at 02:00

View Task Schedule

Click to view the task schedule. The Task Schedule dialog box displays a list of scheduled tasks. Click a task to review the task details. For more information, see View task schedules.

5.
Skip the Dependencies and Tasks sections.
6.
Do one of the following:
◦
Click Run Now to immediately push the script to all devices.

Use this option with caution. See Using the Run and Run Now commands.

◦
Click Save.
Add the DumpXmlInventory registry key to an Agentless-managed Windows device

You must add DumpXmlInventory to a Windows DDP|E client before the appliance can collect field information from that client's inventory.xml file.

For an Agentless-managed Windows device, the process requires that you create a new Group Policy Object on a Windows Server 2008 or 2012 device so that you can deploy the registry setting to multiple devices in a domain.

1.
On a Windows Server 2008 or 2012 device, open the Group Policy Management Console.
2.
Right-click Group Policy Objects and click New.
3.
Provide a description name for the new GPO (for instance, Dell Data Protection | Encryption: Inventory Registry Setting) and click OK.
4.
Right-click the new GPO and click Edit.
5.
Browse to Computer Configuration > Preferences > Windows Settings > Registry.
6.
Right-click Registry and select New > Registry Item.
7.
On the General tab, select Update in the Action drop-down menu.
8.
Select HKEY_LOCAL_MACHINE in the Hive drop-down list.
9.
Specify a Key Path of SYSTEM\CurrentControlSet\services\DellMgmtAgent\Parameters.
10.
Specify a Value name of DumpXmlInventory.
11.
Select REG_DWORD in the Value type drop-down list.
12.
Specify 1 in the Value data field.
13.
Select the Hexadecimal option in the Base group, and click OK.
14.
Close the Group Policy Management Editor.

You can now link this new group policy object to a specific domain, Organizational Unit, and so on.

Important:
 
IMPORTANT: You should test the GPO on a specific computer or set of computers before deploying it to all systems.

Add the DumpXmlInventory registry key to an Agentless-managed Windows device

Add a Dump Inventory registry key to permit inventory collection on Windows DDP|E client devices

Add the DumpXmlInventory registry key to an Agent-managed Windows device
Add the DumpXmlInventory registry key to an Agentless-managed Windows device

If DumpXmlInventory is absent on a Windows DDP|E client, the appliance cannot get access to the inventory .xml file in order to collect the relevant field information.

Dell Data Protection | Encryption is installed on the Windows device. Go to http://www.dell.com/support/home/us/en/19/product-support/product/dell-data-protection-encryption/drivers.

The procedure for adding the key is different for Agent-managed devices and Agentless-managed devices.

Add the DumpXmlInventory registry key to an Agent-managed Windows device

You must add DumpXmlInventory to a Windows DDP|E client before the appliance can collect field information from that client's inventory.xml file.

For Agent-managed Windows devices, you can use a default offline KScript from the appliance scripting feature to set the "dump inventory" registry key. This key is necessary for the DDP|E agent to write the detailed inventory XML data to the appliance file system.

* 
NOTE: After you set the registry key, the DDP|E service requires a full policy update schedule before the appliance is able to collect inventory.
1.
Go to the Script Detail page for the K1000 Enable Detailed DDPE Inventory (Windows) script.
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 Scripting, then click Scripts.
c.
From the list, select K1000 Enable Detailed DDPE Inventory (Windows).
2.
In the Configure section, specify script settings:

Option

Description

Name

K1000 Enable Detailed DDPE Inventory (Windows), the name of this default script.

Enabled

Select this check box to run the script on the target devices. Do not enable a script until you are finished testing it and are ready to run it. Enable the script on a test label before you enable it on all devices.

Type

The script type is Offline KScripts.

Status

Indicates the readiness of the script to be rolled out to the network. Set the status to Production.

Description

Contains the brief description of the actions the default script performs.

Notes

Any additional information you want to provide.

3.
In the Deploy section specify deployment options:

Option

Description

All Devices

Deploy to all devices. Clear the check box to limit the deployment to specific labels or devices.

Labels

Limit deployment to devices that belong to specified labels. To select labels, click Edit, drag labels to the Limit Deployment to window, then click Save.

If you select a label that has a Replication Share or an alternate download location, the appliance copies digital assets from that Replication Share or alternate download location instead of downloading them directly from the appliance.

* 
NOTE: The appliance uses a Replication Share before it uses the KACE Alt Location.

Devices

Limit deployment to one or more devices. To find devices, begin typing in the field.

Operating Systems

The operating systems on which the application runs. Applications are deployed only to devices with the selected operating systems.

1.
Click Manage Operating Systems.
2.
In the Operating Systems dialog box that appears, select the OS versions in the navigation tree, as applicable.

You have an option to select OS versions by their family, product, architecture, release ID, or build version. You can choose a specific build version, or a parent node, as needed. Selecting a parent node in the tree automatically selects the associated child nodes. This behavior allows you to select any future OS versions, as devices are added or upgraded in your managed environment. For example, to select all build current and future versions associated with the Windows 10 x64 architecture, under All > Windows > Windows 10, select x64.

4.
In the Schedule section, specify run options:

Option

Description

None

Run in combination with an event rather than on a specific date or at a specific time.

Every n hours

Run at a specified interval.

Every day/specific day at HH:MM

Run daily at a specified time, or run on a designated day of the week at a specified time.

Run on the nth of every month/specific month at HH:MM

Run on the same day every month, or a specific month, at the specified time.

Run on the nth weekday of every month/specific month at HH:MM

Run on the specific weekday of every month, or a specific month, at the specified time.

Custom

Run according to a custom schedule.

Use standard 5-field cron format (extended cron format is not supported):

* * * * *
| | | | +────────day of week (0-6)(Sun=0)
| | | +────────month (1-12)
| | +────────day of month (1-31)
| +────────hour (0-23)
+────────minute (0-59)

Use the following when specifying values:

•
Spaces ( ): Separate each field with a space.
•
Asterisks (*): Include the entire range of values in a field with an asterisk. For example, an asterisk in the hour field indicates every hour.
•
Commas (,): Separate multiple values in a field with a comma. For example, 0,6 in the day of the week field indicates Sunday and Saturday.
•
Hyphens (-): Indicate a range of values in a field with a hyphen. For example, 1-5 in the day of the week field is equivalent to 1,2,3,4,5, which indicates Monday through Friday.
•
Slashes (/): Specify the intervals at which to repeat an action with a slash. For example, */3 in the hour field is equivalent to 0,3,6,9,12,15,18,21. The asterisk (*) specifies every hour, but /3 restricts this to hours divisible by 3.

Examples:

•
15 * * * * Run 15 minutes after every hour every day
•
0 22 * * * Run at 22:00 every day
•
0 0 1 1,6 * Run at 00:00 on January 1 and June 1
•
30 8,12 * * 1-5 Run weekdays at 08:30 and 12:30
•
0 2 */2 * * Run every other day at 02:00

View Task Schedule

Click to view the task schedule. The Task Schedule dialog box displays a list of scheduled tasks. Click a task to review the task details. For more information, see View task schedules.

5.
Skip the Dependencies and Tasks sections.
6.
Do one of the following:
◦
Click Run Now to immediately push the script to all devices.

Use this option with caution. See Using the Run and Run Now commands.

◦
Click Save.
Add the DumpXmlInventory registry key to an Agentless-managed Windows device

You must add DumpXmlInventory to a Windows DDP|E client before the appliance can collect field information from that client's inventory.xml file.

For an Agentless-managed Windows device, the process requires that you create a new Group Policy Object on a Windows Server 2008 or 2012 device so that you can deploy the registry setting to multiple devices in a domain.

1.
On a Windows Server 2008 or 2012 device, open the Group Policy Management Console.
2.
Right-click Group Policy Objects and click New.
3.
Provide a description name for the new GPO (for instance, Dell Data Protection | Encryption: Inventory Registry Setting) and click OK.
4.
Right-click the new GPO and click Edit.
5.
Browse to Computer Configuration > Preferences > Windows Settings > Registry.
6.
Right-click Registry and select New > Registry Item.
7.
On the General tab, select Update in the Action drop-down menu.
8.
Select HKEY_LOCAL_MACHINE in the Hive drop-down list.
9.
Specify a Key Path of SYSTEM\CurrentControlSet\services\DellMgmtAgent\Parameters.
10.
Specify a Value name of DumpXmlInventory.
11.
Select REG_DWORD in the Value type drop-down list.
12.
Specify 1 in the Value data field.
13.
Select the Hexadecimal option in the Base group, and click OK.
14.
Close the Group Policy Management Editor.

You can now link this new group policy object to a specific domain, Organizational Unit, and so on.

Important:
 
IMPORTANT: You should test the GPO on a specific computer or set of computers before deploying it to all systems.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택