15 Dependencies to Map Before You Migrate
Most VMware migrations fail at the access layer, not the hypervisor. Before you move a single VM, audit these 15 coupling points between your connection broker and your infrastructure. Every unchecked box is a Day 2 outage waiting to happen.
Identity & Authentication
- MFA chain — Does your multi-factor auth flow route through Horizon Connection Server or Workspace ONE?
- AD/LDAP integration — Is your directory lookup handled by the broker, or does it pass through a VMware-specific SAML/IdP bridge?
- Smart card authentication — Are your CAC/PIV certificate mappings configured in the broker, in GPO, or in a VMware-specific middleware layer?
- SSO token handling — Does your single sign-on depend on VMware’s True SSO or a broker-specific token relay?
Protocol & Display
- Protocol negotiation — Is PCoIP/Blast/RDP selection hardcoded to the broker, or can it be negotiated independently?
- DCV/PCoIP licensing — Are your display protocol licenses tied to VMware entitlements or a standalone EULA?
- Session persistence — Does session reconnect logic rely on the broker’s state table, or does it survive a broker failover?
Device & Peripheral Control
- USB passthrough rules — Are your PID/VID allow-lists stored in GPOs, in the broker config, or in Horizon Agent settings that won’t exist post-migration?
- Peripheral redirection — Do scanners, printers, and webcams route through VMware’s Virtual Printing or a broker-neutral channel?
- Client drive mapping — Is folder redirection handled by the hypervisor tools (VMware Tools) or at the protocol layer?
Power & Lifecycle Management
- VM power operations — Do your “power on at login” and “suspend at disconnect” actions call vCenter APIs directly?
- Provisioning automation — Are your pool scaling scripts (grow/shrink) written against vSphere SDKs?
- Snapshot and image management — Does your golden image workflow depend on vCenter Linked Clones or Instant Clones?
Monitoring & Policy
- Session analytics — Are your utilization dashboards pulling from vROps or Horizon Help Desk?
- Access policy enforcement — Are your conditional access rules (geo-fencing, device posture, time-of-day) configured in the broker, or in a VMware-specific policy engine like Workspace ONE UEM?
How Leostream eliminates these dependencies
Leostream sits between your users and your infrastructure as a hypervisor-neutral broker. It handles MFA, AD/LDAP, smart card auth, USB policy, protocol negotiation (PCoIP, DCV, RDP, and others), and VM power operations through a single abstraction layer, so none of the 15 items above are tied to what’s running underneath. Swap VMware for KVM, Nutanix, Hyper-V, or any combination, and the user experience doesn’t change.
Ready to decouple your workstation layer? Download the technical brief Elastic, Secure, and Automated Virtual Workstation Delivery for Energy Research on OpenStack to see how organizations are delivering GPU workstations without infrastructure lock-in.
