Does anyone here know of any method to test a new Anyconnect deployment to a single user from the ASA?
Background: Tasked with the project of pushing anyconnect 4.9. I crashed coursed on ISE set up a client provision to restrict a single user and force the deployment of Anyconnect 4.9. Fast forward to the end of a long tac case it was determined that when attempting to provision a remote user from ISE the installer will fail due to the nature of the connection. Something with the VPN dropping purposefully which kills the connection to the internal ISE server.
So now the org is still wanting to test this deployment to a remote user. Does anyone have any ideas how I can single out a user to pull the Anyconnect 4.9 web deploy package from the ASA while still allowing all other users to utilize the existing 4.7 client.
I have already bumped my pc to 4.9 and have exhibited no issue but they are wanting a deployment test completed before moving the package to priority 1 on the ASA and force feeding it to all users.
Any ideas are appreciated, I had never screwed with Anyconnect prior to this gig so I am playing catch up.
No comments:
Post a Comment