Device Type BYOD Template
This template imports a predefined context that defines the device type of the remote device as BYOD or Corporate, and can be used as a building block in your configuration. It can be found in the
BUILDING BLOCKS category when filtered for
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 Remoting and DaaS 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:
||Defines the remote device device type.
||You must update the following context condition with data suitable for your environment:
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.
When identifying physical devices, replace BIOS_SERIAL_NUMBER_X with BIOS serial numbers of your corporate devices.
When using IGEL OS devices, replace UMS_SERVER_IP:30001 with the IP address of your IGEL UMS Server.
When using IGEL OS devices, replace UMS_CERTIFICATE_THUMBPRINT_SHA256 with your IGEL UMS Server certificate thumprint.
When using eLux devices, replace SCOUT_NAME with the name of your eLux Scout Server.
When using eLux devices, replace SCOUT_CERTIFICATE_THUMBPRINT_SHA256 with your eLux Scout Server certificate thumprint.
If your deviceTRUST installation or configuration does not work as expected, you can use the Troubleshooting guide to start troubleshooting.