Byford-Rew Posted August 21, 2012 Posted August 21, 2012 I have a number of HP t610 Thin Clients that I am planning to use in the network for a Citrix VDi system. These devices are running Windows Embedded Standard 7[E] so that I can ensure that Flash compatability and HDX continues to function. Should these devices be added to the Domain or left as Stand alone devices? If I leave them as stand alone devices I have issues with authentication for web sites when called by HDX Flash Redirection unless there is another way to configure them.
plexer Posted August 21, 2012 Posted August 21, 2012 Confsed as to why you would need to join the thin clients themselves to the domain? Ben
Byford-Rew Posted August 21, 2012 Author Posted August 21, 2012 Confsed as to why you would need to join the thin clients themselves to the domain? Ben Two reasons : 1. To get Single Sign On [sSO] to work for a user logging into a Citrix VDi Session through Citrix Receiver 2. To ensure that the logged on user is authenticated to used the ISA firewall to process html request when Flash is redirected using HDX Flash redirection. If the terminal is left as stand alone when the request is made then a username / password requested comes requesting details.
RJohnson91 Posted April 10, 2017 Posted April 10, 2017 (edited) Two reasons : 1. To get Single Sign On [sSO] to work for a user logging into a Citrix VDi Session through Citrix Receiver 2. To ensure that the logged on user is authenticated to used the ISA firewall to process html request when Flash is redirected using HDX Flash redirection. If the terminal is left as stand alone when the request is made then a username / password requested comes requesting details. We use essentially the same set up here regarding the 'thin clients' and the HDX flash redirection. We ran into the same problem as you, our fat clients aren't on the domain and therefore don't authenticate to allow internet access for the local flash rendering that HDX Flash redirection needs. We run Smoothwall here as our firewall, so to get around this issue we have 'pooled' the fat clients together as reservations and allowed unauthenticated internet access via Smoothwall on the local fat clients IP range. This gets round the blocked internet issue and isn't a problem because the students can't access the local machine, only the storefront. Ryan Edited April 10, 2017 by RJohnson91
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now