RE: How to configure two different SSL Client on ASA 5520

I'm pretty sure this is not possible. Once you're on the AnyConnect client,
future upgrades do not require admin privileges, if that helps for the
future.

-ryan

From: Akber Ali Mirza [mailto:akberali.cisco_at_gmail.com]
Sent: Sunday, September 26, 2010 2:18 AM
To: Radioactive Frog; Ryan West
Cc: CCIE Lab
Subject: Re: How to configure two different SSL Client on ASA 5520 8.2ver

Hello Frog/Ryan,

Thanks for your posts!

Yes, I am aware of the Windows Domain Group policy through which we can push
any client.

However i am curious to know is there a way in ASA to configure one Webvpn
client 1.1.0.154 version for WinXP users

& Any Connect client for Windows 7 users ..so when the users type https://
XXXX.GOV.XX the users as per their

OS should get forwarded to the VPN client version.

Regards,
Akber Mirza.

On Sat, Sep 25, 2010 at 3:49 PM, Radioactive Frog
<pbhatkoti_at_gmail.com<mailto:pbhatkoti_at_gmail.com>> wrote:
As Ryan said, recommended method is to use windows GP to push any-clients.

However, it's possible to rollout phase by department using ASA group-policy.

On Thu, Sep 23, 2010 at 10:41 PM, Ryan West
<rwest_at_zyedge.com<mailto:rwest_at_zyedge.com>> wrote:
Akber,

> -----Original Message-----
> From: nobody_at_groupstudy.com<mailto:nobody_at_groupstudy.com>
[mailto:nobody_at_groupstudy.com<mailto:nobody_at_groupstudy.com>] On
> Behalf Of Akber Ali Mirza
> Subject: How to configure two different SSL Client on ASA 5520 8.2ver
>
>
>
> Hence i am looking forward to know is there any way we can restrict WINXP
> OS users to connect only to old SSL Client and WINdows 7 OS users
>
I don't think this is possible. If it's a Windows domain, I would recommend a
GPO to push out the AnyConnect msi rather than a temporary workaround.

-ryan

Blogs and organic groups at http://www.ccie.net
Received on Mon Sep 27 2010 - 01:02:19 ART