Forum Replies Created
-
Posts
-
Our situation:
1. Gateway
2. Azure (redirect URL)
3. Login + MFA
4. FAS
5. Storefront
I dont get it 🙁 , does it work like this video shows in your setup? https://youtu.be/NjTWpeq4jRY?t=39
I have ThinOS 9.1.6108. , Citrix Workspace App package 21.12.0.18.3.
User Experience = Classic
Workspace Mode = on.
I assume when you put on the TC and he connects to the broker he gives the pop-up like in the video. But that’s not happening on our setup. He gives us the classic logon screen.
Thanks for the heads up. Still the same error.
What do you have in the “Login Experience” section of WMS?
WMS 3.5.2
Netscaler 13.0
ThinOS 9.1.3129
We’re unable to get SAML Azure MFA working. Within a browser session it works flawless, but when trying it via the Wyse we are getting the error: “No active policy is found in primary authentication cascade”
This error comes from the gateway, but the primary authentication policy (Saml) is configured and online.
We tried some suggestions like brian1020 said a few posts above “workspace mode” on and the broker URL set to the store etc..
So what are we doing wrong 😉
SMS Passcode’s latest version has ‘push to verify’ instead of code, does ThinOS support this or do we have to wait for new firmware?
We got it workin finally. On the netscaler under the session profile > published applications. We had the web interface address filled in with the whole storefrontURL including the store. When we entered only the Base URL the job was done.
SMS Passcode Version 10, on premise. (Entrust Datacard)
ThinOS supports sms passcode from Version 9.
Thanks for the reply.
We tried that yes, but did not work. Is that needed to get it working?
Cause you get the extra field with login, and we prefer the pop-up to enter the Passcode instead.
Did you resolve this? 😉
We have the same issue. We got it working internally except for ThinOS.
USB logging output:
09:30:13.395 SF: csg redirect to https://gdt2fa.gouda.lok/vpn/index.html
09:30:13.395 SF: use cgi/login to try
09:30:13.395 SF: csg path http://gdt2fa.gouda.lok/cgi/login
09:30:13.396 SF: csg method start
09:30:13.396 SF: [request] http://gdt2fa.gouda.lok/cgi/login, get 0
09:30:13.396 SF: [url] http://gdt2fa.gouda.lok
09:30:13.481 SF: http get code 200, len 1151
09:30:13.481 SF: csg need passcode
09:30:26.175 SF: [request] http://gdt2fa.gouda.lok/cgi/dlge, get 0
09:30:26.175 SF: [url] http://gdt2fa.gouda.lok
09:30:26.240 SF: no code from http!
09:30:26.240 SF: http get code 302, len 15
09:30:26.240 SF: csg account abnormal…
09:30:26.240 SF: csg login fail, exit
09:30:26.240 SF: roam service failed rc=-2
09:30:26.240 SF: password related state
09:30:26.240 SF: account state 7Known issues are also shown on the dell website. Check if you can find your issues.. https://www.dell.com/support/manuals/nl/nl/nlbsdt1/wyse-thinos-maintenance/thinos_8.6.x_rn/fixed-issues?guid=guid-bb88ece7-832b-48c0-aa0a-24d772ef7dda&lang=en-us
__
Anyways we also have issues now on the latest 8.6_027 with 3040. Name changes of a client does not come through via WMS.
Can someone confirm this?
Thanks! We got it workin finally.
Like you said, under the advanced section, but without the manualoverride.
So this is how it works now with us:
1. In WMS display settings policy removed
2. Central Configuration our wms server
3. Under Advanced resolution line
4. In the wnos.ini Desktop=Background.jpg just to have a line in there
5. in the ini folder the user.ini with specials.
Okay did what you asked about the step-by-step guide.
Unfortunately not the result we hoped for,
Tested with Mouseswap=yes in the user.ini, and that works. So the setup we have seems to work.
Resolution settings in the user.ini
Screen=1 Resolution=1280×720
Screen=2 Resolution=1280×720Does not work and looks like it is overruled by something else.
We’ve putted your syntax in Line 1 under the advanced section. Is that the right place?
Or should it be in the wnos.ini ? That does not work either.
That is funny, we dont have the option “Device Settings (8.6+) in our WMS 1.4.
Is that a PRO-version option?
That is also the reason we’re using the “central configuration” option to do this via the wnos.ini. At first your options:
ManualOverride=yes \
components=Options monitor=yes mouse=yes keyboard=yes timezone=no printer=yes audio=yes network=yesare not working yet on our configuration sad enough.
Jedi Master or any1 else, we have a simular issue like the topicstarter.
We also have 3040 and use WMS standard.
If we configure display settings in WMS, the personal ini’s (with specific resolution settings) will be ignored and overruled by wms. Do you know how to configure a specific resolution per user with a ini and not via gui?
We want to use the {username.ini} for the custom screen resolutions, while maintaining a universal thin client resolution config.
