Restarting which Exchange services causes an outage
Greetings Our environment is Exchange 2007 SP2. We are running SCC, CCR for mailbox servers and seperate HT and CAS servers. Sometimes, if mails are q'ing on the HT's, I'll reboot the HT. Does anyone know if this is dangerous? Is there a risk of losing emails if I reboot the HT? Are there any services I can restart instead? Secondly, does anyone know what services on the mailbox server wil cause an outage/ disruption to users if they are restarted? And what sort of problem I should restart them for?
January 12th, 2011 3:23pm

I would be concerned with why you are getting emails queueing on the hub transport servers that requires a reboot or service restart to begin with. That is not standard practise and would indicate a problem. The only reason I reboot my Exchange servers are for the installation of updates, nothing else. However as long as Windows restart is carried out, and not a "pull the plug" then no content should be lost. With Exchange 2007 the clients connect directly to the mailbox server, so a reboot should not cause any problems for clients. Frequent reboots is not normal, and should be investigated. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources
Free Windows Admin Tool Kit Click here and download it now
January 12th, 2011 3:38pm

Hi The HT problem does occur very sporadically to be fair... > With Exchange 2007 the clients connect directly to the mailbox server, so a reboot should not cause any problems for clients Not even a few minutes disconnection? Are there any servers that I can restart (e.g. System Attendant, Topology service etc) without clients losing connection, even for a very short time?
January 12th, 2011 3:59pm

On Wed, 12 Jan 2011 20:54:10 +0000, Smith1974 wrote: >The HT problem does occur very sporadically to be fair... > >> With Exchange 2007 the clients connect directly to the mailbox server, so a reboot should not cause any problems for clients > >Not even a few minutes disconnection? Are there any servers that I can restart (e.g. System Attendant, Topology service etc) without clients losing connection, even for a very short time? If you have only a single HT server then users MAY notice a problem because the messages they send won't be delivered until the HT server is functioning again. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP
Free Windows Admin Tool Kit Click here and download it now
January 12th, 2011 10:27pm

Thank Rich, but what about restarting services on Exchange mailbox server? Which services will cause an outage/ disruption to users if they are restarted?
January 13th, 2011 2:52pm

On Thu, 13 Jan 2011 19:46:57 +0000, Smith1974 wrote: >Thank Rich, but what about restarting services on Exchange mailbox server? Which services will cause an outage/ disruption to users if they are restarted? Anything the deals with databases or connectivity or protocols will cause an interruption. Stopping services isn't something you should be doing. Is there a reason you do that? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP
Free Windows Admin Tool Kit Click here and download it now
January 13th, 2011 11:32pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics