Forum Replies Created
-
Posts
-
It’s release firmware that was just finalized—I got it directly from support. Feel free to call them and reference TIR 45085 (the internal engineering case number that was created as a result of my case). You can find my simple wnos.ini at http://bink.slew.org/~daniel/pub/wnos.ini .
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.
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.
I’ve been working with Wyse for almost a month and a half on this and they are working on a fix. They are very slow at getting it done, but they do agree it’s a failure with their product. I’ll let you know more when I do, but if you call and complain loudly and move this up the chain, they might actually accelerate the fixing of their broken product.
This configuration doesn’t work for me. Without 2008 TS licensing it works fine—with 2008 TS DEVICE licensing, the WTOS devices refuse to connect. Which devices are you using and what firmware are you running?
I have no issue with this under 6.3.0_22 (though I have other issues with this firmware). If this truly is an issue with your newer firmware, you can ask Wyse to send you the fixed version or simply downgrade to your older known-good firmware. Since you are already leveraging a wnos.ini environment, changing firmware is very simple.
No comments from anyone? Is ANYONE successfully running ThinOS with Windows 2008 TS DEVICE CALs?
I can’t comment on the CD-ROM, but I am doing this with USB sticks without a hitch with V10Ls and Windows 2008. On the server you will need to have Drive and Supported Plug and Play Devices redirection enabled and you will need the following in your wnos.ini (I assume you know what this is):
SessionConfig=ALL MapDisks=yes
Good luck.
