how best to implement exchange 2013 with load balancers in to current 2010 infrastructure

im running a single exchange 2010 server running all roles except edge which we don't use
I have around 2000 users.
I want to move to 2013 exchange and use kemp load balancers
I was thinking I would deploy just 2 servers with all roles installed
what is the best way to implement this without having too much impact on current 2010 mailbox
as this is my first 2013 install I don't want to break existing setup
I have read that as soon as 2013 is installed all mail routes through this
just looking a little help
dougdogAsked:
Who is Participating?
 
Simon Butler (Sembee)ConsultantCommented:
The only thing that will try and do is use the CAS for Autodiscover.
You can correct that by changing the URL to match the existing:

get-clientaccessserver | select identity, autodiscoverserviceinternaluri

gets you the existing address. Once Exchange 2013 is installed run

set-clientaccessserver e2013servername - AutodiscoverServiceInternalURI https://host.example.com/Autodiscover/Autodiscover.xml

where e213 is the name of the new server/s, and host.example.com is the host name used on the existing server.
Don't forget to change it once you are ready to go live, to the host name going through the load balancers.

Simon.
0
 
Simon Butler (Sembee)ConsultantCommented:
Until you move the URLs across to the new platform, there is almost no impact on the end users. Therefore you can just install Exchange 2013 CU8, configure the databases etc and then deploy the load balancers.
Most of the testing can be done by tweaking hosts files so that the names resolve to the new servers without having to touch the live environment.

Otherwise it is nothing different to a regular installation of Exchange 2013, which is heavily documented.

Simon.
0
 
dougdogAuthor Commented:
so if I install exchange 2013 my existing outlook clients wont start connecting to the 2013 cas server
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
dougdogAuthor Commented:
so as soon as 2013 is installed
all existing outlook clients will try to connect to it?
0
 
Marwan OsmanCommented:
.
0
 
Simon Butler (Sembee)ConsultantCommented:
Existing clients MAY try to connect to it.
Autodiscover information is published by the servers at regular intervals. Therefore your new server will publish its information, but at some point after, so will your old server. Depending which server was last to publish will depend on the server they connect to.
Therefore by setting all servers to the same value, the same information is always published to the domain, meaning you control where they connect.

Simon.
0
 
dougdogAuthor Commented:
ok
so as soon as I install first 2013 server if I change the autodiscover settings as you have said
this will not affect my existing 2010 installation
and users will not be affected
leaving me free to test with the new 2013 server and try to get dag and load balacers working etc

then when im happy its working start to migrate users
0
 
dougdogAuthor Commented:
excellent
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.