Adobe Reader DC Template

This template creates a configuration that checks if the remote device is licensed for Adobe Reader DC. It can be found in the LICENSE COMPLIANCE category when filtered for REMOTE platform.

If the remote device is not licensed for Adobe Reader DC, you can choose between two actions:

• Hides Adobe Reader DC from the session with FSLogix App Masking if the remote device is not licensed.
• Denies Adobe Reader DC within the session with Microsoft AppLocker if the remote device is not licensed.

deviceTRUST requires some simple but essential configuration steps to be performed to enable the template for your remoting and DaaS environments. We will guide you step-by-step through simple deviceTRUST configuration steps to enable the template within your remoting or DaaS environment.

We will perform the following steps:

1. Step 1: Prerequisites
2. Step 2: Contexts
3. Step 3: Actions

Step 1: Prerequisites

If the required deviceTRUST components (Agent, Console, Client Extension and License) are not yet installed, please visit the Getting Started for Remote guide and complete step 1 to 5 and then continue here with step 2 below.

Step 2: Contexts

The template has imported the following contexts:

Context	Description	Customizations
Adobe Reader DC Licensed Status	Defines if the remote device is licensed to use Adobe Reader DC within the session.	You must update the following context condition with data suitable for your environment: REMOTE - HARDWARE BIOS SERIAL NUMBER Any Of 3 ITEMS When identifying physical devices, replace BIOS_SERIAL_NUMBER_X with BIOS serial numbers of your licensed devices. Example: PF1J8T36 REMOTE - OS ID Any Of 3 ITEMS When identifying physical devices, replace OS_ID_X with OS ID of your licensed devices. Example: 31f75261-7066-485b-9a95-de9b2c7d4b73 LOCAL - REMOTE CONTROL REMOTE NAME Any Of 3 ITEMS When identifying physical devices, replace REMOTE_DEVICE_NAME_X with Name of your licensed devices. Example: DE-SG01 LOCAL - USER GROUPS Is Member Of Any DOMAIN\GROUP To identify users who can use any physical device, replace DOMAIN\GROUP with a security group. Example: DEMO\Adobe Reader DC License Override
Adobe Reader DC User	Defines if the session user is member of the Adobe Reader DC AD application group.	You must update the following context condition with data suitable for your environment: LOCAL - USER GROUPS Is Member Of Any DOMAIN\GROUP To identify users which are allowed to use the licensed application, replace DOMAIN\GROUP with a security group. Example: DEMO\Adobe Reader DC Licensed Users

Step 3: Actions

The template includes an FSLogix App Masking and a Microsoft AppLocker enforcement action that actively controls access to applications, depending on the technology available. By default both actions are disabled. In addition, an active report action with various report options has been added too.

Action	Description	Default State	Customizations
Adobe Reader DC Licensed Device - Conditional Application Access - FSLogix App Masking	Hides Adobe Reader DC from the session with FSLogix App Masking if the remote device is not licensed.	Deactivated	You must update the following context condition with data suitable for your environment: FSLOGIX APP MASKING Replace ENTER_YOUR_FXA_PATH_HERE with your target .fxa file path on all FSLogix App Masking tasks. Example: %ProgramFiles%\FSLogix\Apps\Rules\NotepadPlusPlus.fxa TERMINATE APP Replace ADD_PROCESS_NAME_X with your target process name on all Terminate App tasks. Example: notepad++.exe
Adobe Reader DC Licensed Device - Conditional Application Access - Microsoft AppLocker	Denies Adobe Reader DC within the session with Microsoft AppLocker if the remote device is not licensed.	Deactivated	You must update the following context condition with data suitable for your environment: MICROSOFT APPLOCKER Replace ENTER_YOUR_PATH_HERE with your target configuration on all Microsoft AppLocker tasks. Example: %PROGRAMFILES%\Notepad++\notepad++.exe
Adobe Reader DC Licensed Device - Conditional Application Access - Reporting	Reports Adobe Reader DC licensing status.	Activated	You must update the following context condition with data suitable for your environment: WEB REQUEST REPORT ADOBE READER DC LICENSED STATUS TO SPLUNK When using Splunk for license compliance reporting, replace YOUR_SPLUNK_SERVER:8088 and YOUR_SPLUNK_AUTH_TOKEN with your Splunk configuration. Example: dtldss02.demo.devicetrust.local:8088 WEB REQUEST REPORT ADOBE READER DC LICENSED STATUS TO ELK STACK When using ELK Stack for license compliance reporting, replace YOUR_ELKSTACK_SERVER:9200 with your ELK Stack configuration. Example: dtldss02.demo.devicetrust.local:9200 WEB REQUEST REPORT ADOBE READER DC LICENSED STATUS TO GRAYLOG When using Graylog for license compliance reporting, replace YOUR_GRAYLOG_SERVER:12201 with your Graylog configuration. Example: dtldss02.demo.devicetrust.local:12201

Troubleshooting

If your deviceTRUST installation or configuration does not work as expected, you can use the Troubleshooting guide to start troubleshooting.