Hello guys. I need some help please. We have been working on centralize our infrastructure to one site. So we have several exchange servers and routing groups. Each routing group have his own OWA service, but they are on the same domain. So now i have the task to move the first exchange/OWA/OMA/RPC server from another site, but cant find information about this. Right now our exchange is like this: Administrative Group1 First Routing Group: (owa1.com) Front End Server 2 Back End server Second Routing Group (owa2.com) 1 Exchange The only usable information I've found is this page: http://technet.microsoft.com/en-us/library/bb125060%28EXCHG.65%29.aspx But this is only to move an exchange server between routing groups. Have anybody experience this before who can give me some advice, or have some Info? Thanks, and have a good day.

Hi there, let me see if I understood your question well: 1. You are trying to centralize your infrastructure in one single site and therefor need to move the existing front-end servers to one single location? Or 2 You want to consolidate as well and have only one front-end server left? Either way, there's a fantastic guide available that'll give you some more information on how front-end/back-end works in Exchange 2003: http://www.microsoft.com/downloads/en/details.aspx?FamilyId=E64666FC-42B7-48A1-AB85-3C8327D77B70&displaylang=en Grts, Michael

Hello Michael, Thanks for the doc. I've read the document and understood all topologies, but none of them match ours. but to answer your question, i want to consolidate all front end servers and i want all OWA namespaces to coexist only through our Front End server on central site. Thats because we have configured RPC on too many laptops from people who works remotely and we cant change the RPC configuration. So after searching for a while, I’m not sure, if all I have to are the next things: * · * Public the domain2 namespace through the public IP address of our central site · * Move the server to the same Routing Group where the Front End Server is · * Configure it as a backend server · * And last, through our firewall direct all incoming connections from domain2 petitions to our Front End server. And let the Front End server to search for their respective mailbox server Do you think this will work? Thanks for you help.

That sounds about right. If you have 'em all in one routing group, you'll be able to use 1 front-end and that server will decide what Mb-server the user's located on. Michael

I have one last question. What will happend to the certificate of the server? will i need to create a new certificate because of the change of IP adress? all our clients will hace to change the certificate?

Certificates aren't tied to IP adresses. If the URL's that are being used don't change, your Certs should be just fine.

Hello Michael. Today is the day of the change, and just now we found a problem with the scheme. Our front end is tied to the owa1 certificate. The other server has owa2 certificate. I made a test using a different name to the second site like this: https://owa2.com/exchange. It asked for a certificate but i could enter the OWA. So i realized that i need both certificates on my Front End. Do you have any idea about how to do this? My last resort is to leave the second server out of the Frond End scheme and use the firewall to NAT it directly to the server holding OWA2 certificate? although this was not the idea Thanks for your help, have a nice day.

Hi there! Let's first look back at what you're doing: just to make sure that I'm right about the situation. You're trying to point your users to one exchange server EX01 (because you "eliminated" EX02), right? If that's the case and you want to use several names to access that server I'd suggest that you use a wildcard certificate. That'll be the easiest for Exchange 2003. The reason that you're getting an error on the certificate when trying to access using server2.com (for example) is because that subject-name isn't available on the certificate that's installed on the server EX01. Greetz, Michael

The reason that you're getting an error on the certificate when trying to access using server2.com (for example) is because that subject-name isn't available on the certificate that's installed on the server EX01. Exactly this is the problem. And no, i dont want to point my users to EX01 because im eliminating EX02. Actually im in the process to consolidate both sites. so i need to move EX02 to primary site. Primary site has a Front end server and actually is holding his own owa domain name certificate. Secondary site has his own owa domain name too, called OWA2.com and he holds too his own owa domain name certificate. So all the modifications i need to do to my firewall are controlled, but when i did the test of using a name that doesnt exist on my Front End, a certificate problem apears. That same issue will happend when i move the server to the primary site. And thats why I need to know how can i use my Front End server using both certificates. Thanks.

if you're going to use both servers for both domain names, you'll have to have a certificate (on both servers) that contains both domain names. it's as simple as that. So if that isn't the case, you should go out and get a certificate that does :-) grts, Michael