Description:
Enterprise customers want to be able to manage printers across remote groups without having to create numerous OUs to assign the printers. An example is a retail store chain or restaurant chain with a handful of devices and printers in remote locations and little to no cross-over in the user population. We currently support naming individual printers in the NativePrint policy using variable substitutions of the MACHINE_NAME and ASSET_ID fields. Would like to be able to do the same in the NativePrintWihtelist and Blacklist policies to show (or hide) printers based on data the administrators can manage.

Use case:
A restaurant has hundreds of locations, each with a printer using a naming convention based on store name / number. With this feature we could bulk upload the entire list of printers and include the store name / number in the id or guid field. Then the Chrome Devices could have the store name / number embedded in the first x characters of a custom field like ASSET_ID. In the white list then the policy for a visible printer could be set to "{$ASSET_ID, 0, 6}" and therefore each device will only see the printer in that restaurant.


Motivation:
To be able to assign printers based on specific data that can be embedded in the device metadata and managed on a device-by-device basis without having to create separate OUs.

Existing workarounds:
Create an OU for every store and assign the devices to the appropriate OU.