Mobile Device Management 2.1.0 beta1 provides additional device information
-
Kopano’s Mobile Device Management (MDM) provides the user an overview of the ActiveSync devices connected to their Kopano account. This includes mobile phones, tablets and also Outlook 2013 and 2016 clients. This first beta introduces a new dialog with additional device information to get a better overview of all device information directly from Kopano WebApp.
What’s new in this version?
This beta introduces a (pop-up) dialog with additional device information. This dialog shows extensive information about the device, sync times, the total amount of folders and the wipe status. If you have connected Outlook with the Kopano OL Extension, this dialog will also show version information of KOE.Additionally, the Z-Push version will be shown in the general settings in WebApp (this requires WebApp 3.2.0 or higher) and there have been minor bug fixes.
For the complete list, check out the changelog.
What’s next?
Before reaching the next final we still have another beta planned in. This beta will focus on implementing some features of the Z-Push shared folder API, that will allow you to add additional folders to your mobile phone. Apart from that we are planning on solving some display issues with the device details screen.Where do I get the packages?
The packages for this new version have been synchronized to the repositories, the portal and the download server! The MDM documentation is available on documentation.kopano.io. As always, the latest development version can be downloaded from the community download server. If you have any feedback, send an email to feedback@kopano.com or open a topic in our forum! -
Problem:
mdm-2.1.0.18_13-RHEL_6_PHP_56-noarch not seeing all devices connected through z-push:Config:
Z-Push: 2.3.5beta0+0
PHP-MAPI: 8.3.0-622
Webapp 3.3.0.432
mdm-2.1.0.18_13Our z-push-connector is currently used by 3 clients:
- iPhone 6C2/1404.27
- Outlook 2016
- Android Motorola (Android-Mail 7.1.1)
They behave without issues - connection-activity can be tracked for all 3 in z-push-top.
When I query the device-list in MDM, only 2 from 3 devices are displayed - the Android-device is missing:[xav@master]# z-push-admin -a lastsync All known devices and users and their last synchronization time Device id Synchronized user Last sync time Short Ids ----------------------------------------------------------------------------------------------------- 3d8171igqd5gl99ie4r6h7ej60 hias 2017-01-25 09:21 Yes 3d8171igqd5gl99ie4r6h7ej60 xav 2017-01-25 10:36 Yes android1437637182168 sepp 2017-01-25 10:13 Yes dd3ba2fe5b424ab294b723916e45602e hias 2017-01-24 18:35 Yes 518c602f1b5c4900858cc2e3c4db03bc xav 2017-01-24 18:58 Yes
Any ideas?
++umgfoin. -
Hello @umgfoin ,
I’m not sure if you misunderstood the plugin or I misunderstand you. You lastsync shows a total of four different device id’s (not three as you said before).
Could it be that the mdm shows you the two devices that are associated with your username? Because if yes, then this is actually the expected behaviour.
-
Hi Felix,
thanks for your reply - I suppose, you’re right: The 4th dev-id is from a second postbox, mounted in the same outlook instance . I’m seeing all devices with mailboxes associated to my user-name. Whereas an iPhone uses the same dev-id for two different mailboxes (hias and xav), outlook creates two separate dev-ids if more than one mailbox is mounted.I think my misunderstanding is that I’m expecting to see all devices (even from other users) in the mdm-tab, if I’m logged into webapp with admin-privileges.
Is it possible to force such behaviour or is the design to show only devices related to the logged-in user?++umgfoin.
-
@umgfoin said in Mobile Device Management 2.1.0 beta1 provides additional device information:
I think my misunderstanding is that I’m expecting to see all devices (even from other users) in the mdm-tab, if I’m logged into webapp with admin-privileges.
Is it possible to force such behaviour or is the design to show only devices related to the logged-in user?Yes, that is indeed not the intended behaviour. The original idea of the MDM plugin was to give the users the ability to manage their own devices, something that the admin otherwise can only do directly on the console.