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

[oumodom]

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.

[ahollifield]

Do you use ISE Posture?  

[oumodom]

Hi @ahollifield 

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

[ahollifield]

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.

[oumodom]

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? 

[ahollifield]

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

[oumodom]

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

[ahollifield]

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.

[oumodom]

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