HELP! OMA "Device type Not Supported"

Our exchange server is running great, OWA works fine... but I'm having problems with OMA.

logging into  I get the following message:

"The device type you are using is not supported.
then it lists the User Agent

The device type you are using is not supported. Press Ok to continue.

Ok, and do not warn me again

I'm able to select OK and continue into my mail.  However I don't want this question to appear at all.  I suspect this is the reason I cannot get our blackberries to sync up to our exchange server.  

Yes, I already have 'Enable unsupported devices' checked under ESM/Global Settings/ Mobile Services.

Ideas?  This all stems from the fact that I'm unable to setup t-mobile Outlook Web Access accounts on our blackberries at the office.  Even though OWA works just fine anywhere, I suspect tmobile/blackberry is using OMA to log into our exchange server to get the e-mail and not using our OWA.  But I could be wrong.  

Who is Participating?
lastlostlastConnect With a Mentor Commented:
as i mentioned earlier... i don't have much information regarding /oma...

i came across an article that mentions the same error that you had initially mentioned... according to it... it's normal...

also check this article and see if it helps you out...
afaik... blackberry devices will get their emails from the BES server that you have... BES sync these mails from the Exchange server... and 'No' this should have no affect if /oma is working or not... u need to check the settings on BES...

for OMA, which is the device that you are using that you get the error message on?
is it a blackberry device or a normal pda device?
Scot_FAuthor Commented:
Sry should have been more clear.  Only one exchange server and no BES.  We are obtaining e-mail (e-mail only) on the blackberry device through t-mobile's "internet e-mail" option which supports OMA as the e-mail source.  See attached picture.  
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

ok... even in the screenshot that you provided... the address that you put in is "".... even in that case the request will go to /exchange and not /oma...

still am not sure...coz i don't have much idea as to how it works... am telling you just from the screenshot provided....

anyways... do you use a SSL certificate on the Exchange server?
Scot_FAuthor Commented:
Yes SSL certificate is installed... I even tried on the t-mobile site (no luck).    

"even in that case the request will go to /exchange and not /oma..."
That's what I thought but access to mail via /exchange works (for our exchange server) in any browser anywhere except on the blackberry.  

The only problem I see on our exchange server is when you go into the mail via /oma and it pop's up that error (see first post).  There's lots of talk about mobile device exchange access via /oma on the net.  So I thought our problem might be related with the /oma error.  Sounds like I'm just going down the wrong rabbit hole...

Talked at length with tmobile and they don't see what the problem is as well (regarding the BB OWA integration).  I even had them log into a test account on our exchange server via /exchange from their browser and they were successful.  

Scot_FAuthor Commented:
No worries...

I finally got a hold of blackberry... And you were correct "the request will go to /exchange and not /oma..." So the whole /oma issue is mute.  My problem (apparently) was I didn't have an ending / in the OWA URL (

Thanks for the help
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.