RDS Device CAL not issue when using Raspberry PI
RDS Device CAL not issue when using Raspberry PI
Hi Aka,
I experiencing issue with the RDS Device licensing issue when using Raspberry Pi 3 with WTware.
In short if I use a windows machine the Device license is able to registered to the license server but not with WTware on Raspberry Pi 3.
Appreciate if you have can take a look on this.
Thanks,
VinCny
I experiencing issue with the RDS Device licensing issue when using Raspberry Pi 3 with WTware.
In short if I use a windows machine the Device license is able to registered to the license server but not with WTware on Raspberry Pi 3.
Appreciate if you have can take a look on this.
Thanks,
VinCny
Re: RDS Device CAL not issue when using Raspberry PI
Shortly speaking, I don't know. I can look on this if you send me everything you know about it. Screenshots, docs...
Re: RDS Device CAL not issue when using Raspberry PI
Hi Akatik,
Thank you for responding, below is the detail on the setup.
We are running on Windows 2012 R2 Remote Desktop Service Host (RDSH), with 2016 Remote Desktop Licensing Server.
If we run a windows 7 or windows 10 machine and do a remote desktop tot he same server the client device license is registered to the license server. Example in Picture 0.
Picture 1 shown that the Windows 2012 R2 is able to detect the 2016 Remote Desktop Licensing Server with available licenses but not issue the license to the Raspberry client.
Attached WTware.txt is the log file when the WTware Raspberry connected to Windows 2012 R2 RDSH.
Note: I have use the latest version and the result is the same.
So far the program work great, hopefully the license issue can be resolve.
Appreciate if you can help check it out.
Thanks,
Ken
Thank you for responding, below is the detail on the setup.
We are running on Windows 2012 R2 Remote Desktop Service Host (RDSH), with 2016 Remote Desktop Licensing Server.
If we run a windows 7 or windows 10 machine and do a remote desktop tot he same server the client device license is registered to the license server. Example in Picture 0.
Picture 1 shown that the Windows 2012 R2 is able to detect the 2016 Remote Desktop Licensing Server with available licenses but not issue the license to the Raspberry client.
Attached WTware.txt is the log file when the WTware Raspberry connected to Windows 2012 R2 RDSH.
Note: I have use the latest version and the result is the same.
So far the program work great, hopefully the license issue can be resolve.
Appreciate if you can help check it out.
Thanks,
Ken
- Attachments
-
- Picture 1.png (97.07 KiB) Viewed 89554 times
-
- Picture 0.png (31.12 KiB) Viewed 89554 times
Re: RDS Device CAL not issue when using Raspberry PI
I still do not understand the problem. WTware connects to server and does not claim about licensing server error. What else do you need?
Re: RDS Device CAL not issue when using Raspberry PI
Hi Akatik,
Well if it doesn't issue license to the session. The session is unlicensed and will seize operation after the trail period about 120 days.
Thanks,
Ken
Well if it doesn't issue license to the session. The session is unlicensed and will seize operation after the trail period about 120 days.
Thanks,
Ken
Re: RDS Device CAL not issue when using Raspberry PI
Try to change date on both servers (terminal and licensing).Will it seize?
Microsoft licensing is a magic. Many years ago wtware always worked with temporary licenses, not permanent. In 2012R2, I see working licensing - in "PER Device" mode license bound to hostname we specify in clienthostname= option (so user can issue licenses for every wtware device, or specify same clienthostname= for all, and all devices work with single license). Seems something changed in 2016 again...
Microsoft licensing is a magic. Many years ago wtware always worked with temporary licenses, not permanent. In 2012R2, I see working licensing - in "PER Device" mode license bound to hostname we specify in clienthostname= option (so user can issue licenses for every wtware device, or specify same clienthostname= for all, and all devices work with single license). Seems something changed in 2016 again...
Re: RDS Device CAL not issue when using Raspberry PI
Hi Akatik,
Thank you for sharing, as it was already in production I can't change the setting.
Anyway, I will try to setup a test environment or wait till 120 days.
Thanks you again for your kind support.
Thanks,
Ken
Thank you for sharing, as it was already in production I can't change the setting.
Anyway, I will try to setup a test environment or wait till 120 days.
Thanks you again for your kind support.
Thanks,
Ken
Re: RDS Device CAL not issue when using Raspberry PI
Hi there! Having the same issue I'm very interested in the outcome.
-
- Posts: 1
- Joined: Wed Jan 10, 2024 5:14 pm
Re: RDS Device CAL not issue when using Raspberry PI
Hey,
I'm also having the same problem. Did anyone find the issue?
Thanks
Philip
I'm also having the same problem. Did anyone find the issue?
Thanks
Philip
Re: RDS Device CAL not issue when using Raspberry PI
I see the same problem was resolved by removing and reinstalling license service on server.
mstsc.exe gets licenses but neither wtware nor freerdp (i.e. any linux clients) does.
Also, I was unable to revoke license issued to wtware on this server. "Revoke license" popup menu was gray.
After reinstalling licensing server and licenses packs, everything (wtware, other linux clients, revoke license) works.
mstsc.exe gets licenses but neither wtware nor freerdp (i.e. any linux clients) does.
Also, I was unable to revoke license issued to wtware on this server. "Revoke license" popup menu was gray.
After reinstalling licensing server and licenses packs, everything (wtware, other linux clients, revoke license) works.