Here is a closer look at the two features I would like to bring out. Specifically we relied on two features in ProcMon (boot logging and process tree view) that I want to show you that helped pin point this issue. With that piece of information we decided to leverage a monitoring tool (ProcMon) from SysInternals to trace what is happening on reboot. This issue appeared to happen sometime after reboot of the KMS server and once fixed never reverted until it was rebooted. We had one piece of information that turned out to be very helpful. Review great blogs such as this one on how to ramp up on KMS. Try slmgr.exe (this is the command line tool to manage Site Licenses) to output KMS key information. ![]() So where to start troubleshooting… Do you have the right key? Recently I helped discover an odd issue with some KMS servers losing their KMS Server Key and becoming a KMS Client. I wanted to share an issue that was resolved using tools from SysInternals. First published on TechNet on Sep 08, 2014Äougga here with a short and simple post.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |