In Exchange 2010 it doesn't matter where you locate your HT. It can be on MB or 
CAS. If you were to set up a load-balancing scenario, it is _SLIGHTLY_ easier 
to configure load-balancing (when using Windows NLB) if the HT is on the MB. 
The configuration is _EXACTLY_ the same if you are using non-on-board LB.

In Exchange 2010, MAPI (that is, Outlook) users connect to the CAS, not to the 
MB server. Ever. If you add MB servers, they don't have to reconfigure. Ever. 
(Unless you move them to a different site, but that should happen 
automagically.)

If you have a DAG and one of the servers goes down - then the other one comes 
up - unless it's set to not automatically activate.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Liby Philip Mathew [mailto:[email protected]]
Sent: Tuesday, May 11, 2010 11:04 AM
To: MS-Exchange Admin Issues
Subject: RE: Introduce E2K10 and remove E2K7

Thanks Mike,
We are an ISV operating from 8 different countries of which 3 countries are 
having close to 200 users.
Right now these 3 countries are operating as separate disjoint internal domains 
and using their own email servers.  We want to integrate all these 3 domains 
into a single domain over site-to-site VPN and use a consistent email id across 
the organization.
Right now we are using [email protected]<mailto:[email protected]>, 
[email protected]<mailto:[email protected]> etc based on the 
country code.  We want to avoid this different email address.
My reasoning to split off CAS from MB, is so that even if there is any change 
in MB server names due introducing new MB servers, the remote users shouldn't 
be affected with reconfiguring Outlook Anywhere.
Moreover what will happen if the complete MB server with CAS & HT is down even 
though I have with SCR / DAG as backup repository?
The most important thing I can't comprehend is where to host the HT.  Should it 
be on MB or CAS?
Later we will have DR between sites.  UM is not important.
Appreciate and thank you for your consistent help
Liby


From: Michael B. Smith [mailto:[email protected]]
Sent: Tuesday, May 11, 2010 5:28 PM
To: MS-Exchange Admin Issues
Subject: RE: Introduce E2K10 and remove E2K7

Ok, then you have an Edge at each site and that brings you down to 3.

I recommend you don't collocate any roles with UM. So that's two.

Now, the question is whether you really want to split off your CAS from your 
MB, and if so - why?

Secondly, what is your goal in having two separate sites? Is it HA based? Or 
are you trying to cover two separate locations with no site-based HA?

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Liby Philip Mathew [mailto:[email protected]]
Sent: Tuesday, May 11, 2010 9:25 AM
To: MS-Exchange Admin Issues
Subject: RE: Introduce E2K10 and remove E2K7

Thanks Mike,
But I guess I made a mistake.  Its 4 servers per site and not 4 server all 
together.
Liby

From: Michael B. Smith [mailto:[email protected]]
Sent: Tuesday, May 11, 2010 3:07 PM
To: MS-Exchange Admin Issues
Subject: RE: Introduce E2K10 and remove E2K7

First, DAG is part of the MB role. It provides HA for the MB role.

You can collocate all roles on the MB and still use DAG (this is a change from 
Exchange 2007 HA roles).

If you only have four servers and you have to support two sites then your only 
choice is to have an Edge server at each site and have a multi-role (HT, CA, 
MB, UM) server at each site.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Liby Philip Mathew [mailto:[email protected]]
Sent: Tuesday, May 11, 2010 7:23 AM
To: MS-Exchange Admin Issues
Subject: RE: Introduce E2K10 and remove E2K7

Oops.  I am sorry.
I don't have the budget to host different roles on different servers.
The maximum I can have is 4 servers. 1 each for MB, CAS, Edge & DAG.
So basically, I need 1 server with MB.  1 server to host CAS.  On which server 
should I have my HT?  on MB server or CAS server?
I forgot to add an important point that is, I will be moving to multi site 
(different geo location) domain with each site having  its own MB, CAS, HT & 
EDGE (for only outbound mails from that site).
Regards
Liby

From: Michael B. Smith [mailto:[email protected]]
Sent: Tuesday, May 11, 2010 1:55 PM
To: MS-Exchange Admin Issues
Subject: RE: Introduce E2K10 and remove E2K7

I don't understand this question: "What all are the roles that is required on 
Mailbox server and CAS server?"

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Liby Philip Mathew [mailto:[email protected]]
Sent: Tuesday, May 11, 2010 1:59 AM
To: MS-Exchange Admin Issues
Subject: Introduce E2K10 and remove E2K7

HI,
I planning to migrate to Exchange 2010 from Exchange 2007.
Presently,
DC                                          Windows 2008 SP2
Exchange                             Exchange 2007 SP2 (MBX, CAS, HT & UM) on 
Windows 2003 R2 all role on 1 server.
Exchange                             Exchange 2007 SP2 (EDGE) on Windows 2003 
R2 in DMZ across ISA 2006.

In the new setup, I would like to introduce coexisting E2K10, move CAS to a 
separate server.  All other roles such as MBX, HT & UM on a separate single 
server in E2K10. DAG on a different server and completely remove E2K7 from the 
environment.
What all are the roles that is required on Mailbox server and CAS server?
How do I achieve this configuration with "0" or minimal downtime?.
Any help is much appreciated.
Regards
Liby



________________________________
Disclaimer
[The information contained in this e-mail message and any attached files are 
confidential information and intended solely for the use of the individual or 
entity to whom they are addressed. This transmission may contain information 
that is privileged, confidential or exempt from disclosure under applicable 
law. If you have received this e-mail in error, please notify the sender 
immediately and delete all copies. If you are not the intended recipient, any 
disclosure, copying, distribution, or use of the information contained herein 
is STRICTLY PROHIBITED. Path Solutions accepts no responsibility for any 
errors, omissions, computer viruses and other defects.]

Reply via email to