Setting Up the Win 365 Connector

Overview

Windows 365 is a cloud-based Windows desktop solution provided by Microsoft. However, Login Enterprise does not provide a direct connection to Windows 365 out-of-the-box, you can integrate Windows 365 with your environment using a custom connector. This article will walk you through the process of setting up the Windows 365 Connector using a PowerShell script and a standalone engine.

The setup process may require a certain level of technical expertise. If you encounter any challenges or need assistance, please feel free to contact Login VSI Support at support@loginvsi.com.

Prerequisites

Before proceeding, ensure you have the following components:

1. PowerShell Script
The connector.ps1 script is required to initiate the connection process. It serves as the workflow script to connect your environment with Windows 365.

2. C# Script
The WindowsAppConnector.cs script works alongside the PowerShell script. The connector interacts with the Windows App in order to establish a connection to a Win 365 Virtual Desktop.

3. Standalone Engine
The standalone engine must be installed on every Launcher that will run the Connector. It executes the connection process once triggered by the PowerShell script.

You can find the necessary scripts under Additional Resources, or you may write your own PowerShell script, though using the provided ones is recommended for simplicity.

Setup Steps

1. Install the Standalone Engine. You can install Universal Web Connector (UWC), which includes the standalone engine you need. For details, see downloading and installing Universal Web Connector.

2. Download the Scripts. You need two important scripts for this to work:

PowerShell script (connector.ps1)
C# script (WindowsAppConnector.cs)

3. Make Sure the Scripts are Accessible. Place both scripts in a folder where they are easy to access, and ensure you know the file paths.

4. Configure the Custom Connector. When you go to your Test settings, you need to select Custom Connector as an option. For information on configuring the Custom Connector settings, see Custom Connector.

Edit the PowerShell Script: Before linking the PowerShell script (connector.ps1), ensure that the paths for both the standalone engine and C# script are correct. Open the connector.ps1 script in a text editor and update the following variables:

Standalone engine path: Update the path to where the standalone engine is installed.
C# script path: Update the path to where the WindowsAppConnector.cs

Once the paths are updated, save the file and link it to the Custom Connector. This will enable the script to properly trigger the connection.

5. Run the PowerShell Script. Now that everything is set up, you’ll run the PowerShell script (connector.ps1).

Running this script will start the process and the standalone engine will begin to connect to Windows 365.

Notes and Considerations

Certain factors in your environment may require additional configuration:

Timing Issues: If you're running the Connector in a virtual desktop environment with network latency, you may need to adjust the wait times in the script. By default, the script assumes actions happen almost immediately, but you may experience delays.
Custom Configurations: If your organization uses Single Sign-On (SSO), you may need to add extra steps to the script’s configuration. This is done by editing the dictionary/array part of the script.
Updates or Changes in Windows 365: Since Windows 365 is continually updated, changes to the platform (like UI or app updates) could affect how the Connector interacts with the system. If UI elements (buttons, controls, etc.) change, you may need to update the script to reflect those changes. Regular maintenance and script adjustments may be necessary.
Editing the Script: If you run into issues during setup, the only part of the script you’ll need to edit is the dictionary/array, which defines the workflow steps. This array is located within the GetStartRemoteConnectionActions() function in the PowerShell script.

For any issues or if you need help editing the script, don’t hesitate to contact Login VSI Support at support@loginvsi.com.

Additional resources