← Selected transformations

Recovering a hosted-desktop service by standardising it properly

Approximately ten client environments inherited as separate lift-and-shift migrations. The recovery came from understanding each one, then turning the common parts into a controlled Citrix service with locked-down, automatically patched Windows endpoints.

~10client environments assessed
65%fewer support tickets year on year
Citrixthe only permitted route into each dedicated environment

The inherited service

The first migration approach had largely virtualised each client’s existing on-premises servers and exposed the same legacy desktop processes remotely over a leased circuit. The infrastructure was hosted, but the operational complexity had moved with it. That included multiple Small Business Server and Windows Server 2008 domain-controller environments that were already beyond the shape of a sustainable managed service.

The clients were not identical, so applying another generic template would have repeated the same mistake. I assessed approximately ten environments individually: identity, Exchange, file services, Citrix, workstation behaviour, antivirus, patching and the practical needs of each business.

Stabilise the foundations

I rebuilt the legacy SBS and Server 2008 domain-controller estates as Server 2016 environments, with virtualised identity services, file servers and controlled file shares. I completed the Exchange migrations, deployed managed antivirus and took control of the Citrix environments. Group Policy was designed for the hosted-desktop context rather than copied from the old office.

Every existing Windows endpoint was moved into kiosk mode. The machines were effectively locked down, automatically patched and permitted to provide only Citrix access into that client’s dedicated hosted environment. The local device stopped being an unmanaged second workplace and became a controlled access point to the service.

That created a known, supportable baseline. Differences remained where a client actually needed them, but they were decisions rather than accidents.

Turn the recovery into an operating model

Once the first environments were stable, the repeatable parts became the pattern for the wider client base. The work was not a one-off technical rescue. It produced a way to assess, migrate and operate future environments with clearer policy, fewer local dependencies and a service desk that knew what it was supporting.

Rebuild the foundationsLegacy SBS and Server 2008 domain controllers became Server 2016 environments, alongside Exchange migrations and managed antivirus.
Control the service boundaryWindows endpoints became patched Citrix kiosks, with applications and data kept inside the dedicated hosted environment.
Operate the whole serviceCitrix, identity, files, messaging, endpoint protection and patching became controlled platform responsibilities.

The outcome

Users moved from an inconsistent mix of ageing servers, local desktops, legacy storage and inherited support problems to a managed Server 2016 and Citrix service. Existing Windows hardware remained useful, but its role was deliberately narrowed and governed. Year-on-year support tickets fell by 65%.

The deeper result was order: a service that could be explained, supported and improved. The technology changed, but the reduction came from making ownership and standards explicit.

If an inherited service is consuming support time without producing confidence, the fractional IT leadership offer starts with a diagnostic and a practical 90-day plan.

Start a conversation

© 2026 Andy Bridson · Isle of Man