"If the Multi-User kernel panics, we’re toast," Elias whispered. NT 4.0 wasn't originally built for multiple people to inhabit the same memory space. One bad application could crash the entire "Hydra" for everyone.

The relationship between Microsoft and Citrix during the development of WTS was highly cooperative but competitive. When Microsoft released Terminal Server, it offered basic multi-user functionality. However, organizations requiring advanced features—such as seamless window publishing, advanced client-side drive mapping, and extensive load balancing—continued to purchase Citrix add-ons.

Windows NT 4.0 Terminal Server Edition was a courageous — if imperfect — first step. It proved that Windows applications could be delivered centrally, opening the door to the cloud and remote work models we take for granted today. For IT professionals managing aging PCs in the late 1990s, TSE was a lifeline. Today, it’s a fascinating historical snapshot of the transition from the PC-centric 1990s to the server-hosted, anywhere-access philosophy of the modern enterprise.

Unlike standard NT Server, which was meant for file and print sharing, "Hydra" was built to host multiple simultaneous graphical user sessions on a single machine. Minimum Requirements Recommended Intel 486 at 33 MHz Pentium or Pentium Pro 16 MB (+ 8 MB per client) 32 MB or higher 128 MB free space 256 MB or higher Key Architectural Notes: Windows NT Terminal Server 4.0 - Jake Auralight's Blog

While Microsoft developed the Remote Desktop Protocol (RDP) for TSE, Citrix continued to offer its more advanced ICA protocol through its MetaFrame add-on, which provided better performance over low-bandwidth connections. Technical Architecture and Key Features