Exchange services Disabled and not starting

How far into the build are you?  It may be quicker to start the installation again that to trouble-shoot the problem you currently have.
Was everything working before the Windows Update?
I can't see an update setting the services to disabled - sounds like something else is wrong.

Hi,
Do you have enough resources on your Server?
I mean what is the RAM/HDD etc. Backpressure is the keyword from the symptoms here
Thanks
Nitin Gupta (gupnit)

Backpressure does not disable services.

Hi,

Luckilly we where at a fairly early stage. There is only a test mailboxes. We had started replicating Public folders but this wouldn't be a problem if we had to start again. I hadn't started configuring connectors or much else.

In relation to the Hardware it's got 16Gb of Memory and two quad core 2.83Ghz processors. Disks are 2 SAS 68Gb drivers Raid-1 and 4 SAS 136Gb Raid-5. Let me know if you need disk speeds on this.

We where able to get some of the services running by applying this http://msexchangeteam.com/archive/2008/07/08/449159.aspx

But I'm having problems connecting to this server via outlook.

As it is a new install - I would be inclined to wipe it and start again.  If it gives you trouble at the start, you can never be sure that it won't continue to do so further down the line.

I never said BP disables serives. I didnt read properly, I saw Transport and Mail, and quick response was BP.!!! A quick check was what I wanted. Mail Delivery.
I would be inclined to check my Setup Logs and Event Viewer, if you are interested in finding the reason, rather than just uninstalling !! Who knows you get same issue again. Run ExBPA and share the report.
 

One option I was considering was a reinstall. I'm assuming a reinstall of win 2008 and then reinstalling exchange with the setup /m:recoverserver option is the best way to do this.can you confirm if the  /DoNotStartTransport option is necessary.

When you say the setup is still in early stages, is the Exchange Server being installed in the Production Environment?
If you are setting up from scratch, then uninstall and go fresh
 

I would start totally fresh rather than try to take a few short cuts especially if nothing critical is on the new exchange box.

The problem has occurred since failed windows update; so it is important to know which DLL/EXE files were updated partially or the files changed might have caused the problem.

Please verify the updates as per installation, check articles which files are getting updated. It will help!!

Hi,
Just wanted to get back to you on a few of those questions.
Yea this server is part of our production environment.
I'm more familiar with the setup /m:recoverserver option than with the option of uninstalling it and removing public folders and connectors. (Some points/guidance/links on this would be great).
I'll go through the logs now to try and confirm what caused the issue.

ExBPA did it show anything yet?

Here is the setup /m:recoverserver details (which you probably know):
http://technet.microsoft.com/en-us/library/aa998656(EXCHG.80).aspx
How to remove Exchange 2007 from a server:
http://technet.microsoft.com/en-us/library/bb123893(EXCHG.80).aspx 

That's good news - hope it stays that way.  Please shout if you need more help.
Alan

No objections from me ;-)