topic Re: Failed Upgrade from AnyConnect v4.9 to Secure Client 5.1 via SCCM in Network Access Control

Failed Upgrade from AnyConnect v4.9 to Secure Client 5.1 via SCCM

oumodom — Mon, 30 Sep 2024 06:22:23 GMT

Dear Cisco ISE lover,

I would like to get your support on my case failed deployment from SCCM upgraded from v4.9 AnyCon to v5.1 Secure client. As we deployed we can see 10 endpoints, successfully upgraded just only 5 endpoints and found issue related to posture file C:\ProgramData\Cisco\Cisco AnyConnect Secure Mobility Client\ISE Posture, No file ConnectionData.xml.

Please kindly share/suggest your idea to address to issue.

Re: Failed Upgrade from AnyConnect v4.9 to Secure Client 5.1 via SCCM

ahollifield — Mon, 30 Sep 2024 12:05:37 GMT

Do you use ISE Posture?

Re: Failed Upgrade from AnyConnect v4.9 to Secure Client 5.1 via SCCM

oumodom — Wed, 02 Oct 2024 13:11:39 GMT

Hi @ahollifield

We use ISE posture (Compliance module agent v4.3.3335. and also Posture agent (v4.9 and & 5.1)).

Re: Failed Upgrade from AnyConnect v4.9 to Secure Client 5.1 via SCCM

ahollifield — Wed, 02 Oct 2024 13:29:24 GMT

Is the compliance module up to date? It seems to me like this is an issue with the way SCCM is upgrading the package. What if you manually copy the XML file to the correct location? That should be generated automatically though when the agent connects to the PSN.

Re: Failed Upgrade from AnyConnect v4.9 to Secure Client 5.1 via SCCM

oumodom — Wed, 02 Oct 2024 13:45:19 GMT

Hi @ahollifield

For manually upload posture file.xml into path secure client 5.1, it is working well.
Compliance module agent v4.3.3335 is the stable one for anyconnect v4.9 and Secure Client 5.1

The strange thing happened as some endpoints are got this posture file.xml with new location (C:\ProgramData\Cisco\Cisco AnyConnect Secure Mobility Client\ISE Posture), and some endpoint failed with posture, just having path of secure client 5.1, but the posture file is still located in path C:\ProgramData\Cisco\Cisco AnyConnect Secure Mobility Client\ISE Posture.

What should I do now to address this issue?

Re: Failed Upgrade from AnyConnect v4.9 to Secure Client 5.1 via SCCM

ahollifield — Mon, 07 Oct 2024 12:28:47 GMT

It sounds like your SCCM deployment is copying the files to the wrong directory.

Re: Failed Upgrade from AnyConnect v4.9 to Secure Client 5.1 via SCCM

oumodom — Mon, 07 Oct 2024 18:09:14 GMT

@ahollifield based on your experienced, Could you share how to properly deploy upgrading version via SCCM please?

Re: Failed Upgrade from AnyConnect v4.9 to Secure Client 5.1 via SCCM

ahollifield — Mon, 07 Oct 2024 19:15:27 GMT

I don't have the experience for that unfortunately. That piece has always been handled by customer's SCCM team directly. I only commented on the symptoms sounded like an issuer with the installer from SCCM.

Re: Failed Upgrade from AnyConnect v4.9 to Secure Client 5.1 via SCCM

oumodom — Thu, 17 Oct 2024 02:33:20 GMT

@ahollifield No worry,
Appreciated for your comment and idea.