The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
So I have a server that's running Windows Server 2003 and Exchange. I also have a 2nd server running Server 2003, if that helps (it's just a file server right now). I want to set the server up so that we can use iPhones with it. I was hoping this would be simple, but it is WAY over my head. Here's what Apple says I need to do:
Exchange ActiveSync Setup
Network confi guration
• Check to ensure port 443 is open on the fi rewall. (Note: If your company allows
Outlook Web Access, port 443 is most likely already open on your fi rewall.)
• On the Front-End Server, verify that a server certificate is installed and enable SSL
for the Exchange ActiveSync virtual directory (require basic SSL authentication).
• On the Microsoft Internet Security and Acceleration (ISA) Server, verify that a server
certifi cate is installed and update the public DNS to properly resolve incoming
connections.
• On the ISA Server, create a Web listener as well as an Exchange Web client access
publishing rule according to Microsoft documentation. This is a necessary step in
enabling Exchange ActiveSync.
• For all fi rewalls and network appliances, set the Idle Session Timeout to 30 minutes (check
your Microsoft Exchange documentation for alternative heartbeat and timeout intervals).
To me this sounds like this:
How to fix a blown transmission in a 1970 Ford Pinto:
• Remove the transmission.
• Replace all broken or damaged parts.
• Set the timing on everything.
• Go for a drive.
Does anyone know where I can find a step by step set of instructions to do what I need to do? I've tried to muddle my way through, but one line in Apple's to do list seems to lead to more and more stuff I need to do and it just kind of spirals out of control.
We have webmail enabled that you can get to from any browser, which I think is what they mean. I'm not 100% sure though because this is all self-taught and I'm hazy on the terminology. Unfortunately there is no one left here who was involved in the webmail setup.
Once you learn the terminology, you can google this stuff fairly easily. But it can be frustrating to work with all the different phones and mobile devices and crackberrys... ugh.
Anyway, if you're running webmail (outlook web access) already, adding the OMA (outlook mobile access) isn't too difficult. Hit this up for exchange OMA - http://www.petri.co.il/configure_oma.htm.
Hell, skip to the end and try a test - setting OMA and OWA both up at the same time is typical.
Basically once that's all working, the iphone should be too.
Thanks very, very much. I've already gotten farther than I had on my own. I've got to take off in 10 minutes or so, but I'll keep working on this. Thanks for the help, and hopefully I'll catch you again as I get further in.
That blog is pretty awesome. Thanks for telling me about it.
Here's where I'm at now with my iPhone issue. I'm able to connect to OMA with a browser both inside and outside the network. I get to it by going to our firewall's IP/oma (http://216.253.xxx.xxx/oma). It tells me the device isn't supported, but I can click ok to acknowledge that and I get in. However, when I try to connect with either the iPhone or the WinWAP emulator (a mobile phone browser emulator, which I'm using because I can't just hold this guy's iPhone hostage) I can't get in. The emulator just gives me a HTTP 401-Unauthorized error.
I'm not sure if we had to load our self-signed cert to the iphone or not, but I think no. We did have to add it to some windows mobile phones before they would work as they didn't have the option of accepting unknown certs.
Posts
Anyway, if you're running webmail (outlook web access) already, adding the OMA (outlook mobile access) isn't too difficult. Hit this up for exchange OMA - http://www.petri.co.il/configure_oma.htm.
Hell, skip to the end and try a test - setting OMA and OWA both up at the same time is typical.
Basically once that's all working, the iphone should be too.
If you don't already, read the exchange team blog. Very good resource and will teach you a lot. http://msexchangeteam.com/
Here's where I'm at now with my iPhone issue. I'm able to connect to OMA with a browser both inside and outside the network. I get to it by going to our firewall's IP/oma (http://216.253.xxx.xxx/oma). It tells me the device isn't supported, but I can click ok to acknowledge that and I get in. However, when I try to connect with either the iPhone or the WinWAP emulator (a mobile phone browser emulator, which I'm using because I can't just hold this guy's iPhone hostage) I can't get in. The emulator just gives me a HTTP 401-Unauthorized error.
Any idea what I'm doing wrong?
If OMA isn't setup to talk over SSL, start here. http://www.petri.co.il/configure_ssl_on_oma.htm
I'm not sure if we had to load our self-signed cert to the iphone or not, but I think no. We did have to add it to some windows mobile phones before they would work as they didn't have the option of accepting unknown certs.