Here the problems:
We have a lot of user connecting to the office remotely. We have some Windows Surface PC with Windows 10 which we which to upgrade to build 1709.
We are using CISCO anyconnect VPN for the connection with a profile for wired and Wireless with NAM.
Everything is working fine. The test user connects to the network with the client anyconnect, and the update packages is being pushed to the client. Then Windows 10 require the client to reboot the PC in order for the update to take place. Once we reboot, the anyconnect client and NAM comes up.,. but NAM doesn't see any WIFI connection anymore... so it is no longer possible to get the test user connected to the office, unless we deactivate the NAM on the network card ( which defy the all purpose of using NAM)
I am looking on the NET for some solutions... I still can't believe we are the only one expericing this problem.
We have tried three versions of anyconnect and we had the same problems:
4.5.04029, 4.5.2036, 4.4.00243)
Anyone has any ideas of what is happening... it feels like Windows 10 is doing something to NAM. Perhaps it is reactivating something and it is not letting NAM deactivate the Windows management of the card.
I thought it was something to do with this bug:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCva84287
But then again this is an old bug...
Any advice suggestions would be apprecitated.
