Return
-
Title
Why is the Compliance option check removed when a GPO is set to disable workflow? -
Description
Why is the Compliance check removed when a GPO is set to non-workflow?
-
Cause
This is by design.
-
Resolution
The reason the Compliance option is not available is that a GPO that has workflow disabled can never be out of compliance. If the GPO is set to "workflow disabled" the changes made to the GPO outside of GPOAdmin are automatically incorporated into the registered GPO within GPOAdmin by the watcher service.
So even if you edit it outside of version control (in the live environment) the watcher service picks up the change, incorporates it and increments the version number.
Changes made from GPOADmin are also immediately "deployed" to live, as this bypasses the working copy system of editing in Workflow Enabled objects.