Outlook RPC over HTTPS doesn’t work in Windows 7

Several of us at the office have been trying out the new Windows 7 – It’s been a positive experience so far and quite a bit faster than Vista.  One problem popped up on all the machines – When we tried to configure Outlook 2007 to connect to our hosted exchange server (using the prf file so we knew it was configured right) it would continuously prompt for the password.

This appears to be the result of the way hosted exchange systems require the use of a full email as the username to differentiate between client domains.  Windows 7 doesn’t care for this and the connection fails.  It may take a bit of doing but if you find your domain name and username from your provider and enter it as follows:


You’ll find it functions perfectly.  The domain is not the domain name from your email it is something else – In our case I had to hit our server configuration and used the settings for configuring mobile activesync on my windows mobile device.  Our provider happens to use a special username to differentiate it’s users.  Once we found that we were happily reading emails again.

IPhone, Exchange, and RapidSSL Certificates

Today I setup my first IPhone on an Exchange Server with Mobile Activesync.  The Exchange setup was nothing special – I enabled HTTPS over RPC using a great article over at Petri.co.il – A Great website to checkout if you haven’t been there.  Next I completed the steps Found on this Apple Information Page for preparing for the IPhone – Again nothing special.  I was then able to test my Exchange setup and send the end user the setup information.  The connection tested fine in outlook but not on the IPhone.  I thought perhaps the IPhone did not have the Equifax certificate needed for the RapidSSL certificate used on the server and after a bit of research found out that correcting this is as easy as emailing the certificate to the phone.

First visit your exchange server using Internet Explorer.  Click the lock next to the address bar (if IE7) and select View Certificates.  Then click install certificate and walk through the wizard.

Next open Internet Options and click “Certificates” on the Content Tab.

Look Under “Other People” for the certificate and After selecting it click “Export”.  Name the certificate something relevant and accept all other defaults.

Once you have your certificate Email it to your Iphone.  This may require you setup a temporary IMAP or POP account with Gmail or elsewhere.  Once you have you email in hand simply open the attachment on the phone and you’ll be prompted to install it.  Once installed setup your Exchange sync as normal.

Exchange SP2 Install Fails while installing Exchange Activesync

While performing a reinstall of Exchange SP2 I was presented with the following Error:

“Setup failed while installing sub-component Exchange ActiveSync with error code 0xC0070643 (please consult the installation logs for a detailed description).  You may cancel the installation or try the failed setup again.”

I took a look in the Exchange Server Setup Progress.log and found the following errors:

[10:30:57] Calling MSXML installer with command line:  “msiexec /i msxml3.msi /q reboot=”ReallySuppress””
[10:30:57] Process created … waiting (-1)
[10:30:58] Process has exited with 0x000643
[10:30:58] The command

msiexec /i msxml3.msi /q reboot=”ReallySuppress”

failed, returning error code 1603 (Fatal error during installation.). — ID:31136 — ScCreateProcess (f:\tisp2\admin\src\libs\exsetup\hiddenw1.cxx:1821)
Error code 0XC0070643 (1603): Fatal error during installation.

After a few Google searches I found the following forum Posting Here

In short – MSXML3 is already installed on the Server – The post outlines the following steps.

  1. Get a copy of the Windows Installer package for the version of MSXML 3 you have installed.
  2. Place a copy inside Exchsrvr\bin
  3. Rename the existing msxml3.msi to msxml3.msi.backup
  4. Make a copy of the latest version MSXML Windows Installer file and rename it to msxml3.msi.  This will leave you with msxml3.msi and msxml3sp?.msi (in my case msxml3sp7.msi).
  5. Click Retry on the error and it should continue as planned.

In my case I didn’t show MSXML 3 Installed – I had the following packages:

MSXML 4.0 SP2 (KB927978)
MSXML 4.0 SP2 (KB936181)
MSXML 4.0 SP2 Parser and SDK
MSXML 6.0 Parser (KB33579)

I tried a number of things but eventually came to the conlusion that I did in fact have MSXML 3.0 SP7 installed and it simply did not show in add remove programs.  I replaced the MSI with the download from this link:


After that I hit retry on the install and still had no luck – I then gave a reboot and a fresh attempt at the install a try using the updated MSI and it proceeded fine.