InterNoded and Zenprise unveiled new versions of their applications for managing different parts of the BlackBerry world for enterprise users. The vendors demonstrated their respective releases at Research in Motion's Wireless Enterprise Symposium going on this week in Orlando.

Both companies are strengthening their ability to work with Microsoft server and client platforms, to centralise management across mixed-vendor mobile deployments. InterNoded focuses on administering and managing the mobile devices, while Zenprise automates monitoring and troubleshooting the entire BlackBerry mobile messaging infrastructure.

InterNoded introduced its InterNoded Mobile Device Manager (MDM) in late 2006, initially creating a single administrative view of the assets and behaviour of BlackBerry handhelds, across multiple BlackBerry Enterprise Server (BES) domains, with either Microsoft Exchange or Lotus Notes on the back end. MDM can set and enforce an array of policies, such as turning off a BlackBerry's onboard camera, and lets administrators optimise user and BES performance by load-balancing across multiple back-end servers.

The most recent version, 3.0, of the application added support for Windows Mobile devices and for Good Mobile Messaging. A Web portal gives users immediate self-service help and configuration tools.

Version 4.0 has been retooled to support two new optional features.

One is the MDM Inspector, a small client application that installs on the target handhelds, captures an array of local details about the device, and feeds it back to the InterNoded server. Coupling this with each user's profile, an administrator can see summaries and details of the device, such as its operating system and installed applications, and use a PIN number to create a record of activities and problems associated with that device.

The data can be used not only in trouble-shooting problems that arise, but avoiding those problems. "We built [Inspector] to do application and policy management," says Julie Palen, InterNoded's president and CEO. "I can see their [client] OS, the available memory, how much of that is free. I can see all users with less than 500Kbits of memory remaining, and plan memory or device upgrades."

Inspector also verifies that new policies created centrally have been successfully deployed to each target device.

The second new option is a full-blown application management program for provisioning devices with software. MDM version 3.2 could schedule software updates through the BES server. The new version goes further, using a rules engine to set policies and controls on which users or groups of users get which applications or updates and when."When you push out an application, we [now] can control that whole piece," Palen says.

This application management feature can work with an array of third-party mobile applications, and can either work with the provisioning features of those products or rely on its own.

Version 4.0 is targeting a very similar set of mobility challenges as Microsoft's just-released System Center Mobile Device Manager 2008. "In a pure Microsoft shop, with Systems Center [deployed], I probably won't add value to that, unless price is a consideration," Palen says.