ThinApp and IE6 Windows Timeout

[tacticsbaby]

Greetings,

We are currently using ThinApp Version 4.6.1 to harvest Internet Explorer 6. We use IE 6 to view older web apps that only work in IE6. When I open IE8 and launch a page that requires IE6 IE6 opens as expected and then we get a message that says that the IE8 window will close in 2 seconds. What I want to know is if there is any way to configure this setting so that IE 8 takes longer to close or does not close at all. Thanks in advance.

[JackMac4]

Have you considered trying 4.6.2? A lot of issues with IE6 and ThinDirect were resolved with that release that may help you out.

[tacticsbaby]

Thanks, I will look into that.

[Pankaj11]

Hi,

If you are seeing a 2 second time out for the IE8 window, then you are definitely using ThinApp 4.6.2, as this was introduced in 4.6.2 only. Unfortunately there is no way to configure this limit. The limit was put in place, because some of our customers, didn't like the ThinDirect page being shown all the time and wanted the page to be closed on it's own after displaying the redirection message. Do you have any specific reason as to why you want the page to remain opened?

Thanks.

[tacticsbaby]

No reason to keep the window open for more than 2 seconds. We just did not understand what we were seeing. By the way, can you also tell me if it is possible to ThinApp IE6 with plugins and install it to a local desktop? I ask because I made an IE6 package but View does not deploy the plugins folder that I created for it. Thanks.

[Pankaj11]

I think you can capture plugins with IE6 (or you can use AppLink to link plugins captured separately). Also, you can install the virtual IE6 package on a desktop. Check out this link for some capture related information: http://blogs.vmware.com/thinapp/2010/06/internet-explorer-6on-windows-7.html

Thanks.

[tacticsbaby]

Yes, I am using applink for the plugins. My problem is that unless I manually copy the plugins folder locally to the VM my IE6 ThinApp cannot find the plugins folder because it does not exist locally. I have gotten around this by putting a link to a plugins folder on a network share in package.ini, but I had hoped that there would be a cleaner way of handling this without streaming. Is there a better different way of handling this?

[TobyFruthParson]

If the plug-ins are being streamed in a View environment, is there an appreciable loss in performance for the IE6 users?