MatthewDK
asked on
Adding Exch 2013 CAS/Mailbox server to existing 2010 environment with Edge Transport
I'm getting ready to add two Exchange 2013 CAS/Mailbox servers to our existing 2010 environment. In our network, we have two 2010 Hub Transport/CAS/Mailbox servers and one 2010 Edge Transport server (all servers are at SP3 CU10).
I understand that as soon as the 2013 servers are added, some important steps need to take place. I'd like to make sure I have my steps in order.
1. Currently, our 2010 HT/CAS/MB servers are in different locations. Their autodiscover URIs are unique, for example, autodiscover.domain1.com and autodiscover.domain2.com. Once the first 2013 server is added (I'm hoping to be able to do this in phases), is it proper to set autodiscover for our domain1.com on the 2013 server while leaving autodiscover for domain2.com alone on the existing 2010 server for the time being? As long as that is the case, I can continue to step 2.
2. I think that once autodiscover has been configured for the new 2013 server, our SSL cert needs to be imported. Is this the right time to do that?
3. We have a 2010 Edge Transport server. Is this the right time to subscribe the new server to Edge? If so, is it just a matter of removing our current subscription and default send connectors and resubscribing, or does a new subscription file need to be created first on the Edge Transport server to be used to subscribe the 2010 and 2013 mailbox servers? Additionally, does the subscription need to take place on the 2013 server, or is that not important?
A lot of moving parts, and I just want to make sure I have my steps right. And as long as it's ok to add one 2013 server at a time (for a period of a couple weeks), that is our preference. Please let me know if that will cause any problems.
I understand that as soon as the 2013 servers are added, some important steps need to take place. I'd like to make sure I have my steps in order.
1. Currently, our 2010 HT/CAS/MB servers are in different locations. Their autodiscover URIs are unique, for example, autodiscover.domain1.com and autodiscover.domain2.com. Once the first 2013 server is added (I'm hoping to be able to do this in phases), is it proper to set autodiscover for our domain1.com on the 2013 server while leaving autodiscover for domain2.com alone on the existing 2010 server for the time being? As long as that is the case, I can continue to step 2.
2. I think that once autodiscover has been configured for the new 2013 server, our SSL cert needs to be imported. Is this the right time to do that?
3. We have a 2010 Edge Transport server. Is this the right time to subscribe the new server to Edge? If so, is it just a matter of removing our current subscription and default send connectors and resubscribing, or does a new subscription file need to be created first on the Edge Transport server to be used to subscribe the 2010 and 2013 mailbox servers? Additionally, does the subscription need to take place on the 2013 server, or is that not important?
A lot of moving parts, and I just want to make sure I have my steps right. And as long as it's ok to add one 2013 server at a time (for a period of a couple weeks), that is our preference. Please let me know if that will cause any problems.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Since 2013 mailbox servers can co-exist with a 2010 Edge server, we want to deploy the new 2013 servers into our existing environment. Unfortunately, the deployment assistant does not specifically cover that type of rollout. That's why I posted our anticipated steps here, hoping someone could confirm we're on the right path.
ASKER
The deployment assistant helped with my first two questions, but I'm still unclear on the Edge coexistence. Can someone explain how/at what point the 2013 CAS/Mailbox server(s) are subscribed to the 2010 Edge server?
And does the New-EdgeSubscription cmdlet need to be executed on the 2010 Edge server first to create a new .xml file, or can the existing subscription file be used to resubscribe the new 2013 and existing 2010 mailbox servers?
And does the New-EdgeSubscription cmdlet need to be executed on the 2010 Edge server first to create a new .xml file, or can the existing subscription file be used to resubscribe the new 2013 and existing 2010 mailbox servers?
I will answer your question shortly. Tied up at the moment.
Will.
Will.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
My question was partially answered. I found the tech note which fully clarified the answer.
ASKER
That said, should we stick to best practices and have one server configured for autodiscover in both of our split DNS zones?
Currently, we have a DNS record for autodiscover.domain1.com established in the DNS zone for domain1.com set to 192.168.1.x. Then We have another DNS record for autodiscover.domain2.com established in the DNS zone for domain2.com set to 192.168.0.x.