We help IT Professionals succeed at work.

Remote Desktop not working

aclaus225
aclaus225 asked
on
483 Views
Last Modified: 2018-02-06
I am not able to login to my remote desktop server remotely.  The error that I am getting when trying to login is that there are no Remote Desktop License Servers available.  

The server that I am logging into is a License Server, but when I go into tsconfig and specify the server, it agrees that it is a license server, but upon hitting okay I get: Unable to complete operation:-2147217396.  I have not been able to find that error through a search of Google.

Does anyone know how to fix this?
Comment
Watch Question

Author

Commented:
Screen capture
I went through this: https://technet.microsoft.com/en-us/library/cc775208(v=ws.10).aspx, following the recommendations for when a server could not be automatically configured and it looked fine.
CoralonSenior Citrix Engineer
CERTIFIED EXPERT

Commented:
When you check the licensing diagnostics, how many licenses do you have available?  And is your RDS server set for the correct type to match the licenses?  I have seen people with user licenses but the server configured for machine licenses.

Coralon
CERTIFIED EXPERT

Commented:
If you are logged into a different domain, read the middle paragraph of the image you posted; it is telling you what the problem is.

Author

Commented:
I have ten user CALs loaded and available on that server. I only have one domain additionally.
CERTIFIED EXPERT

Commented:
Your image says, "to issue RDS per user CALs to users in other domains, this license server must be a member of the Terminal Server License Servers group in those domains." meaning that, if YOUR PC is logged into a different domain, you will have to create a Terminal Server License Servers group in your domain that can use that server for licensing.
If your PC is not logging into a domain, it should not be a problem; but, if you are, its a big problem that will require special routing for the servers to talk to each other and the creation of the Terminal Server License Servers group with both domains included for it to work.
CoralonSenior Citrix Engineer
CERTIFIED EXPERT

Commented:
Can you post a screenshot of the licensing diagnosis screen from the administrative tools/server manager?

Coralon

Author

Commented:
I either am not in another domain (my home machine) or am in the same domain (other local machines that I am trying to connect from) every time. I will post a screen shot Monday. What is posted above is a screenshot from the licensing diagnosis though, isn't it?
CERTIFIED EXPERT

Commented:
There will be events listed (EVENTVWR.MSC) on both the server and your PC which should give better results than the error you posted in your question.
What O/S is running on your PC?
CoralonSenior Citrix Engineer
CERTIFIED EXPERT

Commented:
That's only a partial screenshot.. I want to see the whole thing if possible..

Coralon

Author

Commented:
Licensing Diagnosis
CoralonSenior Citrix Engineer
CERTIFIED EXPERT

Commented:
Ok.. 2 problems..

1. You need to activate the license server itself..  I would recommend installing the license server on another non-RDS machine (it is a very lightweight service that should have almost no impact on any production server).

2. It also looks like there are no RDS licenses installed.. If you activate the server it may fix this problem and the licenses were already installed, then it should just resolve itself. But, once it is activated, then the licenses can be installed.

Coralon

Author

Commented:
Licensing ManagerRD Licensing Manager is showing a green Check next to the server and that there are 10 User CALs available.
CoralonSenior Citrix Engineer
CERTIFIED EXPERT

Commented:
Is the main server itself activated?  Then second screenshot shows everything correct.. but the diagnoser is obviously complaining about activation.

Something else to check..
Make sure you have the SRV records for your licensing server in DNS..

And check the eventlogs on server REMOTE2 to see what errors you get in the Application log.

And since the server is its own licensing server (bad practice.. but I know it is necessary sometimes)..  That also makes me wonder -- if its is possible the server is pointing to a DNS server that doesn't have the SRV records?

Coralon

Author

Commented:
There are no SRV records in my DNS.  

I have moved the licensing service to another server and still get my same error originally, which will not let me update the license server that needs to be pointed to in tsconfig.
CoralonSenior Citrix Engineer
CERTIFIED EXPERT

Commented:
Whats in your TS Licensing key on the RDS host?

 HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing

Coralon

Author

Commented:
That actual key is Default.  The subkey for Hardware has a ClientHWID key and the subkey for Store is Default
CoralonSenior Citrix Engineer
CERTIFIED EXPERT

Commented:
Can you dump it out and paste the export here? (feel free to delete any binary values - those are the real keys)..

Coralon

Author

Commented:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing\HardwareID]
"ClientHWID"=hex:02,00,00,00,32,e8,b9,c4,71,dc,b6,ca,f2,a5,06,af,eb,73,ee,a7

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing\Store]
CoralonSenior Citrix Engineer
CERTIFIED EXPERT

Commented:
My apologies.. my brain was off in the wrong direction..
The key for the RDS licensing server to point to is HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services

You should see a LicensingServers value there..

Coralon

Author

Commented:
I do not see a LicensingServers value there.  

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services]

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client]
"fEnableUsbNoAckIsochWriteToDevice"=dword:00000050
"fEnableUsbBlockDeviceBySetupClass"=dword:00000001
"fEnableUsbSelectDeviceByInterface"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client\UsbBlockDeviceBySetupClasses]
"1000"="{3376f4ce-ff8d-40a2-a80f-bb4359d1415c}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client\UsbSelectDeviceByInterfaces]
"1000"="{6bdd1fc6-810f-11d0-bec7-08002be2092f}"
Senior Citrix Engineer
CERTIFIED EXPERT
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
Thank you for getting it to finally work.  When I logged in this morning it worked fine.  I am guessing setting a group policy for Terminal Services finally did it, but you pointed me in the right direction.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.