At my place of work we use Samsung Galaxy S5 handsets, each of which is managed by BES12. This solution has been working just fine until a recent update to the supporting Secure Work Space application.
Since the update some handsets have been refusing to display the secure work space, citing that the Administrator has disabled it due to policy restrictions.
After much searching it seems that the only difference on the devices is the "SE for Android status"; some are July 12th 2015 (working), while others (not working) are April 27th.
The devices each have the exact same OTA update applied, with the same "Basebuild version", "Build number", etc.
I find this strange, as to my knowledge the security updates should also have come OTA as well, but clearly they are not happened.
So my question is two part -
1 - Does anybody know a way to force the update so that all are on the same version?
2 - Does anybody know why this issue has occurred in the first instance?
Since the update some handsets have been refusing to display the secure work space, citing that the Administrator has disabled it due to policy restrictions.
After much searching it seems that the only difference on the devices is the "SE for Android status"; some are July 12th 2015 (working), while others (not working) are April 27th.
The devices each have the exact same OTA update applied, with the same "Basebuild version", "Build number", etc.
I find this strange, as to my knowledge the security updates should also have come OTA as well, but clearly they are not happened.
So my question is two part -
1 - Does anybody know a way to force the update so that all are on the same version?
2 - Does anybody know why this issue has occurred in the first instance?
Facebook
Twitter
Instagram