Here is the situation we are running into:
We have an application that installs and launches from a website via an ActiveX control. Now the current design of the SVW/SSL VPN is if the ActiveX control and application is installed outside of the SVW then when a user is brought into the SVW it will function as expected. My problem is what if the application has NO possible way of being installed outside of the SVW.
So now the problem I have had since one of the 5.5 releases (yes this did work at one time with the SVW). All of our employees are brought into the SVW if they access our Employees Section of our website from a "non company" computer aka their home PC, public PC, etc. This application they need to use has never been installed outside of the SVW environment on their home PC and cannot be accessed unless they are in our Employee's section and inside the SVW. When they go to launch it from inside the SVW is does not load, etc, and does not work.
So a long story short the application is 100% unusable for out 800+ employees.
Another spin on this is lets say we have a user that goes to a conference and they need to use this application. There is no way we would want that applciation to remain installed on a public conference PC. So it makes sense to have them come into the SVW install the application and then run the application. Then once they are finished they logout of our website and nothing is left on this public conference PC.
Thoughts from the JNET community?
Did they say anything why it does not work with newer releases?
The reason why I ask, I don't guess you will find another solution than juniper fixing that or use the pretty expensive symantec virtual desktop as 3rd party one, assuiming that your a'x is working with this.
But I don't see any other way as maybe accessing any URL without svw, to just push this a'x and run the main URL with the SVW later. This will result in the behaviuour you dislike, as I unterstood, that this applet will remain on the pc.
Unfortunately my experiences dealing with Juniper support have been up and down as you can imagine with this case being open for a year and a half.
I understand this SVW is a environment that is not permanent and gets cleaned up and deleted (as designed for security) but I don't have a problem if each time the application must reinstall within the SVW. Just as long as applications install. Juniper does not seem to grasp this.