Zenprise version 7.0 was released today, adding more mobile device management features, Android support for their file syncing client, and one-click device enrollment.
Zenprise has at its core a standard mobile device management product for iOS, Android, BlackBerry, Windows Mobile, and Symbian. Zenprise uses devices’ built-in email clients and unmodified, native apps—no dual persona sandboxing or app wrapping from them. Zenprise can be cloud-based or installed on-premise, and they also have a mobile file-syncing solution that uses customers’ existing storage.
New features for Zenprise 7.0 include:
- Location or network-based management policies. For example, a device could be wiped or locked if it’s taken off of a particular network or out of a particular area.
- An Android client for their mobile file syncing product (previously only available for iOS)
- The ability to add annotations to files in the iOS file syncing client app.
- Support for Samsung SAFE (Samsung Approved For Enterprise). SAFE is a set of custom APIs that add extra management features for certain Samsung Android. In this case, Zenprise touted the ability to lock tablets down into a kiosk mode, for use in retail and hospitality settings.
- One-click device enrollment.
These new features are all welcome additions. Support for Samsung SAFE will be good for both parties (expect a deep dive into SAFE soon in this blog), and the one-click device enrollment is a really nice feature for them to have. After working with some MDM products that require entering usernames and other credentials, the speed will be greatly appreciated. Overall, though, the Android file syncing client will make the biggest difference for users. We’ve written before that modern file syncing should be the first priority for any mobile effort, and now that Zenprise is adding support for this huge swath of the market, they’ll have a lot more opportunities.
(Note: You must be logged in to post a comment.)
If you log in and nothing happens, delete your cookies from BrianMadden.com and try again. Sorry about that, but we had to make a one-time change to the cookie path when we migrated web servers.