KMS and ADBA - OS segregation

Martin Lopez 96 Reputation points
2021-08-04T09:53:17.163+00:00

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
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,108 questions
0 comments
Accepted answer
  1. Martin Lopez 96 Reputation points
    2021-09-14T11:05:48.58+00:00

    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

    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Martin Lopez 96 Reputation points
    2021-08-06T09:28:05.34+00:00

    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

    0 comments