How many of you find it hard to track to Registry changes across your production machines?
We have some good tools such as sysinternals, regshot but these are limited to a machine.
What if you want to track data center level?
There are several usecases to track Registry. Some of them are as follows:
Does a software is installed/updated across all machines?
Does a machine violates a policy?
Track hardware inventory using Registry
Therefore, it is pretty evident Registry change tracking is useful for monitoring and troubleshooting scenarios.
Several customers agree that this is very important to track but clueless when we ask what they want to track. We can understand this and provided a curated list (considered from autoruns tool) in settings page.
I have worked on this promising feature end-end in Change Tracking solution under OMS at Microsoft. You can find more information at https://docs.microsoft.com/en-us/azure/log-analytics/log-analytics-change-tracking.
No comments:
Post a Comment