Terminal Server & RDP Thin Client Conection Issues
I loaded a new install Windows 2008 R2 32 bit server. Activated and ran Terminal Server without installing license for 120 days.
It worked for 120 days. All of my WYSE clients could see the server. No issues there.
The minute I added the license (TS CAL PER USER) and I have enough TS Cals for every user, every WYSE box STOPPED working, as did 1 machine (XP) running Service Pack 2. None of them could RDP into the same server there were RDPing before the licensing took place.
I have the server set to use the lowest level security for the RDP connection (just as it was before license installed), and it worked fine.
I installed Service Pack 3 on the legacy XP machine, and it worked like a charm. However the WYSE machines still don't work.
Remember everything was working FINE and WITHOUT ISSUES until I activated the licensing for the terminal server. Unfortunately, my client cannot go out and replace 12 WYSE boxes at this time.
If it worked before the TS licensing was activated, it should continue to work after?
Thanks You
Jeremy Baxter
It worked for 120 days. All of my WYSE clients could see the server. No issues there.
The minute I added the license (TS CAL PER USER) and I have enough TS Cals for every user, every WYSE box STOPPED working, as did 1 machine (XP) running Service Pack 2. None of them could RDP into the same server there were RDPing before the licensing took place.
I have the server set to use the lowest level security for the RDP connection (just as it was before license installed), and it worked fine.
I installed Service Pack 3 on the legacy XP machine, and it worked like a charm. However the WYSE machines still don't work.
Remember everything was working FINE and WITHOUT ISSUES until I activated the licensing for the terminal server. Unfortunately, my client cannot go out and replace 12 WYSE boxes at this time.
If it worked before the TS licensing was activated, it should continue to work after?
Thanks You
Jeremy Baxter
kiwistag
Try deleting/revoking all the temporary issued licences/allocations in RD Licensing Manager and see if that helps.
Are you sure you installed the right licensing for your selected licensing model? When you setup the RDS server you had to select per user or per device. You want to make sure your license matches what you installed.
ASKER
Correct. The license said user. So we installed the User License.
Are there any errors in the event log that would indicate why the license model is having a problem ?
ASKER
Thanks for your reply. I will test these today and get back with all of you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi WorldTechMS (Jeremy Baxter),
We are also facing exactly the same issue that you faced last year. We are using Windows Server 2003. Our Wyse S10 worked very fine during the 120 days period but once we installed the "PER DEVICE" TSCALS, some of the devices stopped working. After going in further details, we found that S10 machines with version 6.4.0_06 are not working and S10s with version 6.5.0_22 have no problems.
Can you please share as to what exactly you did that your S10s started working?
Thanking you in advance for your help.
PS: We tried to look for steps to updgrade the firmware but could not find the final solution for the same.
We are also facing exactly the same issue that you faced last year. We are using Windows Server 2003. Our Wyse S10 worked very fine during the 120 days period but once we installed the "PER DEVICE" TSCALS, some of the devices stopped working. After going in further details, we found that S10 machines with version 6.4.0_06 are not working and S10s with version 6.5.0_22 have no problems.
Can you please share as to what exactly you did that your S10s started working?
Thanking you in advance for your help.
PS: We tried to look for steps to updgrade the firmware but could not find the final solution for the same.
ASKER
OK, here is the solutions. We had to get Microsoft involved. The TS server was a VM after rebuilding it several times about the 3rd or 4th time it worked and accepted the license and we were able to connect via thin client using RDP. Microsoft is "looking" into why this did not work the first 2 or 3 times.
Hi WorldTechMS,
Many thanks for your reply. The problem at our end also stands resolved. We contacted Wyse. They provided us with an upgrade to the firmware. After we did that, the problem was resolved.
Many thanks for your reply. The problem at our end also stands resolved. We contacted Wyse. They provided us with an upgrade to the firmware. After we did that, the problem was resolved.
ASKER
We Contacted Microsoft and they were able to walk us through the solutions.