Corporate Device Template

This template creates a configuration that checks if the remote device is a corporate managed device. It can be found in the COMPLIANT APPLICATION ACCESS category when filtered for REMOTE platform.

If the remote device is not a corporate managed device, you can choose between two actions:

• Hides applications with FSLogix App Masking within the session if the remote device is not a corporate managed device.
• Denies access to applications with Microsoft AppLocker within the session if the remote device is not a corporate managed device.

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
Corporate Device	Defines if the remote device is a corporate managed device.	You must update the following context condition with data suitable for your environment: REMOTE - DOMAIN ID Any Of 2 ITEMS When using AD or Azure AD domain joined devices, replace DOMAIN_SID and AZURE_TENANT_ID with your corporate values. Example: S-1-5-21-1397108472-4176295369-1616608269 for a domain SID. REMOTE - HARDWARE BIOS SERIAL NUMBER Any Of 3 ITEMS When identifying physical devices, replace BIOS_SERIAL_NUMBER_X with BIOS serial numbers of your corporate devices. Example: PF1J8T36 REMOTE - IGEL UMS SERVER Equals UMS_SERVER_IP:30001 When using IGEL OS devices, replace UMS_SERVER_IP:30001 with the IP address of your IGEL UMS Server. Example: 192.168.0.22:30001 REMOTE - IGEL UMS CERT THUMPRINT SHA256 Equals UMS_CERTIFICATE_THUMBPRINT_SHA256 When using IGEL OS devices, replace UMS_CERTIFICATE_THUMBPRINT_SHA256 with your IGEL UMS Server certificate thumprint. Example: 0d57fdd21474ef7806818a661a5f1d1cb3361a8bb4ccd660dae6930a6a135a56 REMOTE - ELUX SCOUT NAME Equals SCOUT_NAME When using eLux devices, replace SCOUT_NAME with the name of your eLux Scout Server. Example: DTLDES01 REMOTE - ELUX SCOUT CERT THUMPRINT SHA256 Equals SCOUT_CERTIFICATE_THUMBPRINT_SHA256 When using eLux devices, replace SCOUT_CERTIFICATE_THUMBPRINT_SHA256 with your eLux Scout Server certificate thumprint. Example: 0d57fdd21474ef7806818a661a5f1d1cb3361a8bb4ccd660dae6930a6a135a56

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.

Action	Description	Default State	Customizations
Corporate Device - Conditional Application Access - Enforcement - FSLogix App Masking	Hides applications with FSLogix App Masking within the session if the remote device is not a corporate managed device.	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
Corporate Device - Conditional Application Access - Enforcement - Microsoft AppLocker	Denies access to applications with Microsoft AppLocker within the session if the remote device is not a corporate managed device.	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

Troubleshooting

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