Standard Windows editions (like Windows 10 or 11 Pro) typically limit the number of simultaneous remote desktop sessions to one. This means only one user can log in remotely at a time; if a second user attempts to connect, the first is kicked off. To allow multiple concurrent users, organizations traditionally had to purchase Windows Server and expensive RDS CALs.
Historically, Thinstuff has favored perpetual licensing models (you buy it once, you own it forever for that major version). However, like many software vendors, they have moved toward maintenance models.
If you are searching for information on a , you are likely trying to either extend the life of old hardware, reduce Windows licensing costs, or unlock specific features for a remote desktop farm.
Because rdesktop is licensed under the , Thinstuff is legally required to make their source code available. This creates a fascinating duality in the Thinstuff license structure: thinstuff license
Before dissecting the license, it is essential to understand the software. Thinstuff is a premier provider of remote desktop solutions, best known for its flagship product, .
Thinstuff offers a free version of their software, but it comes with limitations.
is included with the installer for testing purposes, offering the same features as the full version. Key Review Perspectives Standard Windows editions (like Windows 10 or 11
Application/Client licencing for e.g. Thinstuff RDP : r/sysadmin
ThinStuff offers a free version, but it comes with significant restrictions. A free license allows you to connect to a remote server, but you lose:
This is the primary license for business use. When you purchase a , you are typically buying a perpetual license for the XP/VS Terminal Server software. Because rdesktop is licensed under the , Thinstuff
Once you have purchased your license key, activation requires a specific process. Unlike modern cloud apps, ThinStuff uses an offline hardware hash system.
If you inherited a ThinStuff environment and don’t know what licenses you own, run this audit immediately: