Overview
We built and documented a centralized Remote Desktop Services environment where students sign in to a shared Windows desktop and applications securely from their own devices using domain credentials, without joining the domain.
What Runs On The Server
A single Windows Server 2022 box (RDS-SRV01, domain lab8.local) carries every role: the directory, DNS, the session host, and the web access portal.
Active Directory Domain Services
- Domain controller for
lab8.local: holds the user accounts and theRDS_Studentssecurity group that decides who is allowed a remote session.
DNS & Name Resolution
- DNS runs on the same server to resolve the domain. External client PCs reach the host through a
hosts-file entry that maps the server name to its LAN IP.
Remote Desktop Services
- Single-server session-based deployment (Quick Start): the RD Session Host serves a shared Windows desktop and published RemoteApps, brokered on the same box.
RD Web Access
- Browser portal over HTTPS: students sign in and launch
.rdpfiles for a full desktop or individual apps. Served with a self-signed certificate for the lab network.
Clients & Networking
- Physical Windows 11 PCs on a bridged LAN connect with
mstscusing domain credentials - without ever joining the domain.
What I Practiced
Active Directory & groups
Standing up a domain, creating users, and gating access with a security group.
Centralized desktop delivery
Configuring session-based RDS so one server serves desktops and apps to many clients.
Access & certificates
Group-based authorization, a self-signed TLS certificate, and client-side name resolution.
Deliverables & Assets
Scenario description, step-by-step documentation, presentation, and live demonstration.
Documentation
View the full RDS implementation documentation we co-wrote for the lab delivery.
Download Documentation (PDF)Presentation
View the slides we created together and presented during the graded demonstration.
Download Presentation (PDF)