From ee919792c1d85b7c95e447e54f649fa55720af2f Mon Sep 17 00:00:00 2001
From: Orlando Rodriguez <49177883+ojrb@users.noreply.github.com>
Date: Wed, 5 Jun 2019 20:26:34 -0500
Subject: [PATCH] Update hello-adequate-domain-controllers.md

---
 .../hello-for-business/hello-adequate-domain-controllers.md    | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/windows/security/identity-protection/hello-for-business/hello-adequate-domain-controllers.md b/windows/security/identity-protection/hello-for-business/hello-adequate-domain-controllers.md
index 0f5605445d..681692287c 100644
--- a/windows/security/identity-protection/hello-for-business/hello-adequate-domain-controllers.md
+++ b/windows/security/identity-protection/hello-for-business/hello-adequate-domain-controllers.md
@@ -68,6 +68,9 @@ There are several conclusions here:
 
 The preceding was an example to show why it's unrealistic to have a "one-size-fits-all" number to describe what "an adequate amount" means.  In the real world, authentication is not evenly distributed across domain controllers.
 
+> [!NOTE]
+>There was an issue with key trust on Windows Server 2019, refer to [KB4487044](https://support.microsoft.com/en-us/help/4487044/windows-10-update-kb4487044) in order to fix it.
+
 ## Determining total AS Request load
 
 Each organization needs to have a baseline of the AS request load that occurs in their environment. Windows Server provides the KDC AS Requests performance counter that helps you determine this.