However, I don't understand why they even try to talk with the KMS server in the first place as we are running AD activation for these OS'.Īnother finding is that a lot of W7 clients seems to get activated with code 0x0. They all seem to be rejected with error code 0xC004F042 which means mismatch according to MS doc (. Looking at the event viewer log I found attempts from several 2012 servers and W10 clients. Windows Server(R), ServerStandard edition So, current licenses looking at VAMT on the 2008 R2 are: In this analysis I've discovered a few things that created some questions which I was hoping someone could help with. My experience with KMS is little to none as this is the first i'm ever digging into it, so sry if my questioning are at a low level. We are starting an analysis phase of a migration plan for our KMS running on 2008 R2 to a new Windows 2019.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |