Proper Shutdown and Startup sequence for Exchange 2007 SP1. Configuration of Exchange 2007 is below 1. Mail Server (Running on Physical Server) 2. CAS (Running On Hyper-V VHD) 3. HUB (Running On Hyper-V VHD) 3. EDGE (Running On Hyper-V VHD) Note that CAS, HUB and EDGE on 2 Physical Server using Hyper-V (VHD). And Mail Server is not on a Cluster Group and Mail server and Domain Controller is running on different Physical Servers. Please let me know Proper Sequence for Startup and shutdown and which services on each server to run and stop when startup and shutdown sequence. Regards

Start on the outside and work in. So Edge, Hub, CAS, mailbox. Reverse it for startup. No need to stop services maually. Also Exchange 2007 SP1 is no longer supported, you should be on Exchange 2007 with the latest rollup. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

No need to Dismount the database and stop service. Before we got problem when I didn't dismount and stopped service, After starting the server i was unable to mount the .EDB file.

Hi do by this way 1. CAS - now u blocked all clients traffic that means no point of sending a new email 2.Edge -now u blocked all inbound smtp traffic so no point of receiving mail 3.Hub- so now hub will be obviously free 4. Mailbox servers at last For powering follow this sequence mailbox,hub,cas and edge

Start on the outside and work in. So Edge, Hub, CAS, mailbox. Reverse it for startup. No need to stop services maually. Also Exchange 2007 SP1 is no longer supported, you should be on Exchange 2007 with the latest rollup. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Hi do by this way 1. CAS - now u blocked all clients traffic that means no point of sending a new email 2.Edge -now u blocked all inbound smtp traffic so no point of receiving mail 3.Hub- so now hub will be obviously free 4. Mailbox servers at last For powering follow this sequence mailbox,hub,cas and edge Clients do not connect to CAS role on Exchange 2007, unless Outlook Anywhere/OWA. They connect directly to the mailbox role. I have never dismounted databases for a restart or shutdown of the server, and never had a problem with doing so. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Thank for you Quick respond. The .edb file was unable to mount because on the status of shutdown it showed Dirty shutdown. What kind of problem will this be. But just to be on the safe side. its okay to dismount the .edb file and stop service "Information Store" and then shutdown the Server. regards

On Tue, 27 Mar 2012 17:14:45 +0000, IRFAN_MV wrote: >The .edb file was unable to mount because on the status of shutdown it showed Dirty shutdown. What kind of problem will this be. Usually one where you've killed the IS service (or "reset" the server instead of shutting it down) rather than wait for it to shut down normally. >But just to be on the safe side. its okay to dismount the .edb file and stop service "Information Store" and then shutdown the Server. Yes. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Tue, 27 Mar 2012 17:14:45 +0000, IRFAN_MV wrote: >The .edb file was unable to mount because on the status of shutdown it showed Dirty shutdown. What kind of problem will this be. Usually one where you've killed the IS service (or "reset" the server instead of shutting it down) rather than wait for it to shut down normally. >But just to be on the safe side. its okay to dismount the .edb file and stop service "Information Store" and then shutdown the Server. Yes. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

I have also seen this happen when AV exclusions are not set correctly, or some other third party tool doesn't allow Exchange to shutdown gracefully. If it is happening on every reboot/shutdown then that is a sign of a problem in general. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.