Custom Attribute Database Migration

Overview

AirWatch supports moving previous XML custom attribute files to a new custom attribute database that allows for more communication between devices and the consoles for use of custom attributes.

Prerequisites

In order for the new fields to be present in a custom attribute XML file created from a profile, you must upgrade to at least AirWatch v8.1, and the AirWatch Agent for Windows Rugged version must be at least 5.4.66.98.

For clean migration of custom attribute data from XML files to the database, AirWatch recommends that you re-push any profiles that are already installed on any devices so that the new fields are present.

Migration

Follow the instructions below for migrating to a custom attribute database:

  1. Re-push existing profiles to update XML files with data for all profile fields.
  2. Update configuration file "~\AirWatch\AirWatch Core Agent.meta" to use 'AW_REG'
    AirWatch Core Agent.meta
    <CUSTOM-ATTRIBUTE>AW_REG</CUSTOM_ATTRIBUTE>
  3. Run command for custom attribute migration utility.
    UninstallAWAgent.exe
    \Windows\UninstallAWAgent.exe –MigrateCA

After the migration has successfully completed, the following will occur on the device thereafter:

  • Custom attribute profile payloads will be stored in the database when received by the agent
  • Custom attribute samples will be collected from the database and sent to the console through interrogator
  • Custom attribute samples will not be collected from custom attribute XML files

Migrating AirWatch XML files to CA Database

AirWatch recommends re-pushing the Custom Attribute profile from the AirWatch Admin Console after upgrading AirWatch. If you choose to migrate to a CA Database without pushing the updated profile, the following decisions are made by the migration process:

  • Importing Application values:
    • If an Application value does exist for a custom attribute record in an XML file, then the existing value is used as the value for application when the record is inserted into the database.
    • If an Application value does not exist for an attribute record in an XML file, then the File Name is used as the Application value when the record is inserted into the database.
  • Importing Attribute Name values:
    • The name of the custom attribute record in the XML element is imported as the name of the custom attribute database record.
  • Importing value:
    • The value of the custom attribute record in the XML element is imported as the value of the custom attribute database record.
  • Importing is_dynamic values:
    • If an is_dyanmic value does exist for a custom attribute record in an XML file, then the existing values is imported as the is_dynamic value for the database record.
    • If an is_dyanmic value does not exist for a custom attribute record in an XML file, then the is_dynamic value is set to "True" for the database record.
  • Importing Permission values:
    • If a Permission value does exist for a custom attribute record in an XML file, then the existing value is imported as the Permission value for the database record.
    • If a Permission value does not exist for a custom attribute record in an XML file, then the Permission value is set to "read/write" for the database record.
  • Importing sync:
    • If a Sync value does exist for a custom attribute record in an XML file, then the existing value is imported as the Sync value for the database record.
    • If a Sync value does not exist for a custom attribute record in an XML file, then the Sync value is set to "True" for the database record.
Have more questions? Submit a request

0 Comments

Article is closed for comments.