Have a retail customer in the middle of an ISE deployment w/AnyConnect NAM. Their current retail workflow utilizes Microsoft’s fast user switching to allow them to move quickly between open applications and users. As the documentation states, the AnyConnect NAM does not support this, and actually disables the capability as a result of the install. There is a work around published to re-emable fast user switching via registry change, but the issue with this work around, and even utilizing the native Windows supplicant is that there isn’t an event triggered from the supplicant that initiates a new user login, and from a session perspective the original user’s sessions is carried across.
While I understand that the preferred and most logical method is to change workflows to log off and back on again, the customer is concerned that this additional delay will reduce the productivity of the employees and is pushing back. We have informed them that from our research, there are no other work arounds other than Machine validation only, or disabling fast user switching.
I’m looking for comments on validating that this is an accurate understanding of the documentation as I have read it and what we typically see for larger retail customers from a deployment perspective, or if there have been other solutions that have been provided that we can use to our advantage here. Customer is pushing back saying they can’t be the only one that has run into this before.
Thank you for any info
