From 3087e46f8bf903fd11b3f6677ad3bb1ead3beb3e Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Tue, 29 Oct 2019 11:16:03 +0500 Subject: [PATCH 1/5] Added a note I have added a note regarding the SCP script which is not needed to be executed. Problem: https://github.com/MicrosoftDocs/windows-itpro-docs/issues/4776 --- .../hello-for-business/hello-cert-trust-adfs.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md b/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md index 4563787217..16e5b256e2 100644 --- a/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md +++ b/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md @@ -363,6 +363,9 @@ Active Directory Federation Server used for Windows Hello for Business certifica Approximately 60 days prior to enrollment agent certificate’s expiration, the AD FS service attempts to renew the certificate until it is successful. If the certificate fails to renew, and the certificate expires, the AD FS server will request a new enrollment agent certificate. You can view the AD FS event logs to determine the status of the enrollment agent certificate. ### Service Connection Point (SCP) in Active Directory for ADFS Device Registration Service +>[!NOTE] +> Normally this script is not needed as enabling Device Registration via the ADFS Management console already creates the objects. You can validate the SCP using the below script. + Now you will add the Service connection Point to ADFS device registration Service for your Active directory by running the following script: >[!TIP] From f7558e55397cc84c7beab8a7735e677b09f31501 Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Thu, 31 Oct 2019 12:55:38 +0500 Subject: [PATCH 2/5] Update windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- .../hello-for-business/hello-cert-trust-adfs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md b/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md index 16e5b256e2..91d3354350 100644 --- a/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md +++ b/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md @@ -363,7 +363,7 @@ Active Directory Federation Server used for Windows Hello for Business certifica Approximately 60 days prior to enrollment agent certificate’s expiration, the AD FS service attempts to renew the certificate until it is successful. If the certificate fails to renew, and the certificate expires, the AD FS server will request a new enrollment agent certificate. You can view the AD FS event logs to determine the status of the enrollment agent certificate. ### Service Connection Point (SCP) in Active Directory for ADFS Device Registration Service ->[!NOTE] +> [!NOTE] > Normally this script is not needed as enabling Device Registration via the ADFS Management console already creates the objects. You can validate the SCP using the below script. Now you will add the Service connection Point to ADFS device registration Service for your Active directory by running the following script: From 0f6551c614a07b63210b0344f18e23af599f0b10 Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Thu, 31 Oct 2019 12:55:49 +0500 Subject: [PATCH 3/5] Update windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- .../hello-for-business/hello-cert-trust-adfs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md b/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md index 91d3354350..0bceea2876 100644 --- a/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md +++ b/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md @@ -368,7 +368,7 @@ Approximately 60 days prior to enrollment agent certificate’s expiration, the Now you will add the Service connection Point to ADFS device registration Service for your Active directory by running the following script: ->[!TIP] +> [!TIP] > Make sure to change the $enrollmentService and $configNC variables before running the script. ```Powershell From b5d4d883f30d9183400a69518f11efabe7f2bc9a Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Sun, 3 Nov 2019 09:50:05 +0500 Subject: [PATCH 4/5] Update windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- .../hello-for-business/hello-cert-trust-adfs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md b/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md index 0bceea2876..977d7b9dd5 100644 --- a/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md +++ b/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md @@ -364,7 +364,7 @@ Approximately 60 days prior to enrollment agent certificate’s expiration, the ### Service Connection Point (SCP) in Active Directory for ADFS Device Registration Service > [!NOTE] -> Normally this script is not needed as enabling Device Registration via the ADFS Management console already creates the objects. You can validate the SCP using the below script. +> Normally this script is not needed, as enabling Device Registration via the ADFS Management console already creates the objects. You can validate the SCP using the below script. Now you will add the Service connection Point to ADFS device registration Service for your Active directory by running the following script: From 48e2bb48ef06855423f56b45de6f32b3c0461fec Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Wed, 6 Nov 2019 13:13:06 +0500 Subject: [PATCH 5/5] Update windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com> --- .../hello-for-business/hello-cert-trust-adfs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md b/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md index 977d7b9dd5..61d33f495d 100644 --- a/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md +++ b/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md @@ -364,7 +364,7 @@ Approximately 60 days prior to enrollment agent certificate’s expiration, the ### Service Connection Point (SCP) in Active Directory for ADFS Device Registration Service > [!NOTE] -> Normally this script is not needed, as enabling Device Registration via the ADFS Management console already creates the objects. You can validate the SCP using the below script. +> Normally this script is not needed, as enabling Device Registration via the ADFS Management console already creates the objects. You can validate the SCP using the script below. Now you will add the Service connection Point to ADFS device registration Service for your Active directory by running the following script: