This is expected behavior, precisely because it is a NEW KMS server. I feel like MS licensing and activation needs a whole 12 month semester to actually learn properly. I would like to point out that I'm open to switching to AD activation too. How is this possible? It's a brand new server with a brand new volume license key, that I've confirmed is valid.ĭoes anyone have any experience with this horrendous licensing situation and any ideas on how to proceed? I have nothing to go on right now, StackExchange, WOSHub and even Microsoft themselves dont seem to have any proper/valid documents on this. When I try to activate a 2019 or 2022 server client to this new KMS, the error reports that I have insufficient KMS count to activate. Several reboots later and I'm still stumped. The issue is, it doesnt seem to want to work as a KMS host, and flat out refuses to activate anything I throw at it. This was all successful, and the new KMS server is now activated, with the annoying notifications gone. I've then added the KMS host key for 2022 using 'slmgr /ipk ', added firewall rules where required and enabled it. So I've deployed a new KMS server host using Server 2022, and successfully installed the VAMT server roles.
Obviously 2022 is not compatible with 2012 and will require a new KMS server host. I have my KMS keys and MAK keys - ideally we want to continue to use KMS to activate new servers as we presently do.Īt present, we have a KMS host (running 2012R2), which is real simple - installed the KMS host key years and years ago, and its been sitting there, requiring zero maintenance and happily activating all our 2012R2 servers. We have been running Server 2012R2 for some time now, and its been well and truly sweated out as an asset now - we've purchased volume licensing for Server 2022/2019 at great cost. As per usual we have a new Microsoft Server OS and a whole new, confusing, badly planned, poorly implemented volume licensing/activation tools.
0 kommentar(er)
