Exchange 2013 Upgrade with SSL and Name Change
Hello,
We are looking to transition from Exchange 2007 to 2013. We are a relatively small organization (~600 mailboxes), so we have decided to use just one server for MBX+CAS. I have a couple of questions about this upgrade:
We have named our 2007 server and all of the service names "exchangesvr" (except for autodiscover). We are considering switching to use "mail" as the service name for everything except autodiscover, since that seems to be pretty standard. Is it a good idea to use the name "mail", or should we keep our existing name? It seems like we may run into problems during co-existence if we keep the name "exchangesvr" for 2013 because that will still be the name of the physical 2007 machine, even though the service name will have switched to our 2013 server. Also, if we do change the name from "exchangesvr" to "mail", does this mean that we do not need to use a legacy namespace? We can just refer to "exchangesvr" as the legacy server, correct?
Also, our 2007 server has no SSL certificate. We will most definitely be implementing an SSL certificate on the 2013 server. How will that affect users during co-existence? When we go live with 2013, I know we will have to change the ActiveSync profile on all our company phones to the new server name (if we go with a new name) and to use SSL. If a user's mailbox has not been migrated to the 2013 server, will there be issues when the user goes from an SSL connection with the 2013 server to not having an SSL connection with the 2007 server? Would it be possible to have users who haven't been migrated to the new server continuing to use the same ActiveSync settings until we do migrate their mailbox to the new server?
Thanks in advance for your input.
We are looking to transition from Exchange 2007 to 2013. We are a relatively small organization (~600 mailboxes), so we have decided to use just one server for MBX+CAS. I have a couple of questions about this upgrade:
We have named our 2007 server and all of the service names "exchangesvr" (except for autodiscover). We are considering switching to use "mail" as the service name for everything except autodiscover, since that seems to be pretty standard. Is it a good idea to use the name "mail", or should we keep our existing name? It seems like we may run into problems during co-existence if we keep the name "exchangesvr" for 2013 because that will still be the name of the physical 2007 machine, even though the service name will have switched to our 2013 server. Also, if we do change the name from "exchangesvr" to "mail", does this mean that we do not need to use a legacy namespace? We can just refer to "exchangesvr" as the legacy server, correct?
Also, our 2007 server has no SSL certificate. We will most definitely be implementing an SSL certificate on the 2013 server. How will that affect users during co-existence? When we go live with 2013, I know we will have to change the ActiveSync profile on all our company phones to the new server name (if we go with a new name) and to use SSL. If a user's mailbox has not been migrated to the 2013 server, will there be issues when the user goes from an SSL connection with the 2013 server to not having an SSL connection with the 2007 server? Would it be possible to have users who haven't been migrated to the new server continuing to use the same ActiveSync settings until we do migrate their mailbox to the new server?
Thanks in advance for your input.
ASKER CERTIFIED 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.