N900 report as Windows Mobile etc?
 

Hi,

My IT manager would like to know if there is the possibility to have maemo (specifically on the N900) report as windows mobile or palm os or anything else? Similar to firefox with setting the user agent.

I had a google search and a look in these forums but could not find any info on this. Has someone created a plugin or anything that achieves this?

Thanks!

Re: N900 report as Windows Mobile etc?
 

Sorry, just to elaborate - this is when communicating with exchange.

Re: N900 report as Windows Mobile etc?
 

Yes you can change it.

The Maemo Browser is base on Mozilla engine

http://i37.tinypic.com/2lat089.jpg

Re: N900 report as Windows Mobile etc?
 

Re: N900 report as Windows Mobile etc?
 

Sorry, what I meant is that when a mobile syncs with an exchange server for email, it identifies itself (such as palm os, windows mobile etc). Is there an option to have maemo/n900 set itself to report as another OS?

I was just using the user agent change in browsers as an example.

Thanks for the quick reply.

Re: N900 report as Windows Mobile etc?
 

So I guess no one knows?

Re: N900 report as Windows Mobile etc?
 

I doubt there is an easy way, if one exists at all since there is no obvious reason or need for doing this. I'm curious as to what your manager's reason for changing this is. I personally can't see any reason exchange would need this information to be altered.

Re: N900 report as Windows Mobile etc?
 

I'm assuming the application can't sync without it identifiying the device as Palm OS or WinMo?

Re: N900 report as Windows Mobile etc?
 

There are some existing MfE threads that one of the Nokia staff developers has been participating in. He might notice this thread tomorrow, or you could try those threads.

Re: N900 report as Windows Mobile etc?
 

AFAIK, ActiveSync doesn't care what the client is as long as it can speak the correct protocol. The only instance I can think of where there could be issues is if the Exchange server has required security policies set which the client ActiveSync implementation doesn't support - in this case there is probably no way to spoof client information to allow the client to connect without violating the ActiveSync protocol. (Note: I manage an Exchange install of 4 servers for about 1500 mailboxes, so I am familiar with the server side of things)