RE: Exchange2003 SP1 for ESM Question

  • From: "Mark Fugatt" <mark@xxxxxxxxx>
  • To: "'[ExchangeList]'" <exchangelist@xxxxxxxxxxxxx>
  • Date: Sun, 30 May 2004 23:42:48 -0400

Yes, it is normal practice to apply service packs to any machines that have
Exchange or the Exchange System Manager loaded on them.

Mark Fugatt
MCSE, MCT, Microsoft Exchange MVP
Pentech Office Solutions Inc
Rochester, NY
Tel: 585 586 3890
Cell: 585 576 4750

-----Original Message-----
From: Paul Deen [mailto:pdeen@xxxxxxxxxxxx] 
Sent: Sunday, May 30, 2004 11:41 PM
To: [ExchangeList]
Subject: [exchangelist] Exchange2003 SP1 for ESM Question

Should we load/upgrade to Exchange SP1 for our Domain Controller running
only ESM, not Exchange?

More Details:
We have our Exchange server and our Domain Controllers separate. We have
recently applied SP1 on our Exchange 2003 with Windows 2003 Server. All
seems fine so far in our small environment. During the install we noticed
the 'upgrade' portion for ESM.

We had previously loaded the Exchange System Manager (ESM) on our 2003
Domain Controller (Native Mode) so we could get the extra Exchange Tabs and
Tasks. (There should be a way to manage Exchange tasks through Active
Directory Users and Computers (ADUC) without having to load IIS on your
Domain Controllers, keep things cleaner/safer. If there is please let
me know.) And I don't just mean the 'View:Advanced Features'
to show the one Exchange tab.

 I don't like loading things unnecessarily on the Domain Controllers, so, is
it safe (best practice) to apply Exchange 2003 SP1 to a Domain Controller to
update the ESM? Or is it not necessary?

List Archives:
Exchange Newsletters:
Exchange FAQ:
Other Internet Software Marketing Sites:
World of Windows Networking: Leading
Network Software Directory:
No.1 ISA Server Resource Site: Windows Security
Resource Site: Network Security Library: Windows 2000/NT Fax Solutions:
You are currently subscribed to this Discussion List as:
mark@xxxxxxxxx To unsubscribe send a blank email to

Other related posts: