Outlook Anywhere for exchange 2003 mailbox (Full Version)

All Forums >> [Microsoft Exchange 2007] >> Migration



Message

fthekrallah -> Outlook Anywhere for exchange 2003 mailbox (24.Aug.2008 5:59:25 AM)

Dear All;

We have the below environment:
- One exchange server 2003 (FE + BE), OWA and RPC over HTTPS are enabled and all clients are accessing their mailboxes successfully.
- 4 servers for exchange server 2007: 2 mailbox and 2 HT and CAS.


Old OWA (2003) was configured to use a third party certificate under the name (mail.test.com) so I purchase a new certificate for our new CAS servers with the same old name (mail.test.com).
Message routing between Exchange 2003 and Exchange 2007 are working successfully and OWA (2007) is working successfully for both exchange 2003 and exchange 2007 mailboxes.
Now when I changed the External DNS records to point to the new CAS server's outlook anywhere are working well for mailboxes hosted on exchange 2007 server but DID NOT for mailboxes hosted on exchange server 2003.
Is there any other configurations must be done either on exchange 2003 server or exchange 2007 servers?????
I'm suspecting in the old certificate installed on exchange 2003, do I need to remove it??? Or need to install the new certificate (ordered for the new CAS servers) on exchange server 2003??

Please can any one helps me



Best Regards



Sembee -> RE: Outlook Anywhere for exchange 2003 mailbox (25.Aug.2008 12:57:24 PM)

The only thing that I can think might have caused a problem is the require SSL setting on the Exchange 2003 servers. If that is set on the virtual directories then it can cause a problem.

When you purchased your certificates, did you purchase a single name SSL or a SAN/UC certificate? Exchange 2007 handles certificates in a different way to Exchange 2003 and the choice of SSL product is very important.

Simon.



fthekrallah -> RE: Outlook Anywhere for exchange 2003 mailbox (25.Aug.2008 4:31:20 PM)

yes the new purchased certificate is a SAN certificate for webmail.test.com and autodiscover.test.com

if i remove the certificate from exchange 2003 , dose it work correctly ???



Sembee -> RE: Outlook Anywhere for exchange 2003 mailbox (25.Aug.2008 4:45:44 PM)

You have to remove the certificate AND remove the remove the require SSL option to confirm it isn't the cause of the problem.

Is the name that is in Outlook also the common name on the certificate, or one of the additional names?

Simon.



fthekrallah -> RE: Outlook Anywhere for exchange 2003 mailbox (25.Aug.2008 4:50:49 PM)

i used the same name was configured in old certificate 



Sembee -> RE: Outlook Anywhere for exchange 2003 mailbox (25.Aug.2008 5:55:13 PM)

The key point is what is the common name on the certificate.
Outlook 2003 RPC over HTTPS cannot cope with the name being an alternative name, only with it being in the common name (ie what you see when you look at the properties of the certificate).

The other thing that might have caused a problem is authentication mismatch. What do you have the clients set to - NTLM or Basic? What do you have it set to in Exchange? It needs to be the same. You could also cheat and set it to both on the virtual directory manually.

Simon.



fthekrallah -> RE: Outlook Anywhere for exchange 2003 mailbox (26.Aug.2008 1:13:45 AM)

The common name is the same webmail.test.com
and the authentication configured on cas and clients to basic 



Sembee -> RE: Outlook Anywhere for exchange 2003 mailbox (26.Aug.2008 5:30:00 AM)

Have you checked that the feature actually works?
If you create a new profile does it work?
Have you configured Exchange 2003 correctly to be a backend server in ESM?

Simon.



fthekrallah -> RE: Outlook Anywhere for exchange 2003 mailbox (26.Aug.2008 5:56:36 AM)

listen when i typed the name of exchange server 2003 and the username of the exchange 2003 mailbox and then press on the check name button it didn't work , but when i typed the Mailbox 2007 server name and the username of the exchange 2003 mailbox its resolved the name correctly and change the server name to the exchange 2003 server but when starting outlook it hanged and didn't work .

do i need to configure the exchange 2003 as a back end server , or removing the old certificate only will resolve the problem ?

and how to configure exchange 2003 as a back end server , as i remembered this operation is not reversible ???!!



Sembee -> RE: Outlook Anywhere for exchange 2003 mailbox (26.Aug.2008 5:56:08 PM)

The behaviour that you have seen is what I would expect.
Outlook connects to the Exchange 2007 server and is corrected to the actual home of the server. You would then have to ADD the additional RPC over HTTPS settings in the usual way, to force Outlook to use that connection method.

I don't know where you got the impression that making changes was irreversible. The only settings that I am aware of that are irreversible are Domain/Exchange org settings. The Backup setting for RPC over HTTPS is on the properties of the Server in ESM.  

Simon.



fthekrallah -> RE: Outlook Anywhere for exchange 2003 mailbox (26.Aug.2008 6:03:40 PM)

Thanks alot Sembee for replying ,
so if i removed the SSL certificate from old server (Exc 2003) dose it solve the problem ,  or set the Exch 2003 as backend server , or i have to do both options in order to resolve the problem.



Sembee -> RE: Outlook Anywhere for exchange 2003 mailbox (26.Aug.2008 6:19:23 PM)

The server should already be set as a backend server if you had frontend servers before. So that might just require checking.
Removing the SSL certificate cannot do any harm because it is surplus to requirements.
Do ensure that when you are testing that you are putting the additional information in to Outlook for the RPC over HTTPS connection information.

Simon.



fthekrallah -> RE: Outlook Anywhere for exchange 2003 mailbox (27.Aug.2008 7:14:40 AM)

im sure that the configurations on outlook are correct because i use the same information for mailboxes hosted on exchange 2007 server .

i have only one exchange 2003 server (FE + BE) .



fthekrallah -> RE: Outlook Anywhere for exchange 2003 mailbox (28.Aug.2008 1:24:37 PM)

[image]http://forums.msexchange.org/file:///C:/DOCUME%7E1/FTHEKR%7E1/LOCALS%7E1/Temp/moz-screenshot.jpg[/image] i tried to set the exchange 2003 as a back end also i removed the SSL but still outlook anywhere for exchange 2003 mailbox dose not working through cas 2007 ??

please if any one have a documentation for how to configure outlook anywhere in a coexistent environment please pass it to me , my email :




Sembee -> RE: Outlook Anywhere for exchange 2003 mailbox (29.Aug.2008 6:40:11 AM)

Something is inconsistent in your environment somewhere. Possibly something that you haven't mentioned - that you may not know about.
It should work without many changes, as long as the requirements are met - so the server that holds the CAS role does not hold the mailbox role and the GUI has been set correctly in ESM.

The only other thing I can think of is that the setup for RPC over HTTPS on Exchange 2003 wasn't done correctly, and therefore the configuration isn't correct. The only way to fix that is to remove the feature from the Exchange 2003 server completely. You would need to set the GUI in ESM to not part of an RPC HTTP topology, then use add/remove programs to remove the Windows RPC Proxy feature. Remove the virtual directories for RPC from IIS, then run iisreset to apply the change to the iis metabase. Then reinstall the RPC Proxy and set it correctly in ESM as a backend server.

If that still doesn't work then it will have to be a call to Microsoft, as it should work. They can do the one thing that I cannot, which is look at your machines.

You may also want to edit your post above if you can (or ask the moderators to) to remove your email address to reduce the spam that you will receive.

Simon.



fthekrallah -> RE: Outlook Anywhere for exchange 2003 mailbox (30.Aug.2008 6:02:38 AM)

Dear Mr.Sembee ;
i am really thankful for your replies , finally i solved the problem , the RPC Proxy Valid ports was configured on CAS servers to point to the Mailbox Server 2007 as seen below :
MailboxServer2007_Netbiosname:6001-6002;MailboxServer2007_Netbiosname:6004;MailboxServer2007_FQDN:6001-6002;MailboxServer2007_FQDN:6004


then i added the name of exchange 2003 server to the Valid Ports Registry Key :
ExchangeServer2003_Netbiosname:6001-6002;ExchangeServer2003_Netbiosname:6004;ExchangeServer2003_FQDN:6001-6002;ExchangeServer2003_FQDN:6004


so the registry key became as below :
MailboxServer2007_Netbiosname:6001-6002;MailboxServer2007_Netbiosname:6004;MailboxServer2007_FQDN:6001-6002;MailboxServer2007_FQDN:6004;ExchangeServer2003_Netbiosname:6001-6002;ExchangeServer2003_Netbiosname:6004;ExchangeServer2003_FQDN:6001-6002;ExchangeServer2003_FQDN:6004

this solve the problem



cliftonwalsh -> RE: Outlook Anywhere for exchange 2003 mailbox (18.Sep.2008 5:50:50 PM)

I am having the same sort of problem here.
 
Original setup:
1 x Exchange 2003 mailbox server (SP2), RPC over HTTP working using Thwate certificate (AD/GC as well)
 
New setup:
1 x Exchange 2007 CAS/HT server using IPS certificate with the same common name as the Exchange 2003 certificate
1 x Exchange 2007 MBX server
1 x Exchange 2003 mailbox server (set as backend server in RPC over HTTP settings in ESM) (still AD/GC as well)
 
What works:
  • RPC over HTTP connection from Outlook 2007 to Exchange 2003 mailbox when Exchange 2003 RPC proxy is used
  • Outlook Anywhere connection from Outlook 2007 to Exchange 2007 mailbox when CAS server is RPC proxying
  • OWA passthrough to Exchange 2003 from CAS server

What doesn't work:
  • Outlook Anywhere connection from Outlook 2007 to Exchange 2003 mailbox when CAS server is RPC proxying

Rpcping succeeds when going direct to Exchange 2003 but throws a 401 error when going to CAS.
 
The RPC Proxy Valid ports on the CAS server are automatically populated with the Exchange 2003 server ports as expected.  RPC Proxy has been removed and reinstalled on both Exchange 2003 and CAS servers.
 
The odd part of this, is I setup a new Exchange 2003 server to test this, and all tests succeeded.  The only difference I can tell is that the new server wasn't an AD/GC server, although I'm sure there are other configuration changes in the live system.  I tested in the same way descibed here (although I did come up with it all on my lonesome [;)]).
 
I'm thinking my problems could be one/none/all of:
  1. Using the same SSL cert common name - not likely because the test system using same names worked fine
  2. Exchange 2003 being a AD/GC
  3. Some unknown arbitrary configuration setting on the old Exchange 2003 mailbox server that a new install doesn't have

I could just move all mailboxes at the same time as migrating to the CAS, but that would be quite time consuming and would mean all my remote Outlook Anywere-only users wouldn't have their mailbox server automatically changed (since the CAS doesn't seem to talk properly to Exchange 2003 at the moment[&o]).
 
Does anyone have any further ideas on what to look at so that I can get this working?
 
Many thanks,
 
Clifton



Page: [1]