Unsolved
This post is more than 5 years old
1 Rookie
•
74 Posts
0
2251
January 13th, 2011 19:00
New connector options in Web Access (7.2)
So, we are now running 7.2
I noticed that web access has a new pulldown menu where the user can choose between:
-Connector for Windows
-Connector for Linux
-Connector for Mac OS X
-Connector for Java
My first question: Why should a user choose between the first three connectors? They all generate the same .pit file.
It doesn't matter which one you select.
Wouldn't it be nicer to just add two options:
-Connect for Windows/Linux/Mac
-Connector for Java
This way the mac/linux users don't have to select their system everytime, which is pointless anyway.
Second question:
In the web access admin interface you have three options relatad to the connectors:
- Do not automatically download and install a connector (normal operation)
- Allow the user to select which connector to use (e.g. Windows, Java, Mac OS X or Linux)
- Automatically download and install the following connector:
When the first one is selected, you don't see the connector dropdownbox and you also don't get a warning message if you are running an old client. So there is no client detection.
When the second one is selected, you do see the connector dropdownbox and also get the client detection.
We would like to enable the second option (connector dropdownbox), but disable client detection. This is because we have to distribute a new client-package to all our clients, and don't want our clients to install the software themself. Now they get this 'you client it not up to date' box.
jay61
2 Posts
1
January 13th, 2011 21:00
Regarding your second question, I have a work around you can do to get the popup from occurring. What you need to do is select “automatically download and install the following connector.” Once you do that you can change the version number that Web-IT client detection is looking for ie. 7.1.301.358. Then click save changes. Then again select “Allow the user to select which connector to use” and press Save Changes again. This should solve that issue.
rene11
1 Rookie
•
74 Posts
0
January 15th, 2011 09:00
Thanks Jay! That is a work around for us.