windows server 2019 kms activation with kms pico

Self-answer as I have now been able to empirically test this. So I can always postpone adding the 2nd DC until AFTER we have the KMS and then re-license the 1st DC.īut it would require some extra work and another travel to go on-site (no remote access), which I would like to avoid.ĭoes anyone have any experience with this ? I guess the real question is if a KMS setup with unreachable KMS server is treated as an evaluation installation or not.įor the new domain we need 2 DC's anyway. I know that a DC setup with an evaluation license can't be upgraded to proper license, unless you first move the AD roles to another server and reduce this DC to a normal server. I'm hoping I can configure KMS on the Server 2019 (without having actual activation because KMS is not responding) and then can just continue with the domain setup and it will pick up the activation later. There is a lengthy approval process (lots of red tape)Īnd I will not have KMS access for the new servers until a few days, possibly weeks AFTER the installation date for the DC, but we really need to get that domain operational ASAP. Configure the KMS and get the license/activation working, before I add the AD roles.īut: In this case the new domain is behind a firewall and has no normal connection to the company network.ĭue to an administrative oversight the firewall rules to allow access to the KMS were not requested in time.

Normally I would just install the Windows server without a license. Normally we obtain our server licenses/activation from the company KMS system and we need to do that in this case as well.

I'm tasked with setting up a Windows 2019 AD environment (new domain) from scratch.

Windows server 2019 kms activation with kms pico