RE: Exchange Cluster Question

  • From: <ChongJa@xxxxxxxxxxxxxxxx>
  • To: <exchangelist@xxxxxxxxxxxxx>
  • Date: Wed, 7 Dec 2005 14:02:22 -0500

For Exchange you don't really need to move the msdtc to a separate
resource. It's really only for SQL clusters. Theres KB articles on this
if you research. 

-----Original Message-----
From: Medeiros, Jose [mailto:jmedeiros@xxxxxxxxxxxxxxx] 
Sent: Wednesday, December 07, 2005 1:55 PM
To: [ExchangeList]
Subject: [exchangelist] RE: Exchange Cluster Question

Hi Jeffrey, 

Good job on getting it installed. Yes, the documentation is a little
difficult to follow when it comes to an Exchange 2000 /2003 clusters.
The resource I used when I built a Exchange 2000 Cluster using a HP 500
MSA Storage Array, was a book by Bill English & Walter Glenn on Exchange
2000. It has a chapter that covers how to configure Exchange 2000
_1_1/103-5121435-9831000?s=books&v=glance&n=283155  &

However his current book on Exchange 2003 does not cover clustering.
When I wrote him and asked why he left out that section he replied that
it was not a common installation and suggested I use Microsoft's White

Someone else on the list may have a better resource.

Hope this helps,
Jose Medeiros
ADP | National Account Services
ProBusiness Division | Information Services
925.737.7967 | 408-449-6621 CELL

-----Original Message-----
From: Jeffrey Moscone [mailto:jeff@xxxxxxxxxxxxxx]
Sent: Wednesday, December 07, 2005 7:24 AM
To: Medeiros, Jose
Subject: Exchange Cluster Question

Hello Jose,
Thanks for pointing me in the right direction with using iSCSI to build
a Microsoft Windows 2003 Server using a Snap Server. I've successfully
completed that process and am now stuck on building of the Exchange
resources. Some documentation out there is conflicting stating that you
need a separate default Cluster Group (IP, name, storage), MSDTC Group
(IP, name, storage), and the Exchange Virtual Server Group (IP, name,
storage) and some that state you don't. I've configured the default
Cluster Group with a name, IP and dedicated storage, and also added the
MSDTC Resource to the default group. When I attempted to created a
separate group for MSDTC I couldn't move the physical disk as one
document suggested that I do. So, (take a breathe, sorry for the verbose
email) now I'm at the last step to create the Virtual Server (as a
separate group I assume) and it is going to require a physical disk. Is
this correct? If so, how do you assign the physical storage if it is
already part of the default group?
Also, when I installed Exchange & Service Packs on both servers they
don't appear in the ESM nor are the services started. Maybe this is
Thanks for your help in advance. I've read a lot about this, but nothing
definitive enough complete the setup process.
Jeffrey Moscone

List Archives:
Exchange Newsletters: 
Visit for more information about our other sites:
You are currently subscribed to this Discussion List as:
To unsubscribe visit
Report abuse to info@xxxxxxxxxxxxxx

Other related posts: