Link to home
Start Free TrialLog in
Avatar of David XF
David XFFlag for United States of America

asked on

Setting up Internet Explorer with XenApp 6.5

I'm new to XenApp and need a little help setting up Internet Explorer options.  These are two issues we're currently having:

1) When a user opens Internet Explorer in XenApp 6.5, Add-ons do not load.  If the user goes to http://www.adobe.com/software/flash/about/ it does not show the Flash graphic and they get the message "An Add-on for this website failed to run".  Select "Manage Add-ons" and Flash isn't listed.  They also have similar problems going to Google Maps website - no error message, but the page doesn't load (get a blank page).  This appears to be a security issue, since both Flash and Google Maps work without a problem if an Administator logs on.

2) This XenApp 6.5 setup uses a server farm of four servers (all running Windows 2008 R2 64-bit).  A user opens Internet Explorer in XenApp, changes the homepage, logs off, and then logs back on.  The user is logged onto a different server in the server farm and does not receive the new homepage.  How do you get IE settings (such as Homepage and Favorites) to be saved across all servers in the server farm?  This happens for both admins and non-admins.
ASKER CERTIFIED SOLUTION
Avatar of Carl Webster
Carl Webster
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of David XF

ASKER

For #2, the users are setup to use Roaming Profiles on the domain.  Is there a seperate Roaming Profile setup for just Citrix?

I'll check on #1 this later today when I'm onsite.  Thanks.
If the XenApp servers are in their own OU, make sure the OU is not set to Block Inheritance.  That would keep the Roaming Profile policy from being enforced.
Checked the Roaming Profile setup.  It is working correctly when the users logon with their domain profiles.
This was all due to setup issues.
Number one was due to Group Policy security setup for IE.
Number two was due to an error in folder redirection setup.