Access Mode Template
This template imports a predefined context that defines whether the remote device is an internal or external device on the corporate network, and can be used as a building block in your configuration. It can be found in theBUILDING BLOCKS category when filtered forREMOTE platform.
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
- Step 2: Context
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: Context
The template has imported the following context:
| 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:3389When 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:3389When using Microsoft RDP remoting protocol, replace.REMOTING_HOST_DNS_HERE:3389 with your remoting hosts dns suffix.*Example: *.demo.devicetrust.local:3389
|
Troubleshooting
- If your deviceTRUST installation or configuration does not work as expected, you can use the Troubleshooting guide to start troubleshooting.