![]() ![]() Until then I will just keep plugging in activation keys until the issue is resolved. I am not looking to resolve the issue as this is not my department I am merely looking for a possible reason. We preformed an internal DNS name change late last year, (or so I was told) and think that this may be the underlying cause of the issue. What I am suspecting, and it hasn't been confirmed, is a DNS name change snafu. Besides, current activations should in no way affect new activations. I also understand that the activation key is valid for 180 days, but this shouldn't be an issue. Now I am in no way a KMS guru, but from my understanding of how it works, it needs a minimum of 25 host machines that need activated (for Windows 7). It has been three weeks now with no word, so I am reaching out here of a possible reason why these machines are not activating. I was told that they would look into it and get back with me. This issue has been address with the parties who are in charge of the KMS Server and the KMS Keys. Beginning in January this year, while replacing machines, (Windows 7 Enterprise) I have found that the machines are not being activated with Microsoft via the KMS Server. We are running a KMS Server and up until now I have not had any issues.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |