Exchange 2007 Services Startup Types

How should the Exchange 2007 Services be set to start up?

Unfortunately not all exchange 2007 Services are normally on automatic startup type. And when a Exchange update failed for some reason or you used the silent switches (/q /n) with the Rollups you can end up having all Services disabled wondering what their original state was. It wouldn't be dramatic if all Exchange services are on automatic but I'd try to have only the ones running my environment really needs.

Looking for documentation I only found http://technet.microsoft.com/en-us/library/aa998342.aspx which lists the services and if they are required for exchange to work. But that's not the end of the story as some Services like the "Microsoft Exchange Search Indexer" and "Microsoft Search (Exchange)" aren't vital but enabled by default.

So let's try to find out what is the right setting for each situation. Please add your experiences and correct me where I'm wrong here.

So what about the Optionals?
Microsoft Exchange Search Indexer and Microsoft Search (Exchange) on automatic except you don't want it.
POP3 and IMAP4 only on automatic if you intend to enable these protocols
Microsoft Exchange EdgeSync only when an edge Server is used
Microsoft Exchange Anti-spam Update on automatic only if you are using the Anti-Spam feature. On an Edge Server that might be a given but on a Hub its not installed by default. (Install-AntiSpamAgents.ps1)
Microsoft Exchange Monitoring on manual
Microsoft Exchange Transport Log Search on automatic as you will have to search your transport log sooner or later.

And it gets more complicated with the additional Services like IIS.
From what I researched: (assumed all roles on dedicated servers)
on a CAS: HTTP SSL, IISAdmin, and World Wide Web on automatic
on a MBX: HTTP SSL, IISAdmin, and World Wide Web on manual or disabled as I have a Server like that doing just fine. But if your users enter https://Mailboxserver/Exchange instead of https://CASServer/owa to access OWA then I think all should be automatic.
On a HUB: I'm not sure. There is no World Wide Web Service installed. The HTTP SSL is on manual. The IIS Admin Service is on automatic, though on one machine it's not installed, so it might not be needed at all.

What happens when I patch the Servers?
The script "\Bin\ServiceControl.ps1" defines on line 26 which services are "affected" for which Role. With -BeforePatch it records their state and disables them. With -AfterPatch it sets them back to the recorded state. So there is no knowledge embedded on how the services need to start.

But from the List you see some more services you need to examine:
Clussvc - automatic if it is a clustered Mailbox Server
OnePoint and MOM that both belong to Microsoft's System Center Operations Manager so automatic if they exist.
It's interesting that the HTTPFilter Service is not in the List for the CAS and so it will not be stopped for patching. Maybe someone knows about that.