Access Mode Template
This template creates a configuration that checks if the remote device is connected externally. It can be found in the COMPLIANT APPLICATION ACCESS category when filtered for REMOTE platform.
If the remote device is connected externally, you can choose between two actions:
-
Hides applications with FSLogix App Masking within the session if the remote device is connected externally.
-
Denies access to applications with Microsoft AppLocker within the session if the remote device is connected externally.
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:
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 |
|---|---|---|
| Access Mode
|
Defines if the remote device is internal or external to the corporate network.
|
You must update the following context condition with data suitable for your environment |
REMOTE - REMOTING CLIENT OUTBOUND DNS Equals *.REMOTING_HOST_DNS_HERE:3389 When using Microsoft RDP remoting protocol,replace.REMOTING_HOST_DNS_HERE:3389 with your remoting hosts dns suffix.Example:.demo.devicetrust.local:3389* |
||
REMOTE - REMOTING CLIENT OUTBOUND DNS Not Equals *.REMOTING_HOST_DNS_HERE:3389 When using Microsoft RDP remoting protocol, replace. |
||
| REMOTING_HOST_DNS_HERE:3389 with your remoting hosts dns suffix.Example:.demo.devicetrust.local:3389* |
Note:
If a context is not needed, it can be deactivated or deleted. In addition, the corresponding task sequence within the relevant action must be deleted too.
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 |
|---|---|---|---|
| Access Mode - Conditional Application Access - Enforcement - FSLogix App Masking
|
Hides applications with FSLogix App Masking within the session if the remote device is connected externally.
|
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
|
|||
| Access Mode - Conditional Application Access - Enforcement - Microsoft AppLocker
|
Denies access to applications with Microsoft AppLocker within the session if the remote device is connected externally.
|
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
|
Note:
If both actions have been disabled, the contexts will still be created.
Troubleshooting
If your deviceTRUST installation or configuration does not work as expected, you can use the Troubleshooting guide to start troubleshooting.