Exchange 03 Server issue

[neilcritc]

I have a client who originally had a system built with domain name etc. The company has gone into liquidation and emerged as a "new" trading company. I have just recently implemented a Exchange 03 Server with the new email domain my problem is:

The Current DC is called Zeus and hosts the domain 123contracting.co.uk the new company is called 123projects.co.uk, I have email coming into the exchange using a simple catchall account and a pop 3 connector which interfaces with exchange to delivery clients, this arrangement works fine.

I am now looking at making the system have a secure SSL OMA - I have the OMA working remotely using the IP\exchange and this allows logon. I changed the MX records to point at IP address configured the SSL and certificate but cannot get this all to work due to the domain being 123contracting.co.uk....

Has anyone had this issue before is it possible or is it a new domain to fix?

Cheers
Neil

[Mr.James]

Exchange 2003 is a ball ache to set up with SSL. It doesn't support it out of the box.

If you install the certificate on the /exchange virtual directory, OMA tries to proxy back to it and communication doesn't work because it needs it to be unencrypted.

You need to create a /exchange-oma virtual directory which points to the same folder as /exchange and then create a pointer in the registry which directs it to the unencrypted version.

You'll also need to set up an IP restiction so only the Exchange server is allowed to connect to the unencrypted virtual directory to lock it down properly.

There's an MS knowledgebased article that should help you here:

http://support.microsoft.com/kb/817379

You'll also need to make sure that your certificate is for the domain you publish the website on. Your best bet is to get a Unified Communications Certificate (UCC) as it wll let you certify your external and internal domains (up to 3 in total).

Sorry if this don't make perfect sense. Had a few tinnies lol

[neilcritc]

Thank for the advice in the end I sacked https: and just redirected a url at the ip of the http exchange it pops a username and password box and allows access to webmail so tbh that will do. Got so annoyed with Exchange 03 not doing as it should. Going to put a Exchange 10 box on the bench and have a play.

[Mr.James]

Thank for the advice in the end I sacked https: and just redirected a url at the ip of the http exchange it pops a username and password box and allows access to webmail so tbh that will do. Got so annoyed with Exchange 03 not doing as it should. Going to put a Exchange 10 box on the bench and have a play.

Exchange 10 should support it out of the box but can't say for sure as I've not upgraded yet (need to upgrade to Data Protection Manager 2010 first so I can back it up!).

2007 does however and you can setup multiple owa sites. Can't imagine them having removed those features...