Wyse thin client citrix receiver. Configure Receiver on Thin Client to Point to a new Storefront Store

Looking for:

Wyse thin client citrix receiver

Configure Receiver on Thin Client to Point to a new Storefront Store

Asked by Chris Gundry. Wondering if anyone can help me with the nightmare we are having. Basically we want to use Wyse thin clients running the latest ThinOS 8. If you wait for a new 2FA code 60 second rolling token code to generate and enter your password and the new code it loads fine. So we are getting a 'double login' issue. To me clienr seems like a session issue on the NetScaler side, but NetScaler support claim this is not the case and its working fine and passing the session wyse thin client citrix receiver OK.

I am not a NetScaler expert by any means wysf I am thn to verify this myself. If we change the session policy etc to point the Wyse traffic to the PNagent address then the authentication works fine, the client connects and you can load applications no rreceiver.

This however does result in a error in the event wgse on the SF servers:. CitrixAGBasic single sign-on failed because the credentials wyse thin client citrix receiver verification with reason: Failed. This error appears every time a thin client user authenticates. From what I have researched I believe this is because the PNagent приведенная ссылка doesn't support 2FA and is trying to use the 2FA passcode to authenticate, instead of the password, then trying the password and working.

I can't verify this but that is what I ccitrix and someone else told me the same thing. The solution is to not use the PNagent address, but whe we do that we get the original issue Детальнее на этой странице mentioned above, aka 'double login issue'. We моему how to install citrix workspace app ваш tried so many ictrix of auth policies, session policies and general config changes that I can't list them all. Wyse can't make up their mind what is or isn't required, one minute they say that it uses the web receiver policies, the next it uses the full citrix receiver policies.

I have spoken to Citrix support about it and they blame Wyse, but Wyse blame Citrix. I have tried to get 2FA on all wyse 8. Called for Netscaler support and they advised me that radius is working and didn't see an issue. The only thing that helped me was using a public cert.

Пост citrix workspace web download действительно for the response, it's a shame you never got it working. I am glad it is at receivdr working to some degree for us. I have an update on this issue in case anyone else has this wyse thin client citrix receiver in the future. Firstly my Refeiver case number was They clien the issue was a session issue and they had added some code into a new FW version they wanted me to test which appeared wyse thin client citrix receiver set a cookie for the session.

I believe this probably would have fixed the wyse thin client citrix receiver. I had to do some other work on our setup to change the way it was configured for another requirement.

When doing that work the double login issue now seems to be resolved! Basically the work was to separate our internal and external addresses and change the SF name. We were using citrix. In StoreFront I changed it to be storefront. I then changed out session policies to point to storefront.

Once doing this the Wyse clients are connecting without double login issue and are no longer putting errors in the SF event logs. Wyse clients supposedly work without additional policies. I found this to not redeiver the case because the standard receiver policy used for mobile clients etc requires credentials to be set to secondary, which recriver the Wyse client logins, so you need a separate Wyse policy. If you don't use the receiver and only use Web then you can probably get around this with only 2 policies still.

The receiver session policy I am using is now: REQ. You will be able to leave a comment after signing in. Welcome to the Citrix Discussions. Our site does not support outdated browser or earlier versions.

To use our site, please take one of the following actions:. Jump to content. Upvote if you also have this question or find it interesting.

Learn more. Follow, to receive updates on this topic. Sign in to follow this Followers clien. Chris Gundry 8. Chris Gundry Enthusiast 8 Members 64 posts. Posted September 11, Hi all, Wondering if anyone can help me with the nightmare we are having. This however does result in a error in the wyse thin client citrix receiver log on the SF servers: CitrixAGBasic single sign-on failed because the credentials failed verification with reason: Failed.

Rwceiver thanks! Share this post Link to post. Recommended Posts. Mark this reply as best answer, if it answered your question. Upvote if you found this answer helpful or interesting.

Zuriel Cabrera 3. Vitrix Cabrera Enthusiast 3 Members 4 posts. Posted September ghin, For anyone else trying to get Wyse clients setup the following might be helpful: 1. I have them ordered Wyse 80, Receiver 90, Web Please thln in to comment You will be able to leave a comment after signing in Sign in now.

To use our site, please wyse thin client citrix receiver one of the following actions: Upgrade your version of Internet Explorer. You can find more information here Install the Google browser. You can find more wyse thin client citrix receiver here Install the Firefox browser.

Thin OS and Citrix receiver version. - Dell Community

How often is the Citrix Receiver version updated? We are running the latest Thin OS which is 8. Citrix support увидеть больше telling me that the wyse thin client citrix receiver version e need to be is Actually waiting for an answer on that for ages already. Citrix reciever version is very important for a well working Citrix environment and I wish Dell would put more effort in keeping the reciever up to date in WTOS.

Especially since it's not even called Receiver anymore. The version of Receiver in ThinOS is a customized version and will never correlate directly with a windows or linux build of the receiver from Citrix. If you are having a specific problem with receiver /16806.txt ThinOS, open a Dell support ticket and if it requires escalation and interaction with Citrix Dell will escalate wyse thin client citrix receiver resolution.

That's not true. With each iteration there is usually a new Citrix Receiver version. We are on 8. I'm /14000.txt testing firmware update 8. To the others in this thread, i would suggest reading the version release notes and or at least the major release notes because it states what versions of Citrix were tested and also states what features are available in the Citrix Receiver versions.

For example in the 8. I know for myself and my experience with opening tickets with Dell they've been very responsive and at least logging my issues as a known issue and then addressing them between 8. As another users stated, open a ticket and they're usually very helpful. Browse Community. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

Showing results for. Search instead for. Did you mean:. Last reply by BigBJ Unsolved. Start a Discussion. Thin OS and Citrix receiver version.

Labels 1. Labels Labels: Citrix Receiver. All forum topics Previous Topic Next Topic. Replies 6. GSCF 2 Bronze. In response to GSCF. Rosy11 2 Wyse thin client citrix receiver. Hi, Even we are running the latest Thin OS citrix workspace app for windows 1912 ltsr is 8.

I have not yet got any information from Dell Wyse on this. It would be really helpful if anyone has any update that you are aware of. In response to Rosy BigBJ wyse thin client citrix receiver Bronze. In response to sdurrant. Post Reply. Dell Support Resources. Latest Solutions. See More. Top Contributor.

Windows 10 IoT Enterprise for Dell Wyse Thin Clients Administrator’s Guide | Dell Suomi

We have tried so many permutations of auth policies, session policies and general config changes that I can't list them all. Wyse can't make up their mind what is or isn't required, one minute they say that it uses the web receiver policies, the next it uses the full citrix receiver policies. I have spoken to Citrix support about it and they blame Wyse, but Wyse blame Citrix.

I have tried to get 2FA on all wyse 8. Called for Netscaler support and they advised me that radius is working and didn't see an issue. The only thing that helped me was using a public cert. Thanks for the response, it's a shame you never got it working.

I am glad it is at least working to some degree for us. I have an update on this issue in case anyone else has this issue in the future.

Firstly my Wyse case number was They believed the issue was a session issue and they had added some code into a new FW version they wanted me to test which appeared to set a cookie for the session. I believe this probably would have fixed the issue. I had to do some other work on our setup to change the way it was configured for another requirement. When doing that work the double login issue now seems to be resolved! Basically the work was to separate our internal and external addresses and change the SF name.

We were using citrix. In StoreFront I changed it to be storefront. I then changed out session policies to point to storefront. Once doing this the Wyse clients are connecting without double login issue and are no longer putting errors in the SF event logs. Wyse clients supposedly work without additional policies.

I found this to not be the case because the standard receiver policy used for mobile clients etc requires credentials to be set to secondary, which breaks the Wyse client logins, so you need a separate Wyse policy. If you don't use the receiver and only use Web then you can probably get around this with only 2 policies still. The receiver session policy I am using is now: REQ. You will be able to leave a comment after signing in. Welcome to the Citrix Discussions. Our site does not support outdated browser or earlier versions.

To use our site, please take one of the following actions:. Jump to content. Upvote if you also have this question or find it interesting. Learn more. Follow, to receive updates on this topic. Sign in to follow this Followers 0. It checks for updates from vdiManager and automatically updates to the latest version. There is no need to install any additional software on the end-point. The Java Client uses the Java Webstart technology to pull the latest version of the client software from vdiManager.

Supported operating systems are listed below. Some of the Wyse and 10Zig clients supported include:. The certified devices include the following. Ensure to test with specific models to verify that the virtual desktop works.

Citrix appreciates sharing your experiences so that information can be shared with others. Choosing the right user device depends on your use case, goals, and budget. Following are suggestions to help you choose a user device. Desktops: Repurposing old desktops is a low cost solution that provides great performance. Most old desktops are more powerful than many high-end thin clients.

However, old desktops consume much more power than other devices and you have the overhead of managing them. You can use software such as vdiBlaster to lock down the desktops and reduce management overhead. Many users start with old desktops and replace them with thin clients over time.

Thin clients : Thin clients significantly consume lower power than desktops and many provide a zero-maintenance option whereby their firmware can be automatically upgraded from the VDI-in-a-Box server. Wyse ThinOS7 thin clients are one such example. However, note that low-end thin clients do not handle media streaming and Flash as well as the higher-end thin clients.

Also, the embedded operating system makes a difference. Use the lower-end thin clients for task workers and the higher-end thin clients for users who need access to media, such as to watch training videos. Mobile devices : Mobile devices are ideal for those who need a very portable desktop that can be accessed from anywhere. Failed to load featured products content, Please try again. Customers who viewed this article also viewed.

Search This Blog

allbest 3calcioop-woxo