Your Test Isn’t Using All Those Monitors | Workspace Weekly

September 9, 2026

Setting up a multi-monitor VDI is easy. The challenge is validating how it performs across those displays.  A desktop session can expose two, three, or four monitors while every automated application still launches and runs on the primary display.

Think about a financial-services worker who normally has several applications spread across multiple monitors. If the automated workload keeps everything on Monitor 1, the session may have the right monitor count, but the test is not reproducing the way that desktop is normally used.

If you are comparing GPU profiles, validating remoting behavior, measuring user experience, or looking at what changes as display count and resolution increase, presenting multiple monitors is not enough.

Your workload needs to use that desktop the way a real user would. That is why we built the Login Enterprise Multi-Monitor Preview.

This is an engineering Preview intended for evaluation and feedback. It is not yet a built-in or supported Login Enterprise feature. The Preview is available now on GitHub.

A Multi-Monitor Session Is Not a Multi-Monitor Test

A multi-monitor session can still behave like a single-monitor workload when all the application activity stays on the primary display.

I keep coming back to the same distinction: monitor count tells you what the session exposes, while workload placement tells you how much of that desktop your test is using.

The Preview lets Login Enterprise workloads use those additional displays instead of leaving them idle.

Figure 1: A Login Enterprise workload opening and placing applications across two displays.

What the Preview Does: Round-Robin Window Placement

The Preview detects the monitors available to the Windows session and places the main application window on a selected display before the workload continues.

The current Preview uses deterministic, primary-first round-robin placement.

Round-Robin Placement in Practice

On a two-monitor desktop, a simple sequence could look like this:

• Word > Monitor 1
• Edge > Monitor 2
• Excel > Monitor 1
• PowerPoint > Monitor 2

I used a round robin because it was simple, predictable, and easy to validate in a Preview. It is not a requirement for how Login Enterprise would implement this as a supported product capability.

Main Windows Only

The Preview also focuses on the main application window. Temporary UI such as splash screens, dialogs, popups, and secondary windows does not automatically consume another monitor assignment.

Compare EUX, GPU, and Remoting Behavior Across Display Configurations

Once the workload is using additional displays, you can start making more meaningful comparisons.

For example, run the same workload across one, two, three, and four monitors while keeping the rest of the environment as consistent as possible. Then compare what changes in EUX, endpoint latency, GPU behavior, remoting activity, or application response times.

You can do the same thing after changing resolution, GPU or vGPU profile, desktop image, or remoting configuration.

The workload remains useful across those comparisons. Instead of only confirming that Windows presented the requested displays, you make applications use more of the desktop by putting more of the graphics and remoting stack into play. That is much closer to the behavior you are trying to validate.

How to Try the Multi-Monitor Preview

The basic path is:

1. Upload the Preview DLL to the Login Enterprise appliance.
2. Add the Multi-Monitor Prepare workload.
3. Use one of the included examples or adapt an existing workload.
4. Run it in a Windows session with multiple monitors.

You can use web workloads, too. I validated the Preview with both Login Enterprise web workload paths: the newer Playwright-based Web Recorder and the legacy Selenium-based browser workloads. The browser starts through its normal automation path, the workload resolves and places the native browser window, and Playwright or Selenium continues controlling it afterward. The repo’s adaptation guidance and AI skill can use the same pattern when adapting web workloads.

The repository has detailed requirements, setup steps, quick start, examples, validation guidance, and known limitations.

View the Multi-Monitor Preview on GitHub

Adapt Existing Workloads With the Included AI Skill

The repository also includes an AI skill and adaptation guidance for existing Login Enterprise workloads.

You can give a coding agent an existing workload, describe the multi-monitor behavior you want in natural language, and produce an adapted workload for review.

The agent can speed up the mechanical work, and the result should be reviewed and tested in the intended Login Enterprise environment.

See the AI-assisted workload adaptation guide

What I Want to Learn From Your Environments

The current implementation is a practical engineering Preview. The round-robin behavior, helper DLL, and other implementation choices are ways to prove the use case, not a specification for a future product implementation.

What matters now is learning how this behaves in real environments.

Try your own workloads. Try different monitor counts, resolutions, scaling configurations, and desktop layouts. I especially want to understand where placement behavior becomes awkward, which applications need special handling, and what configuration users want.

The existing public feature request also covers multi-monitor support for recording and playback of workloads, so feedback on the authoring experience matters too.

Try the Preview and Tell Us What You Think

The Login Enterprise Multi-Monitor Preview is available now on GitHub:

Try the Multi-Monitor Preview

If multi-monitor workload support matters in your environment, add your feedback to the public feature request:

Multi-monitor support for recording and playback of workloads

I am especially interested in feedback around monitor topology, display count, application compatibility, placement behavior, window sizing, and how monitor selection should fit into workload recording and authoring.

For discussion or troubleshooting during the Preview, you can also reach the Login VSI product team in the Login VSI Customer Slack.