Anyconnect NAM and Windows Native Supplicant

[dan.letkeman]

Hello,

Would anyone know if there is a way to integrate the native windows supplicant with the Anyconnect NAM?  It seems that the windows supplicant knows when you are connected to a wireless network using the Anyconnect NAM, but when you want to connect to a new network using the native supplicant it just sits there and says connecting.....

This seems like an odd way to present a connection error to an end user and would cause unwanted helpdesk tickets.   Not to mention that it is not intuitive to have to go into the Anyconnect NAM to connect to a network vs using the native supplicant.

Can you have the native supplicant re-direct users to the Anyconnect NAM when a user tries to connect to a wireless network?

Thanks,
Dan.

[Rahul Govindan]

Not that I know of. But you can remove the networking icon to show up on the task bar using GPO This is mentioned in the Anyconnect Admin guide:

http://www.cisco.com/c/en/us/td/docs/security/vpn_client/anyconnect/anyconnect40/administration/guide/b_AnyConnect_Administrator_Guide_4-0/configure-nam.html

"Confusion about the Windows network status task tray icon—Network Access Manager overrides Windows network management. Therefore, after installing the Network Access Manager, you cannot use the network status icon to connect to networks.

Recommended Action   Remove the Windows network icon from the task tray by setting Remove the networking icon in a Windows group policy. This setting affects only the tray icon. The user can still create native wireless networks using the Control Panel."