Exchange Server

Slow Shutdown of Exchange 2003 Server Installed on DC

Exchange 2003 on a Domain Controller

or

“Why does my Exchange 2003 server take 10 minutes or more to shutdown” and other problems

Sponsored Content

What is “Inside Microsoft Teams”?

“Inside Microsoft Teams” is a webcast series, now in Season 4 for IT pros hosted by Microsoft Product Manager, Stephen Rose. Stephen & his guests comprised of customers, partners, and real-world experts share best practices of planning, deploying, adopting, managing, and securing Teams. You can watch any episode at your convenience, find resources, blogs, reviews of accessories certified for Teams, bonus clips, and information regarding upcoming live broadcasts.

It seems that most users that install Exchange Server 2003 on a Windows Server 2003 machine that is also configured as a Domain Controller may experience a slow shutdown when they try to reboot/shutdown the server.

This is because the Active Directory related services shut down before the Exchange services, thus causing the Exchange services to fail repeatedly while looking for the DS. Exact and detailed explanations for this behavior and restrictions can be found in the KB articles listed below.

Note: Although installing Exchange on a server that is also a DC is possible, changing the server status while Exchange is already installed is NOT supported by Microsoft. For an example, if you demote a DC with Exchange Server install to a member server, the DS2MB service (which copies Active Directory data from A/D to the IIS metabase) stops working throughout an Exchange organization. Although some of these issues CAN be fixed, un-knowing administrators might ruin their configurations and as stated before – they will not be supported by Microsoft.

There are 2 known solutions for this problem (besides listening to me and NOT installing Exchange on a DC in the first place…). One is to change the timeout for a failed service to shutdown itself, and the second is to manually stop the Exchange services BEFORE shutting down the server.

Method #1: Services kill timeout

Follow these easy steps:

  1. Run Regedit and navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WaitToKillServiceTimeout
  1. The default value of WaitToKillServiceTimeout is set to 600000. Change it to 20000.
  2. Exit the registry editor and reboot the server.

Note: Changing the WaitToKillServiceTimeout value may have some undesired effects on other services, use this method at your own risk.

Method #2: Manually stop Exchange related services – my choice

The best choice is to manually shutdown the Exchange related services before trying to shutdown or reboot the server. You can do so manually by going to the Services snap-in in the Administrative Tools menu and stopping the specific Exchange related services, or doing so from the CMD:

​ net stop MSExchangeES
 net stop IMAP4Svc
 net stop POP3Svc
 net stop RESvc
 net stop MSExchangeSRS
 net stop MSExchangeMGMT
 net stop MSExchangeMTA
 net stop MSExchangeIS /Y
 net stop MSExchangeSA /Y

Alternatively, you could use the following script (Original script written by Yizhar Hurwitz – thanks!):

Download Script to Shutdown / Reboot Exchange 2003 on a DC (2kb)

Double-click the installation file, it will copy the script to a folder on your server and create a shortcut on the Quick Launch toolbar. Whenever you want to shutdown or reboot your server, click on the shortcut icon.

Links

Faster reboot on Exchange Server 2003 servers that are also Domain Controllers – 555526

Exchange Server 2003 and Domain Controllers – A Summary

Overview of Operating System and Active Directory Requirements for Exchange Server 2003 – 822179

Exchange Server 2003 Computer Takes Longer Than You Expect to Shut Down – 829361

DCPROMO does not retain permissions on some IIS folders – 332097

Exchange Considerations for Promoting a Domain Controller to a Global Catalog Server – 304403

Exchange Server-Related Considerations for Demoting a Global Catalog Server to a Domain Controller – 305065

Global catalog server placement and ratios in an Exchange 2000 Server organization or in an Exchange Server 2003 organization – 875427

Exchange Server 2003 and Domain Controllers – A Summary

Related Topics:

BECOME A PETRI MEMBER:

Don't have a login but want to join the conversation? Sign up for a Petri Account

Register
Comments (0)

Leave a Reply

External Sharing and Guest User Access in Microsoft 365 and Teams

This eBook will dive into policy considerations you need to make when creating and managing guest user access to your Teams network, as well as the different layers of guest access and the common challenges that accompany a more complicated Microsoft 365 infrastructure.

You will learn:

  • Who should be allowed to be invited as a guest?
  • What type of guests should be able to access files in SharePoint and OneDrive?
  • How should guests be offboarded?
  • How should you determine who has access to sensitive information in your environment?

Sponsored by:

 
Office 365 Coexistence for Mergers & Acquisitions: Don’t Panic! Make it SimpleLive Webinar on Tuesday, November 16, 2021 @ 1 pm ET

In this session, Microsoft MVPs Steve Goodman and Mike Weaver, and tenant migration expert Rich Dean, will cover the four most common steps toward Office 365 coexistence and explain the simplest route to project success.

  • Directory Sync/GAL Sync – How to prepare for access and awareness
  • Calendar Sharing – How to retrieve a user’s shared calendar, or a room’s free time
  • Email Routing – How to guarantee email is routed to the active mailbox before and after migration
  • Domain Sharing – How to accommodate both original and new SMTP domains at every stage

Aimed at IT Admins, Infrastructure Engineers and Project Managers, this session outlines both technical and project management considerations – giving you a great head start when faced with a tenant migration.the different layers of guest access and the common challenges that accompany a more complicated Microsoft 365 infrastructure.

Sponsored by: