on 01-12-2016 2:24 PM
Hello experts.
Does Afaria support OMA -DM? Is it used only for Windows or for others devices too (Android, iOS)?
I would like to learn more about the interaction OMA –DM and Afaria 7.
Also.
In Android, iOS devices the Afaria client installed by downloading from Google Play or App Store.
However, Windows devices have a built-in client. Does this client (service) have a name?
Thanks.
Olga,
No OMA-DM is not supported in Afaria 7. OMA-DM is the old Nokia operating system and they haven't actually shipped any of these devices in years. It is neither windows or Android. It was a proprietary operating system.
For part two are you speaking of Windows Phone or 32 bit clients?
Tracy Barkley
Sr. Technical Support Engineer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Tracy,
Thanks for your help.
I am interested in the information about Windows Phones. Unfortunately I have no way to test the Windows Phone devices, so I don't know if it will be there the Afaria sign.
I know that every Windows 10 device (and also Windows 8.1 device) has mobile device management client that ships along with the operating system. And the syntax that MDM servers need to use to manage Windows devices using this agent is what we call the Windows Mobile Device Management protocols. There are two such protocols – one governing how a Windows device registers with the server so it can start managing the device called MS-MDE, and the second called MS-MDM governing how an MDM server can send down commands to manage the different settings (and which settings) on the Windows device.
So, what protocols are in Afaria and Windows devices?
Olga,
I am checking on the protocols for you but there are actually two clients possibly in use with Windows Phone. The first is the built in MDM client. This is where you enter your email address and the address of the MDM server. That client then activates and enrolls the device into Afaria. If you have your Afaria server set to deliver the actual signed Afaria client, it will download shortly after the enrollment completes.
The devices can still be managed without the Afaria client, but it is required for outbound. Otherwise the device only connects in on schedule and pulls whatever policies it needs at that time. If you wanted to outbound and apply policies on demand you will need the Afaria client as well.
Hope this helps,
Tracy
Olga,
Basically when you run the basic client you are providing the address of the server it will be connecting to. It reaches out to the MDM server (the Afaria server) and provides Afaria its information (email address) and the client gets whatever configuration Afaria is set up to give. That is about all that happens. I am not sure exactly what details you are looking for? The client merely calls on basic MDM functionality alreday present on the phone.
Tracy
User | Count |
---|---|
81 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.