Wireless Access

Hi,

We are trying to configure the installation of VIA client using SCCM (System Center Configuration Manager). When wet set the authprofile parameter to a specific one in the command line, we noticed that in the VIA client this parameter is not predeterminated. 

We have two authentication profiles, one for internal users and antoher for external ones. In the VIA installation command line, we would like to set the authentication profile parameter to the suitable one. In this way, users do not need to select the authentication profile in a drop down list.

Nevertheless, when we set the gateway parameter in the command line to a specific IP address, we observed that this parameter is succesfully predeterminated in the VIA client.

Could you please tell us if there is another problem reported with setting the authentication profile parameter in the command line? Is there something that we are forgetting in the way we are configuring it?

Thanks in advance,

Regards,

---

@SPF wrote:

 

Hi,

 

We are trying to configure the installation of VIA client using SCCM (System Center Configuration Manager). When wet set the authprofile parameter to a specific one in the command line, we noticed that in the VIA client this parameter is not predeterminated. 

We have two authentication profiles, one for internal users and antoher for external ones. In the VIA installation command line, we would like to set the authentication profile parameter to the suitable one. In this way, users do not need to select the authentication profile in a drop down list.

 

Nevertheless, when we set the gateway parameter in the command line to a specific IP address, we observed that this parameter is succesfully predeterminated in the VIA client.

 

Could you please tell us if there is another problem reported with setting the authentication profile parameter in the command line? Is there something that we are forgetting in the way we are configuring it?

 

Thanks in advance,

 

Regards,

 

---

What are the exact commandline parameters you are using and what version of the MSI are you using?

Hi,

This is the commnad line parameters we are using:

msiexec /i ansetup.msi /passive GATEWAY=<GatewayName> AUTHPROFILE=<VIAAuthenticationProfile>

The Client VIA version is  2.1.0.1.34126

Thanks,

That is the syntax.  Did you try it without the passive switch? Also, the profile is case sensitive, so make sure that is entered correctly.

Hi Joseph,

We described below the tests done:

1.-Without /passive and checking that the authprofile is well written. Even, we have copied the AuthprofileName defined in the controller just for avoiding problems with the case sensitive.

The MSI command line executed is :  msiexec /i ansetup.msi GATEWAY=<GatewayName> AUTHPROFILE=<AuthProfileName>

After the VIA client installation, the authprofile is not predeterminated in the VIA client. Instead of that, a drop down menu is shown.

Besides, we have checked in its Registry Key associated HKEY_CURRENT_USER\SOFTWARE\Aruba Networks\VIA\AuthProfile [AUTHPROFILE], that the Authprofile value was changed to the one fixed in the command line. In spite of this, the VIA client still shows a drop down authentication list. Even, if we set the Registry Key HKEY_CURRENT_USER\SOFTWARE\Aruba Networks\VIA\AuthProfile [AUTHPROFILE] to a specific Authentication profile, the behaviour is the same.

2.- In the controller, we  have enabled in the connection profile (associated to a concrete authentication profile) the  feature of "Lockdown all settings" just for test if it works.  We execute: msiexec /i ansetup.msi AUTHPROFILE=<AuthProfileName>

And the result is the same than in the upper case. A drop down list was shown, but once the authentication profile is donwload, this profile is setting and lockdown, so as to users can not  modify it.

Could you have any idea, suggestion,etc..?

Thanks and regards,

---

@SPF wrote:

 

Hi Joseph,

 

We described below the tests done:

 

1.-Without /passive and checking that the authprofile is well written. Even, we have copied the AuthprofileName defined in the controller just for avoiding problems with the case sensitive.

The MSI command line executed is :  msiexec /i ansetup.msi GATEWAY=<GatewayName> AUTHPROFILE=<AuthProfileName>

 

After the VIA client installation, the authprofile is not predeterminated in the VIA client. Instead of that, a drop down menu is shown.

Besides, we have checked in its Registry Key associated HKEY_CURRENT_USER\SOFTWARE\Aruba Networks\VIA\AuthProfile [AUTHPROFILE], that the Authprofile value was changed to the one fixed in the command line. In spite of this, the VIA client still shows a drop down authentication list. Even, if we set the Registry Key HKEY_CURRENT_USER\SOFTWARE\Aruba Networks\VIA\AuthProfile [AUTHPROFILE] to a specific Authentication profile, the behaviour is the same.

 

2.- In the controller, we  have enabled in the connection profile (associated to a concrete authentication profile) the  feature of "Lockdown all settings" just for test if it works.  We execute: msiexec /i ansetup.msi AUTHPROFILE=<AuthProfileName>

And the result is the same than in the upper case. A drop down list was shown, but once the authentication profile is donwload, this profile is setting and lockdown, so as to users can not  modify it.

 

Could you have any idea, suggestion,etc..?

 

Thanks and regards,

 

---

SPF,

The Authprofile parameter also requires the username and password parameter to download the profile when it is installing.

It is probably better that you just install the gateway parameter, allow the user to launch and enter username and password, and allow the backend to ONLY present that user with the profile that he needs.

Again, during installation, the profile will not be downloaded unless there is a username and password parameter entered, so it is better to just put the gateway.  When the user launches, the user will be asked for username and password and the profile automatically downloaded and used.

Hi Joseph,

We have already tested it with the gateway, getconfig, user and password parameters, and I am sorry but it still does not work.

Is there any way to establish the VIA authentication profile to a predeterminate value? We have two VIA authentication Profiles according to the user's profile (corporative user and non corporative users). For instance, for a corporative users we would like to set the VIA authentication profile to a especific one avoiding to show a  list with both profiles.

Thanks and regards,

---

@SPF wrote:

 

Hi Joseph,

 

We have already tested it with the gateway, getconfig, user and password parameters, and I am sorry but it still does not work.

Is there any way to establish the VIA authentication profile to a predeterminate value? We have two VIA authentication Profiles according to the user's profile (corporative user and non corporative users). For instance, for a corporative users we would like to set the VIA authentication profile to a especific one avoiding to show a  list with both profiles.

 

Thanks and regards,

---

SPF,

Unfortunately, if there is more than one profile, the user has to choose.  The only way you can do this at install this is if you have a dummy username and password that is in a specific group, then you would do:

msiexec.exe /q /I ansetup.msi GETCONFIG=1 GATEWAY=<remote server> AUTHPROFILE=<profile name> USER=<username> PASSWORD=<password> [NOCERTWARN=1]

That should install the specific profile and then the user would put in a username and password after and already have that profile downloaded.  

So long story short, if you have more than one profile then users have to choose.  

There might be another way:  What is the difference between the two profiles you are trying to create?  There is a way, within the same single profile to provide different firewall roles or firewall policies with user derivation, instead of different profiles...

Hi Joseph,

Thanks for your reply.

We have two profiles, one for corporative users and other for non corporative users. For the first case, the authentication is based on a NPS (domain user) and for the second case the authentication is based on a client certificate and user/pwd of the internal data base of the controller.

If there is no other way, we will show a list with both profiles, and users shoudl select a choice.

Regards,

 Hi,

We have already upgraded VIA client to the lastest version 2.1.1.3.40312 . We are trying to set the gateway parameter with the command line,  but we noticed that this parameter is not set in the Remote server VIA´s field (user has to type it manually).

VIA installation is launched with SCCM (System Center Configuration Manager).  Is there any problem reported with this kind of installation?

Thanks in advance,

Regards,