02-15-2016 03:23 AM
Hello,
we're about to roll out AnyConnect to our remote users, but supporting or upgrading our thin clients is a bit troublesome. Anyone any experience with this or recommendations?
Thin clients have their own proprietary OS. Users have no rights to write onto the box per se. AnyConnect tries an auto-connect once the user logged in to the box.
In order to upgrade the device, the user needs to log out from the box without killing the VPN session. An admin then logs in, sets the box to allow write operations and restarts it in order for that change to take effect.
As the user will again be autoconnected the same process of logging out of the box with VPN persistent has to be performed. The admin can now upgrade the box etc. and set it to read only again when done. Then another restart is necessary.
The whole process is really cumbersome. Anyone any ideas how to make it more user friendly? A user with admin/write rights is a no-go.
Cheers...
02-15-2016 11:04 AM
Do the boxes support running a privileged shell or command?
If so, you could create a magic user called "upgrade". Have the users login as "upgrade" once, and then have AnyConnect start a command to run a privileged shell, and run the upgrade. If you can't do the upgrade directly perhaps you can download the image and add it to the devices startup sequence to run once, and then have the script reboot the system. Something like that anyway.
Another option is a box swap. Prep 5 devices with the new client. Swap them out, and then prep the next batch.
02-22-2016 05:20 AM
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