SharePoint 2010 appication pools in a stopped or shutdown state after rebooting the server

After rebooting your SharePoint 2010 farm you noticed that all (or some) application pools are in a stopped state! This will more likely occur if you have a AD Domain Policy applied to your SharePoint servers. If you do have a Active Directory Domain Policy applied to your SharePoint 2010 servers, ensure the Application Pool user account  (normally a AD user account) has “Log on as batch job” and "Log on as service” rights in the policy. The best way to do this without editing the policy it self each time a new web application is created, is to create a AD Security Group and assign the application pool user accounts as members. This way you only need to specify the AD Security Group in the domain policy!