• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 525
  • Last Modified:

What's the order for rebooting Exchange 2003, 2007 and 2010 serevices?

What's the order for rebooting Exchange 2003, 2007 and 2010 serevices?
0
SAM2009
Asked:
SAM2009
  • 2
  • 2
2 Solutions
 
Stelian StanNetwork AdministratorCommented:
For Exchange 2007 and 2010 you can run PS:

Test-ServiceHealth | Select-Object -Expand ServicesNotRunning | Start-Service

that way it will start the services in the right order.

As for Exchange 2003 I use a script:

net start "Microsoft Exchange Information Store"
net start "Microsoft Exchange MTA Stacks"
net start "Microsoft Exchange Event"
net start "Microsoft Exchange Management"
net start "Microsoft Exchange Routing Engine"
net start "Microsoft Exchange System Attendant"
0
 
EMJSRCommented:
In what context? Are some of those servers front-end or back-end server? Usually I would go in the order of LAN -> WAN (so innermost server in the LAN setup, to outermost server in the setup (if you look at the network as a ring, with the outer edge of the ring being exposed to the internet).

Other than that, the services usually come back automatically and Windows handles the order.

Please elaborate further if that didn't answer your question.
0
 
SAM2009Author Commented:
I'm just curious and want to know if there is any specific order to stop/start exchange service instead to reboot the mailbox server.
0
 
EMJSRCommented:
Oh I see. Well, usually the only service you need to restart is the "Exchange Information Store" service and perhaps the "Mail Transport" service. The "Information Store" service is enough though usually. And it should restart its own dependencies.
0
 
SAM2009Author Commented:
Thanks
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now