Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi Bobby,Yes — that's the right switch. Set "Group Policy with RADIUS Filter-Id" to Enabled, and since your Authentication Type is already RADIUS, the MX side is ready.One thing matters just as much though: enabling that toggle only tells the MX to h...
Hi Bobby,Your screenshot tells the story: you're on AnyConnect, and you're pinning the policy manually under Network-wide → Clients → Device Policy. That manual pin is the cause — it's tied to the client entry, so when the client re-identifies (new s...
Hi Bobby,Before you consider making any significant change — one check first. This started the day you went to 19.2.8 and it hits both VPN and wired clients at once, which is the signature of a firmware regression, not a flaw in how you assign polici...
Hi Bobby,The key question is how the policies are assigned, because that decides the cause:Manually applied (Network-wide → Clients → Policy): pinned to the client's identity (MAC). Not permanent — if a client ages out of the client list or its ident...
Hi manuela-weiss,Webex doesn't let you set a custom coloured dot, but it does have an unread indicator and pop-up alerts that should stop you missing messages — they're probably just turned down. Two things to check:Notifications (the real fix): prof...
