We have been running Exchange 2007 POP and OWA for several years. I want to migrate over to RPC over HTTP and drop the POP accounts but I have to do the remote offices and traveling folks in stages which will take about a month. I would like to use my existing IP Address, certificate, hostname that I use for POP. My email hostname for POP is mail.domain.com Can I setup the RPC using the same mail.domain.com or do I have to use another name? If it's another name what do folks usually use for RPC? If I can use the same mail.domain.com can I then simply turn on RPC, setup an outlook box for testing, and start migrating my traveling folks over to RPC? If I can do this will the POP folks notice issues or will the server slow down? Thanks! NC Beach BumThanks - NC Beach Bum

You can use whatever name that you like for Outlook Anywhere. As long as it resolves to the correct place and is on the commercial signed SSL certificate it will be fine. However you may need a new SSL certificate to support autodiscover. Depends if your external DNS host supports SRV records or not. http://support.microsoft.com/kb/940881 You can just enable Outlook Anywhere and then test it. Existing non-Exchange clients will not be affected. Then when you are ready, just change the Outlook profile and import the PST file. No impact on everyone else. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

You can use whatever name that you like for Outlook Anywhere. As long as it resolves to the correct place and is on the commercial signed SSL certificate it will be fine. However you may need a new SSL certificate to support autodiscover. Depends if your external DNS host supports SRV records or not. http://support.microsoft.com/kb/940881 You can just enable Outlook Anywhere and then test it. Existing non-Exchange clients will not be affected. Then when you are ready, just change the Outlook profile and import the PST file. No impact on everyone else. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Agree with Sembee. You might encounter certificate error for web-based servic including Autodiscover service, OAB, EWS. We may change the external url for web-based services but not Autodiscover service external url is pre-defined. Refer to: http://technet.microsoft.com/en-us/library/bb332063(EXCHG.80).aspx http://technet.microsoft.com/en-us/library/bb123889(EXCHG.80).aspx Fiona Liao TechNet Community Support

Fiona & Simon - Thanks so very much! So far my testing has been 100% successful with the only issue being my Autodiscover.domain.com certificate. The mail.domain.com certificate is installed on Exchange server so suspect I just need to contact our Cert Server folks and purchase the Autodiscover.domain.com cert and install it on the Exchange server. I see the Autodiscover on the default website so I am going to guess I need to add the cert to the default website. Correct? Thanks very much for your help! Thanks - NC Beach Bum

Simon - I found out our External DNS host does support SRV records. I created one and will do some additional testing so hopefully we won't need the additional ssl certificate. Don't want to spend budget money if I don't have to. :-) Thanks! for your help! Thanks - NC Beach Bum