10-19-2017 05:05 PM - edited 03-12-2019 04:38 AM
Hi Everyone,
Has anyone had issues using the Cisco Any Connect Mobility Client with Cisco Network Access Manager in Windows 10?
Our environment includes a wired network, which if not hard wired, switches to a wireless network that replicates our internal wired environment. This has worked extremely well with our Windows 7 images over the years, but as mentioned Windows 10 it is not integrating nicely.
We have tested with different Windows 10 builds, different models, different versions of the Cisco clients (4.5 or 4.7) . Furthermore, we have seen it on Dell laptops and tablets, as well as HP laptops and tablets and a variety of docking stations.
Below are some symptoms:
- Issues connecting to internal network after undocking and re-docking, but can also occur without undocking/redocking.
- Usually switches to a external wifi and IP (usually displays network 2).
- Can connect to the internet, just cannot access any internal resources.
- Typically a temp fix is a reboot.
- We have tried updating to the latest drivers as per the manufacturer websites and other system settings, to no avail.
The issue seems be fine after Network Access Manager is removed, whether it is version 4.5 or 4.7. We have custom config files so everything seems to point to these files not being in the right location/s for Network Access Manager.
Can anyone clarify, if you have custom files specifying the network priorities, what location/s should they be in? So far we've seen:
C:\ProgramData\Cisco\Cisco AnyConnect Secure Mobility Client\Network Access Manager\system
C:\ProgramData\Cisco\Cisco AnyConnect Secure Mobility Client\Profile
Should there be a folder somewhere under C:\Users\AppData as well?
Any input or pointers would be great.
Thanks
01-09-2019 12:45 PM
The custom NAM config file should be placed in C:\ProgramData\Cisco\Cisco AnyConnect Secure Mobility Client\Network Access Manager\newConfigFiles then run a network repair. This will make the NAM client update the profile.
For fresh installs you can put your NAM config file in profiles folder under nam in the AnyConnect package as well. This will install NAM profile.
Also make sure your config file is always named as configuration.xml
Let us know if this helps.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide