Brian Madden Logo
Your independent source for application and desktop virtualization.
advertisement

Wyse ThinOS/V10L and Windows 2008 SP2, in the Terminal Services forum on BrianMadden.com

rated by 0 users
Answered (Verified) This post has 1 verified answer | 6 Replies | 3 Followers

Not Ranked
Points 115
Bink Sad [:(] posted on Tue, Jun 16 2009 9:18 PM

Is anyone here successfully using Wyse ThinOS thin clients and Windows 2008 TS DEVICE licensing?  I’m having issues where clients are only able to connect once to the Terminal Server and would love to hear back from those who have ThinOS-based thin clients, Windows 2008 Terminal Servers and are using TS device CALs.  Wyse has been unable to fix the issue.

Thanks.

Answered (Verified) Verified Answer

Not Ranked
Points 115
Answered (Verified) Bink replied on Wed, Jul 29 2009 12:57 PM
Verified by Bink

Wyse has just released updated firmware that appears to address all my open items with regard to this—and I have just deployed it to all my clients.  The firmware is version 6.4.0_12.

  • | Post Points: 40

All Replies

Not Ranked
Points 45
Eivind Bentsen replied on Wed, Jun 24 2009 4:29 AM

Have you tried using the "FixLicense=clean" parameter?

This will clear the TScal from the ThinClient.

you need to have implemented .ini (HPCP/.ini) administration on your thinclients.

  • | Post Points: 20
Not Ranked
Points 115
Bink replied on Wed, Jun 24 2009 8:34 AM

We have used ClearLicense=yes without success.  As a matter of fact, after the clients were issued a CAL, they all stopped connecting and the only way to get them to connect again was to put this in the ini file.  However, this is only a workaround as the clients can still only connect ONCE and this parameter is now required simply to make this one connection.  After this connection is made, subsequent connections do not work and the devices must be restarted to make a connection.

  • | Post Points: 20
Not Ranked
Points 45

ok, i Guess this all works fine on SP1 for W2k8? It seams to be working for me anyway.

Hope Wyse will issue a new FW for the ThinOS which fixes this.

I will post the solution if I get a FW from Wyse that fixes this, cool if you could do the same if you figure it out.

  • | Post Points: 20
Not Ranked
Points 115
Bink replied on Wed, Jun 24 2009 9:11 AM

I have not tried SP1.  Are you using a 2008 server to issue DEVICE CALs?  I have a CIR open with Wyse on this issue, but it’s a bit slow getting them to fix the problem.  Their latest firmware, 6.4.0_06, also has the issue, but I’ll report back if I have a resolution.

  • | Post Points: 5
Not Ranked
Points 115
Answered (Verified) Bink replied on Wed, Jul 29 2009 12:57 PM
Verified by Bink

Wyse has just released updated firmware that appears to address all my open items with regard to this—and I have just deployed it to all my clients.  The firmware is version 6.4.0_12.

  • | Post Points: 40
Not Ranked
Points 190

Just to note for people who are viewing this in the future.... 6.4.0_12 firmware update DOES NOT fix this problem with the TCAL per device licensing when connecting to Windows 2008 with PAgent running on XenApp...

Version 6.4.0_24 is the version that actually fixes it.  As well as a lot of other windows 2008 issues.

 

Cheers,

 

Andrew

 

Page 1 of 1 (7 items) | RSS