From 54f1a411e866d58dfff95e61a9c5b1a6c40d2cff Mon Sep 17 00:00:00 2001 From: Frank Rojas <45807133+frankroj@users.noreply.github.com> Date: Mon, 16 Oct 2023 11:53:44 -0400 Subject: [PATCH 1/3] Add additional links Add additional links --- .../activate-using-key-management-service-vamt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/volume-activation/activate-using-key-management-service-vamt.md b/windows/deployment/volume-activation/activate-using-key-management-service-vamt.md index 8c36f27930..6d911b23fc 100644 --- a/windows/deployment/volume-activation/activate-using-key-management-service-vamt.md +++ b/windows/deployment/volume-activation/activate-using-key-management-service-vamt.md @@ -191,7 +191,7 @@ For more information about the use and syntax of the script `slmgr.vbs`, see [Sl > [!IMPORTANT] > -> Clients require RPC over TCP/IP connectivity to the KMS host to successfully activate. +> Clients require RPC over TCP/IP connectivity to the KMS host to successfully activate. For more information, see (Key Management Services (KMS) activation planning: Network requirements)[/windows-server/get-started/kms-activation-planning#network-requirements] and (Remote Procedure Call (RPC) errors troubleshooting guidance)[/troubleshoot/windows-client/networking/rpc-errors-troubleshooting] ## Related articles From 5ed70a1ef89cb807beb4fab0104f7cdb0fe836d7 Mon Sep 17 00:00:00 2001 From: Frank Rojas <45807133+frankroj@users.noreply.github.com> Date: Mon, 16 Oct 2023 11:58:28 -0400 Subject: [PATCH 2/3] Update ms.date Update ms.date --- .../activate-using-key-management-service-vamt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/volume-activation/activate-using-key-management-service-vamt.md b/windows/deployment/volume-activation/activate-using-key-management-service-vamt.md index 6d911b23fc..12f1d9ac39 100644 --- a/windows/deployment/volume-activation/activate-using-key-management-service-vamt.md +++ b/windows/deployment/volume-activation/activate-using-key-management-service-vamt.md @@ -8,7 +8,7 @@ author: frankroj manager: aaroncz ms.author: frankroj ms.localizationpriority: medium -ms.date: 10/13/2023 +ms.date: 10/16/2023 ms.topic: how-to ms.collection: - highpri From c499dc1ffcdb2971da2102b2b48362181be3a103 Mon Sep 17 00:00:00 2001 From: Frank Rojas <45807133+frankroj@users.noreply.github.com> Date: Mon, 16 Oct 2023 12:04:14 -0400 Subject: [PATCH 3/3] Fix links Fix links --- .../activate-using-key-management-service-vamt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/volume-activation/activate-using-key-management-service-vamt.md b/windows/deployment/volume-activation/activate-using-key-management-service-vamt.md index 12f1d9ac39..b1056c9728 100644 --- a/windows/deployment/volume-activation/activate-using-key-management-service-vamt.md +++ b/windows/deployment/volume-activation/activate-using-key-management-service-vamt.md @@ -191,7 +191,7 @@ For more information about the use and syntax of the script `slmgr.vbs`, see [Sl > [!IMPORTANT] > -> Clients require RPC over TCP/IP connectivity to the KMS host to successfully activate. For more information, see (Key Management Services (KMS) activation planning: Network requirements)[/windows-server/get-started/kms-activation-planning#network-requirements] and (Remote Procedure Call (RPC) errors troubleshooting guidance)[/troubleshoot/windows-client/networking/rpc-errors-troubleshooting] +> Clients require RPC over TCP/IP connectivity to the KMS host to successfully activate. For more information, see [Key Management Services (KMS) activation planning: Network requirements](/windows-server/get-started/kms-activation-planning#network-requirements) and [Remote Procedure Call (RPC) errors troubleshooting guidance](/troubleshoot/windows-client/networking/rpc-errors-troubleshooting). ## Related articles