Receive prompt to install Citrix plugin despite it being installed already, Internet Explorer 9

I am trying to reach our company's https://remote.mydomain.com Citrix web interface to launch apps and keep getting prompted to install the citrix client, as see in the attachment.  I already have the latest client installed – CitrixOnlinePluginFull 12.1.44.1  - it is 'special' for IE9.  I have uninstalled reinstalled the client and receive same prompt.  I hesitate to click  ‘install’, when prompted by the browser, because it will uninstall the FULL plugin and install the web only plugin. As well, if I press 'skip to logon', the interface showing published apps opens but attempting to launch any apps results in pop-up dialog bar asking to download 'launch.ica'.  other published apps, through the PNAagent run fine.  This appears to be something related to IE9 and active x but not sure what to try to fix.  I have tried all the recommendations in the below article, with the exception of the registry hack, and no go.  Any experts have any insight on how to make this work with IE9?

http://support.citrix.com/article/CTX129082
 
remote-nhrmc-org-prompt-install2.jpg
LVL 1
davisAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Matt VCommented:
There is a special release of the client for IE9.

http://support.citrix.com/article/CTX129082
0
davisAuthor Commented:
Yes - that is the same link I entered in my original post.  As well, I've tried most of those suggestions in that article with no success.
0
Ayman BakrSenior ConsultantCommented:
After uninstalling the plugin and before reinstalling it is better to clean the remnants. Follow this article to clean the remnants:

http://support.citrix.com/article/CTX131620

After uninstalling and cleanly removing the remnants why don't you install the Citrix receiver 3.0 instead (if you want the full features with the PN agent like plugin you will have to install the Citrix receiver enterprise)
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

davisAuthor Commented:
Although, a very good suggestion, I received the same results with Citrix Receiver 3.0 Enterprise.   - Followed your reccomendation and uninstalled OnlinePlugin completely, rebooted, and installed Receiver.  Still prompts for installation of OnlinePluginWeb

Is there an activeX setting that can be modified to allow the browser to recognize the Plugin?
0
davisAuthor Commented:
FYI - Just tried latest version of Google chrome with same results - received popup to install client, even though 'onlinepluginfull' already installed.
0
Ayman BakrSenior ConsultantCommented:
It seems you have client deployment enabled on your web interface.

You can do one of the following:

1. If you don't want to deploy any client to the users in any scenario then go to the web interface console > go to 'client deployment' > uncheck 'offer upgrades for clients'

2. If you don't want to disable client deployment but you only want to skip it for the installed clients then browse to :
c:\inetpub\wwwroot\Citrix\XenApp\conf
Open the file: we interface.conf
Scroll to the ICA section and locate where the plugin file name is mentioned. There you need to append to the end of the statement after the comma the version as:
Version:12.1.44

This will have the effect of bypassing the prompt if you have a later version installed on the client.
0
CoralonCommented:
I've complained about this for years.  The client auto-detection is 'broken' on Web Interface, and Citrix needs to fix it.

Here is the problem:
The Full Version of the client (including Receiver 3.0 & going back several years) sets up a file association for .ica files as Citrix.ICAClient.2.7.  (some older ones do Citrix.ICAClient.2.5,etc.)
The Web Interface site actually does the detection by trying to instantiate Citrix.ICAClient.  It does not use the full name that the installer configures.
The Web Client version, registers the filetype as Citrix.ICAClient

You can test this easily enough by changing the file association on the client side
To see it (from a command prompt):
assoc .ica

Open in new window

and then use:
ftype <assoc from above> typically this will be:
ftype Citrix.ICAClient.2.7

Open in new window


To fix it, do this:
ftype Citrix.ICAClient = "C:\Program Files (x86)\Citrix\ICA Client\wfcrun32.exe" "%1"

Open in new window

(or whatever the path from above is)
assoc .ica=Citrix.ICAClient

Open in new window


The server side fix is to modify the detection script.  I'm not a javascript guy, maybe one of them can chime in with the proper coding

The file to modify is:
<path to wi site>\app_data\clientDetection\clientscripts\nativeClientDetect.js
Example: c:\inetpub\wwwroot\Citrix\XenApp\app_data\clientDetection\clientscripts\nativeClientDetect.js

Look for the function createIcaObj:
Here is the code from a WI 5.4 site:
// Create an ActiveX ICA object
function createIcaObj() {
     var obj = null;
     try {
          obj = new ActiveXObject("Citrix.ICAClient");
      } catch (e) {
      }
      return obj;
}

Open in new window


What it needs to do is an Or type of configuration like (this is my sort-of code.. not tested or necessarily valid.. just shows the concept)
// Create an ActiveX ICA object
function createIcaObj() {
     var obj = null;
     try {
          obj = new ActiveXObject("Citrix.ICAClient");
--->          if obj = null {obj = new ActiveXObject("Citrix.ICAClient.2.7")};
      } catch (e) {
      }
      return obj;
}

Open in new window


I'll keep yelling @ Citrix.. they need to either fix the full plugin installer to create their file association correctly, or fix the WI code to detect it correctly. Until they do, the only other solution is to install the web client alongside the full client, or one of the 2 above I mentioned.  

Coralon
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
davisAuthor Commented:
I did another serarch on EE and found the answer.  (Note:  I always search the EE site and 'Google' for a solution, prior to posting but did not find it originally)

Basically, it seems, IE9 64Bit doesn't work!  However, IE 9 32Bit is working just fine...

http://www.experts-exchange.com/OS/Miscellaneous/Q_27424529.html?sfQueryTermInfo=1+10+30+citrix+ie9

Although it seems I was able to find the solution myself, I appreciate your feedback.  What is the appropriate action regarding points?
0
Ayman BakrSenior ConsultantCommented:
Well Davis, you are not obliged to give anybody the points if you had the issue resolved by yourself.

However I would like to add that not working on IE 9 64 bit gives you the option for a workaround to have IE9 32 bit but not actually find the root cause of the issue.

Coralon has a good point and may be what he is suggesting might be the root cause. I would advise you to try his suggestions because then you might not need then to reinstall the 32 bit version for all your clients after all.
0
davisAuthor Commented:
Understood - what I found is simply A workaround and not the root cause.  It's a bit unsettling/interesting that this issue affects the entire population of Internet explorer9 64bit users.

I have to ask -is the recommendation a two part solution, where changes need to be made to the client and the server?  Or can I simply change the settings for the application (64 bit version of IE)?  Appreciate your clarification -
0
CoralonCommented:
Well, the problem is the client detection.  You can do either the client fix (changing the association) or the server side fix which only has to be done one time.

The only problem on the server side is I'm not a javascript guy, so the code I put in there has a pretty good chance of being syntactically wrong.  The key is that detection code.  It says instantiate Citrix.ICAClient which only exists if the web client is installed.  It doesn't even *try* to instantiate Citrix.ICAClient.2.7 which is what all of the more recent clients do.  As I said.. some of the older clients try to instantiate Citrix.ICAClient.2.5, but that is still broken.

The idea on that code is to tell it basically try to instantiate Citrix.ICAClient and if that doesn't work, then try the Citrix.ICAClient.2.7.  (you could (in theory) next multiple if statements to catch some of the older versions also).

Coralon
0
Ayman BakrSenior ConsultantCommented:
Well, I think both - coralon can shed more lights on this.

However I am really interested on whether applying the version number in the conf file would actually resolve your issue or not - you might want to try one or both of the solutions I also provided to you.
0
CoralonCommented:
It's not a versioning problem, just the client detection.  The versioning problem (at least it used to) throws a specific error saying your client is too old.  Unless you configure versioning in WI, it is turned off by default.  

In the older versions (pre 12.1.44) When you used IE9, the client detection would do it's thing (as I posted above).  However, you would never get the yellow bar at the bottom to launch/save the file.  If you checked your temp directory at the time, you would get a file called launch.ica.partial.<somerandomcharacters> that had the content of the launch.ica file, but the file itself never completed.

You could take the the partial file and rename it, or copy it to launch.ica, and then double click it, and it would launch just fine.  Or, you could right click on the web page, and do a Save target as... and get the full file properly.  This is why they released the 12.1.44 version - it got rid of that .partial problem.

The behavior with IE9 is correct to use the download bar at the bottom.. (I use IE9 pretty much exclusively, so this extra click to launch is almost a non-thought for me.. it just happens).  I don't *think* there is a way for it to launch without that bar, but I haven't spent a lot of time figuring it out.  

My only thought on IE9 x64 is that maybe it can't instantiate the ICA Client, because it is a 32-bit client?  (Citrix and most other vendors don't have 64bit plugins for IE yet.. that will probably take years).  

Coralon
0
Ayman BakrSenior ConsultantCommented:
My suggestion to include the version number, although may seem to sound like a versioning issue, is not actually related to versioing as is. My suggestion to include a lesser version in the ICA section of the .conf file would dictate the Web Interface not to prompt for installing a plugin when the installed plugin on the client side is the same version or higher.

If it really that IE9 64bit client detection is broken then coralon's solution might resolve the issue. However, if my assumption that the web interface is detecting an 'unvalid' plugin it will always prompt for installing a plugin if you have client deployment enabled. So either you disable client deployment for all or you trick the web interface not to prompt for installation for a certain version or higher.
0
CoralonCommented:
I wish it was broken for just IE9.  That client detection script that I quoted/posted above applies to all fo the current versions of WI and the client.  I first saw this back with WI 4 (if I remember right) and the clients back as far as v10 for sure.  It's completely reproducible..  I had stopped rolling out the web based version rollouts because of it.  

Coralon

0
davisAuthor Commented:
Coralon appears to have the issue pretty well pinpointed, explaining the ROOT of the issue within client detection.  Currently, it is best for me to simply use either IE9 32Bit or Google Chrome with the 'IE Compatibility' plugin, which works as well.  I don't have access to the Citrix Farm Servers or WI servers and my 'alternate browser choice' is an immediate solution.   I can see you spent considerable time troubleshooting, struggled with this issue, and can sense your frustration in the post!  So, points go to you.  Thanks to you and all -
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Citrix

From novice to tech pro — start learning today.