

That's when things went from bad to really bad. After about an hour of "undoing changes", the servers restarted. At 99% completion, I was told that one of the updates had failed (impossible to know which one), and all pending updates were going to be undone. They obviously needed to be applied, so I began the process. When I checked for updates, there were over 200 available updates, nearly all of which were "critical". I had several Windows Server 2012 R2 servers to update. Today's post is in response to a problem I encountered last week. Documenting processes and resolutions is a key part of my business, and that can sometimes leak out to the public. I love it when someone else gets something out of my posts, but in some cases, the only person that may get something out of a post is me. Today's post may not be for everyone, and that's completely ok.

" Has Kevin gone mad? Why is he talking about Windows, and Windows Server at that?" Well, the truth is, I use and support Windows on a daily basis, even Windows Server.
