This can happen in the following scenario:
- Both changes were made without restarting the watcher service
- The change, and subsequent reversion of the change, cause the "hash value" to stay the same.
This hash value is stored by the watcher service on startup.
This does not affect changes to GPO settings, it seems to be only relevant when the AD / SYSVOL version number do not change.
A change to the User or Computer Configuration enabled setting, and reverting to the original value, will cause this.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center