Articles on: Secure RDP

How to setup the Secure Connect Agent for non-AD computers

How to setup the Secure Connect Agent for non-AD computers

We have a component called TruGrid Secure Connect, which is an agent that can be deployed directly to non-AD (Active Directory) joined computers, to report them into the TruGrid portal for assigning to AD users, just like you would with AD computers. Users can then login to the TruGrid Portal (or Desktop or mobile connectors) and launch their non-AD desktops the same way. This TruGrid Secure Connect agent can also be used on AD computers, for example, computers that are not local to the TruGrid Sentry Agent.

If you are switching a computer from being brokered by the TruGrid Sentry agent (typically used for AD computers) to use this TruGrid Secure Connect agent, please see this article.

How to set it up
Install the latest TruGrid SecureConnect agent on the Windows computer and activate it with the TG-XXXXXX Authorization Code for the domain the user is associated with. The TG-XXXXXX Authorization Code for a TruGrid domain can be found under the RESOURCE ASSIGMENT menu
Logon to your TruGrid Portal and assign computers to users. See further instructions here on assigning users to computers.

Important Notes:
Enable RDP on the Windows computer you installed the TruGrid Secure Connect agent onto and ensure the Windows OS firewall RDP port 3389 is open. Make sure you can connect from another computer on the local network to validate this is working ok.
When end users authenticate to TruGrid Web or Native Connector and then launch desktops, they will be asked for the local credential of the standalone computers that they are connecting to. This is because these computers are not part of AD. However, when they get the usual RDP logon prompt, they can choose the REMEMBER ME checkbox so that they will get the experience of SSO in subsequent logons.
The endpoint must be running a version of Windows that allows remote RDP into it. For example, Windows Home does not support inbound RDP. A user can connect FROM a Windows Home computer but Windows Home cannot accept inbound RDP connections.
In order to decommission a computer that previously had SecureConnect on it, please uninstall the SecureConnect software.

Updated on: 08/03/2023

Was this article helpful?

Share your feedback


Thank you!