Manage custom compare value types

Learn how to manage custom compare value types in SAM Core on Snow Atlas.

Add custom compare value types

1. On the SAM Core menu, under Home, select Administration.
2. Select Custom compare value types.
3. Select Add.
4. Enter a Name for the custom compare value type.
5. Optionally, enter a Description for the custom compare value type.
6. To use a value in a custom field as the basis for compliance calculations, select Use a custom field value for compliance, and then select the custom field from the list.
   note

   You can only select a custom field with the following properties:

   • Category: Computer/Mobile device
   • Type: Digit If there are no custom fields with these properties, the Use a custom field value for compliance option will not appear.
7. Select Save.

Edit custom compare value types

1. On the SAM Core menu, under Home, select Administration.
2. Select Custom compare value types.
3. Select the custom compare value type you want to edit.
4. In Edit custom compare value type, add or edit the applicable information, see Add custom compare value types.
5. Select Save.

Delete custom compare value types

1. On the SAM Core menu, under Home, select Administration.
2. Select Custom compare value types.
3. Select the delete icon next to the name of the custom compare value type you want to delete.
4. Select OK to confirm.

Example: Use a custom compare value type for compliance calculations

The license requirement for Client Access Licenses (CALs) for Microsoft Exchange Server 2010 cannot be discovered by the Snow Inventory Agents. Instead, you choose to define the number of required licenses manually on the application.

This is an overview of the steps to make.

1. Create a custom compare value type called Exchange CAL. For more information, see Add custom compare value types.

2. On the application Microsoft Exchange Server 2010 Standard User CAL:

   1. On the License settings tab, add the metric Custom compare value, and then select Exchange CAL as the Custom compare value type.
   2. On the Compare values tab, add a Quantity of required licenses for each Organization that uses the application.

   For more information, see Edit applications.

3. On the license for Microsoft Exchange Server 2010 Standard User CAL, enter the number of purchased licenses in Quantity, and select Custom compare value as the Metric. For more information, see Add licenses.

4. Recalculate the compliance.

Example: Use a custom compare value type and a custom field for compliance calculations

The license requirement for Client Access Licenses (CALs) for Microsoft Exchange Server 2010 cannot be discovered by the Snow Inventory Agents. Instead, you choose to define the number of required licenses by using a custom field on the computers and mobile devices.

This is an overview of the steps to make.

1. Create a custom field called Exchange CAL requirement.
   note

   The custom field must have the following properties:

   • Category: Computer/Mobile device
   • Type: Digit
   For more information, see Add custom fields.
2. Create a custom compare value type called Exchange CAL. Select to use the value in the custom field Exchange CAL requirement as basis for compliance calculations. For more information, see Add custom compare value types.
3. On the application Microsoft Exchange Server 2010 Standard User CAL, add the metric Custom compare value, and then select Exchange CAL as the Custom compare value type. For more information, see Edit applications.
4. On the license for Microsoft Exchange Server 2010 Standard User CAL, enter the number of licenses purchased in Quantity, and select Custom compare values as the Metric. For more information, see Add licenses.
5. For all computers and mobile devices that have the application Microsoft Exchange Server 2010 Standard User CAL, you need to add and populate the Exchange CAL requirement custom field with a value that represents the license requirement. Do this manually or update the relevant computers and mobile devices via the data import functionality. For more information, see Manage data imports.
6. Recalculate the compliance.