The "Terminal Server" environment, known in Windows 2000, has evolved over the years and is still a part of Windows Server 2022, albeit under a different name and with expanded functionalities. In modern Windows Server versions, including Windows Server 2022, this functionality is known as Remote Desktop Services (RDS).
Remote Desktop Services in Windows Server 2022 allows multiple users to connect to the server remotely and use the server's resources as if they were sitting in front of the server. This includes running applications, using network resources, or accessing files, all in their own sessions. The core idea remains the same as it was with Terminal Services, but RDS includes enhancements and new features such as:
- Remote Desktop Session Host (RDSH): Allows a server to host multiple, simultaneous client sessions.
- Remote Desktop Virtualization Host (RDVH): Integrates with Hyper-V to host virtual desktops.
- Remote Desktop Connection Broker (RDCB): Manages the connection requests from clients, including reconnection to existing sessions.
- Remote Desktop Gateway (RDG): Enables authorized users to connect to remote desktops, RemoteApp programs, and session-based desktops over the Internet.
- Remote Desktop Web Access (RDWA): Allows users to access RemoteApp and Desktop Connection through the Start Menu or a web browser.
- Remote Desktop Licensing (RDL): Manages the licenses for RDS.
This suite of features in RDS provides a much more comprehensive and flexible environment for remote work and application delivery than the older Terminal Services in Windows 2000, reflecting the advancements in technology and the increased need for secure, remote access solutions.
The Terminal Server environment uses very little of the local system resources. This allows the local user tremendous flexibility managing his/her applications. In many organizations, users need access to applications on their local computers, but would benefit from access to services provided on a Windows 2000 Server.
Users access Terminal Services by opening Terminal Services Client from the Program menu. When a user connects to the Terminal Server, the user environment on the client looks the same as the Windows 2000 Server and Windows 2000 Professional environment. The fact that the application is not running locally is transparent to the user.