2.0 applications can be started at system boot or in order, can be run as LocalSystem,, and can be more easily made to be cluster aware. This feature is configured at deployment in the Component Services GUI, not programmatically. Low memory scenarios. For example, a component might need to create another component, but no memory is left for that action to complete. Low memory scenarios are not well debugged by most developers, and Microsoft hasn't created an infrastructure to handle these scenarios.
Resume allows future activations.
Disable prevents future activations, though existing activations are not affected, and state remains during a reboot. Enable allows future activations. This leaves the target environment virtually untouched. Binary implementation sharing will require less code and offer developers a way to get their solutions to market more quickly. Public components can be activated from other applications, while Private components can only be seen and activated from other components within the same application.