Hello, I have front end/back end exchange 2003 set up and running in a single domain. OWA is operational at the moment with https://owa.xxxxxxxx.ac.uk. My organisation is going to change its name and would like to have a new domain name as well, which is operational as yyyyyyyy.ac.uk. I have created the email addresses within exchange so all users have both domain addresses and it works fine. However, I can't get OWA to show the new domain. Can I set up the existing Front End server with a second domain within it? So that I have both https://owa.xxxxxx.ac.uk as well as https://owa.yyyyyyy.ac.uk. If so how? Failing that can I have a front end exchange server in the new domain that links to the back end server in the original domain? Will this new server reflect the new domain name or because of its link to the original back end server still has xxxxxxx.ac.uk as its address etc?? Or do I need to set up a completely new front/back end cluster in the new domain?? -- Markthetech
Create a new HTTP virtual Server within ESM, using a dedicated IP with SSL You can assign the SSL cert within IIS. Oliver
Hello Oliver, Thanks for the reply its appreciated. Any chance you could give me a little more detail about the procedure please? When you mention a dedicated IP I'm assuming you are putting a second IP on the network card - or am I missing something here? I should explain that I have inherited the exchange setup and have administered it but never actually set one up from scratch so there are gaps in my knowledge (large gaps!). Many thanks -- Markthetech "Oliver Moazzezi [MVP]" wrote: > Create a new HTTP virtual Server within ESM, using a dedicated IP with SSL > > You can assign the SSL cert within IIS. > > Oliver > > >
Hi there, Assign a new IP to your Exchange FE. Once that is done within ESM, expand the console | Administrative Groups | First Administrative Group | Servers | your FE | Protocols | HTTP From here Right Click, new HTTP virtual server, bind it to your newly assigned IP. The DS2MB process will then create the new HTTP virtual server in IIS. You can then follow this document to secure it with SSL http://www.msexchange.org/tutorials/OWA_Exchange_Server_2003.html Note the additional IP is needed if you want to secure the site with SSL, as the site can't be listening on the same Port and IP as your current other OWA site. Oliver
