Use XML provisioning to collect custom attributes based on device details. Custom attributes enable you to use advanced product provisioning functionality.

Implementation

To begin collecting custom attributes, take the following steps.

  1. Navigate to Devices > Staging & Provisioning > Components > Files/Actions > Add and select Windows > Windows Desktop as your platform.
  2. Complete the steps to create an XML product as mentioned in Create an XML Provisioning File. Upload the XML file and specify the download path as {installation path}\AirWatch\AgentUI\Cache\Profiles.

Upon receiving the XML file, the AirWatch Unified Agent creates a custom attributes output file. During the next check-in with Workspace ONE ™ UEM, the AirWatch Agent sends the output file to the UEM console.

Once the XML file installs, the custom attributes requested in the file are reported to the UEM console. These values display in the console in the Device Details page under custom attributes. This page allows you to view the name of the attribute and the values returned from each device. These values can be used to create product assignment rules using the Custom Rules system.

Prod_Prov_WinDeskCustomAttributes

Note:

Note: Custom Attributes support the HKLM registry hive only.

You can also view existing custom attributes for all devices at a particular organization group and manually create custom attributes directly in the console. Navigate to Devices > Staging & Provisioning > Custom Attributes > List View to see these custom attributes listed. Any custom attribute created in this manner automatically associates with a device and its respective custom attribute value that is successfully transmitted to the console.

Syncing Registry Settings

To synchronize the registry settings on a Windows 8 device with the console, which is likely the most common use of custom attributes for Windows 8 devices, you need to create a custom XML file. Below is an example of the format of an XML file that can pull information from the registry on a device:

Windows 8.1 Example

<?xml version="1.0"?>
                  -<wap-provisioningdoc>
                  	-<characteristic type="com.airwatch.getregistryinfo.winpc">
                  		<reg_value value_name="KeyName(i.e. CommonFilesDir)" key_name="RegistryPath(i.e.
                  Software\Wow6432Node\Microsoft\Windows\CurrentVersion)" custom_attribute_name="AttributeName"/> 
                  		<reg_value value_name="Keyname ..." key_name="Path\...." custom_attribute_name="AttributeName2"/>
                  	</characteristic>
                  </wap-provisioningdoc>
                  
                  
                  
               

Windows 10 Example

<xml version="1.0">

<wap-provisioningdoc name="System Info /V_1">

<characteristic type="com.windowspc.getregistryinfo.managed">

<reg_value

custom_attribute_name="Hostname"

key_name="SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerName"

value_name="ComputerName"/>

</characteristic>

</wap-provisioningdoc>

It must be in the previous format for the XML file to get correctly parsed and the registry settings to be outputted to a key value pair that can be exported back to the AirWatch Console. In this example, the registry key path is “HKEY_LOCAL_MACHINE\Ident” for two of the values and within that key path it is reading the values of “Username” and “OrigName”. The ‘custom_attribute_name’ parameter is the name of the custom attribute that displays in the console and corresponds to the value read from the device.