Hello Mike, Thanks for the reply. When I went to install ESM on the Domain Controller, it popped up something telling me I needed to have some IIS components installed before I could install the ESM. Maybe I'm going insane faster than I thought, heh. This is with Windows 2003 AD in native mode. That's very interesting that your experiences with ESM on a DC did not require IIS. Can you or anyone else confirm this? I would love to remove all IIS components from my AD box, but was afraid it would break ESM or fudge Exchange components in AD. Thanks! PD -----Original Message----- From: Mike Liddekee [mailto:mliddekee@xxxxxxxxx] Sent: Tuesday, June 01, 2004 12:23 PM Subject: RE: Exchange2003 SP1 for ESM Question You need to run the SP update on any machine that has ESM loaded. Something curious in your message. You mentioned that you had to load IIS on the DC in order to do exchange tasks. The only thing you need to have loaded to administrator Exchange options for AD users is the AD Users & Computers along w/ the ESM. IIS isn't required. Regards, Mike Liddekee Network Engineer Humco Holding Group, Inc. 7400 Alumax Dr. Texarkana, TX 75501 Ph: (903) 831-7808 ext 697 -----Original Message----- From: Paul Deen [mailto:pdeen@xxxxxxxxxxxx] Sent: Sunday, May 30, 2004 10:41 PM To: [ExchangeList] Subject: [exchangelist] Exchange2003 SP1 for ESM Question http://www.MSExchange.org/ Hello, 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,...to 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? Thanks! PD ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this MSEXchange.org Discussion List as: mliddekee@xxxxxxxxx To unsubscribe send a blank email to