<div>
<div class="content wysiwyg-content">
This is regarding Terminal Server / RDP on Windows Server 2003 64 bit Standard edition. Activated and ran Terminal Server without installing license for about 95 days in the available 120 grace days. All the WYSE clients could see the server without any problems.<br />
<br />
The moment we added the license (TS CAL PER DEVICE) some WYSE S10 STOPPED working while the rest of them are working fine. Even the Windows Login screen would not appear in the ones which are not working, although they were RDPing before the licensing took place.<br />
<br />
We also looked for the differences in any settings between the ones which are working and the others which are not. All the settings were same. But found one difference. The model S10 is same but versions are different. Version 6.4.0_06 S10s are not working while versions 6.5.0_22; 6.5.0_40; 6.1.0_08; 6.2.0_08 are okay. We could not find a procedure to upgrade / change the version.<br />
<br />
If we connect in &quot;Console Mode&quot; using Administrator login, even 6.4.0_06 are able to connect.<br />
<br />
Remember everything was working FINE and WITHOUT ISSUES until we activated the licensing for the terminal server. If it worked before the TS licensing was activated, it should continue to work after?
</div>
</div>


This is regarding Terminal Server / RDP on Windows Server 2003 64 bit Standard edition. Activated and ran Terminal Server without installing license for about 95 days in the available 120 grace days. All the WYSE clients could see the server without any problems.

The moment we added the license (TS CAL PER DEVICE) some WYSE S10 STOPPED working while the rest of them are working fine. Even the Windows Login screen would not appear in the ones which are not working, although they were RDPing before the licensing took place.

We also looked for the differences in any settings between the ones which are working and the others which are not. All the settings were same. But found one difference. The model S10 is same but versions are different. Version 6.4.0_06 S10s are not working while versions 6.5.0_22; 6.5.0_40; 6.1.0_08; 6.2.0_08 are okay. We could not find a procedure to upgrade / change the version.

If we connect in "Console Mode" using Administrator login, even 6.4.0_06 are able to connect.

Remember everything was working FINE and WITHOUT ISSUES until we activated the licensing for the terminal server. If it worked before the TS licensing was activated, it should continue to work after?

Wyse S10 not working after installing TS Cals on Windows Server 2003

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Remote access may refer to the connection to a data-processing system from a remote location, for example through a virtual private network remote desktop software, terminal emulation, or the activation of features of a business telephone system from outside the business's premises.

Remote Access

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.