

I think I'm good for now, but I'll keep an eye on the numbers to see if I see a quick decrease again.

This is good, as I can compare it against my "All MS OS" list for machines missing the key, and can look for the specific values that won't play nice with our patching software, and update both of them via script. In many cases, you are creating the key when you set it for the first time.Īfter a couple days, this seems to have settled down, and I'm showing 1928 assets with a key value. It keeps windows from applying its own patches until you have a patch window, so you can minimize interruption. This is one of the values you change in a windows OS if you are managing updates from a 3rd party commercial product.
