Symbian OS /Unknown OS

Usage and Config MDM
1

(imported topic written by shedd44)

Hello,

I try manage Symbian phones devices through our Management Extender for Exchange, but in TEM console show as Unknown OS and I cannot manage it.

Roman Sobota

2

(imported comment written by BenKus)

Hey Roman,

There is a mapping between the activesync names and the “friendly OS names”… Do you know what kind of device it is?

Ben

3

(imported comment written by DTan)

To help troubleshooting this, we have added Analysis#140 to the MDM Production site (Version#12).

Please activate that analysis to find out what ActiveSync User Agent string you Exchange Server is using to describe the model/type of your Symbian device.

Feel free to post the ActiveSync User Agent string here or send it to us, so that we can add entry to the DeviceMapping.csv that is used by the MS Exchange Extender.

-Dawson

4

(imported comment written by shedd44)

Hello,

there is some ActiveSync User Agent strings:

NokiaC600/2.05(0)MailforExchange 3gpp-gba

NokiaC503/3.00(109)MailforExchange 3gpp-gba

NokiaE71/3.00(50)MailforExchange

NokiaN97/3.00(73)MailforExchange

NokiaE51/1.0

NokiaE66/2.09(176)MailforExchange

NokiaE600/1.00(0)MailforExchange 3gpp-gba

NokiaE700/1.00(0)ActiveSync 3gpp-gba

NokiaE521/2.02(0)MailforExchange 3gpp-gba

SAMSUNG-GT-I8150/100.20306 - it is Androind OS

SAMSUNG-GT-I9100/100.20304 - it is Androind OS

SAMSUNG-GT-S5660/100.202 - it is Androind OS

NokiaE721/2.02(0)MailforExchange

NokiaN97mini/3.00(73)MailforExchange

Roman

5

(imported comment written by DTan)

Hi Roman,

We have published Fixlet#142 “Updated DeviceMapping.cvs Now Available” in MDM Production site (Version#16). Please try it out and let us know if you still have issue.

In the future release, we will enhance this work flow further by applying this mapping automatically.

-Dawson

6

(imported comment written by shedd44)

Hi Dawson,

it works fine, but if I try wipe Symbinan device, action wipe still ends with fail status.

Is there any steps(prereq) or see some log to find why action failed.

Roman

7

(imported comment written by DTan)

You can check below two folders on the Management Extender machine:

Proxy Agent Log:

C:\Program Files (x86)\BigFix Enterprise\Management Extender__Logs

Exchange Plugin Log:

C:\Program Files (x86)\BigFix Enterprise\Management Extender\plugin

8

(imported comment written by shedd44)

Thanks,

I find error.

Roman