by vincny » Fri Jun 23, 2017 5:34 am
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
- Attachments
-
- Picture 1.png (97.07 KiB) Viewed 89573 times
-
- Picture 0.png (31.12 KiB) Viewed 89573 times
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