dougdog
asked on
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
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
ASKER
so if I install exchange 2013 my existing outlook clients wont start connecting to the 2013 cas server
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
so as soon as 2013 is installed
all existing outlook clients will try to connect to it?
all existing outlook clients will try to connect to it?
.
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.
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.
ASKER
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
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
ASKER
excellent
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.