Migrating from Anyconnect to Secure Client

[gaigl]

Hello,

one more question about migrating to Secure Client:

we use AnyConnect with SBL, authentication with Machine Cert, only Windows 10/11, as Custom Attribute "dynamic-split-exclude-domains", no posture or something else.

Firepower 21xx and 41xx with ASA 9.18.x, ASDM 7.19.x

Is there any Problem to expect? Anything to care about?

thank you

Karl

[Milos_Jovanovic]

Hi @gaigl,

All of this is supported on Secure Client same way as it is supported on AnyConnect. You can see guidelines here. However, I do believe they are exactly the same as for AC v4.10.

Just make sure you go with latest release, as it fixes most of the known bugs.

Kind regards,

Milos

[gaigl]

thank you, then I'll try

[gaigl]

So now I've tried an Update -> failed:

with the new Client in a public net I don't get a name Resolution, so the Client can't find the Gateway.

The Client in our LAN: no Problem

With AnyConnect 4.x that's no Problem.

Any Idea where to fix this?