I've tried to find a similar question on this forum but haven't managed to. Please excuse me if it's been posted before.
I published IE through a vbscript which works perfectly well on W2K3 32 bit windows server, IE8 with Citrix. The vbscript launches the application directly on the server, and also via the users's Citrix web front end.
Set objExplorer = CreateObject("InternetExplorer.Application")objExplorer.Navigate http://www.google.comobjExplorer.ToolBar = 0objExplorer.StatusBar = 0objExplorer.Width = 1024objExplorer.Height = 768objExplorer.Left = 0objExplorer.Top = 0objExplorer.Visible = 1
I have published exactly the same batch file, which runs vb script launching IE, on W2K8, 64 bit, IE8. The vbscript launches the application directly on the server without problem. But, via the user's citrix web front end, the IE window flashes up for a second and then disappears. It looks like the 64 bit version of IE is called regardless of whether the vbscript is run on the server or via Citrix front end.
I am using the vbscript above because this is for external clients and we don't want them to have access to internet options.
I've spent weeks trawling through Google and haven't managed to find the answer, though I have found that other people have had the same issue.
Any help would be greatly appreciated.
Thanks for your replies which I have now tried out. Unfortunately still same thing is happening.
I was surprised that "pause" didn't work. It worked on the server, but again via Citrix web front end it closed immediately.
I also tried leaving out the .cmd but still same thing happened. I do appreciate these suggestions!
Is .NET 1.1 installed on the server that runs the Web Interface ?
So there is no difference in the accounts you used i.e. published desktop where it works and published app where it doesn't both session using the same user account?
Have you run process monitor on the server then connected to the published app? Just filter for iexplore.exe and see what that throws up.
Yes the user logged into the server is my own logon, which I use for front end as well.
We are not using .NET 1.1 but we can do if it might help.
Do you mean procexp?
No ! .NET 1.1 will *NOT* help. The symptoms you're describing are very similar to the ones obtained when .NET 1.1 is installed on the web server : Apps work under TS or the console using a specific account and not thru the Citrix Web interface using the same account. In this case, the application start and close immediately without launching the ICA stuff.
Your problem seems to take place deeper in the system, prior to the step "Running the CMD file" as the integrated command PAUSE failed. This means that even the call to a new command interpreter is not successful.
Have you tried to build a new web server from scratch ?
Thanks for all your help.
I was wondering if anybody has the facility to just test my scripts from citrix front end using Citrix server:
Windows 2008, (if possible Release 1, SP2)
I have found another thread, where someone had a similar problem but they did not get this resolved, they used kiosk mode instead. Kiosk mode isn't suitable for us.
Also I've tried to get this rewritten and compiled as an EXE, 32 bit and 64 bit, to see if the problem is the combination of w2k8/64 bit/citrix/vbscript. Same thing happened. We tried launching IE and then a page which displays IE as we wish, but it looked untidy to use for client's, required download of active X. I just thought a lot of people would have had this problem, or else a lot of people are easily using this type of script, I'm not sure which!
I was looking at this as a general problem that someone else must have come across, but may be it is a server issue.
I've tested your scripts on W2K8 R2 and they work fine. I can't test on a R1. Sorry.
Have you tried this:
I found this while looking for Citrix Receiver for Android...
Thanks for all your help and ideas. I tried again as follows with pause, and it worked. We have decided to leave it with "pause" and hide this using runh.exe.
start /wait %systemroot%\SysWow64\wscript.exe fm01.vbspause
Someone is testing this and no problems so far.
I thought the issue had been resolved but it hadn't. Our script works without problem on XenApp6 with W2K8 R2.
So we are still using a 2003 server with xenapp5 on our older Xenapp5 W2K8 R1 system to get round this.
Did you try publishing it as an installed application but running it with the /k option to enable kiosk mode?
c:\program files (x86)\Internet Explorer\iexplore.exe -k "https://www.google.com/"
This will launch it as a kiosk mode, full screen, without even an address bar. You can remove other options on it by editing local group policy.
here are millions of people trying to make a blog and trying even harder to get it noticed.Men's Franklin Marshall Hoodies Sweatshirts When making a good blog it is all about the post and the content. Spending too much time on the look and the ads is just going to leave you in the white space of Google with one big headache.Franklin Marshall Women's