Case studyGOV-01 · Government
State agency rescues a failed Citrix migration and stabilizes its VDI
Z7 Solutions™ rescued a stalled Citrix to Horizon migration for a state agency, retired Citrix and standardized both data centers on Horizon 8. Logins got roughly 48% to 60% faster and session crashes fell over 80%.
Part 1 of 2 · State agency VDI programAt a glance
GOV-01 · Government
- 48% to 60% Improvement in login times after GPO cleanup and image tuning
- 80%+ Fewer session crashes and disconnects
- About 40% Fewer recurring VDI support tickets, based on ticket analytics
- Zero Citrix licensing left after the platform was retired
The client
A state agency, referred to here as the State Entity, that supports thousands of users across multiple agencies and locations. Its VDI environment spans two primary data centers running VMware Horizon on vSAN and Dell compute. Z7 Solutions has served as its long-term engineering and managed services partner for VDI and end-user computing.
The challenge
Years before Z7 was engaged, the agency launched a migration from Citrix to VMware Horizon that never truly completed. It stalled and drifted until both platforms coexisted and neither was healthy. Users faced slow logons, frequent disconnects, and had very little confidence in the platform.
- Site A Horizon crashingSite A ran an unstable Horizon deployment that crashed often, with session drops, desktop freezes, and inconsistent performance.
- Oversubscribed vSAN at Site AvSAN and Dell compute clusters at Site A were oversubscribed, misconfigured, and not monitored in a disciplined way.
- Site B build abandonedSite B held a Horizon build abandoned mid-project, App Volumes packages that were incomplete or broken, and no standards for image lifecycle, patching, or configuration.
- Citrix still in productionCitrix was still partially in production, which meant duplicate tool sets, extra complexity, and unnecessary licensing cost.
- Stale AD, conflicting GPOsActive Directory held thousands of stale objects, Group Policy was layered and conflicting, and App Volumes and DEM were used without clear rules, causing random application failures.
- Untested DR, high ticket loadDR was limited to basic backups with no regular validation, and the help desk carried a high volume of tickets on logons, profiles, printing, and session stability.
What we did
The engagement as a living map: where the client started, the work Z7 did, and what was delivered and measured.
- challenge in
- Z7 work
- delivered
- measured
Read the engagement
Before on top, Z7's work in the middle, results below: point at a node to light its wiring, click to pin its story here.
Site A ran an unstable Horizon deployment that crashed often, with session drops, desktop freezes, and inconsistent performance.
vSAN and Dell compute clusters at Site A were oversubscribed, misconfigured, and not monitored in a disciplined way.
Site B held a Horizon build abandoned mid-project, App Volumes packages that were incomplete or broken, and no standards for image lifecycle, patching, or configuration.
Citrix was still partially in production, which meant duplicate tool sets, extra complexity, and unnecessary licensing cost.
Active Directory held thousands of stale objects, Group Policy was layered and conflicting, and App Volumes and DEM were used without clear rules, causing random application failures.
DR was limited to basic backups with no regular validation, and the help desk carried a high volume of tickets on logons, profiles, printing, and session stability.
VDI rescue and standardization, Phase 1.
Scope: VDI stabilization, Citrix retirement, Directory and policy cleanup, Governance and DR.
Z7 treated Site B as a greenfield reference design, deploying Horizon 8 components on supported, current versions, correcting vSAN policy, datastore layout, and host configuration, and expanding Dell compute to remove oversubscription. The team rebuilt App Volumes packaging and entitlements on a clean model, standardized DEM, and hardened and documented golden images with clear ownership and lifecycle.
With a clean reference in place, Z7 cleaned vCenter, snapshots, and orphaned virtual machines and fixed misaligned storage policies and cluster configurations. The team aligned App Volumes strategy and DEM configuration with Site B, stabilized performance, and removed recurring failure patterns.
In parallel, Z7 migrated the remaining Citrix hosted workloads into Horizon, consolidated and standardized golden images for the Horizon pools, and decommissioned Citrix components, dependencies, and licensing.
Z7 rebuilt the OU design to match business and technical needs, removed thousands of stale user and computer objects, and retired hundreds of obsolete or conflicting GPOs. Simplified logon policies led directly to faster and more reliable logons.
Z7 implemented two-site NetApp replication for key Horizon infrastructure and user data, used cloud for backup and DR validation without moving production desktops out of the data centers, and documented DR runbooks and tested failover patterns. Formal governance now covers image lifecycle, app packaging, and change control, backed by monitoring and analytics that trend recurring issues.
Across thousands of endpoints in the VDI footprint, the improvements were measurable and sustained.
Improvement in login times after GPO cleanup and image tuning.
Fewer session crashes and disconnects.
Fewer recurring VDI support tickets, based on ticket analytics.
Citrix licensing left after the platform was retired.
Login times improved by about 48% to 60% after image tuning and GPO cleanup.
Session crashes and disconnects dropped by more than 80%, and users reported far fewer interruptions, especially during peak hours.
Overall VDI performance improved by an estimated 20% to 30%, largely due to vSAN remediation and added compute capacity.
Recurring VDI tickets fell by roughly 40% according to ticket system analytics, and support teams could shift more time from firefighting to planned maintenance and project work. Outages and emergency fixes decreased, which reduced soft costs and stress on staff.
Citrix licensing and support expenses were fully removed, and validated DR processes and cloud-supported backups lowered operational risk. Image, application, and policy ownership became clear and traceable.
Both data centers now run a single, well-governed Horizon 8 architecture on premises, the foundation for Phase 2: Horizon Cloud on Azure, FSLogix profiles, Turbo containers, and endpoint modernization.
- challenge in
- Z7 work
- delivered
- measured
Tap a node to read its story.
Step by step
-
Rebuild Site B as the reference design
Z7 treated Site B as a greenfield reference design, deploying Horizon 8 components on supported, current versions, correcting vSAN policy, datastore layout, and host configuration, and expanding Dell compute to remove oversubscription. The team rebuilt App Volumes packaging and entitlements on a clean model, standardized DEM, and hardened and documented golden images with clear ownership and lifecycle.
-
Repair and align Site A to the standard
With a clean reference in place, Z7 cleaned vCenter, snapshots, and orphaned virtual machines and fixed misaligned storage policies and cluster configurations. The team aligned App Volumes strategy and DEM configuration with Site B, stabilized performance, and removed recurring failure patterns.
-
Retire Citrix completely
In parallel, Z7 migrated the remaining Citrix hosted workloads into Horizon, consolidated and standardized golden images for the Horizon pools, and decommissioned Citrix components, dependencies, and licensing.
-
Clean up Active Directory and GPOs
Z7 rebuilt the OU design to match business and technical needs, removed thousands of stale user and computer objects, and retired hundreds of obsolete or conflicting GPOs. Simplified logon policies led directly to faster and more reliable logons.
-
Strengthen DR and governance
Z7 implemented two-site NetApp replication for key Horizon infrastructure and user data, used cloud for backup and DR validation without moving production desktops out of the data centers, and documented DR runbooks and tested failover patterns. Formal governance now covers image lifecycle, app packaging, and change control, backed by monitoring and analytics that trend recurring issues.


Results
Across thousands of endpoints in the VDI footprint, the improvements were measurable and sustained.
- Logins about 48% to 60% fasterLogin times improved by about 48% to 60% after image tuning and GPO cleanup.
- Crashes down more than 80%Session crashes and disconnects dropped by more than 80%, and users reported far fewer interruptions, especially during peak hours.
- Estimated 20% to 30% fasterOverall VDI performance improved by an estimated 20% to 30%, largely due to vSAN remediation and added compute capacity.
- Tickets down roughly 40%Recurring VDI tickets fell by roughly 40% according to ticket system analytics, and support teams could shift more time from firefighting to planned maintenance and project work. Outages and emergency fixes decreased, which reduced soft costs and stress on staff.
- Citrix gone, DR validatedCitrix licensing and support expenses were fully removed, and validated DR processes and cloud-supported backups lowered operational risk. Image, application, and policy ownership became clear and traceable.
- One governed Horizon 8 baseBoth data centers now run a single, well-governed Horizon 8 architecture on premises, the foundation for Phase 2: Horizon Cloud on Azure, FSLogix profiles, Turbo containers, and endpoint modernization.

Technology
- VMware Horizon 8
- Citrix
- App Volumes
- DEM
- vSAN
- vCenter
- Dell compute
- NetApp replication
- Active Directory
- Group Policy
The series: State agency VDI program
2 parts
- Part 1 of 2 · you are readingState agency stabilizes VDI after a failed migration
- Part 2 of 2 · read nextState agency modernizes Horizon VDI on Azure
Want results like these?
Start with a conversation. We will tell you what applies to your environment and what does not.