question

MartinLopez-5556 avatar image
0 Votes"
MartinLopez-5556 asked MartinLopez-5556 answered

KMS and ADBA - OS segregation

Scenario

An organization is currently using a multi-Forest environment and activating W10 devices in Forest A, from a KMS infrastructure in Forest B.

They now want a native ADBA in Forest A to only activate their new W2019 servers, and leave the W10 clients (existing and new), to carry on activating from the old KMS server in Forest B.

Is this a possible scenario that can be achieved, or will new W10 clients added to Forest A be automatically activated by the new ADBA implementation?

Thanks.
Martin





windows-server
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MartinLopez-5556 avatar image
0 Votes"
MartinLopez-5556 answered

Hi,

I've figured out the solution.

Using the VLActivationType registry setting, you can control where the clients go by default for activation, and remain there.

Thanks,
Martin

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MartinLopez-5556 avatar image
0 Votes"
MartinLopez-5556 answered

Hi Luis,

Thanks for your reply.

The KMS section has been up and running for a while and activating W10 clients without any issue.

My question is centered around the introduction on ADBA and whether this will have any impact in the existing W10 KMS activations. We don't want the W10 clients to suddenly start seeing that ADBA is available and start using that instead of the current KMS infrastructure.

We only want ADBA to be used for the new Windows 2019 servers.

Thanks,
Martin

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.