For manually installed services, we -should- keep the behavior. What good is it to have a user install a reference to an Apache service which won't work?
For automated installs, e.g. the package installer, I see the benefit of offering more than one behavior. E.g. the win32 installer, or someone's external deployment scripts, should be able to override the tests.
Would that satisfy your requirements?
Indeed it would!
Bill