Solved

ThinPro HP Thin Client Connecting to Terminal Services Server Problems

Posted on 2012-03-22
17
2,692 Views
Last Modified: 2012-03-27
I am trying to connect my HP Thin Client using ThinPro to a Windows 2008 Server running Terminal Services. Off a fresh install of ThinPro, I setup the connection and it works fine the first time if I disconnect and try to reconnect again it doesn't work. I don't get any error messages...it just doesn't connect. I tired looking at the server but I don't think that's the problem because if I reinstall ThinPro on the thin client, it works again, but only for one time again. I feel the problem lies somewhere in the thin client.

Any ideas?
0
Comment
Question by:itadminnek
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 10
  • 7
17 Comments
 
LVL 31

Expert Comment

by:Cláudio Rodrigues
ID: 37766705
Did you check the RDS Server event log? Could be a licensing issue. As you are aware of, Terminal Services (RDS) requires RDS licensing to be available, activated and depending on the licensing mode you choose (per user or per device), to have available licenses.
Is your Terminal Server set to per device or per user?

Cláudio Rodrigues
Microsoft MVP - RDS
Citrix CTP
0
 

Author Comment

by:itadminnek
ID: 37767195
Thanks for the post! I have per device setup on our server with 5 Per Device CALs installed.

I am getting the following errors in the TS Server event log:

One or more of the TS Licensing certificates on the Terminal Services license server "server01" are corrupted. Therefore, the Terminal Services license server will only issue temporary licenses until it is reactivated.

The Terminal Services license server "server01" does not have any Terminal Services client access licenses (TS CALs) installed and registered with the Microsoft Clearinghouse for product "Windows Server® 2008 - Terminal Server Per Device CAL Token". Therefore, the Terminal Services license server cannot issue TS CALs of the type "Windows Server® 2008 - Terminal Server Per Device CAL Token" to the terminal server "server01". To resolve this problem, install additional TS CALs as required.

Any ideas?

Note: I have Terminal Services...not Remote Desktop Services. I don't know if there is a difference. If there is, could you please explain what the difference is? Thanks!
0
 
LVL 31

Expert Comment

by:Cláudio Rodrigues
ID: 37767214
Is your server 2008 or 2008 R2?
Remote Desktop Services is just the new name for Terminal Services (it is not called TS anymore).
Go to the licensing server and reactivate it. There is an option right there to do it.
That should fix your problem.

Cláudio Rodrigues
Microsoft MVP - RDS
Citrix CTP
0
Get 15 Days FREE Full-Featured Trial

Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users

 

Author Comment

by:itadminnek
ID: 37767336
We have 2008 R2? Where would I reactivate the license?
0
 

Author Comment

by:itadminnek
ID: 37767370
Check out the picture...does this help?
Doc1.doc
0
 

Author Comment

by:itadminnek
ID: 37767794
Any ideas on the above picture?

I also noticed that we installed Per Device CALs instead of Per User CALs. I have installed Per User CALs instead now but how would I uninstall the Per Device CALs?

Thanks for all your help!
0
 
LVL 31

Accepted Solution

by:
Cláudio Rodrigues earned 500 total points
ID: 37767945
Just right click the computer name NEKOOSA01 on that screenshot and choose 'Activate'. That will reactivate the box with the Microsoft Clearinghouse.
Also on the 2008 TS, is it set to Per User or Per Device? You need to launch the Remote Desktop Services Session Host Configuration tool on that server and check what it is set to.

Cláudio Rodrigues
Microsoft MVP - RDS
Citrix CTP
0
 

Author Comment

by:itadminnek
ID: 37768003
I deactivated and then activated the server again and I still get the same message.

I also found in the Terminal Services Configuration screen that the licensing mode was Per Device which I changed it to Per User and rebooted but still got the same error in the picture above.
0
 

Author Comment

by:itadminnek
ID: 37768334
Okay I figured it out...I had to change my TS Licensing Manager's Configuration Discovery Scope to Forest instead of Domain.

I still have a problem though...I also noticed that we installed Per Device CALs instead of Per User CALs. I have installed Per User CALs instead now but how would I uninstall the Per Device CALs?
0
 
LVL 31

Expert Comment

by:Cláudio Rodrigues
ID: 37768411
Is the licensing server Windows Server 2008 or 2008 R2?

Cláudio Rodrigues
Microsoft MVP - RDS
Citrix CTP
0
 

Author Comment

by:itadminnek
ID: 37768420
2008 R2
0
 
LVL 31

Expert Comment

by:Cláudio Rodrigues
ID: 37768449
All explained here:
http://www.shogan.co.uk/?p=404

Cláudio Rodrigues
Microsoft MVP - RDS
Citrix CTP
0
 
LVL 31

Expert Comment

by:Cláudio Rodrigues
ID: 37768451
By the way you do not need to use the Telephone method. The internet one works as well.

Cláudio Rodrigues
Microsoft MVP - RDS
Citrix CTP
0
 

Author Comment

by:itadminnek
ID: 37768533
Sweet got it! One more question.

We have 8 thin clients that we are connecting to this terminal server. Now on all 8 thin clients, we want to sign in with one user called Production. How do the CALs work with this? Would we just need 1 Per User CAL? Or 8 Per Device CALs? Which would be the best legal route to go?
0
 

Author Comment

by:itadminnek
ID: 37772692
Any thoughts on the above question?
0
 
LVL 31

Expert Comment

by:Cláudio Rodrigues
ID: 37772764
Does not matter you are sharing the username. You need either:
- As many RDS User CALS as there will be users using these 8 thin clients.
- As many RDS Device CALS as there are thin clients (eight in this case).
Which one makes more sense depends on how many users will share these thin clients. If you are in a factory with let's say 24 people sharing these 8 devices in three shifts, it makes more sense financially to get 8 Per Device RDS CALs instead of 24 Per User RDS CALs.

Cláudio Rodrigues
Microsoft MVP - RDS
Citrix CTP
0
 

Author Comment

by:itadminnek
ID: 37772777
Okay makes sense...thanks for all the help!
0

Featured Post

Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article, I'll explain how to setup a Plex Media Server (https://plex.tv/) on a Redhat (Centos) 7 based NAS with screenshots to help those looking for assistance.  What is Plex? If you aren't familiar with Plex, it’s a DLNA media serv…
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Suggested Courses

628 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question