Question Locked

Microsoft Exchange Server and the iPhone

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi everyone. Please bare with me as I am a complete newbie when it comes to configuring Microsoft Exchange. Here's the situation.

My company have Outlook Web Access enabled so people can access their email via the internet. However, it only works with standard http and not https. In other words http://www.domain.com/exchange works but https://www.domain.com/exchange doesn't work. This is preventing me from setting up people to use Outlook on their local machines at home.

It is also a problem for me in setting up my chairman's new iPhone with his email, because the iPhone automatically looks for https (you can't specify a protocol) in much the same way as RPC access in Outlook does.

The only way I can get it to work at the moment is to re-direct all his exchange email through an imap or pop3 account , but this is no good as he needs his contacts and calendar etc.

Can anybody let me know how I can re-configure Exchange Server 2003 to use https instead of http for ActiveSync?

8 replies

by Former member

Exchange 2003 Configuration for RPC over HTTP Proxy

Remember that HTTP over RPC is new, so it's not available in Exchange Server 2000, or Outlook 2000.
Install the RPC over HTTP Proxy Service
I have to say that locating the server setting for RPC over HTTP had me in a spin. Then I remembered how Exchange 2003 relies on Windows 2003. Now it's easy, Add or Remove Programs, Windows Components, Network Services and add RPC over HTTP Proxy.
Configure Basic Authentication in IIS
Your goal is to configure Basic Authentication. Launch the IIS snap-in. From there expand the ServerName, Default Web Site. The tricky part is right clicking and finding RPC. Next, select properties make sure Basic Authentication is checked and Anonymous is disabled.
Optionally, you can configure the encryption level. On the Directory Service tab, click edit, secure communications and then require 128 Bit Encryption.
Deploy Front-end server inside the firewalls
Either position a front-end server in the perimeter network and then install the RPC Proxy service; or deploy an ISA server which then connects to the front-end server. (See Diagram above.)
Configuring for non-SSL connections
Your goal is edit the registry on the front-end server and add a DWORD called: AllowAnonymous
1.Launch Regedit, Navigate to this registry key:
2.HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy
3.Add a new REG_DWORD called: AllowAnonymous
4.Set the value = 1 (Meaning Enabled)
Configuring Outlook 2003 for RPC over HTTP
Getting Outlook 2003 to work with RPC over HTTP is not a trivial task. So for a large roll-out I suggest investigating the ORK (Office Resource Kit). Which ever method you employ, the steps are similar, here is my checklist:
1.The XP clients, repeat XP, needs SP2 or hotfix Q331320
2.Head for the Control Panel, Mail icon. Create a new email account which uses Microsoft Exchange Server. So far so good.
3.Now for the first tricky part. Turn OFF Cached Exchange mode - just while you test and get it connected, later you can revert to the cached mode. Type in the username.
4.Here is the really difficult section. Our task is to find the 'Connect to my Exchange mailbox using HTTP'. Observe the Connection tab, note 4 options, but select the 'Connect to my Exchange mailbox using HTTP' check box, and then click Exchange Proxy Settings.
5.This Outlook 2003 client needs the name of the Exchange 2003 server, so in the dialog box called: 'Use this URL to connect to my proxy server for Exchange', type in your server and domain name, for example https://paris .cp.com (did you use HTTPS?). You should see another box called Connect Using SSL only, check this box and enable SSL.
6.Outlook 2003 is now ready to connect to Exchange 2003 using RPC over HTTP.

Troubleshooting RPC over HTTP
On the Exchange 2003 server, remember to install the RPC over HTTP network service.
Make sure that you have a Server certificate on the Exchange 2003 machine, not just on the domain controller.
If you navigate to the connections menu, but cannot see the 'Connect to my Exchange mailbox using HTTP'. tab, then apply SP2 to your Windows XP machine.
If you have problems connecting to Exchange 2003. From the Outlook 2003 client try: Run outlook rpcdiag.

Please post back if you have any more problems or questions.

by foruseonforums

OK, I got the RPC added through windows components.

I then opened IIS and found the RPC under SERVERNAME > Web Sites > Default Web Site

I right clicked on RPC and choose Properties.

This gave me a dialog with 6 tabs - Virtual Directory - Documents - Directory Security - HTTP Headers - Custom Errors - ASP.NET

Under Directory Security I clicked the button to Edit under "Authentication and access control".

I then unticked "Enable anonymous access"

I Clicked OK back to the main IIS screen.

That's as far as I got.

What do I do now?

FYI - I access Outlook Web Acccess currently through http://ipaddress/exchange

by Former member

On the Directory Service tab, click edit, secure communications and then require 128 Bit Encryption.

by Former member

Deploy Front-end server inside the firewalls
Either position a front-end server in the perimeter network and then install the RPC Proxy service; or deploy an ISA server which then connects to the front-end server.
Then slowly go through the rest of my earlier post and when all is finished you will need to do a test. Like i said it might work it might not but you are going in the right direction.

by Former member

Please post back if you have any more problems or questions.

by foruseonforums

Found the problems now.

1. The SSL certificate never got renewed by my predecessor, and because up until now there has been no need for OWA or RPC over HTTP, I never came across it. I've now renewed the certificate and have an user working on his laptop externally in Outlook using RPC over HTTP.

2. As for the iPhone, our incompetent O2 Business Account Manager hadn't told her technical people to switch my boss's SIM card over to an iPhone enabled SIM (iPhone Bolt-On).

Despite everything being in place though it still will not sync the phone.

Here's what I have tried so far.

1. Remove the Exchange local domain name from the server setting i.e. DOMAIN\Username - Didn't fix the problem

2. Disable SSL for the account - Didn't fix the problem

3. Turn the device on and off - Didn't fix the problem

4. Remove all email accounts, turn the device off and try setting up the email account again - Didn't fix the problem

Is anybody able to help at all?

This exchange server is running MS Exchange 2003 SP2. It is configured with an SSL certificate, Outlook Web Access works via https://www.domain.com/exchange, and it is also configured for RPC over HTTP. I have an external user, who's Outlook I have setup to use RPOC over HTTP for his Exchange account and this is all working ok.

The settings in the iPhone I have configured are:

Email = username@domain.com (this is the primary alias set in AD)

Serverl = www.domain.com (the address the certificate was bought for)

Username = DOMAIN\username (where DOMAIN is the LAN name in the office here)
Password = LAN password

Use SSL is on.

This discussion is closed to new replies.