HI,
I have successfully connected OTC clients on 0.4.5 to Windows 2003 terminal
servers using Windows 2003 license servers. I am trying to transition
everything to Windows 2008 but have run into a problem. I'm am
not getting any errors from either the OTC side or the Windows side so I'm
not sure where to investigate.
I run my OTC clients in kiosk mode and automatically RDP to a Windows
terminal server.
I have a virtual Windows 2008 terminal server (VMware esxi) that is also
the terminal license server. I have Windows 2008 device CALs. The same
server is also my OTC server. I am using OTC 1.0. Connecting to my
physical Windows 2003 terminal servers is not a problem. (Because of
unrelated problems, the windows 2003 terminal servers are in user mode
rather than device mode. However, with OTC 0.4.5, I had no licensing
problems when the terminal servers were in per device mode.)
When I was testing and the Windows 2008 terminal server was in the
licensing grace period, I had no problem connecting to the terminal server.
Now with my licensing set to per device, I can log in an OTC terminal once.
I get a temporary terminal server license. At the second login, the
temporary license should be converted to a permanent license. However, the
licensing is apparently refused and the terminal server closes the RDP
connection. I can find no errors in either the OTC client log nor the
Windows 2008 server logs.
As a test I changed the windows 2008 terminal server from per device to per
user and I had no problems logging in. The Windows server recorded several
errors/warnings in its logs that stem from CAl type mismatch but things
seemed to work.
I'd like to figure out why Windows 2008 licensing doesn't seem to like OTC.
Any suggestions?
Thanks,
--
Gary Horneman
Technology Director
Rosary High School
630 896-0831 x27
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
The Open Source Thin Client Solution http://openthinclient.org
openthinclient-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openthinclient-user
