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.