- This topic is empty.
29. September 2008 at 15:31 #1491
Where do I start… We were using 8 Server 2003 32 bit terminal servers several months ago with 30 or so Wyse S10’s and everything was working flawlessly. We then decided to migrate the servers to 2008 64 bit (2 reasons, needed to utilize more ram and wanted to be able to publish programs via the terminal web). We quickly found out that the S10’s are not compatilbe with the way the licensing works with 2008 and so we contacted Wyse and began testing this with them. They actually told us we were the first ones to contact them about this! We tried several fixes and firmwares with Wyse with no luck. We didn’t have time to test anymore so we just replaced all the S10’s with S30’s and we are back up and running. Now after several months I have 30 S10’s sitting here and wouldn’t mind getting them to work again.
Before I spend a bunch of time and money getting maintenance on our dusty S10’s I was hoping that this new firmware was the key or someone has a work around.
When we connect to the TS’s we get this:
RDP: Out Of License
That’s it, nothing else29. September 2008 at 21:32 #14026DpizzleMember
- Total Post: 19
- Regular Joe
I just tried to connect to our 2k8 terminal server from one of our S10 clients and it worked fine. What kind of licensing are you using on your terminal servers? Per-User or Per-Device?30. September 2008 at 14:31 #14031
It is set to per device. We did switch it once to per user and had some luck, I guess that’s the answer. But when we did do that we had a huge issue for those that don’t use S10’s. They would get licensing errors. I was just told that it takes days for the licenses to be released, that they can only be manually released like 30 at a time. We may start experimenting with this, but I wish there was a better solution. Like a way to load the latest Remote Desktop client on the S10’s.30. September 2008 at 15:46 #14032ConfGenKeymaster
- Total Post: 11009
- Jedi Master
Are you using NLA? You have to disable it if you are using it.
Is your License Server activated?
CG30. September 2008 at 15:54 #14033
By an NLA, do you mean an NLB? If so yes, we just started to use a Barracuda NLB 340. The Barracuda engineers have been using as a beta site and this past weekend we finally got it working.
We are using a 2008 DC as the License Server and it is active and handing out licenses.30. September 2008 at 15:58 #14034DpizzleMember
- Total Post: 19
- Regular Joe
NLA is network level authentication. It is a new 2k8 thing for TS. you have to have this disabled for the S10s or V10s for that matter to connect to a 2k8 terminal server happily.
I’m pretty sure that the issue you were running into was due to the per-device licenses.30. September 2008 at 17:15 #14036
I found where NLA is configured in the RDP-Tcp Properties on the terminal servers and the domain controller, and it is not checked on any of them.
Security is set to Negotiate and Encryption is set to Client Compatible. I think all the rest of the RDP properties should be compatible.
If it is just a matter of license type and there is no software/firmware work-around, I may try and convince our server manager to change the license type over a long weekend, like Thanksgiving or something.
- You must be logged in to reply to this topic.