# Configuration mgmt use case

**URL:** <https://forum.ansible.com/t/configuration-mgmt-use-case/28387>\
**Category:** AWX Project\
**Tags:** windows\
**Created:** [August 21, 2018, 5:34pm UTC](https://forum.ansible.com/t/configuration-mgmt-use-case/28387 "2018-08-21T17:34:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![harshal2006](https://avatars.discourse-cdn.com/v4/letter/h/a88e57/32.png) [@harshal2006](https://forum.ansible.com/u/harshal2006)\
**Post date:** [August 21, 2018, 5:34pm UTC](https://forum.ansible.com/t/configuration-mgmt-use-case/28387/1 "2018-08-21T17:34:53Z")

</div>

Since system audit tracker is deprecated, how can we check changes to configs? Also, I created playbook that check specific registry keys on Windows with register but can’t see them in facts in those hosts under inventory. Please help!

Thanks

---

<div class="post-metadata">

**Author:** ![Christopher\_Meyers](https://avatars.discourse-cdn.com/v4/letter/c/3e96dc/32.png) [@Christopher\_Meyers](https://forum.ansible.com/u/Christopher_Meyers)\
**Post date:** [August 21, 2018, 5:43pm UTC](https://forum.ansible.com/t/configuration-mgmt-use-case/28387/2 "2018-08-21T17:43:58Z")

</div>

The “replacement” for system tracking is the system\_tracking logger in AWX. AWX will emit changes in facts as it detects them over the system\_tracking logger. On the other end, you can have something like a elk stack to store those log messages and have a history.

In reply to your question about windows facts via register; I’m going to need more information. Maybe your example playbook and job template setup in AWX.

-Chris