We help IT Professionals succeed at work.

SBS 2003 - HTTP redirect not working & OMA not syncing with WM6 device

spudboy23 asked
Last Modified: 2013-12-05
I'm having two problems with a client's SBS 2003 machine, and try as I might I'm not having any luck resolving them. I'm hoping someone here can help out.

This SBS 2003 box was pretty messed up when I started on it. The person who set it up didn't understand how SBS works, so he simply installed the first part, then manually installed Exchange. When I started working on it, most of the SBS IIS functionality wasn't working (no monitoring, RWW, backups, companyweb, etc.). However, OWA and OMA were working correctly. I've spent a fair amount of time on it and I've managed to get everything working really well without having to re-install Exchange (which I'm trying very hard to avoid), except for these two issues:

1) normally when an SBS 2003 installation finishes correctly, HTTP: address requests to the server for OWA and RWW (and I think OMA, though this is the first time I've worked with OMA) automatically redirect to HTTPS. I read on another EE thread that this is supposed to be configured automatically by CEICW, but it is not working on this machine and I have had no success finding a way (including the CEICW) to make it work. When I try to access an HTTP address for this server for any of the exchange services or RWW, I get a "page not found" error. HTTPS works great. This behavior is the same internally or externally. I'd really like to get this function working again.

2) one of the client's Windows Mobile 6.1 device was able to synchronize mail & whatnot with this server before I repaired the other issues, but now now matter what I  try, I cannot get it to sync. I've tried recreating teh Exchange virtual directories, recreating the "exchange-oma" vdir, messing with SSL configurations and pretty much every KB procedure and solution I've found on EE and MSExchangeBlog.com and petri.co.il and a few other sites, but still no success. There are no errors recorded in the event logs when I try to access, it just says "error authorizing" on the phone and that's it.

I was able at one point to get OMA to load in a web browser via "https://servername/oma" and I could see mail and calendar items, but that was broken again when I continued to try resolving this issue by changing SSL settings. it is my understanding that OMA is supposed to be accessible via "http://servername/oma", not the secure address, but this simply gives a 404 error.

At this point I've spent a number of (unpaid) hours on this and gotten nowhere. I'm afraid to keep messing with things, especially the certificate and SSL settings, as the lone Mac on the network had some trouble sending mail through the server at one point, citing a certificate error. I suspect the OMA problem is related to the apparently well known conflict between OWA needing SSL and OMA requiring basic authentication only, and I'm hoping that by fixing the redirect issue that it will somehow magically resolve the problem.

I'd greatly appreciate any guidance or empirical wisdom from someone who's resolved this type of issue before. I don't know if there's some type of EAS logging that happens in WM6 that might help, but I know I'm not finding much useful info on the server itself. If I have to, I will re-install Exchange, but I'd very very much like to avoid this, as I can see that being a can of worms if something goes wrong.
Watch Question

Jerry SolomonNetwork  Administrator

It may seem like a personal failure to do this, but I would seriously consider this:
1. Get the keys to the building, a good book, and order Pizza.
2. Export all exchange mailboxes to PST, all usernames and passwords, and format- and reinstall the SBS the right way.  
Even if you get everyting kinda-working, you'll have a mess on your hands any time you need to fix something in the future.

I was too afraid to say the same thing so thanks to JerrytheGreat leading the way.  I have attempted to do this with two new clients in the past 3 years that had botched SBS installs.  The first one I ended up doing the reinstall after 1 year of messing around with everything.  Ironically enough, similar to your #2, the final straw was when I could not get a mobile phone to sync after a SSL certificate install.  The second time around, I was honest with the client and told them that SBS needs to be installed from the beginning a certain way and our best plan was to reinstall after the first month of working wtih them.  Perhaps I just don't know enough to work through the problems, but both these clients have been happy for years now.  Just wanted to share some experience as I know this is no kind of solution that you were looking for.  Best of luck to you, Rob.
Jerry SolomonNetwork  Administrator

I have also been-there, and done that, and if I could have done it again, I would take my advice--I would not have to have eaten so much labor, and the client would have a more stable environment--the one thing I never fixed was RPC-HTTP.  Everything else is working, but I hit my wall there after about 10 hours of work (and billing for 5).


hmmm, I was afraid that might be where this is going. Fortunately, there are only 4 users and they don't use the sharepoint at all, so it won't be that difficult too difficult to get things back together after a complete re-install. I'm not looking forward to it by any means, but I suspect this will probably be the best route to take overall.

I'm going to leave this open for a couple of weeks to see if anyone can offer any other suggestions that might avoid the full reinstall. I'm going on vacation and won't have time to do the re-install until after I return anyway. I'll keep an eye on this thread and I'll award points when I've resolved it one way or another.

Well, if you wanted to play with it some more, you could try the following from Microsoft.  It is an article on how to reset the virtual directories for Exchange.  Good luck, Rob.


I've already tried that a few times, but thanks for the suggestion. I ended up re-installing exchange in a last-ditch effort to get it fixed without having to fully re-install. Interestingly, it fixed the OMA sync with MY phone, but not the client's. I think that's progress, as mine wouldn't sync either before the re-install, but I won't know until I can work with the client's phone and see if I can get it to work. That should happen tomorrow.

The redirect still doesn't work, though. It's easy enough to get around but it's also nice to have when it does work.
This one is on us!
(Get your first solution completely free - no credit card required)

Gain unlimited access to on-demand training courses with an Experts Exchange subscription.

Get Access
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Empower Your Career
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.