I setup OMA and anyone who tries to access the URL gets:

  Your user account has not been enabled for wireless access. Please contact 
your system administrator for additional assistance.

--I verified that user accounts in Active Directory have OMA enabled 
(default).
--I am attempting to use SSL.  It is configured for our OWA install which is 
on the same server.
--When I am prompted for login information, it seems to be authenticating 
against the local exchange server NOT active directory.  Is that expected?

OMA setup appears to be really straightforward, yet I simply cannot get it 
to work.  Any suggestions are greatly appreciated.

Jeff

I think i found the issue documented in 
http://support.microsoft.com/kb/817379

We are requiring SSL on the default website and have forms based 
authentication enabled.  We also only have one Exchange server which serves 
as the FE and BE.

The workaround is scary. . . .but so is asking for $$$ to reconfigure and 
re-architecht our environment

Jeff

"Jeff"  wrote in message 
news:edgGzFqCIHA.2004@TK2MSFTNGP06.phx.gbl...
>I setup OMA and anyone who tries to access the URL gets:
>
>  Your user account has not been enabled for wireless access. Please 
> contact your system administrator for additional assistance.
>
> --I verified that user accounts in Active Directory have OMA enabled 
> (default).
> --I am attempting to use SSL.  It is configured for our OWA install which 
> is on the same server.
> --When I am prompted for login information, it seems to be authenticating 
> against the local exchange server NOT active directory.  Is that expected?
>
> OMA setup appears to be really straightforward, yet I simply cannot get it 
> to work.  Any suggestions are greatly appreciated.
>
> Jeff
>
>

Even worse news, Exchange 2007 does not include OMA.  With Windows Mobile 6 
now out, why would anyone need OMA?

-- 
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2008
Microsoft Certified Partner


"Jeff"  wrote in message 
news:u17mCXqCIHA.2324@TK2MSFTNGP03.phx.gbl...
>I think i found the issue documented in 
>http://support.microsoft.com/kb/817379
>
> We are requiring SSL on the default website and have forms based 
> authentication enabled.  We also only have one Exchange server which 
> serves as the FE and BE.
>
> The workaround is scary. . . .but so is asking for $$$ to reconfigure and 
> re-architecht our environment
>
> Jeff
>
> "Jeff"  wrote in message 
> news:edgGzFqCIHA.2004@TK2MSFTNGP06.phx.gbl...
>>I setup OMA and anyone who tries to access the URL gets:
>>
>>  Your user account has not been enabled for wireless access. Please 
>> contact your system administrator for additional assistance.
>>
>> --I verified that user accounts in Active Directory have OMA enabled 
>> (default).
>> --I am attempting to use SSL.  It is configured for our OWA install which 
>> is on the same server.
>> --When I am prompted for login information, it seems to be authenticating 
>> against the local exchange server NOT active directory.  Is that 
>> expected?
>>
>> OMA setup appears to be really straightforward, yet I simply cannot get 
>> it to work.  Any suggestions are greatly appreciated.
>>
>> Jeff
>>
>>
>

Yikes, that is even worse news.

My solution to the requestor was I would research options in E2K7. . . the 
driver for this is one (yes 1) person in our environment who bought an Apple 
iPhone and wants to get Exchange data on it.  I was going to use OMA and 
ahve him use his mobile web browser.

Oh well, I need to research E2K7 for other reasons. . . .

Jeff

"John Oliver, Jr. [MVP]"  wrote in message 
news:4975A966-4653-4D2B-A5E3-F616D7854FBB@microsoft.com...
> Even worse news, Exchange 2007 does not include OMA.  With Windows Mobile 
> 6 now out, why would anyone need OMA?
>
> -- 
> John Oliver, Jr
> MCSE, MCT, CCNA
> Exchange MVP 2008
> Microsoft Certified Partner

On Tue, 9 Oct 2007 14:46:25 -0500, "Jeff" 
wrote:

>
>Yikes, that is even worse news.
>
>My solution to the requestor was I would research options in E2K7. . . the 
>driver for this is one (yes 1) person in our environment who bought an Apple 
>iPhone and wants to get Exchange data on it.  I was going to use OMA and 
>ahve him use his mobile web browser.
>
>Oh well, I need to research E2K7 for other reasons. . . .
>
Solution for the iPhone is IMAP. It's certainly not OMA. IMAP is
included in Exchange 2007.

"Jeff"  wrote in message 
news:edgGzFqCIHA.2004@TK2MSFTNGP06.phx.gbl...
>I setup OMA and anyone who tries to access the URL gets:
>
>  Your user account has not been enabled for wireless access. Please 
> contact your system administrator for additional assistance.
>
> --I verified that user accounts in Active Directory have OMA enabled 
> (default).
> --I am attempting to use SSL.  It is configured for our OWA install which 
> is on the same server.
> --When I am prompted for login information, it seems to be authenticating 
> against the local exchange server NOT active directory.  Is that expected?
>
> OMA setup appears to be really straightforward, yet I simply cannot get it 
> to work.  Any suggestions are greatly appreciated.
>
> Jeff

Before going to the trouble of doing the KB817379 procedure (which does 
normally solve the SSL problem), try temporarily turning off the requirement 
for SSL on your Exchange Virtual Directory, and see if OMA works okay.

Lee.

-- 
______________________________________

Outlook Web Access For PDA , OWA For WAP
www.leederbyshire.com
email a@t leederbyshire d.0.t c.0.m
______________________________________

> Solution for the iPhone is IMAP. It's certainly not OMA. IMAP is
> included in Exchange 2007.

IMAP is Ok for mail but won't give users a view of their calendar from the 
iPhone. . .

Jeff

> Before going to the trouble of doing the KB817379 procedure (which does
> normally solve the SSL problem), try temporarily turning off the 
> requirement for SSL on your Exchange Virtual Directory, and see if OMA 
> works okay.

I can try that. . .but if that does correct the issue, then what? We want to 
require SSL for accessing OWA. . .

Also, we will be moving to E2K7 in the next few months.  If OMA is 
depricated, then it's kind of a moot point. .  .

Jeff

On Wed, 10 Oct 2007 11:06:08 -0500, "Jeff" 
wrote:

>
>
>> Solution for the iPhone is IMAP. It's certainly not OMA. IMAP is
>> included in Exchange 2007.
>
>IMAP is Ok for mail but won't give users a view of their calendar from the 
>iPhone. . .
>
>Jeff 

Yeah well, shouda got a Windows Mobile, BlackBerry or a phone you can
use the RoadSync on shouldn't they.

>
> Yeah well, shouda got a Windows Mobile, BlackBerry or a phone you can
> use the RoadSync on shouldn't they.

Point taken. . .    I am going to let our policymakers deal with that one 
;)

That'll be a barrel ' laughs.
Any policy makers who let business users connect to the Exchange
server with an iPhone without coming to you or someone with a decent
set of business requirements (hell, you already know all that!!)

"Jeff"  wrote in message 
news:uIb7Oh1CIHA.2004@TK2MSFTNGP06.phx.gbl...
>
>> Before going to the trouble of doing the KB817379 procedure (which does
>> normally solve the SSL problem), try temporarily turning off the 
>> requirement for SSL on your Exchange Virtual Directory, and see if OMA 
>> works okay.
>
> I can try that. . .but if that does correct the issue, then what? We want 
> to require SSL for accessing OWA. . .
>
> Also, we will be moving to E2K7 in the next few months.  If OMA is 
> depricated, then it's kind of a moot point. .  .
>
> Jeff

If it does correct the issue, then you will need to use KB817379 .  It's not 
too complicated, and you can ask about it if you need any assistance.

OMA is not included with E2007.  If you still need that kind of 
functionality, I've done a PDA version of OWA that is better (IMHO) than OMA 
. http://www.leederbyshire.com

Lee.

Lee is right.

Use method 2 of the article, it works perfectly and can be implemented in 5 
minutes.

Helio

"Lee Derbyshire [MVP]" <email a@t leederbyshire d.0.t c.0.m> wrote in 
message news:uYMDqM2CIHA.1188@TK2MSFTNGP04.phx.gbl...
> "Jeff"  wrote in message 
> news:uIb7Oh1CIHA.2004@TK2MSFTNGP06.phx.gbl...
>>
>>> Before going to the trouble of doing the KB817379 procedure (which does
>>> normally solve the SSL problem), try temporarily turning off the 
>>> requirement for SSL on your Exchange Virtual Directory, and see if OMA 
>>> works okay.
>>
>> I can try that. . .but if that does correct the issue, then what? We want 
>> to require SSL for accessing OWA. . .
>>
>> Also, we will be moving to E2K7 in the next few months.  If OMA is 
>> depricated, then it's kind of a moot point. .  .
>>
>> Jeff
>
> If it does correct the issue, then you will need to use KB817379 .  It's 
> not too complicated, and you can ask about it if you need any assistance.
>
> OMA is not included with E2007.  If you still need that kind of 
> functionality, I've done a PDA version of OWA that is better (IMHO) than 
> OMA . http://www.leederbyshire.com
>
> Lee.
>
>