This post will go into the steps that happen during the OMA 2003 logon process. As I work in Support Services, I get to explain this a lot so I wanted to share it. The general flow goes like this: ...
Updated Jul 01, 2019
Version 2.0
Blog Post
Hi,
Found this topic very interesting, but it doesn't quite give me the answer to my problem.
I have SBS 2003 exchange and am trying to use OMA. I have the exchange configured correctly - I think - and can access OMA from a desktop browser and a wap enabled phone, but when I try and access OMA from an Orange Smartphone SPVM2000, it seems to hang. When I type the URL in IE, the screen with Inbox, Calendar etc. is displayed and in the address field I get what I assume to be a session id - changes every time I try. However, when I click on the inbox or calendar, nothing happens. Also, I don't get the MSExchangeOMA event log message saying the OMA browser application has started. I do get this message when I access OMA from another device. I'm assuming it may be related to the smartphone using cache. It also doesn't request username and password as I requested those details to be saved the first time I tried. I've cleared the history and deleted files on the smartphone, all to no avail. Has anyone experienced this, or have any odeas what it may be.
Any hekpl would be gratefully received.
Jason
Found this topic very interesting, but it doesn't quite give me the answer to my problem.
I have SBS 2003 exchange and am trying to use OMA. I have the exchange configured correctly - I think - and can access OMA from a desktop browser and a wap enabled phone, but when I try and access OMA from an Orange Smartphone SPVM2000, it seems to hang. When I type the URL in IE, the screen with Inbox, Calendar etc. is displayed and in the address field I get what I assume to be a session id - changes every time I try. However, when I click on the inbox or calendar, nothing happens. Also, I don't get the MSExchangeOMA event log message saying the OMA browser application has started. I do get this message when I access OMA from another device. I'm assuming it may be related to the smartphone using cache. It also doesn't request username and password as I requested those details to be saved the first time I tried. I've cleared the history and deleted files on the smartphone, all to no avail. Has anyone experienced this, or have any odeas what it may be.
Any hekpl would be gratefully received.
Jason