RE: OWA/Mobile not working + 1054 and 506 errors
- From: v-robmen@xxxxxxxxxxxxxxxxxxxx ("Robbin Meng [MSFT]")
- Date: Fri, 04 Jul 2008 10:54:49 GMT
Hello Larry,
Thank you for your post.
Please allow me to confirm that my understandings are correct. As I
understand it, the issue is:
You have recently converted a three-server domain (front end running ISA
2006, two DCs, one running Exchange 2003 SP2) to a single server SBS 2003
R2. Conversion is not smoothly and both OWA and OMA didn't work properly.
If I have misunderstood your concerns please feel free to let me know.
First, based on your latest reply, I am glad to know after you modified the
OWA virtual directory authentication, the OWA access works normally now.
Therefore, I would like to know:
1. Is the OMA begin to work now?
2. Do you still receive the Event ID 506 and 1054 error?
3. What are the current symptoms and situation?
Please understand, for every post in news group, it is recommended to only
focus on one issue at a time so that we can get the specific issue resolved
more efficiently and void confusion. So, please let me know what your main
concern is and would like to fix first. Thanks for your understanding.
Regarding OMA in SBS 2003 server, please see the following suggestions:
Changes to SBS 2003 During Setup of Exchange Server 2003
1. An additional Exchange virtual directory called Exchange-OMA is created
during SBS 2003 setup
2. Details of this new Virtual Directory:
a) This directory is used for OMA-Browse and OMA-Sync to connect to the
Exchange store. SSL cannot be required since it is not supported by OMA on
some devices. IP restrictions are never changed on this virtual directory
even if the entire site is exposed to the Internet.
b) Restricted access to the internal IP of the server and the loopback
address of 127.0.0.1.
c) SSL never required.
d) Authentication Methods: Integrated Windows Authentication and Basic
3. The built in OMA directory is configured to include the default domain
in the Authentication Methods.
4. In order for Exchange OMA and Server ActiveSync to be aware of the new
virtual directory, special configuration is required in the registry.
HKLM\System\CurrentControlSet\Service\MasSync\Parameters
a) The parameter added is called "ExchangeVDir"
b) The contents are "/Exchange-oma"
So you may need to contact the Mobile machine vendor to clarify some
information, because there are some devices that do not support using an
untrusted certificate, or that simply do not support adding certificates at
all. Pocket PC 2002 devices do not support untrusted certificates so they
would require either a trusted certificate, or they can be configured to
disable the trusted certificate.
This is the reason that SSL is not required on the exchange-oma virtual
directory.
If you use 3rd party certificate, please ensure the client install the
3rd-party certificate on the mobile device:
Deploying Windows Mobile 5.0 with Windows Small Business Server 2003
http://www.microsoft.com/downloads/details.aspx?familyid=8BE70D72-1E5A-4128-
A30C-DAFEEB43544D&displaylang=en
Note: See Option B in Step 4.
If we cannot resolve the issue after we perform the above steps, please
help me collect some information for further investigation:
Information Need
==============
1. Check event viewer on the SBS server for related information, if there
are anything related "OMA" or "ActiveSync", please help save it to *.evt
and send to me at v-robmen@xxxxxxxxxxxxx
2. If possible, please capture some screenshot when the error messages
appear and send them to me : v-robmen@xxxxxxxxxxxxx , or describe the
exact error messages appears on the mobile device.
More information to be noticed before you begin to upgrade, it is
recommended that you complete the following tasks:
How to Upgrade to Windows Small Business Server 2003 R2
http://www.microsoft.com/windowsserver2003/sbs/upgrade/default.mspx
Hope this helps. Also, if you have any questions or concerns, please do not
hesitate to let me know.
Thank you for your time and cooperation
Best regards,
Robbin Meng(MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- Follow-Ups:
- RE: OWA/Mobile not working + 1054 and 506 errors
- From: Larry Heimendinger
- RE: OWA/Mobile not working + 1054 and 506 errors
- Prev by Date: Re: Outlook over Internet Issues
- Next by Date: Re: VPN remote client not getting IP address
- Previous by thread: Re: OWA/Mobile not working + 1054 and 506 errors
- Next by thread: RE: OWA/Mobile not working + 1054 and 506 errors
- Index(es):
Relevant Pages
|