Has anyone developed a process to identify who’s ZApp agents are turned off or not running? Seems there are no alerts or reports. My concern is that service desk is disabling agents when troubleshooting and forgetting to turn the agents back on. I know it gets turned back on on reboot, but with Mac users, they can go days without a reboot.
Today the best way to determine this is based on the devices last seen date. If this is current it is still online.
We are adding some capabilities soon that should also help with this also, which include a grace period for re-enabling services automatically, and also displaying a current status in the Zscaler App Portal to indicate if users have logged out or not.
Thanks David. Where can I find the value for devices last seen date?
You can find this by going to Policy -> Zscaler App Portal -> Enrolled
Devices, then select/click the device.
Thank you @skottieb! I didn’t know there were more details. After I exported the list I have everything I need. I will use this method in the meantime.
@dcreedy Are there any updates on the additional features for checking ZApp status and forcing app to connect after grace period?
These are still planned for the next release which is in development now.
I can’t comment on the timelines at this point.
Does this refer to back end functionality or the app? Our new security folk are not impressed we can’t force the app on if it is turned off. We still have 1.3.1 of the app and can’t see anything relating into this in the 1.4.x release notes.
We’ve added grace period for ZIA to the 1.5 release, which is currently being updated on all clouds. You can view the release notes for this here: https://help.zscaler.com/z-app/zscaler-app-1.5-release-notes
We are upgrading all of the clouds to the associated mobile portal release over the next few weeks.
Thanks David, appreciate the response. Our Sec guys will be pleased.
Is it recommended to upgrade incrementally through the 1.4.x versions or are these changes rolled up in version 1.5?
All the changes are rolled up, however we only support direct upgrading from previous supported versions, generally N-2. If you are running 1.3, I’d recommend first upgrading to 1.4 and then to 1.5, primarily so that if there are problems during the upgrade we can pin point where the issue was.