Configuring VMware Horizon View For Remote Desktop Access

VMware Horizon View provides a controlled way to deliver Windows desktops and applications to employees, contractors, and students without placing complete corporate workstations in users’ homes. A successful deployment depends on more than installing Horizon components: identity, network security, desktop images, certificates, monitoring, and user support all need to work together.

For Australian organisations, location and connectivity matter. A user in central Melbourne may have a very different experience from someone working through the NBN in regional Queensland or Western Australia. Planning for latency, ISP variability, Australian Eastern time zones, and privacy obligations helps turn a proof of concept into a dependable remote access service.

The Horizon platform has also evolved, so administrators should confirm the supported combination of vSphere, Connection Server, agents, Unified Access Gateway, operating systems, and Horizon Client versions before deployment. The product may be called Horizon rather than Horizon View in current documentation, but the core remote desktop architecture remains familiar.

Design The Horizon Architecture

A typical deployment places Horizon Connection Servers on protected internal networks, with Unified Access Gateway appliances in a DMZ. Users connect through the Horizon Client or HTML Access, authenticate against the chosen identity provider, and receive an entitlement to a desktop pool or published application. Connection Servers broker the session; they should not be exposed directly to the public internet.

Begin with a clear naming and DNS design. External and internal fully qualified domain names should resolve to the correct interfaces, while certificates must include every name presented to users. A certificate warning on a managed laptop in Sydney can quickly become a service desk issue, especially when staff are connecting from home networks or personal broadband.

High availability should cover the Connection Server pair, vSphere management, storage, and the network path to the desktop pools. Review HA and DRS troubleshooting before relying on automated recovery, because restarting a virtual machine is not the same as restoring a working Horizon session.

Prepare vSphere And Desktop Pools

Create a dedicated desktop resource structure in vCenter, with appropriate permissions, folders, networks, and resource pools. Decide whether users need persistent full clones, linked-clone-style management through supported technologies, or instant clones. Instant clones generally simplify rapid provisioning and patch cycles, while dedicated assignments may suit specialist users who require application customisation.

The golden image should be treated as a managed build. Install the operating system updates, VMware Tools, Horizon Agent, security software, monitoring agents, and required applications in a repeatable sequence. Remove unnecessary startup tasks and validate printer, Teams, webcam, USB, and display redirection policies before publishing the image.

Pool sizing should reflect concurrency rather than the total employee count. A contact centre, university lab, and engineering team have different CPU, memory, graphics, and storage profiles. Test login storms as well as ordinary use; a Monday morning surge in Melbourne or a shift change in Brisbane can expose storage latency and profile bottlenecks that a small pilot will miss.

Secure Internet And Identity Access

Unified Access Gateway provides the secure edge for external Horizon access. Place it behind an appropriate load-balancing design, restrict management access, apply current patches, and expose only the services required for Horizon protocols. Use a trusted certificate, strong TLS configuration, and a documented process for rotating certificates before expiry.

Multi-factor authentication should be integrated with the organisation’s identity platform through supported SAML, RADIUS, or other validated methods. Apply conditional access where practical, considering device compliance, location, risk, and session duration. Australian businesses should also align the design with the Privacy Act and internal controls influenced by the Essential Eight, particularly around patching, privileged access, and application control.

Avoid assuming that every regional user has the same network quality. NBN performance, household Wi-Fi, mobile broadband, and evening congestion can affect the Blast Extreme experience. Monitoring packet loss, round-trip latency, and protocol performance is more useful than simply measuring whether the user can log in.

Validate The End-User Experience

Test the complete workflow from an unmanaged external device, a corporate laptop, and a representative mobile connection. Confirm DNS resolution, authentication, MFA, entitlement, desktop launch, reconnect behaviour, clipboard rules, printing, audio, USB redirection, and session timeout policies. Test both Horizon Client and HTML Access if browser-based access is part of the service.

Profile and application delivery can have a greater effect on satisfaction than the broker itself. Folder redirection, roaming profiles, DEM policies, FSLogix components where supported, and redirected folders should be measured under realistic conditions. A desktop that launches quickly but takes several minutes to open Outlook or Teams will still be judged as slow.

Keep operational knowledge close to the platform. The VMware series can provide useful background for administrators connecting Horizon work with broader VMware infrastructure, automation, and virtualisation practices. Document common faults such as black screens, certificate errors, agent unavailability, stuck logins, and disconnected sessions with clear escalation paths.

Operate And Improve The Service

Monitoring should cover Connection Server health, UAG status, broker events, vCenter alarms, datastore latency, pool capacity, agent state, login duration, and protocol performance. Retain enough logs to investigate authentication failures and suspicious access while respecting retention policies and privacy requirements.

Patch Horizon components in a controlled order and maintain a tested rollback plan. Keep a small validation pool for agent and image changes before broad release. Schedule disruptive work around Australian business hours, remembering that a maintenance window stated in AEST may affect Perth, Darwin, and international teams differently.

Practical Deployment Recommendations

Access model Best suited to Main strengths Key watchpoints
On-premises Horizon Organisations with existing vSphere and data centre operations Direct control of identity, storage, and network design Capacity planning, hardware lifecycle, and site resilience
Hybrid Horizon Businesses with mixed workloads or multiple offices Flexible placement and staged modernisation More complex routing, support boundaries, and licensing
Hosted or cloud-connected Horizon Teams seeking elastic capacity or reduced infrastructure ownership Faster expansion and access to managed services Provider dependency, data sovereignty, and recurring costs

Remote desktop access is most reliable when treated as an end-to-end service rather than a single VMware product. Define the user journeys, secure the access edge, standardise desktop images, and measure real performance across Australian locations. With those foundations in place, Horizon can provide a consistent workspace for staff in the office, at home, or travelling between sites.

Review the design against your environment, test the failure paths before production, and document the operating model so the next administrator can support it with confidence.