What internet connection is needed for hosted desktop services?

The right internet connection for hosted desktop services is determined by the number of simultaneous users, the applications they run and the quality of the connection at each location, rather than by download speed alone. A connection should provide enough capacity for normal hosted desktop traffic while other business activity continues, with predictable performance during busy periods.

Assess the connection against the way the hosted desktop will be used. Basic office applications and text-based work generally place less demand on a connection than video conferencing, voice calls, rich web applications, high-resolution graphics or frequent printing. Users working with large files, specialist software or multiple displays may also create different requirements from users performing routine administration. The assessment should therefore consider:

• the number of users connected at the same time;
• the busiest expected period, rather than the quietest part of the day;
• voice and video traffic running alongside the hosted desktop;
• cloud synchronisation, backups and other internet usage at the same site;
• printing, scanning, audio, video and peripheral redirection; and
• whether staff use one display or several, and whether applications generate frequent screen changes.

A provider should measure the connection at the premises where people will use the service. The advertised package speed is only one part of the assessment. Actual results can be affected by contention, network congestion, wireless coverage, internal cabling, router configuration and the amount of traffic generated by other devices. Testing at different times and under normal working conditions gives a more useful indication than a single speed test.

Latency, jitter and packet loss need separate attention. Latency affects how quickly activity is reflected in the hosted session. Jitter causes that delay to vary, while packet loss can lead to retransmissions, visual disruption or a session that becomes difficult to use. A connection with a high headline speed may still provide a poor user experience if these characteristics fluctuate. Monitoring should record consistency as well as peak performance.

The local network is part of the connection. Where practical, fixed-wired connections are preferable for desktop workstations because they avoid some of the interference and coverage problems associated with Wi-Fi. If Wi-Fi is necessary, access point placement, capacity, channel configuration and separation from non-business devices should be reviewed. Switching equipment, cabling and the site router should also be capable of handling the combined traffic generated by users and other services.

Capacity should include headroom for ordinary business activity. Running the hosted desktop at the exact limit of a connection leaves little room for meetings, software updates, web use or temporary increases in demand. Traffic prioritisation may help protect interactive hosted desktop, voice or video traffic from being overwhelmed by less time-sensitive transfers, but it does not replace a connection with adequate capacity.

Resilience is another design consideration. A second connection, potentially using a different access method or network route, can provide an alternative when the primary service is unavailable. Its suitability depends on the number of users, the applications in use and how the hosted desktop platform handles interrupted sessions. Failover should be tested rather than assumed, including the behaviour of active sessions, authentication and locally connected equipment.

Security controls must not be weakened to make connectivity easier. The router and firewall should be kept maintained, unnecessary inbound access should be avoided, and remote access should use the security controls required by the hosted desktop platform. Authentication, device access and network permissions should be reviewed alongside the connection design. A faster connection does not make an exposed or poorly configured network secure.

For a new deployment, the practical process is to document users and workloads, measure the existing connection, test representative hosted desktop sessions, review concurrent traffic and confirm the result during busy periods. Testing should include the locations from which staff actually connect, including branch offices and home working arrangements where they form part of the service. The findings can then be used to choose an appropriate primary connection, local network design and, where justified, a separate failover option.

S2 Technology Group can help businesses assess connectivity as part of a wider hosted desktop and managed IT strategy, considering the relationship between the internet service, office network, security controls and users’ applications.