Forum Replies Created
-
Posts
-
Are there any USB devices plugged into the thin clients that are hanging? We’ve had a similar problem where if a user had one of the newer Blackberries plugged into it at boot time, the device would hang at the bios screen. This was resolved by upgrading to the newest 1.19 bios revision for the V10L
There is no way to prevent the taskbar from spanning across both screens even with MDS running using RDP, or at least I’ve not found a way of doing this.
The taskbar option on the device itself only controls the taskbar on the device desktop and does not translate into the session itself.
I don’t think it is a Wyse issue. Check your Citrix Access Management Console. Under the Farm Settings, in the ICA – Display section, you should have a “Maximum memory” item. It is most likely set to a value that is too low to support that display configuration. Set it to 8192 kb, which is the maximum you can have and log in from the thin client. It should work properly now.
Thanks for the response. Turned out that it wasn’t a certificate issue after all. The firmware that we were about to deploy has a bug in it where the logon would fail trying to authenticate into a load balanced PNAgent url secured using ssl/https with a verisign certificate.
Thanks for your help
But how would I be able to tell which CA each of those certificates is valid for?
Thanks
That shouldn’t be happening. If seamless published applications are launched directly on the V10L they should have monitor awareness regardless whether or not you have MHA/MDS installed and enabled on the server. I did have an issue with a very early 5.2.x release of the firmware where monitor awareness was completely broken, but that was resolved in subsequent releases. This issue also occured if you are running your published apps from Presentation Server 4.5 R01 with a firmware revision earlier than 6.0.0_21.
What firmware revision does your V10L unit have? What version of Presentation Server are you launching your apps from?
As for messages and dialog boxes coming up in the middle of two screens, I’ve not been able to resolve this issue completely with published apps.
Thanks for the quick reply!. I am still waiting for an official statement from my Wyse SE regarding this, but this helps a lot.
One other PNLite advantage that I just found is that if your AD account is locked out, you will actually get an error message telling you that it’s locked out as opposed to just a beep at the logon screen.
I played with it a little while back and hated it. I didn’t explicitly test the .ini compatibility stuff. I just tested it as a direct competitor to the WTOS devices. The issues that I had with the device were:
1.Took much longer than a S10/V10L to boot
2. HP’s .ini files are not documented
3. HP didn’t support direct editing of their .ini files, so in order to make any config changes, you had to have a 5135 on site wherever you are.
4. Didn’t support mixed RDP and ICA PNAgent connections
5. Confusing user interface.The above may have changed since I looked at the device, but this is what I remember some of my issues were.
I didn’t do any WDM vs Altiris testing since I don’t use either one.
Hmm. That’s weird. I’ve been running my devices with the include=$mac.ini for at least a year and my included files do have the .ini extension on them and I’ve not had a single issue. My wyse support guys have never corrected me on this.
Not saying that is correct or anything, I am thinking that it’s more like the include parameter just takes whatever you give it and resolves the variable if it can. IE. if I put include=$mac.blah, my files would have to be named with the .blah extension and as long as the files are in the /inc folder, they would be properly parsed.
I’ve been using this one for a while. I use it when I need to setting to “stick” to a specific device without affecting other users and devices on the ftp server. For example, if I want to configure a locally attached printer for a device that is always available regardless of whom is logging into it. I’ve also used this to set display settings.
in the wnos.ini I just add include=$mac.ini
in your wysewnos directory create a folder “inc”
place your $mac.ini files within that folder, the device matching the mac address will pick up that file automatically at boot, in the device event log you should be able to see it using the new .ini file.This should work in any version higher than 5.2.0_46. Might work with earlier 5.2.0 releases, but can’t be sure of this one.
What drives me nuts is that Wyse won’t officially support this functionality.
Hope this helps
..
