Workspace Weekly: 6.3 feature – Process Tracking for Custom Connectors
November 7, 2025
This week’s Workspace Weekly digs into a Login Enterprise 6.3 feature that makes connector runs more dependable: process tracking for Custom Connectors.
You tell the Launcher what to watch, so results reflect the real session, not a guess based on timeouts. Practically speaking, sessions end when they should, false fails drop, and troubleshooting is speedier.
Check out this doc for step-by-step directions on process tracking for custom connectors: Process Tracking.
Figure 1: Custom Connector settings > Process Tracking section
What it means for you
Custom Connectors often start a helper and then hand it off to another process. If the first process closes early, results can look wrong or hang. With process tracking, the Launcher binds to the right process or window, so the test run shows true start and stop behavior. This way you get trustworthy signals and less noise during triage.
What you get
- Reliable session endings: the session stops when the tracked process or window closes.
- Fewer false “Could not connect” errors: less reliance on broad timeouts.
- Clearer diagnostics: It is easier to see what happened and when it finished.
How it works
Open your Custom Connector and find Process Tracking. Add values to any of the three optional fields to enable tracking. Leave all blank to keep tracking off.
- Process name: exact process name to monitor, for example mstsc or wfica32
- Command-line token: substring to match in the process command line, for example {sessionId}
- Window title token: substring to match in the main window title, for example {sessionId}
Matching is logical and across whatever fields you set. If you enter process name and Window title token, both must match the tracking to bind. If no match is found, Login Enterprise falls back to legacy behavior. The global timeout still applies as a safety net.
Check out how to use this feature in a demo:
Notes and requirements
- Requires Launcher 6.3 or later.
- Each field supports up to 255 characters and trims leading or trailing spaces on save.
- Tokens like {sessionId}, {username}, {password}, {domain}, {custom1} are supported.
- Use process names without extensions, for example mstsc, not mstsc.exe.
- In multi-session tests, relying on Process name only can collide across sessions.
Imagine if you are…
A VDI engineer running parallel RDP sessions. You set Process name to mstsc and include {sessionId} in the command line or window title. The Launcher locks onto the right instance for each session and closes it cleanly when the user’s session ends.
A Citrix admin validating a published app. You track wfica32 and add a window title token with {sessionId}. Similar looking processes no longer trip over each other, so your results line up with user reality.
A services lead delivering a POC. Your connector script launches a shell that starts the real client. You track the client process, not the wrapper, so your timeline reflects the true end of the user’s session.
Quick tips
- Prefer a window title or command-line token that includes {sessionId} for uniqueness.
- Avoid Process name only in multi-session scenarios.
- Track the remote client process, not the wrapper script.
- Keep the tokens short and specific. Matching is substring based; no wildcards are needed.
- Start simple, validate a match, then add a second token if you need a tighter bind.
Ready to try 6.3? Upgrade your appliance, then follow this documentation to add and use Process Tracking. Next week’s Workspace Weekly will cover more features from our 6.3 release. Don’t forget to join #workspace-weekly on Slack to share your own tips and stories. As always, your feedback helps make Login Enterprise better for you.
Workspace Weekly
