Windows Server

Remote Desktop Services (RDS)

RDS remains the practical way to deliver a Windows application to many users from one place, especially line-of-business software that was never web-enabled. A good farm is invisible; a bad one is slow, prints badly and gets hacked through an exposed RDP port.

We design RDS with a gateway and MFA in front, FSLogix profiles, session host images built from a template and monitoring on session health.

At a glance

RolesSession Host, Connection Broker, Gateway, Web Access, Licensing
LicensingRDS CALs per user or device, plus Windows Server
ProfilesFSLogix profile containers, UPD (legacy)
SecurityRD Gateway with MFA, no direct 3389, NLA, lockout policies

What RackLedge does

How we work

Windows Server work follows the roles, not the boxes. Domain controllers, file servers, application servers, RDS and SQL each have their own migration path, and we plan them separately so one cutover does not take everything down. New servers are built from a hardened template with patching, monitoring and backup agents from day one.

Every version has a support date and we track them for you: what is in mainstream support, what is extended, what needs Extended Security Updates and what must move now. Licensing is reviewed at the same time so a refresh does not turn into an audit problem.

Hyper-V, Active Directory, RDS, Exchange and SQL Server are supported as first-class roles, with hardening baselines and documentation handed over at the end of every project.

Related services

More on windows server

Frequently asked questions

RDS or Azure Virtual Desktop?

AVD if users are mostly remote and you want Microsoft to host the infrastructure. RDS if the application and data stay on-prem.

Need a hand with this?

Tell us what you are running and what is slowing you down. You get a straight assessment and a plan, with no obligation. Support desk is staffed 24/7.

Get in touch