ThinPro HP Thin Client Connecting to Terminal Services Server Problems

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?
itadminnekAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Cláudio RodriguesConnect With a Mentor Founder and CEOCommented:
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
 
Cláudio RodriguesFounder and CEOCommented:
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
 
itadminnekAuthor Commented:
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
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Cláudio RodriguesFounder and CEOCommented:
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
 
itadminnekAuthor Commented:
We have 2008 R2? Where would I reactivate the license?
0
 
itadminnekAuthor Commented:
Check out the picture...does this help?
Doc1.doc
0
 
itadminnekAuthor Commented:
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
 
itadminnekAuthor Commented:
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
 
itadminnekAuthor Commented:
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
 
Cláudio RodriguesFounder and CEOCommented:
Is the licensing server Windows Server 2008 or 2008 R2?

Cláudio Rodrigues
Microsoft MVP - RDS
Citrix CTP
0
 
itadminnekAuthor Commented:
2008 R2
0
 
Cláudio RodriguesFounder and CEOCommented:
All explained here:
http://www.shogan.co.uk/?p=404

Cláudio Rodrigues
Microsoft MVP - RDS
Citrix CTP
0
 
Cláudio RodriguesFounder and CEOCommented:
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
 
itadminnekAuthor Commented:
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
 
itadminnekAuthor Commented:
Any thoughts on the above question?
0
 
Cláudio RodriguesFounder and CEOCommented:
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
 
itadminnekAuthor Commented:
Okay makes sense...thanks for all the help!
0
All Courses

From novice to tech pro — start learning today.