![]() ![]() If you wish, you can generate an output status from your KMShost, and post that here for us to analyse and confirm for you. [This is all detailed in the wiki article I wrote above, and in the links I placed in that wiki article) (Office KMShost is a different situation - Office KMShost is Office-version-specific) You can also "upgrade" the KMShost issuing capability, such that an "older" Windows Server version can issue activations for "newer" KMSclient versions, by installing the relevant KMS Host Pack and the corresponding KMShost WS2012R2, when configured as a KMShost, can issues KMSclient activations for WS2012R2/WS2012//WS2008R2/WS2008/Win8.1/Win8.0/Win7/WinVista, and, there is no need to "install" any other Windows KMShost keys on that KMShost machine. WS2012 when configured as a KMShost, can issue KMSclient activations for WS2012/WS2008R2/WS2008/Win8.0/Win7/WinVista, and, there is no need to "install" any other Windows KMShost keys on that KMShost machine. " then that certainly is a "client OS" product key.Īnd, such a key cannot be "installed" on a Windows Server OS KMShost machine.Īnd, there is no need to do so, because, a Windows Server OS which is correctly configured with Windows Server KMShost product key, is already capable of issuing activations for KMSclients of the "client OS" type. ![]() If you are using a CSVLK (KMShost product key) labelled "Windows 7. I have 2 volume license windows 7 keys for KMS activation. I am not using a "client OS" product key for activation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |