From 11ae2c3f71a0d29d8e8cad5915266a31b7cd7c6c Mon Sep 17 00:00:00 2001 From: botmoto <42125490+botmoto@users.noreply.github.com> Date: Sun, 7 Apr 2019 16:23:10 -0700 Subject: [PATCH 01/67] Update credential-guard-manage.md --- .../credential-guard-manage.md | 20 +++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) diff --git a/windows/security/identity-protection/credential-guard/credential-guard-manage.md b/windows/security/identity-protection/credential-guard/credential-guard-manage.md index 0edce00395..c5e98ffb47 100644 --- a/windows/security/identity-protection/credential-guard/credential-guard-manage.md +++ b/windows/security/identity-protection/credential-guard/credential-guard-manage.md @@ -20,6 +20,7 @@ ms.date: 03/01/2019 **Applies to** - Windows 10 - Windows Server 2016 +- Windows Server 2019 Prefer video? See [Windows Defender Credential Guard Deployment](https://mva.microsoft.com/en-us/training-courses/deep-dive-into-credential-guard-16651?l=sRcyvLJyC_3304300474) in the Deep Dive into Windows Defender Credential Guard video series. @@ -150,9 +151,13 @@ To disable Windows Defender Credential Guard, you can use the following set of p 1. If you used Group Policy, disable the Group Policy setting that you used to enable Windows Defender Credential Guard (**Computer Configuration** -> **Administrative Templates** -> **System** -> **Device Guard** -> **Turn on Virtualization Based Security**). 2. Delete the following registry settings: - HKEY\_LOCAL\_MACHINE\\System\\CurrentControlSet\\Control\\LSA\LsaCfgFlags - - HKEY\_LOCAL\_MACHINE\\Software\\Policies\\Microsoft\\Windows\\DeviceGuard\\EnableVirtualizationBasedSecurity - - HKEY\_LOCAL\_MACHINE\\Software\\Policies\\Microsoft\\Windows\\DeviceGuard\\RequirePlatformSecurityFeatures - + - HKEY\_LOCAL\_MACHINE\\Software\\Policies\\Microsoft\\Windows\\DeviceGuard\\LsaCfgFlags +> [!NOTE] +> If you also wish to disable virtualization-based security delete the following registry settings: +```syntax +HKEY\_LOCAL\_MACHINE\\Software\\Policies\\Microsoft\\Windows\\DeviceGuard\\EnableVirtualizationBasedSecurity +HKEY\_LOCAL\_MACHINE\\Software\\Policies\\Microsoft\\Windows\\DeviceGuard\\RequirePlatformSecurityFeatures +``` > [!IMPORTANT] > If you manually remove these registry settings, make sure to delete them all. If you don't remove them all, the device might go into BitLocker recovery. @@ -164,9 +169,8 @@ To disable Windows Defender Credential Guard, you can use the following set of p bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi" bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215} - bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS + bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X: - bcdedit /set hypervisorlaunchtype off mountvol X: /d ``` @@ -175,7 +179,11 @@ To disable Windows Defender Credential Guard, you can use the following set of p 4. Alternatively, you can disable the virtualization-based security features to turn off Windows Defender Credential Guard. > [!NOTE] -> The PC must have one-time access to a domain controller to decrypt content, such as files that were encrypted with EFS. If you want to turn off both Windows Defender Credential Guard and virtualization-based security, run the following bcdedit command after turning off all virtualization-based security Group Policy and registry settings: bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS +> The PC must have one-time access to a domain controller to decrypt content, such as files that were encrypted with EFS. If you want to turn off both Windows Defender Credential Guard and virtualization-based security, run the following bcdedit commands after turning off all virtualization-based security Group Policy and registry settings: +```syntax +bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS +bcdedit /set vsmlaunchtype off +``` > [!NOTE] > Credential Guard and Device Guard are not currently supported when using Azure IaaS VMs. These options will be made available with future Gen 2 VMs. From 573f21284ce3d693bbf5e4d985513290c4c4e81f Mon Sep 17 00:00:00 2001 From: botmoto <42125490+botmoto@users.noreply.github.com> Date: Sun, 7 Apr 2019 19:15:27 -0700 Subject: [PATCH 02/67] Update credential-guard-manage.md Formatting Update credential-guard-manage.md --- .../credential-guard-manage.md | 24 ++++++++----------- 1 file changed, 10 insertions(+), 14 deletions(-) diff --git a/windows/security/identity-protection/credential-guard/credential-guard-manage.md b/windows/security/identity-protection/credential-guard/credential-guard-manage.md index c5e98ffb47..e02b561b04 100644 --- a/windows/security/identity-protection/credential-guard/credential-guard-manage.md +++ b/windows/security/identity-protection/credential-guard/credential-guard-manage.md @@ -152,16 +152,13 @@ To disable Windows Defender Credential Guard, you can use the following set of p 2. Delete the following registry settings: - HKEY\_LOCAL\_MACHINE\\System\\CurrentControlSet\\Control\\LSA\LsaCfgFlags - HKEY\_LOCAL\_MACHINE\\Software\\Policies\\Microsoft\\Windows\\DeviceGuard\\LsaCfgFlags -> [!NOTE] -> If you also wish to disable virtualization-based security delete the following registry settings: -```syntax -HKEY\_LOCAL\_MACHINE\\Software\\Policies\\Microsoft\\Windows\\DeviceGuard\\EnableVirtualizationBasedSecurity -HKEY\_LOCAL\_MACHINE\\Software\\Policies\\Microsoft\\Windows\\DeviceGuard\\RequirePlatformSecurityFeatures -``` +3. If you also wish to disable virtualization-based security delete the following registry settings: + - HKEY\_LOCAL\_MACHINE\\Software\\Policies\\Microsoft\\Windows\\DeviceGuard\\EnableVirtualizationBasedSecurity + - HKEY\_LOCAL\_MACHINE\\Software\\Policies\\Microsoft\\Windows\\DeviceGuard\\RequirePlatformSecurityFeatures > [!IMPORTANT] > If you manually remove these registry settings, make sure to delete them all. If you don't remove them all, the device might go into BitLocker recovery. -3. Delete the Windows Defender Credential Guard EFI variables by using bcdedit. From an elevated command prompt, type the following commands: +4. Delete the Windows Defender Credential Guard EFI variables by using bcdedit. From an elevated command prompt, type the following commands: ``` syntax mountvol X: /s @@ -174,16 +171,15 @@ HKEY\_LOCAL\_MACHINE\\Software\\Policies\\Microsoft\\Windows\\DeviceGuard\\Requi mountvol X: /d ``` -2. Restart the PC. -3. Accept the prompt to disable Windows Defender Credential Guard. -4. Alternatively, you can disable the virtualization-based security features to turn off Windows Defender Credential Guard. +5. Restart the PC. +6. Accept the prompt to disable Windows Defender Credential Guard. +7. Alternatively, you can disable the virtualization-based security features to turn off Windows Defender Credential Guard. > [!NOTE] > The PC must have one-time access to a domain controller to decrypt content, such as files that were encrypted with EFS. If you want to turn off both Windows Defender Credential Guard and virtualization-based security, run the following bcdedit commands after turning off all virtualization-based security Group Policy and registry settings: -```syntax -bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS -bcdedit /set vsmlaunchtype off -``` + + bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS + bcdedit /set vsmlaunchtype off > [!NOTE] > Credential Guard and Device Guard are not currently supported when using Azure IaaS VMs. These options will be made available with future Gen 2 VMs. From 03d24fad2d232e17851a51ba9f5b872d829fd6d6 Mon Sep 17 00:00:00 2001 From: botmoto <42125490+botmoto@users.noreply.github.com> Date: Sun, 7 Apr 2019 16:23:10 -0700 Subject: [PATCH 03/67] Update credential-guard-manage.md Update credential-guard-manage.md Formatting Update credential-guard-manage.md --- .../credential-guard-manage.md | 20 +++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/windows/security/identity-protection/credential-guard/credential-guard-manage.md b/windows/security/identity-protection/credential-guard/credential-guard-manage.md index 0edce00395..e02b561b04 100644 --- a/windows/security/identity-protection/credential-guard/credential-guard-manage.md +++ b/windows/security/identity-protection/credential-guard/credential-guard-manage.md @@ -20,6 +20,7 @@ ms.date: 03/01/2019 **Applies to** - Windows 10 - Windows Server 2016 +- Windows Server 2019 Prefer video? See [Windows Defender Credential Guard Deployment](https://mva.microsoft.com/en-us/training-courses/deep-dive-into-credential-guard-16651?l=sRcyvLJyC_3304300474) in the Deep Dive into Windows Defender Credential Guard video series. @@ -150,13 +151,14 @@ To disable Windows Defender Credential Guard, you can use the following set of p 1. If you used Group Policy, disable the Group Policy setting that you used to enable Windows Defender Credential Guard (**Computer Configuration** -> **Administrative Templates** -> **System** -> **Device Guard** -> **Turn on Virtualization Based Security**). 2. Delete the following registry settings: - HKEY\_LOCAL\_MACHINE\\System\\CurrentControlSet\\Control\\LSA\LsaCfgFlags + - HKEY\_LOCAL\_MACHINE\\Software\\Policies\\Microsoft\\Windows\\DeviceGuard\\LsaCfgFlags +3. If you also wish to disable virtualization-based security delete the following registry settings: - HKEY\_LOCAL\_MACHINE\\Software\\Policies\\Microsoft\\Windows\\DeviceGuard\\EnableVirtualizationBasedSecurity - HKEY\_LOCAL\_MACHINE\\Software\\Policies\\Microsoft\\Windows\\DeviceGuard\\RequirePlatformSecurityFeatures - > [!IMPORTANT] > If you manually remove these registry settings, make sure to delete them all. If you don't remove them all, the device might go into BitLocker recovery. -3. Delete the Windows Defender Credential Guard EFI variables by using bcdedit. From an elevated command prompt, type the following commands: +4. Delete the Windows Defender Credential Guard EFI variables by using bcdedit. From an elevated command prompt, type the following commands: ``` syntax mountvol X: /s @@ -164,18 +166,20 @@ To disable Windows Defender Credential Guard, you can use the following set of p bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi" bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215} - bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS + bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X: - bcdedit /set hypervisorlaunchtype off mountvol X: /d ``` -2. Restart the PC. -3. Accept the prompt to disable Windows Defender Credential Guard. -4. Alternatively, you can disable the virtualization-based security features to turn off Windows Defender Credential Guard. +5. Restart the PC. +6. Accept the prompt to disable Windows Defender Credential Guard. +7. Alternatively, you can disable the virtualization-based security features to turn off Windows Defender Credential Guard. > [!NOTE] -> The PC must have one-time access to a domain controller to decrypt content, such as files that were encrypted with EFS. If you want to turn off both Windows Defender Credential Guard and virtualization-based security, run the following bcdedit command after turning off all virtualization-based security Group Policy and registry settings: bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS +> The PC must have one-time access to a domain controller to decrypt content, such as files that were encrypted with EFS. If you want to turn off both Windows Defender Credential Guard and virtualization-based security, run the following bcdedit commands after turning off all virtualization-based security Group Policy and registry settings: + + bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS + bcdedit /set vsmlaunchtype off > [!NOTE] > Credential Guard and Device Guard are not currently supported when using Azure IaaS VMs. These options will be made available with future Gen 2 VMs. From 900a8d0c28fb44f2ac52ac1d36b3a91ac2ba4d02 Mon Sep 17 00:00:00 2001 From: Malin De Silva Date: Wed, 24 Apr 2019 18:47:47 +0530 Subject: [PATCH 04/67] Added Azure AD MFA Auth with O365 --- .../hello-for-business/hello-hybrid-key-trust-prereqs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md index f59a78c750..c191cc7a49 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md @@ -97,7 +97,7 @@ You can deploy Windows Hello for Business key trust in non-federated and federat ## Multifactor Authentication ## Windows Hello for Business is a strong, two-factor credential the helps organizations reduce their dependency on passwords. The provisioning process lets a user enroll in Windows Hello for Business using their user name and password as one factor, but needs a second factor of authentication. -Hybrid Windows Hello for Business deployments can use Azure’s Multi-factor Authentication service or they can use multi-factor authentication provides by Windows Server 2012 R2 or later Active Directory Federation Services, which includes an adapter model that enables third parties to integrate their multi-factor authentication into AD FS. +Hybrid Windows Hello for Business deployments can use Azure’s Multi-factor Authentication service or they can use multi-factor authentication provides by Windows Server 2012 R2 or later Active Directory Federation Services, which includes an adapter model that enables third parties to integrate their multi-factor authentication into AD FS. The Multi-factor authentication enabled in Office 365 license is sufficient for direct Multi-factor Authentication against Azure AD. ### Section Review > [!div class="checklist"] From 7d8272272e88665e0ca5bc441f51c94f5c4fbdb5 Mon Sep 17 00:00:00 2001 From: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> Date: Thu, 25 Apr 2019 18:54:11 +0530 Subject: [PATCH 05/67] Update windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md Co-Authored-By: Malind19 --- .../hello-for-business/hello-hybrid-key-trust-prereqs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md index c191cc7a49..a4a1cc41b4 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md @@ -97,7 +97,7 @@ You can deploy Windows Hello for Business key trust in non-federated and federat ## Multifactor Authentication ## Windows Hello for Business is a strong, two-factor credential the helps organizations reduce their dependency on passwords. The provisioning process lets a user enroll in Windows Hello for Business using their user name and password as one factor, but needs a second factor of authentication. -Hybrid Windows Hello for Business deployments can use Azure’s Multi-factor Authentication service or they can use multi-factor authentication provides by Windows Server 2012 R2 or later Active Directory Federation Services, which includes an adapter model that enables third parties to integrate their multi-factor authentication into AD FS. The Multi-factor authentication enabled in Office 365 license is sufficient for direct Multi-factor Authentication against Azure AD. +Hybrid Windows Hello for Business deployments can use Azure’s Multi-factor Authentication service or they can use multi-factor authentication provided by Windows Server 2012 R2 or later Active Directory Federation Services, which include an adapter model that enables third parties to integrate their multi-factor authentication into AD FS. The Multi-factor authentication enabled in Office 365 license is sufficient for direct Multi-factor Authentication against Azure AD. ### Section Review > [!div class="checklist"] From 4e534972c11a14e238e7b022290435c41bb7961f Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Fri, 26 Apr 2019 16:13:26 +0500 Subject: [PATCH 06/67] update hello-cert-trust-deploy-mfa.md --- .../hello-for-business/hello-cert-trust-deploy-mfa.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-cert-trust-deploy-mfa.md b/windows/security/identity-protection/hello-for-business/hello-cert-trust-deploy-mfa.md index 561df3ca7b..afee1b6159 100644 --- a/windows/security/identity-protection/hello-for-business/hello-cert-trust-deploy-mfa.md +++ b/windows/security/identity-protection/hello-for-business/hello-cert-trust-deploy-mfa.md @@ -23,7 +23,7 @@ ms.date: 08/19/2018 - Certificate trust -On-premises deployments must use the On-premises Azure MFA Server using the AD FS adapter model Optionally, you can use a third-party MFA server that provides an AD FS Multifactor authentication adapter. +On-premises deployments must use on-premises MFA Server that provides an AD FS Multifactor authentication adapter. It could be Azure Multi-Factor Authentication Server or third-party MFA solution. >[!TIP] >Please make sure you've read [Validate and Deploy Multifactor Authentication Services (MFA)](hello-cert-trust-validate-deploy-mfa.md) before proceeding any further. From 94c56a08ecf1eceec1d2ce0d1a0852ac5cc6cbf8 Mon Sep 17 00:00:00 2001 From: illfated Date: Sun, 28 Apr 2019 18:23:56 +0200 Subject: [PATCH 07/67] Windows/Privacy: URL correction update This is a follow-up to my previous PR #3305 (Windows/Privacy: change formatting code to text). I found one URL that I missed in my previous solution. This is a 1 line change, making the starting and ending asterisk show up on the page, instead of formatting the text as italics. Addendum: For future web page documentation, it may be a good idea to use the HTML codes `*` + `\` for `*` and `\` respectively, to avoid situations where pages look OK on Github, but not translating well to the docs.microsoft.com pages. Ref. issue ticket #3304 (Domain misspelling) --- .../privacy/windows-endpoints-1809-non-enterprise-editions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/privacy/windows-endpoints-1809-non-enterprise-editions.md b/windows/privacy/windows-endpoints-1809-non-enterprise-editions.md index b6be3b5acd..1df90d39e0 100644 --- a/windows/privacy/windows-endpoints-1809-non-enterprise-editions.md +++ b/windows/privacy/windows-endpoints-1809-non-enterprise-editions.md @@ -98,7 +98,7 @@ We used the following methodology to derive these network endpoints: | *.e-msedge.net | HTTPS | Used by OfficeHub to get the metadata of Office apps. | | *.g.akamaiedge.net | HTTPS | Used to check for updates to maps that have been downloaded for offline use. | | *.s-msedge.net | HTTPS | Used by OfficeHub to get the metadata of Office apps. | -| *.tlu.dl.delivery.mp.microsoft.com/* | HTTP | Enables connections to Windows Update. | +| \*.tlu.dl.delivery.mp.microsoft.com/\* | HTTP | Enables connections to Windows Update. | | *geo-prod.dodsp.mp.microsoft.com.nsatc.net | HTTPS | Enables connections to Windows Update. | | arc.msn.com.nsatc.net | HTTPS | Used to retrieve Windows Spotlight metadata. | | au.download.windowsupdate.com/* | HTTP | Enables connections to Windows Update. | From 516a00b153a899ba80256385771790a00cfd92c9 Mon Sep 17 00:00:00 2001 From: Michael Niehaus Date: Wed, 1 May 2019 10:26:12 -0400 Subject: [PATCH 08/67] Update user-driven-hybrid.md Adjusted the AD DC requirements to make them more clear. --- windows/deployment/windows-autopilot/user-driven-hybrid.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopilot/user-driven-hybrid.md b/windows/deployment/windows-autopilot/user-driven-hybrid.md index d69c5869ba..c75f3e2df4 100644 --- a/windows/deployment/windows-autopilot/user-driven-hybrid.md +++ b/windows/deployment/windows-autopilot/user-driven-hybrid.md @@ -29,7 +29,8 @@ To perform a user-driven hybrid AAD joined deployment using Windows Autopilot: - **Hybrid Azure AD joined** must be specified as the selected option under **Join to Azure AD as** in the Autopilot profile. - If using Intune, a device group in Azure Active Directory must exist with the Windows Autopilot profile assigned to that group. - The device must be running Windows 10, version 1809 or later. -- The device must be connected to the Internet and have access to an Active Directory domain controller. +- The device must be able to access an Active Directory domain controller, so it must be connected to the organization's network (where it can resolve the DNS records for the AD domain and the AD domain controller, and communicate with the domain controller to authenticate the user). +- The device must be able to access the Internet, following the [documented Windows Autopilot network requirements](windows-autopilot-requirements-network.md). - The Intune Connector for Active Directory must be installed. - Note: The Intune Connector will perform an on-prem AD join, therefore users do not need on-prem AD-join permission, assuming the Connector is [configured to perform this action](https://docs.microsoft.com/intune/windows-autopilot-hybrid#increase-the-computer-account-limit-in-the-organizational-unit) on the user's behalf. - If using Proxy, WPAD Proxy settings option must be enabled and configured. From 33f1c7e37a5e64a7b30c5214c8aea7b1fbcd46bc Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Thu, 2 May 2019 15:39:26 +0500 Subject: [PATCH 09/67] update hello-planning-guide.md --- .../hello-for-business/hello-planning-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-planning-guide.md b/windows/security/identity-protection/hello-for-business/hello-planning-guide.md index 1700566e52..a936892039 100644 --- a/windows/security/identity-protection/hello-for-business/hello-planning-guide.md +++ b/windows/security/identity-protection/hello-for-business/hello-planning-guide.md @@ -274,7 +274,7 @@ Public key infrastructure prerequisites already exist in your planning worksheet If box **1a** on your planning worksheet reads **cloud only**, ignore the public key infrastructure section of your planning worksheet. Cloud only deployments do not use a public key infrastructure. -If box **1b** on your planning worksheet reads **key trust**, write **N/A** in box **5b** on your planning worksheet. +If box **1b** on your planning worksheet reads **key trust**, write **N/A** in box **5b** on your planning worksheet. Key trust doesn't require any change in public key infrastructure, skip this part and go to **Cloud** section. The registration authority only relates to certificate trust deployments and the management used for domain and non-domain joined devices. Hybrid Azure AD joined devices managed by Group Policy need the Windows Server 2016 AD FS role to issue certificates. Hybrid Azure AD joined devices and Azure AD joined devices managed by Intune or a compatible MDM need the Windows Server NDES server role to issue certificates. From 38811a81906227c6da50e83308f429cd4bc87f84 Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Thu, 2 May 2019 17:02:24 +0500 Subject: [PATCH 10/67] update hello-planning-guide.md --- .../hello-for-business/hello-planning-guide.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-planning-guide.md b/windows/security/identity-protection/hello-for-business/hello-planning-guide.md index a936892039..05fb09a45a 100644 --- a/windows/security/identity-protection/hello-for-business/hello-planning-guide.md +++ b/windows/security/identity-protection/hello-for-business/hello-planning-guide.md @@ -77,7 +77,7 @@ A deployment's trust type defines how each Windows Hello for Business client aut The key trust type does not require issuing authentication certificates to end users. Users authenticate using a hardware-bound key created during the built-in provisioning experience. This requires an adequate distribution of Windows Server 2016 domain controllers relative to your existing authentication and the number of users included in your Windows Hello for Business deployment. Read the [Planning an adequate number of Windows Server 2016 Domain Controllers for Windows Hello for Business deployments](hello-adequate-domain-controllers.md) to learn more. -The certificate trust type issues authentication certificates to end users. Users authenticate using a certificate requested using a hardware-bound key created during the built-in provisioning experience. Unlike key trust, certificate trust does not require Windows Server 2016 domain controllers. Users can authenticate using their certificate to any Windows Server 2008 R2 or later domain controller. +The certificate trust type issues authentication certificates to end users. Users authenticate using a certificate requested using a hardware-bound key created during the built-in provisioning experience. Unlike key trust, certificate trust does not require Windows Server 2016 domain controllers (but still requires [Windows Server 2016 Active Directory schema](https://docs.microsoft.com/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-trust-prereqs#directories)). Users can authenticate using their certificate to any Windows Server 2008 R2 or later domain controller. #### Device registration @@ -101,7 +101,6 @@ Cloud only and hybrid deployments provide many choices for multi-factor authenti > * Azure Active Directory Premium > * Enterprise Mobility Suite > * Enterprise Cloud Suite ->* A per-user and per-authentication consumption-based model that is billed monthly against Azure monetary commitment (Read [Multi-Factor Authentication Pricing](https://azure.microsoft.com/pricing/details/multi-factor-authentication/) for more information) #### Directory synchronization From 9584215fd34e27cfa6c5a264f536a7a31f6d9f1a Mon Sep 17 00:00:00 2001 From: msjbja <49055479+msjbja@users.noreply.github.com> Date: Thu, 2 May 2019 08:50:14 -0500 Subject: [PATCH 11/67] Update windows-local-autopilot-reset.md Addition of the permission required to perform this task --- .../windows-autopilot/windows-autopilot-reset-local.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/windows/deployment/windows-autopilot/windows-autopilot-reset-local.md b/windows/deployment/windows-autopilot/windows-autopilot-reset-local.md index ac25a597f7..2df22358c3 100644 --- a/windows/deployment/windows-autopilot/windows-autopilot-reset-local.md +++ b/windows/deployment/windows-autopilot/windows-autopilot-reset-local.md @@ -19,6 +19,8 @@ ms.topic: article **Applies to: Windows 10, version 1709 and above +The Microsoft Intune Service Administrator Directory role is required to perform this task. The process of adding directory roles is documented at https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal + IT admins can perform a local Windows Autopilot Reset to quickly remove personal files, apps, and settings, and reset Windows 10 devices from the lock screen any time and apply original settings and management enrollment (Azure Active Directory and device management) so the devices are ready to use. With a local Autopilot Reset, devices are returned to a fully configured or known IT-approved state. To enable local Autopilot Reset in Windows 10: From 4336fb97432614ec0cfe4b69e2c61bbb200e404c Mon Sep 17 00:00:00 2001 From: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> Date: Thu, 2 May 2019 12:13:50 -0500 Subject: [PATCH 12/67] Update windows/deployment/windows-autopilot/windows-autopilot-reset-local.md Adjusting the wording based on suggestion by JohnFreelancer9 Co-Authored-By: msjbja <49055479+msjbja@users.noreply.github.com> --- .../windows-autopilot/windows-autopilot-reset-local.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopilot/windows-autopilot-reset-local.md b/windows/deployment/windows-autopilot/windows-autopilot-reset-local.md index 2df22358c3..5f82790f46 100644 --- a/windows/deployment/windows-autopilot/windows-autopilot-reset-local.md +++ b/windows/deployment/windows-autopilot/windows-autopilot-reset-local.md @@ -19,7 +19,7 @@ ms.topic: article **Applies to: Windows 10, version 1709 and above -The Microsoft Intune Service Administrator Directory role is required to perform this task. The process of adding directory roles is documented at https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal +The Microsoft Intune Service Administrator Directory role is required to perform this task. To learn more about the process of adding directory roles, refer to https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal IT admins can perform a local Windows Autopilot Reset to quickly remove personal files, apps, and settings, and reset Windows 10 devices from the lock screen any time and apply original settings and management enrollment (Azure Active Directory and device management) so the devices are ready to use. With a local Autopilot Reset, devices are returned to a fully configured or known IT-approved state. From b37b1b9e69ebd787de443bc26d601baa6d431bf2 Mon Sep 17 00:00:00 2001 From: Joyce Y <47188252+mypil@users.noreply.github.com> Date: Thu, 2 May 2019 12:44:43 -0500 Subject: [PATCH 13/67] Update windows/deployment/windows-autopilot/windows-autopilot-reset-local.md Changes committed to fit Microsoft style Co-Authored-By: msjbja <49055479+msjbja@users.noreply.github.com> --- .../windows-autopilot/windows-autopilot-reset-local.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopilot/windows-autopilot-reset-local.md b/windows/deployment/windows-autopilot/windows-autopilot-reset-local.md index 5f82790f46..c94be655bb 100644 --- a/windows/deployment/windows-autopilot/windows-autopilot-reset-local.md +++ b/windows/deployment/windows-autopilot/windows-autopilot-reset-local.md @@ -19,7 +19,7 @@ ms.topic: article **Applies to: Windows 10, version 1709 and above -The Microsoft Intune Service Administrator Directory role is required to perform this task. To learn more about the process of adding directory roles, refer to https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal +The Intune Service Administrator role is required to perform this task. Learn more about how to [Assign Azure Active Directory roles](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal). IT admins can perform a local Windows Autopilot Reset to quickly remove personal files, apps, and settings, and reset Windows 10 devices from the lock screen any time and apply original settings and management enrollment (Azure Active Directory and device management) so the devices are ready to use. With a local Autopilot Reset, devices are returned to a fully configured or known IT-approved state. From 07120081bf9e857679d3206b06f47f00adb65b01 Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Fri, 3 May 2019 12:25:57 +0500 Subject: [PATCH 14/67] update hello-planning-guide.md --- .../hello-for-business/hello-planning-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-planning-guide.md b/windows/security/identity-protection/hello-for-business/hello-planning-guide.md index 05fb09a45a..77945e6f69 100644 --- a/windows/security/identity-protection/hello-for-business/hello-planning-guide.md +++ b/windows/security/identity-protection/hello-for-business/hello-planning-guide.md @@ -77,7 +77,7 @@ A deployment's trust type defines how each Windows Hello for Business client aut The key trust type does not require issuing authentication certificates to end users. Users authenticate using a hardware-bound key created during the built-in provisioning experience. This requires an adequate distribution of Windows Server 2016 domain controllers relative to your existing authentication and the number of users included in your Windows Hello for Business deployment. Read the [Planning an adequate number of Windows Server 2016 Domain Controllers for Windows Hello for Business deployments](hello-adequate-domain-controllers.md) to learn more. -The certificate trust type issues authentication certificates to end users. Users authenticate using a certificate requested using a hardware-bound key created during the built-in provisioning experience. Unlike key trust, certificate trust does not require Windows Server 2016 domain controllers (but still requires [Windows Server 2016 Active Directory schema](https://docs.microsoft.com/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-trust-prereqs#directories)). Users can authenticate using their certificate to any Windows Server 2008 R2 or later domain controller. +The certificate trust type issues authentication certificates to end users. Users authenticate using a certificate requested using a hardware-bound key created during the built-in provisioning experience. Unlike key trust, certificate trust does not require Windows Server 2016 domain controllers (but still requires [Windows Server 2016 Active Directory schema](https://docs.microsoft.com/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-trust-prereqs#directories)). Users can use their certificate to authenticate to any Windows Server 2008 R2, or later, domain controller. #### Device registration From 355c7ccc34fd830e040373cd7156aa1a33ae36d7 Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Fri, 3 May 2019 16:11:27 +0500 Subject: [PATCH 15/67] update nodecache-csp.md removed DFType value, as it is out of the scope of this article --- windows/client-management/mdm/nodecache-csp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/mdm/nodecache-csp.md b/windows/client-management/mdm/nodecache-csp.md index 28bcf637f6..d04fa8b63b 100644 --- a/windows/client-management/mdm/nodecache-csp.md +++ b/windows/client-management/mdm/nodecache-csp.md @@ -30,7 +30,7 @@ The following diagram shows the NodeCache configuration service provider in tree ![nodecache csp](images/provisioning-csp-nodecache.png) **./Device/Vendor/MSFT and ./User/Vendor/MSFT** -Required. The root node for the NodeCache object. Supported operation is Get. This configuration service provider is used for enterprise device management only. This is a predefined MIME type to identify this managed object in OMA DM syntax. Starting in Windows 10, version 1607 the value is com.microsoft/\/MDM/NodeCache. +Required. The root node for the NodeCache object. Supported operation is Get. This configuration service provider is used for enterprise device management only. This is a predefined MIME type to identify this managed object in OMA DM syntax. ***ProviderID*** Optional. Group settings per DM server. Each group of settings is distinguished by the server’s Provider ID. It should be the same DM server **PROVIDER-ID** value that was supplied through the [w7 APPLICATION configuration service provider](w7-application-csp.md) XML during the enrollment process. Only one enterprise management server is supported. That is, there should be only one *ProviderID* node under **NodeCache**. Scope is dynamic. From 621e845fe599d4e1b7f4f94be41ac938c7328a46 Mon Sep 17 00:00:00 2001 From: Malin De Silva Date: Mon, 6 May 2019 15:02:11 +0530 Subject: [PATCH 16/67] added skipping auto enrollment info --- windows/deployment/windows-autopilot/enrollment-status.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/windows/deployment/windows-autopilot/enrollment-status.md b/windows/deployment/windows-autopilot/enrollment-status.md index d2e6471454..895cf49881 100644 --- a/windows/deployment/windows-autopilot/enrollment-status.md +++ b/windows/deployment/windows-autopilot/enrollment-status.md @@ -20,6 +20,8 @@ ms.topic: article The Windows Autopilot Enrollment Status page displaying the status of the complete device configuration process. Incorporating feedback from customers, this provides information to the user to show that the device is being set up and can be configured to prevent access to the desktop until the configuration is complete. ![Enrollment status page](images/enrollment-status-page.png) + +From Windows 10 version 1803 onwards, you can opt-out of the account setup phase. When it is skipped, the settings will be applied for the users when as they access their desktop for the first time. ## Available settings From 9873e82524118009a405dc1c5f523587aef8bcca Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Mon, 6 May 2019 14:56:41 +0500 Subject: [PATCH 17/67] update hello-cert-trust-deploy-mfa.md --- .../hello-for-business/hello-cert-trust-deploy-mfa.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-cert-trust-deploy-mfa.md b/windows/security/identity-protection/hello-for-business/hello-cert-trust-deploy-mfa.md index afee1b6159..3c90a6c465 100644 --- a/windows/security/identity-protection/hello-for-business/hello-cert-trust-deploy-mfa.md +++ b/windows/security/identity-protection/hello-for-business/hello-cert-trust-deploy-mfa.md @@ -23,7 +23,7 @@ ms.date: 08/19/2018 - Certificate trust -On-premises deployments must use on-premises MFA Server that provides an AD FS Multifactor authentication adapter. It could be Azure Multi-Factor Authentication Server or third-party MFA solution. +On-premises deployments must use an on-premises MFA Server that provides an AD FS Multifactor authentication adapter. It can be an Azure Multi-Factor Authentication Server or a third-party MFA solution. >[!TIP] >Please make sure you've read [Validate and Deploy Multifactor Authentication Services (MFA)](hello-cert-trust-validate-deploy-mfa.md) before proceeding any further. From 80b15d0cc524e910cb285465199a5b765e87f121 Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Mon, 6 May 2019 17:34:28 +0500 Subject: [PATCH 18/67] update activate-using-active-directory-based-activation-client.md source: [KMS Activation for Windows Server 2016](https://blogs.technet.microsoft.com/askpfeplat/2016/10/24/kms-activation-for-windows-server-2016/) --- .../activate-using-active-directory-based-activation-client.md | 1 + 1 file changed, 1 insertion(+) diff --git a/windows/deployment/volume-activation/activate-using-active-directory-based-activation-client.md b/windows/deployment/volume-activation/activate-using-active-directory-based-activation-client.md index 03e0029f83..ddbabe01f8 100644 --- a/windows/deployment/volume-activation/activate-using-active-directory-based-activation-client.md +++ b/windows/deployment/volume-activation/activate-using-active-directory-based-activation-client.md @@ -20,6 +20,7 @@ ms.topic: article - Windows 8 - Windows Server 2012 R2 - Windows Server 2012 +- Windows Server 2016 **Looking for retail activation?** - [Get Help Activating Microsoft Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644) From e177eeff58aac8b8445d5c425016e9e74dac7f68 Mon Sep 17 00:00:00 2001 From: Nicole Turner <39884432+nenonix@users.noreply.github.com> Date: Mon, 6 May 2019 22:38:39 +0200 Subject: [PATCH 19/67] Update hello-adequate-domain-controllers.md Typo and grammar fixes https://github.com/MicrosoftDocs/windows-itpro-docs/issues/3203 --- .../hello-adequate-domain-controllers.md | 28 +++++++++---------- 1 file changed, 14 insertions(+), 14 deletions(-) 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 ebb6eed030..680fe15627 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 @@ -24,21 +24,21 @@ ms.date: 08/20/2018 ## How many is adequate -How can you find out how many domain controllers are needed? You can use performance monitoring on your domain controllers to determine existing authentication traffic. Windows Server 2016 includes the KDC AS Requests performance counter. You can use these counters to determine how much of a domain controllers load is due to initial Kerberos authentication. It's important to remember that authentication for a Windows Hello for Business key trust deployment does not affect Kerberos authentication--it remains unchanged. +How can you find out how many domain controllers are needed? You can use performance monitoring on your domain controllers to determine existing authentication traffic. Windows Server 2016 includes the KDC AS Requests performance counter. You can use these counters to determine how much of a domain controller's load is due to initial Kerberos authentication. It's important to remember that authentication for a Windows Hello for Business key trust deployment does not affect Kerberos authentication--it remains unchanged. Windows 10 accomplishes Windows Hello for Business key trust authentication by mapping an Active Directory user account to one or more public keys. This mapping occurs on the domain controller, which is why the deployment needs Windows Server 2016 domain controllers. Public key mapping is only supported by Windows Server 2016 domain controllers. Therefore, users in a key trust deployment must authenticate to a Windows Server 2016 domain controller. -Determining an adequate number of Windows Server 2016 domain controllers is important to ensure you have enough domain controllers to satisfy all authentication requests, including users mapped with public key trust. What many administrators do not realize is that adding the most current version of a domain controller (in this case Windows Server 2016) to a deployment of existing domain controllers (Windows Server 2008R2 or Windows Server 2012R2) instantly makes that single domain controller susceptible to carrying the most load, or what is commonly referred to as "piling on". To illustrate the "piling on" concept, consider the following scenario. +Determining an adequate number of Windows Server 2016 domain controllers is important to ensure you have enough domain controllers to satisfy all authentication requests, including users mapped with public key trust. What many administrators do not realize is that adding the most current version of a domain controller (in this case Windows Server 2016) to a deployment of existing domain controllers (Windows Server 2008R2 or Windows Server 2012R2) instantly makes that single domain controller susceptible to carrying the most load, or what is commonly referred to as "piling on". To illustrate the "piling on" concept, consider the following scenario: -Consider a controlled environment where there are 1000 client computers and the authentication load of these 1000 client computers is evenly distributed across 10 domain controllers in the environment. The Kerberos AS requests load would look something like the following. +Consider a controlled environment where there are 1000 client computers and the authentication load of these 1000 client computers is evenly distributed across 10 domain controllers in the environment. The Kerberos AS requests load would look something like the following: ![dc-chart1](images/plan/dc-chart1.png) -The environment changes. The first change includes DC1 upgraded to Windows Server 2016 to support Windows Hello for Business key-trust authentication. Next, 100 clients enroll for Windows Hello for Business using the public key trust deployment. Given all other factors stay constant, the authentication would now look like the following. +The environment changes. The first change includes DC1 upgraded to Windows Server 2016 to support Windows Hello for Business key-trust authentication. Next, 100 clients enroll for Windows Hello for Business using the public key trust deployment. Given all other factors stay constant, the authentication would now look like the following: ![dc-chart2](images/plan/dc-chart2.png) -The Windows Server 2016 domain controller is handling 100 percent of all public key trust authentication. However, it is also handling 10 percent of the password authentication. Why? This behavior occurs because domain controllers 2- 10 only support password and certificate trust authentication; only a Windows Server 2016 domain controller supports authentication public key trust authentication. The Windows Server 2016 domain controller understands how to authenticate password and certificate trust authentication and will continue to share the load of authenticating those clients. Because DC1 can handle all forms of authentication, it will be bear more of the authentication load, and easily become overloaded. What if another Windows Server 2016 domain controller is added, but without deploying Windows Hello for Business to anymore clients. +The Windows Server 2016 domain controller is handling 100 percent of all public key trust authentication. However, it is also handling 10 percent of the password authentication. Why? This behavior occurs because domain controllers 2- 10 only support password and certificate trust authentication; only a Windows Server 2016 domain controller supports authentication public key trust authentication. The Windows Server 2016 domain controller understands how to authenticate password and certificate trust authentication and will continue to share the load of authenticating those clients. Because DC1 can handle all forms of authentication, it will be bear more of the authentication load, and easily become overloaded. What if another Windows Server 2016 domain controller is added, but without deploying Windows Hello for Business to anymore clients? ![dc-chart3](images/plan/dc-chart3.png) @@ -63,7 +63,7 @@ The preceding was an example to show why it's unrealistic to have a "one-size-fi ## Determining total AS Request load -Each organization needs to have an 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. +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. Pick a site where you plan to upgrade the clients to Windows Hello for Business public key trust. Pick a time when authentication traffic is most significant--Monday morning is great time as everyone is returning to the office. Enable the performance counter on *all* the domain controllers in that site. Collect KDC AS Requests performance counters for two hours: * A half-hour before you expect initial authentication (sign-ins and unlocks) to be significant @@ -75,29 +75,29 @@ For example, if employees are scheduled to come into the office at 9:00am. Your > [!NOTE] > To capture all the authentication traffic. Ensure that all computers are powered down to get the most accurate authentication information (computers and services authenticate at first power up--you need to consider this authentication in your evaluation). -Aggregate the performance data of all domain controllers. Look for the maximum KDC AS Requests for each domain controller. Find the median time when the maximum number of requests occurred for the site, this should represent when the site is experience the highest amount of authentication. +Aggregate the performance data of all domain controllers. Look for the maximum KDC AS Requests for each domain controller. Find the median time when the maximum number of requests occurred for the site, this should represent when the site is experiencing the highest amount of authentication. -Add the number of authentications for each domain controller for the median time. You now have the total authentication for the site during a peak time. Using this metric, you can determine the distribution of authentication across the domain controllers in the site by dividing the domain controller's authentication number for the median time by the total authentication. Multiple the quotient by 10 to convert the distribution to a percentage. To validate your math, all the distributions should equal 100 percent. +Add the number of authentications for each domain controller for the median time. You now have the total authentication for the site during a peak time. Using this metric, you can determine the distribution of authentication across the domain controllers in the site by dividing the domain controller's authentication number for the median time by the total authentication. Multiply the quotient by 10 to convert the distribution to a percentage. To validate your math, all the distributions should equal 100 percent. -Review the distribution of authentication. Hopefully, none of these are above 70 percent. It's always good to reserve some capacity for the unexpected. Also, the primary purposes of a domain controller is to provide authentication and handle Active Directory operations. Identify domain controllers with lower distributions of authentication as potential candidates for the initial domain controller upgrades in conjunction with a reasonable distribution of clients provisioned for Windows Hello for Business. +Review the distribution of authentication. Hopefully, none of these are above 70 percent. It's always good to reserve some capacity for the unexpected. Also, the primary purposes of a domain controller are to provide authentication and handle Active Directory operations. Identify domain controllers with lower distributions of authentication as potential candidates for the initial domain controller upgrades in conjunction with a reasonable distribution of clients provisioned for Windows Hello for Business. ## Monitoring Authentication -Using the same methods previously described above, monitor the Kerberos authentication after upgrading a domain controller and your first phase of Windows Hello for Business deployments. Make note of the delta of authentication before and after upgrading the domain controller to Windows Server 2016. This delta is representative of authentication resulting from the first phase of your Windows Hello for Business clients. This gives you a baseline for your environment to where you can form a statement such as +Using the same methods previously described above, monitor the Kerberos authentication after upgrading a domain controller and your first phase of Windows Hello for Business deployments. Make note of the delta of authentication before and after upgrading the domain controller to Windows Server 2016. This delta is representative of authentication resulting from the first phase of your Windows Hello for Business clients. This gives you a baseline for your environment from which you can form a statement such as ```"Every n Windows Hello for Business clients results in x percentage of key-trust authentication."``` -Where _n_ equals the number of clients you switched to Windows Hello for Business and _x_ equals the increased percentage of authentication from the upgraded domain controller. Armed with information, you can apply the observations of upgrading domain controllers and increasing Windows Hello for Business client count to appropriately phase your deployment. +Where _n_ equals the number of clients you switched to Windows Hello for Business and _x_ equals the increased percentage of authentication from the upgraded domain controller. Armed with this information, you can apply the observations of upgrading domain controllers and increasing Windows Hello for Business client count to appropriately phase your deployment. Remember, increasing the number of clients changes the volume of authentication distributed across the Windows Server 2016 domain controllers. If there is only one Windows Server 2016 domain controller, there's no distribution and you are simply increasing the volume of authentication for which THAT domain controller is responsible. -Increasing the number of number of domain controllers distributes the volume of authentication, but doesn't change it. Therefore, as you add more domain controllers, the burden of authentication for which each domain controller is responsible decrease. Upgrading two domain controller changes the distribution to 50 percent. Upgrading three domain controllers changes the distribution to 33 percent, and so on. +Increasing the number of domain controllers distributes the volume of authentication, but doesn't change it. Therefore, as you add more domain controllers, the burden of authentication, for which each domain controller is responsible, decreases. Upgrading two domain controller changes the distribution to 50 percent. Upgrading three domain controllers changes the distribution to 33 percent, and so on. ## Strategy The simplest strategy you can employ is to upgrade one domain controller and monitor the single domain controller as you continue to phase in new Windows Hello for Business key-trust clients until it reaches a 70 or 80 percent threshold. -Then, upgrade a second domain controller. Monitor the authentication on both domain controllers to determine how the authentication distributes between the two domain controllers. Introduce more Windows Hello for Business clients while monitoring the authentication on the two upgraded domain controllers. Once those reach your environments designated capacity, then upgrade another domain controller. +Then, upgrade a second domain controller. Monitor the authentication on both domain controllers to determine how the authentication distributes between the two domain controllers. Introduce more Windows Hello for Business clients while monitoring the authentication on the two upgraded domain controllers. Once those reach your environment's designated capacity, you can upgrade another domain controller. Repeat until your deployment for that site is complete. Now, monitor authentication across all your domain controllers like you did the very first time. Determine the distribution of authentication for each domain controller. Identify the percentage of distribution for which it is responsible. If a single domain controller is responsible for 70 percent of more of the authentication, you may want to consider adding a domain controller to reduce the distribution of authentication volume. -However, before considering this, ensure the high load of authentication is not a result of applications and services where their configuration has a statically configured domain controller. Adding domain controllers will not resolve the additional authentication load problem in this scenario. Instead, manually distribute the authentication to different domain controllers among all the services or applications. Alternatively, try simply using the domain name rather than a specific domain controller. Each domain controller has an A record registered in DNS for the domain name, which DNS will round robin with each DNS query. It's not the best load balancer, however, it is a better alternative to static domain controller configurations, provided the configuration is compatible with your service or application. +However, before considering this, ensure the high load of authentication is not a result of applications and services where their configuration has a statically-configured domain controller. Adding domain controllers will not resolve the additional authentication load problem in this scenario. Instead, manually distribute the authentication to different domain controllers among all the services or applications. Alternatively, try simply using the domain name rather than a specific domain controller. Each domain controller has an A record registered in DNS for the domain name, which DNS will round robin with each DNS query. It's not the best load balancer, however, it is a better alternative to static domain controller configurations, provided the configuration is compatible with your service or application. From 7556ea14b48f3b3bc481507b95395b3a9c3560ad Mon Sep 17 00:00:00 2001 From: Nicole Turner <39884432+nenonix@users.noreply.github.com> Date: Mon, 6 May 2019 22:42:41 +0200 Subject: [PATCH 20/67] Update hello-hybrid-key-trust.md Typo https://github.com/MicrosoftDocs/windows-itpro-docs/issues/3203 --- .../hello-for-business/hello-hybrid-key-trust.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust.md index 303b6ce403..d74bd02a0e 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust.md @@ -34,7 +34,7 @@ The new deployment baseline helps organizations who are moving to Azure and Offi This baseline provides detailed procedures to move your environment from an on-premises only environment to a hybrid environment using Windows Hello for Business to authenticate to Azure Active Directory and to your on-premises Active Directory using a single Windows sign-in. -You’re next step is to familiarize yourself with the prerequisites needed for the deployment. Many of the prerequisites will be new for organizations and individuals pursuing the new deployment baseline. Organizations and individuals starting from the federated baseline will likely be familiar with most of the prerequisites, but should validate they are using the proper versions that include the latest updates. +Your next step is to familiarize yourself with the prerequisites needed for the deployment. Many of the prerequisites will be new for organizations and individuals pursuing the new deployment baseline. Organizations and individuals starting from the federated baseline will likely be familiar with most of the prerequisites, but should validate they are using the proper versions that include the latest updates. > [!div class="nextstepaction"] > [Prerequistes](hello-hybrid-key-trust-prereqs.md) From 52f92056d8658810a2cfa33861389b441956b207 Mon Sep 17 00:00:00 2001 From: Nicole Turner <39884432+nenonix@users.noreply.github.com> Date: Mon, 6 May 2019 22:48:13 +0200 Subject: [PATCH 21/67] Update hello-hybrid-key-new-install.md Typos https://github.com/MicrosoftDocs/windows-itpro-docs/issues/3203 --- .../hello-for-business/hello-hybrid-key-new-install.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-new-install.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-new-install.md index d9874f88c3..831a9879cb 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-new-install.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-new-install.md @@ -80,7 +80,7 @@ If you do not have an existing public key infrastructure, please review [Certifi > [!IMPORTANT] > For Azure AD joined device to authenticate to and use on-premises resources, ensure you: > * Install the root certificate authority certificate for your organization in the user's trusted root certificate store. -> * Publish your certificate revocation list to a location that is available to Azure AD joined devices, such as a web-based url. +> * Publish your certificate revocation list to a location that is available to Azure AD joined devices, such as a web-based URL. ### Section Review ### @@ -135,7 +135,7 @@ Alternatively, you can configure Windows Server 2016 Active Directory Federation > * Review the overview and uses of Azure Multifactor Authentication. > * Review your Azure Active Directory subscription for Azure Multifactor Authentication. > * Create an Azure Multifactor Authentication Provider, if necessary. -> * Configure Azure Multifactor Authentiation features and settings. +> * Configure Azure Multifactor Authentication features and settings. > * Understand the different User States and their effect on Azure Multifactor Authentication. > * Consider using Azure Multifactor Authentication or a third-party multifactor authentication provider with Windows Server Active Directory Federation Services, if necessary. From e486b2536bf6035772818f7579d5618c8b662771 Mon Sep 17 00:00:00 2001 From: Nicole Turner <39884432+nenonix@users.noreply.github.com> Date: Mon, 6 May 2019 22:53:20 +0200 Subject: [PATCH 22/67] Update hello-hybrid-key-trust-devreg.md Typos https://github.com/MicrosoftDocs/windows-itpro-docs/issues/3203 --- .../hello-for-business/hello-hybrid-key-trust-devreg.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-devreg.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-devreg.md index 9a49d7ab15..f7ec72d697 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-devreg.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-devreg.md @@ -38,7 +38,7 @@ Begin configuring device registration to support Hybrid Windows Hello for Busine To do this, follow the **Configure device settings** steps under [Setting up Azure AD Join in your organization](https://azure.microsoft.com/documentation/articles/active-directory-azureadjoin-setup/) -Next, follow the guidance on the [How to configure hybrid Azure Active Directory joined devices](https://docs.microsoft.com/azure/active-directory/device-management-hybrid-azuread-joined-devices-setup) page. In the **Configuration steps** section, identify you configuration at the top of the table (either **Windows current and password hash sync** or **Windows current and federation**) and perform only the steps identified with a check mark. +Next, follow the guidance on the [How to configure hybrid Azure Active Directory joined devices](https://docs.microsoft.com/azure/active-directory/device-management-hybrid-azuread-joined-devices-setup) page. In the **Configuration steps** section, identify your configuration at the top of the table (either **Windows current and password hash sync** or **Windows current and federation**) and perform only the steps identified with a check mark.

@@ -47,7 +47,7 @@ Next, follow the guidance on the [How to configure hybrid Azure Active Directory ## Follow the Windows Hello for Business hybrid key trust deployment guide 1. [Overview](hello-hybrid-cert-trust.md) -2. [Prerequistes](hello-hybrid-cert-trust-prereqs.md) +2. [Prerequisites](hello-hybrid-cert-trust-prereqs.md) 3. [New Installation Baseline](hello-hybrid-cert-new-install.md) 4. [Configure Directory Synchronization](hello-hybrid-key-trust-dirsync.md) 5. Configure Azure Device Registration (*You are here*) From 83a316f4dfa239f785f48abf9ea612ebb056841a Mon Sep 17 00:00:00 2001 From: yoosi Date: Mon, 6 May 2019 14:06:22 -0700 Subject: [PATCH 23/67] correct typo in bitlocker-basic-deployment.md --- .../bitlocker/bitlocker-basic-deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/information-protection/bitlocker/bitlocker-basic-deployment.md b/windows/security/information-protection/bitlocker/bitlocker-basic-deployment.md index c9ba5464a6..9ea0ddd3dc 100644 --- a/windows/security/information-protection/bitlocker/bitlocker-basic-deployment.md +++ b/windows/security/information-protection/bitlocker/bitlocker-basic-deployment.md @@ -529,7 +529,7 @@ Disable-BitLocker -MountPoint E:,F:,G: ``` ## See also -- [Prepare your organization for BitLocker: Planning and p\\olicies](prepare-your-organization-for-bitlocker-planning-and-policies.md) +- [Prepare your organization for BitLocker: Planning and policies](prepare-your-organization-for-bitlocker-planning-and-policies.md) - [BitLocker recovery guide](bitlocker-recovery-guide-plan.md) - [BitLocker: How to enable Network Unlock](bitlocker-how-to-enable-network-unlock.md) - [BitLocker overview](bitlocker-overview.md) From 68c1c54c477b45cfb1f12eeb9831de1c349c2650 Mon Sep 17 00:00:00 2001 From: Nicole Turner <39884432+nenonix@users.noreply.github.com> Date: Mon, 6 May 2019 23:13:19 +0200 Subject: [PATCH 24/67] Update hello-planning-guide.md Typos https://github.com/MicrosoftDocs/windows-itpro-docs/issues/3203 --- .../hello-for-business/hello-planning-guide.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-planning-guide.md b/windows/security/identity-protection/hello-for-business/hello-planning-guide.md index 1700566e52..462ce37ed5 100644 --- a/windows/security/identity-protection/hello-for-business/hello-planning-guide.md +++ b/windows/security/identity-protection/hello-for-business/hello-planning-guide.md @@ -136,7 +136,7 @@ The Windows Hello for Business deployment depends on an enterprise public key in ### Cloud -Some deployment combinations require an Azure account and some require Azure Active Directory for user identities. These cloud requirements may only need an Azure account while other features need an Azure Active Directory Premium subscription. The planning process identifies and differentiates the components that are needed from the those that are optional. +Some deployment combinations require an Azure account, and some require Azure Active Directory for user identities. These cloud requirements may only need an Azure account while other features need an Azure Active Directory Premium subscription. The planning process identifies and differentiates the components that are needed from the those that are optional. ## Planning a Deployment @@ -150,13 +150,13 @@ Choose the deployment model based on the resources your users access. Use the f If your organization does not have on-premises resources, write **Cloud Only** in box **1a** on your planning worksheet. -If your organization is federated with Azure or uses any online service, such as Office365 or OneDrive, or your users access cloud and on-premises resources, write **Hybrid** in box **1a** on your planning worksheet. +If your organization is federated with Azure or uses any online service, such as Office365 or OneDrive, or your users' access cloud and on-premises resources, write **Hybrid** in box **1a** on your planning worksheet. If your organization does not have cloud resources, write **On-Premises** in box **1a** on your planning worksheet. >[!NOTE] >If you’re unsure if your organization is federated, run the following Active Directory Windows PowerShell command from an elevated Windows PowerShell prompt and evaluate the results. >```Get-AdObject “CN=62a0ff2e-97b9-4513-943f-0d221bd30080,CN=Device Registration Configuration,CN=Services,CN=Configuration,DC=corp,DC=[forest_root_CN_name],DC=com" -Properties keywords``` ->* If the command returns an error stating it could not find the object, then you have yet to configured AAD Connect or on-premises Device Registration Services using AD FS. Ensure the name is accurate and validate the object does not exist with another Active Directory Management tool such as **ADSIEdit.msc**. If the object truly does not exist, then you environment does not bind you to a specific deployment or require changes to accommodate the desired deployment type. +>* If the command returns an error stating it could not find the object, then you have yet to configured AAD Connect or on-premises Device Registration Services using AD FS. Ensure the name is accurate and validate the object does not exist with another Active Directory Management tool such as **ADSIEdit.msc**. If the object truly does not exist, then your environment does not bind you to a specific deployment or require changes to accommodate the desired deployment type. >* If the command returns a value, compare that value with the values below. The value indicates the deployment model you should implement > * If the value begins with **azureADName:** – write **Hybrid** in box **1a**on your planning worksheet. > * If the value begins with **enterpriseDrsName:** – write **On-Premises** in box **1a** on your planning worksheet. @@ -197,7 +197,7 @@ If box **1a** on your planning worksheet reads **cloud only**, write **N/A** in If box **1a** on your planning worksheet reads **hybrid**, then write **Azure AD Connect** in box **1e** on your planning worksheet. -If box **1a** on your planning worksheet reads **on-premises**, then write **Azure MFA Server**. This deployment exclusively uses Active Directory for user information with the exception of the multi-factor authentication. The on-premises Azure MFA server synchronizes a subset of the user information, such as phone number, to provide multi-factor authentication while the user’s credential remain on the on-premises network. +If box **1a** on your planning worksheet reads **on-premises**, then write **Azure MFA Server**. This deployment exclusively uses Active Directory for user information with the exception of the multi-factor authentication. The on-premises Azure MFA server synchronizes a subset of the user information, such as phone number, to provide multi-factor authentication while the user’s credentials remain on the on-premises network. ### Multifactor Authentication From f3d02254eb14dddf1734357306dd5d6a73d869e5 Mon Sep 17 00:00:00 2001 From: Nicole Turner <39884432+nenonix@users.noreply.github.com> Date: Mon, 6 May 2019 23:23:32 +0200 Subject: [PATCH 25/67] Update hello-hybrid-key-trust.md Typo "prerequisites" --- .../hello-for-business/hello-hybrid-key-trust.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust.md index 303b6ce403..1c42c615c5 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust.md @@ -37,7 +37,7 @@ This baseline provides detailed procedures to move your environment from an on-p You’re next step is to familiarize yourself with the prerequisites needed for the deployment. Many of the prerequisites will be new for organizations and individuals pursuing the new deployment baseline. Organizations and individuals starting from the federated baseline will likely be familiar with most of the prerequisites, but should validate they are using the proper versions that include the latest updates. > [!div class="nextstepaction"] -> [Prerequistes](hello-hybrid-key-trust-prereqs.md) +> [Prerequisites](hello-hybrid-key-trust-prereqs.md)

@@ -45,7 +45,7 @@ You’re next step is to familiarize yourself with the prerequisites needed for ## Follow the Windows Hello for Business hybrid key trust deployment guide 1. Overview (*You are here*) -2. [Prerequistes](hello-hybrid-key-trust-prereqs.md) +2. [Prerequisites](hello-hybrid-key-trust-prereqs.md) 3. [New Installation Baseline](hello-hybrid-key-new-install.md) 4. [Configure Directory Synchronization](hello-hybrid-key-trust-dirsync.md) 5. [Configure Azure Device Registration](hello-hybrid-key-trust-devreg.md) From 6ee5d7c96f8b0cb7104bd52e67fd3b3c9ec656a4 Mon Sep 17 00:00:00 2001 From: Nicole Turner <39884432+nenonix@users.noreply.github.com> Date: Tue, 7 May 2019 05:27:22 +0200 Subject: [PATCH 26/67] Update hello-hybrid-key-trust.md Prerequisites typo --- .../hello-for-business/hello-hybrid-key-trust.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust.md index d74bd02a0e..129be903cb 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust.md @@ -37,7 +37,7 @@ This baseline provides detailed procedures to move your environment from an on-p Your next step is to familiarize yourself with the prerequisites needed for the deployment. Many of the prerequisites will be new for organizations and individuals pursuing the new deployment baseline. Organizations and individuals starting from the federated baseline will likely be familiar with most of the prerequisites, but should validate they are using the proper versions that include the latest updates. > [!div class="nextstepaction"] -> [Prerequistes](hello-hybrid-key-trust-prereqs.md) +> [Prerequisites](hello-hybrid-key-trust-prereqs.md)

@@ -45,7 +45,7 @@ Your next step is to familiarize yourself with the prerequisites needed for the ## Follow the Windows Hello for Business hybrid key trust deployment guide 1. Overview (*You are here*) -2. [Prerequistes](hello-hybrid-key-trust-prereqs.md) +2. [Prerequisites](hello-hybrid-key-trust-prereqs.md) 3. [New Installation Baseline](hello-hybrid-key-new-install.md) 4. [Configure Directory Synchronization](hello-hybrid-key-trust-dirsync.md) 5. [Configure Azure Device Registration](hello-hybrid-key-trust-devreg.md) From 1e39927854b20f76169b9f32d18468f1617ea401 Mon Sep 17 00:00:00 2001 From: Nicole Turner <39884432+nenonix@users.noreply.github.com> Date: Tue, 7 May 2019 05:30:27 +0200 Subject: [PATCH 27/67] Update hello-hybrid-key-new-install.md Typo Prerequisites --- .../hello-for-business/hello-hybrid-key-new-install.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-new-install.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-new-install.md index 831a9879cb..4a4a80eced 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-new-install.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-new-install.md @@ -124,7 +124,7 @@ If your organization uses Azure MFA on a per-consumption model (no licenses), th Once you have created your Azure MFA authentication provider and associated it with an Azure tenant, you need to configure the multi-factor authentication settings. Review the [Configure Azure Multi-Factor Authentication settings](https://docs.microsoft.com/azure/multi-factor-authentication/multi-factor-authentication-whats-next) section to configure your settings. #### Azure MFA User States #### -After you have completed configuring your Azure MFA settings, you want to review configure [User States](https://docs.microsoft.com/azure/multi-factor-authentication/multi-factor-authentication-get-started-user-states) to understand user states. User states determine how you enable Azure MFA for your users. +After you have completed configuring your Azure MFA settings, you want to review configure [User States](https://docs.microsoft.com/azure/multi-factor-authentication/multi-factor-authentication-get-started-user-states) to understand user states. User states determine how you enable Azure MFA for your users. ### Azure MFA via ADFS ### Alternatively, you can configure Windows Server 2016 Active Directory Federation Services (AD FS) to provide additional multi-factor authentication. To configure, read the [Configure AD FS 2016 and Azure MFA](https://docs.microsoft.com/windows-server/identity/ad-fs/operations/configure-ad-fs-2016-and-azure-mfa) section. @@ -148,7 +148,7 @@ Alternatively, you can configure Windows Server 2016 Active Directory Federation ## Follow the Windows Hello for Business hybrid key trust deployment guide 1. [Overview](hello-hybrid-key-trust.md) -2. [Prerequistes](hello-hybrid-key-trust-prereqs.md) +2. [Prerequisites](hello-hybrid-key-trust-prereqs.md) 3. New Installation Baseline (*You are here*) 4. [Configure Directory Synchronization](hello-hybrid-key-trust-dirsync.md) 5. [Configure Azure Device Registration](hello-hybrid-key-trust-devreg.md) From 9cd14c4a4cab864228c727e44dff1e1184c5849c Mon Sep 17 00:00:00 2001 From: Nicole Turner <39884432+nenonix@users.noreply.github.com> Date: Tue, 7 May 2019 05:41:47 +0200 Subject: [PATCH 28/67] Update hello-hybrid-key-trust-dirsync.md Typos https://github.com/MicrosoftDocs/windows-itpro-docs/issues/3203 --- .../hello-for-business/hello-hybrid-key-trust-dirsync.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-dirsync.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-dirsync.md index 2c4dc3093c..617e922f94 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-dirsync.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-dirsync.md @@ -26,7 +26,7 @@ ms.date: 08/19/2018 You are ready to configure directory synchronization for your hybrid environment. Hybrid Windows Hello for Business deployment needs both a cloud and an on-premises identity to authenticate and access resources in the cloud or on-premises. ## Deploy Azure AD Connect -Next, you need to synchronizes the on-premises Active Directory with Azure Active Directory. To do this, first review the [Integrating on-prem directories with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnect) and [hardware and prerequisites](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnect-prerequisites) needed and then [download the software](http://go.microsoft.com/fwlink/?LinkId=615771). +Next, you need to synchronize the on-premises Active Directory with Azure Active Directory. To do this, first review the [Integrating on-prem directories with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnect) and [hardware and prerequisites](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnect-prerequisites) needed and then [download the software](http://go.microsoft.com/fwlink/?LinkId=615771). > [!NOTE] @@ -38,7 +38,7 @@ Next, you need to synchronizes the on-premises Active Directory with Azure Activ ## Follow the Windows Hello for Business hybrid key trust deployment guide 1. [Overview](hello-hybrid-key-trust.md) -2. [Prerequistes](hello-hybrid-key-trust-prereqs.md) +2. [Prerequisites](hello-hybrid-key-trust-prereqs.md) 3. [New Installation Baseline](hello-hybrid-key-new-install.md) 4. Configure Directory Synchronization (*You are here*) 5. [Configure Azure Device Registration](hello-hybrid-key-trust-devreg.md) From 322c28aa7290a18f3f4fcc861e91e1625646d7f4 Mon Sep 17 00:00:00 2001 From: Nicole Turner <39884432+nenonix@users.noreply.github.com> Date: Tue, 7 May 2019 05:48:08 +0200 Subject: [PATCH 29/67] Update hello-hybrid-cert-trust.md Typos --- .../hello-for-business/hello-hybrid-cert-trust.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-trust.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-trust.md index f8613819f5..c622ab65bb 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-trust.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-trust.md @@ -37,10 +37,10 @@ This baseline provides detailed procedures to move your environment from an on-p ## Federated Baseline ## The federated baseline helps organizations that have completed their federation with Azure Active Directory and Office 365 and enables them to introduce Windows Hello for Business into their hybrid environment. This baseline exclusively focuses on the procedures needed to add Azure Device Registration and Windows Hello for Business to an existing hybrid deployment. -Regardless of the baseline you choose, you’re next step is to familiarize yourself with the prerequisites needed for the deployment. Many of the prerequisites will be new for organizations and individuals pursuing the new deployment baseline. Organizations and individuals starting from the federated baseline will likely be familiar with most of the prerequisites, but should validate they are using the proper versions that include the latest updates. +Regardless of the baseline you choose, your next step is to familiarize yourself with the prerequisites needed for the deployment. Many of the prerequisites will be new for organizations and individuals pursuing the new deployment baseline. Organizations and individuals starting from the federated baseline will likely be familiar with most of the prerequisites, but should validate they are using the proper versions that include the latest updates. > [!div class="nextstepaction"] -> [Prerequistes](hello-hybrid-cert-trust-prereqs.md) +> [Prerequisites](hello-hybrid-cert-trust-prereqs.md)

@@ -48,7 +48,7 @@ Regardless of the baseline you choose, you’re next step is to familiarize your ## Follow the Windows Hello for Business hybrid certificate trust deployment guide 1. Overview (*You are here*) -2. [Prerequistes](hello-hybrid-cert-trust-prereqs.md) +2. [Prerequisites](hello-hybrid-cert-trust-prereqs.md) 3. [New Installation Baseline](hello-hybrid-cert-new-install.md) 4. [Device Registration](hello-hybrid-cert-trust-devreg.md) 5. [Configure Windows Hello for Business settings](hello-hybrid-cert-whfb-settings.md) From 91e9e7b8089f61f08260c8c101090f457372bc4b Mon Sep 17 00:00:00 2001 From: Nicole Turner <39884432+nenonix@users.noreply.github.com> Date: Tue, 7 May 2019 06:14:48 +0200 Subject: [PATCH 30/67] Update hello-hybrid-cert-new-install.md Typos lines 83,131,144, --- .../hello-for-business/hello-hybrid-cert-new-install.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-new-install.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-new-install.md index 2e3ac6b145..81a325489b 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-new-install.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-new-install.md @@ -80,7 +80,7 @@ If you do have an existing public key infrastructure, please review [Certificati ### Section Review ### > [!div class="checklist"] -> * Miniumum Windows Server 2012 Certificate Authority. +> * Minimum Windows Server 2012 Certificate Authority. > * Enterprise Certificate Authority. > * Functioning public key infrastructure. @@ -128,7 +128,7 @@ Alternatively, you can configure Windows Server 2016 Active Directory Federation > * Review the overview and uses of Azure Multifactor Authentication. > * Review your Azure Active Directory subscription for Azure Multifactor Authentication. > * Create an Azure Multifactor Authentication Provider, if necessary. -> * Configure Azure Multufactor Authentiation features and settings. +> * Configure Azure Multifactor Authentication features and settings. > * Understand the different User States and their effect on Azure Multifactor Authentication. > * Consider using Azure Multifactor Authentication or a third-party multifactor authentication provider with Windows Server 2016 Active Directory Federation Services, if necessary. @@ -141,7 +141,7 @@ Alternatively, you can configure Windows Server 2016 Active Directory Federation ## Follow the Windows Hello for Business hybrid certificate trust deployment guide 1. [Overview](hello-hybrid-cert-trust.md) -2. [Prerequistes](hello-hybrid-cert-trust-prereqs.md) +2. [Prerequisites](hello-hybrid-cert-trust-prereqs.md) 3. New Installation Baseline (*You are here*) 4. [Configure Azure Device Registration](hello-hybrid-cert-trust-devreg.md) 5. [Configure Windows Hello for Business settings](hello-hybrid-cert-whfb-settings.md) From b6816dedf09d7422aa581f96e5a8880c252c90ec Mon Sep 17 00:00:00 2001 From: Nicole Turner <39884432+nenonix@users.noreply.github.com> Date: Tue, 7 May 2019 06:32:48 +0200 Subject: [PATCH 31/67] Update hello-hybrid-cert-trust-devreg.md Typos lines 37, 103, 517 --- .../hello-for-business/hello-hybrid-cert-trust-devreg.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-trust-devreg.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-trust-devreg.md index bab9bcf458..273991ec82 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-trust-devreg.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-trust-devreg.md @@ -28,13 +28,13 @@ Your environment is federated and you are ready to configure device registration > [!IMPORTANT] > If your environment is not federated, review the [New Installation baseline](hello-hybrid-cert-new-install.md) section of this deployment document to learn how to federate your environment for your Windows Hello for Business deployment. -Use this three phased approach for configuring device registration. +Use this three-phased approach for configuring device registration. 1. [Configure devices to register in Azure](#configure-azure-for-device-registration) 2. [Synchronize devices to on-premises Active Directory](#configure-active-directory-to-support-azure-device-syncrhonization) 3. [Configure AD FS to use cloud devices](#configure-ad-fs-to-use-azure-registered-devices) > [!NOTE] -> Before proceeding, you should familiarize yourself with device regisration concepts such as: +> Before proceeding, you should familiarize yourself with device registration concepts such as: > * Azure AD registered devices > * Azure AD joined devices > * Hybrid Azure AD joined devices @@ -100,7 +100,7 @@ Federation server proxies are computers that run AD FS software that have been c Use the [Setting of a Federation Proxy](https://docs.microsoft.com/windows-server/identity/ad-fs/deployment/checklist--setting-up-a-federation-server-proxy) checklist to configure AD FS proxy servers in your environment. ### Deploy Azure AD Connect -Next, you need to synchronizes the on-premises Active Directory with Azure Active Directory. To do this, first review the [Integrating on-prem directories with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnect) and [hardware and prerequisites](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnect-prerequisites) needed and then [download the software](http://go.microsoft.com/fwlink/?LinkId=615771). +Next, you need to synchronize the on-premises Active Directory with Azure Active Directory. To do this, first review the [Integrating on-prem directories with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnect) and [hardware and prerequisites](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnect-prerequisites) needed and then [download the software](http://go.microsoft.com/fwlink/?LinkId=615771). When you are ready to install, follow the **Configuring federation with AD FS** section of [Custom installation of Azure AD Connect](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnect-get-started-custom). Select the **Federation with AD FS** option on the **User sign-in** page. At the **AD FS Farm** page, select the use an existing option and click **Next**. @@ -514,7 +514,7 @@ For your reference, below is a comprehensive list of the AD DS devices, containe ## Follow the Windows Hello for Business hybrid certificate trust deployment guide 1. [Overview](hello-hybrid-cert-trust.md) -2. [Prerequistes](hello-hybrid-cert-trust-prereqs.md) +2. [Prerequisites](hello-hybrid-cert-trust-prereqs.md) 3. [New Installation Baseline](hello-hybrid-cert-new-install.md) 4. Configure Azure Device Registration (*You are here*) 5. [Configure Windows Hello for Business settings](hello-hybrid-cert-whfb-settings.md) From 42b878163fe6c35d274c36ee3107938ba214604b Mon Sep 17 00:00:00 2001 From: Nicole Turner <39884432+nenonix@users.noreply.github.com> Date: Wed, 8 May 2019 11:25:01 +0530 Subject: [PATCH 32/67] Update windows/deployment/windows-autopilot/enrollment-status.md Co-Authored-By: Malind19 --- windows/deployment/windows-autopilot/enrollment-status.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopilot/enrollment-status.md b/windows/deployment/windows-autopilot/enrollment-status.md index 895cf49881..fd2778c09b 100644 --- a/windows/deployment/windows-autopilot/enrollment-status.md +++ b/windows/deployment/windows-autopilot/enrollment-status.md @@ -21,7 +21,7 @@ The Windows Autopilot Enrollment Status page displaying the status of the comple ![Enrollment status page](images/enrollment-status-page.png) -From Windows 10 version 1803 onwards, you can opt-out of the account setup phase. When it is skipped, the settings will be applied for the users when as they access their desktop for the first time. +From Windows 10 version 1803 onwards, you can opt out of the account setup phase. If it is skipped, settings will be applied for users when they access their desktop for the first time. ## Available settings From 3e80f2b5777a6ba91c4f8701338bdb1045212e83 Mon Sep 17 00:00:00 2001 From: botmoto <42125490+botmoto@users.noreply.github.com> Date: Thu, 9 May 2019 04:57:14 -0700 Subject: [PATCH 33/67] Update credential-guard-manage.md Cosmetic formatting --- .../credential-guard/credential-guard-manage.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/windows/security/identity-protection/credential-guard/credential-guard-manage.md b/windows/security/identity-protection/credential-guard/credential-guard-manage.md index e02b561b04..59b6865e4e 100644 --- a/windows/security/identity-protection/credential-guard/credential-guard-manage.md +++ b/windows/security/identity-protection/credential-guard/credential-guard-manage.md @@ -128,8 +128,7 @@ DG_Readiness_Tool_v3.5.ps1 -Ready ``` > [!NOTE] - -For client machines that are running Windows 10 1703, LsaIso.exe is running whenever virtualization-based security is enabled for other features. +> For client machines that are running Windows 10 1703, LsaIso.exe is running whenever virtualization-based security is enabled for other features. - We recommend enabling Windows Defender Credential Guard before a device is joined to a domain. If Windows Defender Credential Guard is enabled after domain join, the user and device secrets may already be compromised. In other words, enabling Credential Guard will not help to secure a device or identity that has already been compromised, which is why we recommend turning on Credential Guard as early as possible. From 089238bd71ac1a5e82f177e147c1ea10b5605297 Mon Sep 17 00:00:00 2001 From: John Kaiser <35939694+CoveMiner@users.noreply.github.com> Date: Thu, 9 May 2019 10:24:07 -0700 Subject: [PATCH 34/67] Update assettag.md --- devices/surface/assettag.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/devices/surface/assettag.md b/devices/surface/assettag.md index 9771aacb0d..03a43060a5 100644 --- a/devices/surface/assettag.md +++ b/devices/surface/assettag.md @@ -27,7 +27,7 @@ for Surface devices. It works on Surface Pro 3 and all newer Surface devices. To run Surface Asset Tag: 1. On the Surface device, download **Surface Pro 3 AssetTag.zip** from the [Microsoft Download - Center](http://www.microsoft.com/download/details.aspx?id=44076), + Center](https://www.microsoft.com/en-us/download/details.aspx?id=46703), extract the zip file, and save AssetTag.exe in desired folder (in this example, C:\\assets). From 8b6c29d5325aa3f5b15a61db64f46e515c7b9711 Mon Sep 17 00:00:00 2001 From: Jina Yoon <45857656+msft-jinayoon@users.noreply.github.com> Date: Thu, 9 May 2019 16:28:26 -0400 Subject: [PATCH 35/67] Updating Domain/ComputerName node info MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Incorporating the following info: • This node edits the DNS hostname of the computer. • If using the %RAND:x% or %SERIAL% macros, the new name is limited to 15 characters • If the serial number generated from the %SERIAL% macro is too long, the serial number will be truncated from the beginning of the serial number sequence, not the end. (e.g. 123ABCDEF456 --> CDEF456) • If the new name is a constant string (i.e. not using any of the macros) the new name can be up to 63 characters long • Validation for accepted characters are based on the SetComputerNameEx function: https://docs.microsoft.com/en-us/windows/desktop/api/sysinfoapi/nf-sysinfoapi-setcomputernameexa • This node does not work properly for hybrid-joined AAD/AD devices (it only works for fully AAD joined devices) I would love feedback and additional edits on how to make the proposed changes more customer-doc-friendly. Thanks! --- windows/client-management/mdm/accounts-csp.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/windows/client-management/mdm/accounts-csp.md b/windows/client-management/mdm/accounts-csp.md index 19820b0309..18e6657277 100644 --- a/windows/client-management/mdm/accounts-csp.md +++ b/windows/client-management/mdm/accounts-csp.md @@ -26,9 +26,13 @@ Root node. Interior node for the account domain information. **Domain/ComputerName** -This node specifies the name for a device. This setting can be managed remotely. A couple of macros can be embedded within the value for dynamic substitution: %RAND:<# of digits>% and %SERIAL%. +This node specifies the DNS hostname for a device. This setting can be managed remotely, but note that this not supported for devices hybrid joined to Azure Active Directory and an on-premises Active directory. The server must explicitly reboot the device for this value to take effect. A couple of macros can be embedded within the value for dynamic substitution. Using any of these macros will limit the new name to 15 characters. -Examples: (a) "Test%RAND:6%" will generate a name "Test" followed by 6 random digits (e.g., "Test123456"). (b) "Foo%SERIAL%", will generate a name "Foo" followed by the serial number derived from device's ID. The server must explicitly reboot the device for this value to take effect. +Available naming macros: +|Macro|Description|Example|Generated Name| +|:---|:---|:---|:---| +|%RAND:<# of digits>|Generates the specified number of random digits.|Test%RAND:6%|Test123456| +|%SERIAL%|Generates the serial number derived from the device. If the serial number causes the new name to exceed the 15 character limit, the serial number will be truncated from the beginning of the sequence.|Test-Device-%SERIAL%|Test-Device-456| Supported operation is Add. @@ -46,4 +50,4 @@ Supported operation is Add. **Users/_UserName_/LocalUserGroup** This optional node specifies the local user group that a local user account should be joined to. If the node is not set, the new local user account is joined just to the Standard Users group. Set the value to 2 for Administrators group. This setting can be managed remotely. -Supported operation is Add. \ No newline at end of file +Supported operation is Add. From 170fce992d89ff18362e18f604274665307b5ac1 Mon Sep 17 00:00:00 2001 From: Daniel Simpson Date: Thu, 9 May 2019 16:00:36 -0700 Subject: [PATCH 36/67] Update safety-scanner-download.md adding version info link --- .../threat-protection/intelligence/safety-scanner-download.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/windows/security/threat-protection/intelligence/safety-scanner-download.md b/windows/security/threat-protection/intelligence/safety-scanner-download.md index 890f7e0401..5a4ea7bd10 100644 --- a/windows/security/threat-protection/intelligence/safety-scanner-download.md +++ b/windows/security/threat-protection/intelligence/safety-scanner-download.md @@ -22,6 +22,8 @@ Microsoft Safety Scanner is a scan tool designed to find and remove malware from - [Download Microsoft Safety Scanner (64-bit)](https://go.microsoft.com/fwlink/?LinkId=212732) +[!NOTE] The security intelligence update version of the Microsoft Safety Scaner matches the version described [in this web page](https://www.microsoft.com/en-us/wdsi/definitions). + Safety Scanner only scans when manually triggered and is available for use 10 days after being downloaded. We recommend that you always download the latest version of this tool before each scan. > **NOTE:** This tool does not replace your antimalware product. For real-time protection with automatic updates, use [Windows Defender Antivirus on Windows 10 and Windows 8](https://www.microsoft.com/en-us/windows/windows-defender) or [Microsoft Security Essentials on Windows 7](https://support.microsoft.com/help/14210/security-essentials-download). These antimalware products also provide powerful malware removal capabilities. If you are having difficulties removing malware with these products, you can refer to our help on [removing difficult threats](https://www.microsoft.com/en-us/wdsi/help/troubleshooting-infection). @@ -49,4 +51,4 @@ For more information about the Safety Scanner, see the support article on [how t - [Microsoft Security Essentials](https://support.microsoft.com/help/14210/security-essentials-download) - [Removing difficult threats](https://support.microsoft.com/help/4466982/windows-10-troubleshoot-problems-with-detecting-and-removing-malware) - [Submit file for malware analysis](https://www.microsoft.com/wdsi/filesubmission) -- [Microsoft antimalware and threat protection solutions](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/windows-defender-advanced-threat-protection) \ No newline at end of file +- [Microsoft antimalware and threat protection solutions](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/windows-defender-advanced-threat-protection) From 5a0d6d9e959aa2c19f362029a757a85c08525dd7 Mon Sep 17 00:00:00 2001 From: Justin Hall Date: Fri, 10 May 2019 11:12:09 -0700 Subject: [PATCH 37/67] Update hello-hybrid-key-trust-prereqs.md --- .../hello-for-business/hello-hybrid-key-trust-prereqs.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md index a4a1cc41b4..4d48eaed74 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md @@ -85,7 +85,7 @@ Organizations using older directory synchronization technology, such as DirSync
## Federation with Azure ## -You can deploy Windows Hello for Business key trust in non-federated and federated environments. For non-federated environments, key trust deployments work in environments that have deployed [Password Synchronization with Azure AD Connect](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnectsync-implement-password-synchronization) and [Azure Active Directory Pass-through-Authentication](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnect-pass-through-authentication). For federated environments, you can deploy Windows Hello for Business key trust using Active Directory Federation Services (AD FS) 2012 R2 or later. +You can deploy Windows Hello for Business key trust in non-federated and federated environments. For non-federated environments, key trust deployments work in environments that have deployed [Password Synchronization with Azure AD Connect](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnectsync-implement-password-synchronization) and [Azure Active Directory Pass-through-Authentication](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnect-pass-through-authentication). For federated environments, you can deploy Windows Hello for Business key trust using Active Directory Federation Services (AD FS) beginning with Windows Server 2012 R2. ### Section Review ### > [!div class="checklist"] @@ -97,7 +97,7 @@ You can deploy Windows Hello for Business key trust in non-federated and federat ## Multifactor Authentication ## Windows Hello for Business is a strong, two-factor credential the helps organizations reduce their dependency on passwords. The provisioning process lets a user enroll in Windows Hello for Business using their user name and password as one factor, but needs a second factor of authentication. -Hybrid Windows Hello for Business deployments can use Azure’s Multi-factor Authentication service or they can use multi-factor authentication provided by Windows Server 2012 R2 or later Active Directory Federation Services, which include an adapter model that enables third parties to integrate their multi-factor authentication into AD FS. The Multi-factor authentication enabled in Office 365 license is sufficient for direct Multi-factor Authentication against Azure AD. +Hybrid Windows Hello for Business deployments can use Azure’s Multifactor Authentication (MFA) service or they can use MFA provided by AD FS beginning with Windows Server 2012 R2, which includes an adapter model that enables third parties to integrate their MFA into AD FS. The MFA enabled by an Office 365 license is sufficient for Azure AD. ### Section Review > [!div class="checklist"] From 33bc56ed1e0f1e68b4ffdebe277e2dc44a36fcbd Mon Sep 17 00:00:00 2001 From: Justin Hall Date: Fri, 10 May 2019 11:13:55 -0700 Subject: [PATCH 38/67] Update hello-hybrid-key-trust-prereqs.md --- .../hello-for-business/hello-hybrid-key-trust-prereqs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md index 4d48eaed74..e7e22f7c8f 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md @@ -97,7 +97,7 @@ You can deploy Windows Hello for Business key trust in non-federated and federat ## Multifactor Authentication ## Windows Hello for Business is a strong, two-factor credential the helps organizations reduce their dependency on passwords. The provisioning process lets a user enroll in Windows Hello for Business using their user name and password as one factor, but needs a second factor of authentication. -Hybrid Windows Hello for Business deployments can use Azure’s Multifactor Authentication (MFA) service or they can use MFA provided by AD FS beginning with Windows Server 2012 R2, which includes an adapter model that enables third parties to integrate their MFA into AD FS. The MFA enabled by an Office 365 license is sufficient for Azure AD. +Hybrid Windows Hello for Business deployments can use Azure’s Multifactor Authentication (MFA) service or they can use multifactor authentication provided by AD FS beginning with Windows Server 2012 R2, which includes an adapter model that enables third parties to integrate their MFA into AD FS. The MFA enabled by an Office 365 license is sufficient for Azure AD. ### Section Review > [!div class="checklist"] From 6a6fe30fe138e9f0ce63896660bd5820a3e92ecc Mon Sep 17 00:00:00 2001 From: Daniel Simpson Date: Fri, 10 May 2019 14:36:01 -0700 Subject: [PATCH 39/67] Update safety-scanner-download.md fixing NOTE style --- .../threat-protection/intelligence/safety-scanner-download.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/intelligence/safety-scanner-download.md b/windows/security/threat-protection/intelligence/safety-scanner-download.md index 5a4ea7bd10..69dfef35ee 100644 --- a/windows/security/threat-protection/intelligence/safety-scanner-download.md +++ b/windows/security/threat-protection/intelligence/safety-scanner-download.md @@ -22,7 +22,7 @@ Microsoft Safety Scanner is a scan tool designed to find and remove malware from - [Download Microsoft Safety Scanner (64-bit)](https://go.microsoft.com/fwlink/?LinkId=212732) -[!NOTE] The security intelligence update version of the Microsoft Safety Scaner matches the version described [in this web page](https://www.microsoft.com/en-us/wdsi/definitions). +> **NOTE** The security intelligence update version of the Microsoft Safety Scaner matches the version described [in this web page](https://www.microsoft.com/en-us/wdsi/definitions). Safety Scanner only scans when manually triggered and is available for use 10 days after being downloaded. We recommend that you always download the latest version of this tool before each scan. From 774a98767c45c9edaf490cd3ef55e6d0ab648518 Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Fri, 10 May 2019 15:38:34 -0700 Subject: [PATCH 40/67] Added 19H1 policy --- .../policy-configuration-service-provider.md | 4 ++ .../mdm/policy-csp-experience.md | 72 +++++++++++++++++++ 2 files changed, 76 insertions(+) diff --git a/windows/client-management/mdm/policy-configuration-service-provider.md b/windows/client-management/mdm/policy-configuration-service-provider.md index 4913c03360..8c6acf42f8 100644 --- a/windows/client-management/mdm/policy-configuration-service-provider.md +++ b/windows/client-management/mdm/policy-configuration-service-provider.md @@ -1262,6 +1262,9 @@ The following diagram shows the Policy configuration service provider in tree fo
Experience/PreventUsersFromTurningOnBrowserSyncing
+
+ Experience/ShowLockOnUserTile +
### ExploitGuard policies @@ -4369,6 +4372,7 @@ The following diagram shows the Policy configuration service provider in tree fo - [Experience/DoNotShowFeedbackNotifications](./policy-csp-experience.md#experience-donotshowfeedbacknotifications) - [Experience/DoNotSyncBrowserSettings](./policy-csp-experience.md#experience-donotsyncbrowsersetting) - [Experience/PreventUsersFromTurningOnBrowserSyncing](./policy-csp-experience.md#experience-preventusersfromturningonbrowsersyncing) +- [Experience/ShowLockOnUserTile](policy-csp-experience.md#experience-showlockonusertile) - [ExploitGuard/ExploitProtectionSettings](./policy-csp-exploitguard.md#exploitguard-exploitprotectionsettings) - [FileExplorer/TurnOffDataExecutionPreventionForExplorer](./policy-csp-fileexplorer.md#fileexplorer-turnoffdataexecutionpreventionforexplorer) - [FileExplorer/TurnOffHeapTerminationOnCorruption](./policy-csp-fileexplorer.md#fileexplorer-turnoffheapterminationoncorruption) diff --git a/windows/client-management/mdm/policy-csp-experience.md b/windows/client-management/mdm/policy-csp-experience.md index c0d7b7cad4..cbc286da97 100644 --- a/windows/client-management/mdm/policy-csp-experience.md +++ b/windows/client-management/mdm/policy-csp-experience.md @@ -96,6 +96,9 @@ ms.date: 05/01/2019
Experience/PreventUsersFromTurningOnBrowserSyncing
+
+ Experience/ShowLockOnUserTile +
@@ -1569,6 +1572,75 @@ Validation procedure: +
+ + +**Experience/ShowLockOnUserTile** + + + + + + + + + + + + + + + + + + + + + +
HomeProBusinessEnterpriseEducationMobileMobile Enterprise
cross markcross markcheck mark6check mark6check mark6
+ + + +[Scope](./policy-configuration-service-provider.md#policy-scope): + +> [!div class = "checklist"] +> * Device + +
+ + + +Shows or hides lock from the user tile menu. + +If you enable this policy setting, the lock option is shown in the User Tile menu. + +If you disable this policy setting, the lock option is never shown in the User Tile menu. + +If you do not configure this policy setting, the lock option is shown in the User Tile menu. Users can choose if they want to show the lock in the user tile menu from the Power Options control panel. + + + +ADMX Info: +- GP English name: *Show lock in the user tile menu* +- GP name: *ShowLockOption* +- GP path: *File Explorer* +- GP ADMX file name: *WindowsExplorer.admx* + + + +Supported values: +- false (default) - The lock option is not displayed in the User Tile menu. +- true - The lock option is displayed in the User Tile menu. + + + + + + + + + + From 1f9ba5ca8659274066e82e3671004cc7097608bb Mon Sep 17 00:00:00 2001 From: Jose Ortega Date: Sun, 12 May 2019 04:33:26 -0500 Subject: [PATCH 41/67] Solving issue #880 --- .../deployment/deploy-enterprise-licenses.md | 53 ++++++++++++------- 1 file changed, 33 insertions(+), 20 deletions(-) diff --git a/windows/deployment/deploy-enterprise-licenses.md b/windows/deployment/deploy-enterprise-licenses.md index afc9f144c2..038c839c38 100644 --- a/windows/deployment/deploy-enterprise-licenses.md +++ b/windows/deployment/deploy-enterprise-licenses.md @@ -12,14 +12,20 @@ author: greg-lindsay ms.topic: article --- + + # Deploy Windows 10 Enterprise licenses +>[!IMPORTANT] +>Licenses E3 and E5 brings windows 10 license enterprise with them, this tutorial is special for the use and implementation of these licenses in a on-premises Active Directory environment. + + This topic describes how to deploy Windows 10 Enterprise E3 or E5 licenses with [Windows 10 Enterprise Subscription Activation](windows-10-enterprise-subscription-activation.md) or [Windows 10 Enterprise E3 in CSP](windows-10-enterprise-e3-overview.md) and Azure Active Directory (Azure AD). >[!NOTE] ->Windows 10 Enterprise Subscription Activation (EA or MPSA) requires Windows 10 Pro, version 1703 or later.
->Windows 10 Enterprise E3 in CSP requires Windows 10 Pro, version 1607 or later.
->Automatic, non-KMS activation requires Windows 10, version 1803 or later on a device with a firmware-embedded activation key.
+>* Windows 10 Enterprise Subscription Activation (EA or MPSA) requires Windows 10 Pro, version 1703 or later. +>* Windows 10 Enterprise E3 in CSP requires Windows 10 Pro, version 1607 or later. +>* Automatic, non-KMS activation requires Windows 10, version 1803 or later on a device with a firmware-embedded activation key. ## Firmware-embedded activation key @@ -35,9 +41,9 @@ If the device has a firmware-embedded activation key, it will be displayed in th If you are an EA customer with an existing Office 365 tenant, use the following steps to enable Windows 10 Subscription licenses on your existing tenant: -1. Work with your reseller to place an order for one $0 SKU per user. There are two SKUs available, depending on their current Windows Enterprise SA license:
- a. **AAA-51069** - Win10UsrOLSActv Alng MonthlySub Addon E3
- b. **AAA-51068** - Win10UsrOLSActv Alng MonthlySub Addon E5
+1. Work with your reseller to place an order for one $0 SKU per user. There are two SKUs available, depending on their current Windows Enterprise SA license: + a. **AAA-51069** - Win10UsrOLSActv Alng MonthlySub Addon E3 + b. **AAA-51068** - Win10UsrOLSActv Alng MonthlySub Addon E5 2. After placing an order, the OLS admin on the agreement will receive a service activation email, indicating their subscription licenses have been provisioned on the tenant. 3. The admin can now assign subscription licenses to users. @@ -59,7 +65,7 @@ Also in this article: You probably have on-premises Active Directory Domain Services (AD DS) domains. Users will use their domain-based credentials to sign in to the AD DS domain. Before you start deploying Windows 10 Enterprise E3 or E5 licenses to users, you need to synchronize the identities in the on-premises ADDS domain with Azure AD. -You might ask why you need to synchronize these identities. The answer is so that users will have a *single identity* that they can use to access their on-premises apps and cloud services that use Azure AD (such as Windows 10 Enterprise E3 or E5). This means that users can use their existing credentials to sign in to Azure AD and access the cloud services that you provide and manage for them. +You might ask why you need to synchronize these identities. The answer is that users will have a **single identity** that they can use to access their on-premises apps and cloud services that use Azure AD (**such as Windows 10 Enterprise E3 or E5**). This means that users can use their existing credentials to sign in to Azure AD and access the cloud services that you provide and manage for them. **Figure 1** illustrates the integration between the on-premises AD DS domain with Azure AD. [Microsoft Azure Active Directory Connect](https://www.microsoft.com/en-us/download/details.aspx?id=47594) (Azure AD Connect) is responsible for synchronization of identities between the on-premises AD DS domain and Azure AD. Azure AD Connect is a service that you can install on-premises or in a virtual machine in Azure. @@ -72,6 +78,13 @@ For more information about integrating on-premises AD DS domains with Azure AD, - [Integrating your on-premises identities with Azure Active Directory](https://azure.microsoft.com/documentation/articles/active-directory-aadconnect/) - [Azure AD + Domain Join + Windows 10](https://blogs.technet.microsoft.com/enterprisemobility/2016/02/17/azure-ad-domain-join-windows-10/) +>[!NOTE] +>If you are implementing Azure AD, and have already an on-premises, you don't need to join the computers into Azure AD, since your main authentication method is your internal AD. In case, that you want to manage all your infrastructure on the cloud, then you can safely remote your domain controller and work with the join of the computers into the Azure AD, but you won't be able to apply fine control into the computers using GPO. +>The whole idea of using Azure AD, is mostly when you don't have any on-premises servers, and you want and enterprise administration of devices worldwide. + + + + ## Preparing for deployment: reviewing requirements Devices must be running Windows 10 Pro, version 1703, and be Azure Active Directory joined, or hybrid domain joined with Azure AD Connect. Customers who are federated with Azure Active Directory are also eligible. For more information, see [Review requirements on devices](#review-requirements-on-devices), later in this topic. @@ -151,12 +164,12 @@ Now the device is Azure AD joined to the company’s subscription. ### Step 2: Pro edition activation >[!IMPORTANT] ->If the device is running Windows 10, version 1803 or later, this step is no longer necessary when there is a firmware-embedded activation key on the device. Starting with Windows 10, version 1803 the device will automatically activate Windows 10 Enterprise using the firmware-embedded activation key.
+>If the device is running Windows 10, version 1803 or later, this step is no longer necessary when there is a firmware-embedded activation key on the device. Starting with Windows 10, version 1803 the device will automatically activate Windows 10 Enterprise using the firmware-embedded activation key. >If the device is running Windows 10, version 1703 or 1709, then Windows 10 Pro must be successfully activated in **Settings > Update & Security > Activation**, as illustrated in **Figure 7a**. Windows 10 Pro activated -
**Figure 7a - Windows 10 Pro activation in Settings**
+**Figure 7a - Windows 10 Pro activation in Settings** Windows 10 Pro activation is required before Enterprise E3 or E5 can be enabled (Windows 10, versions 1703 and 1709 only). @@ -176,16 +189,16 @@ You can verify the Windows 10 Enterprise E3 or E5 subscription in **Settings &g Windows 10 activated and subscription active -
**Figure 9 - Windows 10 Enterprise subscription in Settings**
+**Figure 9 - Windows 10 Enterprise subscription in Settings** If there are any problems with the Windows 10 Enterprise E3 or E5 license or the activation of the license, the **Activation** panel will display the appropriate error message or status. You can use this information to help you diagnose the licensing and activation process. >[!NOTE] ->If you use slmgr /dli or /dlv commands to retrieve the activation information for the Windows 10 E3 or E5 license, the license information displayed will be the following:
->Name: Windows(R), Professional edition
->Description: Windows(R) Operating System, RETAIL channel
->Partial Product Key: 3V66T
+>If you use slmgr /dli or /dlv commands to retrieve the activation information for the Windows 10 E3 or E5 license, the license information displayed will be the following: +>Name: Windows(R), Professional edition +>Description: Windows(R) Operating System, RETAIL channel +>Partial Product Key: 3V66T ## Virtual Desktop Access (VDA) @@ -211,23 +224,23 @@ Use the following figures to help you troubleshoot when users experience these c - [Figure 12](#win-10-not-activated-subscription-not-active) (below) illustrates a device on which Windows 10 Pro license is not activated and the Windows 10 Enterprise subscription is lapsed or removed. -
+ Windows 10 not activated and subscription active -
**Figure 10 - Windows 10 Pro, version 1703 edition not activated in Settings**
+**Figure 10 - Windows 10 Pro, version 1703 edition not activated in Settings** + -
Windows 10 activated and subscription not active -
**Figure 11 - Windows 10 Enterprise subscription lapsed or removed in Settings**
+**Figure 11 - Windows 10 Enterprise subscription lapsed or removed in Settings** + -
Windows 10 not activated and subscription not active -
**Figure 12 - Windows 10 Pro, version 1703 edition not activated and Windows 10 Enterprise subscription lapsed or removed in Settings**
+**Figure 12 - Windows 10 Pro, version 1703 edition not activated and Windows 10 Enterprise subscription lapsed or removed in Settings** ### Review requirements on devices From f2e7db1c27a2f01fe8490dc7ce55e3f62a1b8352 Mon Sep 17 00:00:00 2001 From: Jose Gabriel Ortega Castro Date: Mon, 13 May 2019 10:04:55 -0500 Subject: [PATCH 42/67] Update windows/deployment/deploy-enterprise-licenses.md Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com> --- windows/deployment/deploy-enterprise-licenses.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/deploy-enterprise-licenses.md b/windows/deployment/deploy-enterprise-licenses.md index 038c839c38..ca9c5911b9 100644 --- a/windows/deployment/deploy-enterprise-licenses.md +++ b/windows/deployment/deploy-enterprise-licenses.md @@ -164,7 +164,7 @@ Now the device is Azure AD joined to the company’s subscription. ### Step 2: Pro edition activation >[!IMPORTANT] ->If the device is running Windows 10, version 1803 or later, this step is no longer necessary when there is a firmware-embedded activation key on the device. Starting with Windows 10, version 1803 the device will automatically activate Windows 10 Enterprise using the firmware-embedded activation key. +>If your device is running Windows 10, version 1803 or later, this step not needed. Starting with Windows 10 version 1803 the device will automatically activate Windows 10 Enterprise using the firmware-embedded activation key. >If the device is running Windows 10, version 1703 or 1709, then Windows 10 Pro must be successfully activated in **Settings > Update & Security > Activation**, as illustrated in **Figure 7a**. From bd221ac09c378556b5d5b985485edcc9805736fa Mon Sep 17 00:00:00 2001 From: Jose Ortega Date: Mon, 13 May 2019 10:11:25 -0500 Subject: [PATCH 43/67] Corrections --- windows/deployment/deploy-enterprise-licenses.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/windows/deployment/deploy-enterprise-licenses.md b/windows/deployment/deploy-enterprise-licenses.md index ca9c5911b9..9a03873d7c 100644 --- a/windows/deployment/deploy-enterprise-licenses.md +++ b/windows/deployment/deploy-enterprise-licenses.md @@ -19,7 +19,6 @@ ms.topic: article >[!IMPORTANT] >Licenses E3 and E5 brings windows 10 license enterprise with them, this tutorial is special for the use and implementation of these licenses in a on-premises Active Directory environment. - This topic describes how to deploy Windows 10 Enterprise E3 or E5 licenses with [Windows 10 Enterprise Subscription Activation](windows-10-enterprise-subscription-activation.md) or [Windows 10 Enterprise E3 in CSP](windows-10-enterprise-e3-overview.md) and Azure Active Directory (Azure AD). >[!NOTE] @@ -82,9 +81,6 @@ For more information about integrating on-premises AD DS domains with Azure AD, >If you are implementing Azure AD, and have already an on-premises, you don't need to join the computers into Azure AD, since your main authentication method is your internal AD. In case, that you want to manage all your infrastructure on the cloud, then you can safely remote your domain controller and work with the join of the computers into the Azure AD, but you won't be able to apply fine control into the computers using GPO. >The whole idea of using Azure AD, is mostly when you don't have any on-premises servers, and you want and enterprise administration of devices worldwide. - - - ## Preparing for deployment: reviewing requirements Devices must be running Windows 10 Pro, version 1703, and be Azure Active Directory joined, or hybrid domain joined with Azure AD Connect. Customers who are federated with Azure Active Directory are also eligible. For more information, see [Review requirements on devices](#review-requirements-on-devices), later in this topic. @@ -225,7 +221,6 @@ Use the following figures to help you troubleshoot when users experience these c - [Figure 12](#win-10-not-activated-subscription-not-active) (below) illustrates a device on which Windows 10 Pro license is not activated and the Windows 10 Enterprise subscription is lapsed or removed. - Windows 10 not activated and subscription active **Figure 10 - Windows 10 Pro, version 1703 edition not activated in Settings** From c020150f3684eb897ef425c8c9d4a3a7d0008685 Mon Sep 17 00:00:00 2001 From: Jose Gabriel Ortega Castro Date: Mon, 13 May 2019 10:12:49 -0500 Subject: [PATCH 44/67] Update windows/deployment/deploy-enterprise-licenses.md Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com> --- windows/deployment/deploy-enterprise-licenses.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/deploy-enterprise-licenses.md b/windows/deployment/deploy-enterprise-licenses.md index 9a03873d7c..8c90e9f4ba 100644 --- a/windows/deployment/deploy-enterprise-licenses.md +++ b/windows/deployment/deploy-enterprise-licenses.md @@ -24,7 +24,7 @@ This topic describes how to deploy Windows 10 Enterprise E3 or E5 licenses with >[!NOTE] >* Windows 10 Enterprise Subscription Activation (EA or MPSA) requires Windows 10 Pro, version 1703 or later. >* Windows 10 Enterprise E3 in CSP requires Windows 10 Pro, version 1607 or later. ->* Automatic, non-KMS activation requires Windows 10, version 1803 or later on a device with a firmware-embedded activation key. +>* Automatic, non-KMS activation requires Windows 10, version 1803 or later, on a device with a firmware-embedded activation key. ## Firmware-embedded activation key From ea00510908b1f1de7bdece0cebfa77aab8d83dc1 Mon Sep 17 00:00:00 2001 From: Jose Gabriel Ortega Castro Date: Mon, 13 May 2019 10:12:58 -0500 Subject: [PATCH 45/67] Update windows/deployment/deploy-enterprise-licenses.md Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com> --- windows/deployment/deploy-enterprise-licenses.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/deploy-enterprise-licenses.md b/windows/deployment/deploy-enterprise-licenses.md index 8c90e9f4ba..83fbd2a73f 100644 --- a/windows/deployment/deploy-enterprise-licenses.md +++ b/windows/deployment/deploy-enterprise-licenses.md @@ -64,7 +64,7 @@ Also in this article: You probably have on-premises Active Directory Domain Services (AD DS) domains. Users will use their domain-based credentials to sign in to the AD DS domain. Before you start deploying Windows 10 Enterprise E3 or E5 licenses to users, you need to synchronize the identities in the on-premises ADDS domain with Azure AD. -You might ask why you need to synchronize these identities. The answer is that users will have a **single identity** that they can use to access their on-premises apps and cloud services that use Azure AD (**such as Windows 10 Enterprise E3 or E5**). This means that users can use their existing credentials to sign in to Azure AD and access the cloud services that you provide and manage for them. +You might ask why you need to synchronize these identities. The answer is so that users will have a *single identity* that they can use to access their on-premises apps and cloud services that use Azure AD (such as Windows 10 Enterprise E3 or E5). This means that users can use their existing credentials to sign in to Azure AD and access the cloud services that you provide and manage for them. **Figure 1** illustrates the integration between the on-premises AD DS domain with Azure AD. [Microsoft Azure Active Directory Connect](https://www.microsoft.com/en-us/download/details.aspx?id=47594) (Azure AD Connect) is responsible for synchronization of identities between the on-premises AD DS domain and Azure AD. Azure AD Connect is a service that you can install on-premises or in a virtual machine in Azure. From 67f98f7e71c82dcdb80bd8042948accab6e44060 Mon Sep 17 00:00:00 2001 From: Jose Gabriel Ortega Castro Date: Mon, 13 May 2019 10:13:06 -0500 Subject: [PATCH 46/67] Update windows/deployment/deploy-enterprise-licenses.md Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com> --- windows/deployment/deploy-enterprise-licenses.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/deploy-enterprise-licenses.md b/windows/deployment/deploy-enterprise-licenses.md index 83fbd2a73f..9721ecd2be 100644 --- a/windows/deployment/deploy-enterprise-licenses.md +++ b/windows/deployment/deploy-enterprise-licenses.md @@ -42,7 +42,7 @@ If you are an EA customer with an existing Office 365 tenant, use the following 1. Work with your reseller to place an order for one $0 SKU per user. There are two SKUs available, depending on their current Windows Enterprise SA license: a. **AAA-51069** - Win10UsrOLSActv Alng MonthlySub Addon E3 - b. **AAA-51068** - Win10UsrOLSActv Alng MonthlySub Addon E5 +- **AAA-51068** - Win10UsrOLSActv Alng MonthlySub Addon E5 2. After placing an order, the OLS admin on the agreement will receive a service activation email, indicating their subscription licenses have been provisioned on the tenant. 3. The admin can now assign subscription licenses to users. From f5ca28c6688d8184e914da54a4a258bea602e573 Mon Sep 17 00:00:00 2001 From: Jose Gabriel Ortega Castro Date: Mon, 13 May 2019 10:13:14 -0500 Subject: [PATCH 47/67] Update windows/deployment/deploy-enterprise-licenses.md Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com> --- windows/deployment/deploy-enterprise-licenses.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/deploy-enterprise-licenses.md b/windows/deployment/deploy-enterprise-licenses.md index 9721ecd2be..cdecd2c70f 100644 --- a/windows/deployment/deploy-enterprise-licenses.md +++ b/windows/deployment/deploy-enterprise-licenses.md @@ -78,7 +78,7 @@ For more information about integrating on-premises AD DS domains with Azure AD, - [Azure AD + Domain Join + Windows 10](https://blogs.technet.microsoft.com/enterprisemobility/2016/02/17/azure-ad-domain-join-windows-10/) >[!NOTE] ->If you are implementing Azure AD, and have already an on-premises, you don't need to join the computers into Azure AD, since your main authentication method is your internal AD. In case, that you want to manage all your infrastructure on the cloud, then you can safely remote your domain controller and work with the join of the computers into the Azure AD, but you won't be able to apply fine control into the computers using GPO. +>If you are implementing Azure AD, and you already have an on-premises domain, you don't need to integrate with Azure AD, since your main authentication method is your internal AD. If you want to manage all your infrastructure in the cloud, you can safely configure your domain controller remotely to integrate your computers with Azure AD, but you won't be able to apply fine controls using GPO. Azure AD is best suited for the global administration of devices when you don't have any on-premises servers. >The whole idea of using Azure AD, is mostly when you don't have any on-premises servers, and you want and enterprise administration of devices worldwide. ## Preparing for deployment: reviewing requirements From 4ad41520e7864728f84d69c50b0ea11cc417bcef Mon Sep 17 00:00:00 2001 From: Jose Gabriel Ortega Castro Date: Mon, 13 May 2019 10:13:28 -0500 Subject: [PATCH 48/67] Update windows/deployment/deploy-enterprise-licenses.md Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com> --- windows/deployment/deploy-enterprise-licenses.md | 1 - 1 file changed, 1 deletion(-) diff --git a/windows/deployment/deploy-enterprise-licenses.md b/windows/deployment/deploy-enterprise-licenses.md index cdecd2c70f..38252eee03 100644 --- a/windows/deployment/deploy-enterprise-licenses.md +++ b/windows/deployment/deploy-enterprise-licenses.md @@ -79,7 +79,6 @@ For more information about integrating on-premises AD DS domains with Azure AD, >[!NOTE] >If you are implementing Azure AD, and you already have an on-premises domain, you don't need to integrate with Azure AD, since your main authentication method is your internal AD. If you want to manage all your infrastructure in the cloud, you can safely configure your domain controller remotely to integrate your computers with Azure AD, but you won't be able to apply fine controls using GPO. Azure AD is best suited for the global administration of devices when you don't have any on-premises servers. ->The whole idea of using Azure AD, is mostly when you don't have any on-premises servers, and you want and enterprise administration of devices worldwide. ## Preparing for deployment: reviewing requirements From 33cec4871e6275f66bbaa57f1b32b20f1257d8b3 Mon Sep 17 00:00:00 2001 From: Jose Gabriel Ortega Castro Date: Mon, 13 May 2019 10:13:39 -0500 Subject: [PATCH 49/67] Update windows/deployment/deploy-enterprise-licenses.md Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com> --- windows/deployment/deploy-enterprise-licenses.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/deploy-enterprise-licenses.md b/windows/deployment/deploy-enterprise-licenses.md index 38252eee03..b1b4b2b9d5 100644 --- a/windows/deployment/deploy-enterprise-licenses.md +++ b/windows/deployment/deploy-enterprise-licenses.md @@ -41,7 +41,7 @@ If the device has a firmware-embedded activation key, it will be displayed in th If you are an EA customer with an existing Office 365 tenant, use the following steps to enable Windows 10 Subscription licenses on your existing tenant: 1. Work with your reseller to place an order for one $0 SKU per user. There are two SKUs available, depending on their current Windows Enterprise SA license: - a. **AAA-51069** - Win10UsrOLSActv Alng MonthlySub Addon E3 +- **AAA-51069** - Win10UsrOLSActv Alng MonthlySub Addon E3 - **AAA-51068** - Win10UsrOLSActv Alng MonthlySub Addon E5 2. After placing an order, the OLS admin on the agreement will receive a service activation email, indicating their subscription licenses have been provisioned on the tenant. 3. The admin can now assign subscription licenses to users. From 85e9423476bb32060213ca9bb7e15691c189362d Mon Sep 17 00:00:00 2001 From: Jose Gabriel Ortega Castro Date: Mon, 13 May 2019 10:13:57 -0500 Subject: [PATCH 50/67] Update windows/deployment/deploy-enterprise-licenses.md Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com> --- windows/deployment/deploy-enterprise-licenses.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/deploy-enterprise-licenses.md b/windows/deployment/deploy-enterprise-licenses.md index b1b4b2b9d5..fd04ba220b 100644 --- a/windows/deployment/deploy-enterprise-licenses.md +++ b/windows/deployment/deploy-enterprise-licenses.md @@ -17,7 +17,7 @@ ms.topic: article # Deploy Windows 10 Enterprise licenses >[!IMPORTANT] ->Licenses E3 and E5 brings windows 10 license enterprise with them, this tutorial is special for the use and implementation of these licenses in a on-premises Active Directory environment. +>Office 365 Enterprise E3 and Office 365 Enterprise E5 include a Windows 10 Enterprise license. This article is about the use and implementation of these licenses in a on-premises Active Directory environment. This topic describes how to deploy Windows 10 Enterprise E3 or E5 licenses with [Windows 10 Enterprise Subscription Activation](windows-10-enterprise-subscription-activation.md) or [Windows 10 Enterprise E3 in CSP](windows-10-enterprise-e3-overview.md) and Azure Active Directory (Azure AD). From 73007e7e463bd4fa727fb2652090d6287a4f9063 Mon Sep 17 00:00:00 2001 From: Jose Gabriel Ortega Castro Date: Mon, 13 May 2019 10:54:17 -0500 Subject: [PATCH 51/67] Update windows/deployment/deploy-enterprise-licenses.md Co-Authored-By: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- windows/deployment/deploy-enterprise-licenses.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/deploy-enterprise-licenses.md b/windows/deployment/deploy-enterprise-licenses.md index fd04ba220b..c202b6f22e 100644 --- a/windows/deployment/deploy-enterprise-licenses.md +++ b/windows/deployment/deploy-enterprise-licenses.md @@ -159,7 +159,7 @@ Now the device is Azure AD joined to the company’s subscription. ### Step 2: Pro edition activation >[!IMPORTANT] ->If your device is running Windows 10, version 1803 or later, this step not needed. Starting with Windows 10 version 1803 the device will automatically activate Windows 10 Enterprise using the firmware-embedded activation key. +>If your device is running Windows 10, version 1803 or later, this step is not needed. From Windows 10, version 1803, the device will automatically activate Windows 10 Enterprise using the firmware-embedded activation key. >If the device is running Windows 10, version 1703 or 1709, then Windows 10 Pro must be successfully activated in **Settings > Update & Security > Activation**, as illustrated in **Figure 7a**. From cbf9fa503667e7e718f929b9f7f255cbcd8350bf Mon Sep 17 00:00:00 2001 From: Justin Hall Date: Mon, 13 May 2019 14:54:28 -0700 Subject: [PATCH 52/67] added caveat about excluded apps --- .../customize-attack-surface-reduction.md | 16 +++++++--------- ...customize-controlled-folders-exploit-guard.md | 9 +++++---- .../enable-attack-surface-reduction.md | 4 ++-- .../enable-controlled-folders-exploit-guard.md | 6 +++--- 4 files changed, 17 insertions(+), 18 deletions(-) diff --git a/windows/security/threat-protection/windows-defender-exploit-guard/customize-attack-surface-reduction.md b/windows/security/threat-protection/windows-defender-exploit-guard/customize-attack-surface-reduction.md index 6dbb17c57d..fe9741366e 100644 --- a/windows/security/threat-protection/windows-defender-exploit-guard/customize-attack-surface-reduction.md +++ b/windows/security/threat-protection/windows-defender-exploit-guard/customize-attack-surface-reduction.md @@ -11,7 +11,7 @@ ms.pagetype: security ms.localizationpriority: medium author: andreabichsel ms.author: v-anbic -ms.date: 05/08/2019 +ms.date: 05/13/2019 --- # Customize attack surface reduction rules @@ -31,20 +31,18 @@ You can use Group Policy, PowerShell, and MDM CSPs to configure these settings. ## Exclude files and folders -You can exclude files and folders from being evaluated by all attack surface reduction rules. This means that even if the file or folder contains malicious behavior as determined by an attack surface reduction rule, the file will not be blocked from running. - -This could potentially allow unsafe files to run and infect your devices. +You can exclude files and folders from being evaluated by attack surface reduction rules. This means that even if an attack surface reduction rule detects that the file contains malicious behavior, the file will not be blocked from running. >[!WARNING] ->Excluding files or folders can severely reduce the protection provided by attack surface reduction rules. Files that would have been blocked by a rule will be allowed to run, and there will be no report or event recorded. -> ->If you are encountering problems with rules detecting files that you believe should not be detected, you should [use audit mode first to test the rule](evaluate-attack-surface-reduction.md). +>This could potentially allow unsafe files to run and infect your devices. Excluding files or folders can severely reduce the protection provided by attack surface reduction rules. Files that would have been blocked by a rule will be allowed to run, and there will be no report or event recorded. -You can specify individual files or folders (using folder paths or fully qualified resource names) but you cannot specify if the exclusions should only be applied to individual rules: the exclusions will apply to all rules that are enabled (or placed in audit mode) and that allow exclusions. +An exclusion applies to all rules that allow exclusions. You can specify an individual file, folder path, or the fully qualified domain name for a resource, but you cannot limit an exclusion to certain rules. + +An exclusion is applied only when when the excluded application or service starts. For example, if you add an exclusion for an update service that is already running, the update service will continue to trigger events until the service is stopped and restarted. Attack surface reduction supports environment variables and wildcards. For information about using wildcards, see [Use wildcards in the file name and folder path or extension exclusion lists](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/configure-extension-file-exclusions-windows-defender-antivirus#use-wildcards-in-the-file-name-and-folder-path-or-extension-exclusion-lists). +If you are encountering problems with rules detecting files that you believe should not be detected, you should [use audit mode first to test the rule](evaluate-attack-surface-reduction.md). -Exclusions apply to all attack surface reduction rules. Rule description | GUID -|:-:|- diff --git a/windows/security/threat-protection/windows-defender-exploit-guard/customize-controlled-folders-exploit-guard.md b/windows/security/threat-protection/windows-defender-exploit-guard/customize-controlled-folders-exploit-guard.md index bf18867655..deed0e6c2e 100644 --- a/windows/security/threat-protection/windows-defender-exploit-guard/customize-controlled-folders-exploit-guard.md +++ b/windows/security/threat-protection/windows-defender-exploit-guard/customize-controlled-folders-exploit-guard.md @@ -11,7 +11,7 @@ ms.pagetype: security ms.localizationpriority: medium author: andreabichsel ms.author: v-anbic -ms.date: 05/07/2019 +ms.date: 05/13/2019 --- # Customize controlled folder access @@ -89,13 +89,14 @@ Use the [./Vendor/MSFT/Policy/Config/Defender/GuardedFoldersList](https://docs.m You can specify if certain apps should always be considered safe and given write access to files in protected folders. Allowing apps can be useful if you're finding a particular app that you know and trust is being blocked by the controlled folder access feature. >[!IMPORTANT] ->By default, Windows adds apps that it considers friendly to the allowed list - apps added automatically by Windows are not recorded in the list shown in the Windows Security app or by using the associated PowerShell cmdlets. +>By default, Windows adds apps that it considers friendly to the allowed list—apps added automatically by Windows are not recorded in the list shown in the Windows Security app or by using the associated PowerShell cmdlets. >You shouldn't need to add most apps. Only add apps if they are being blocked and you can verify their trustworthiness. -You can use the Windows Security app or Group Policy to add and remove apps that should be allowed to access protected folders. - When you add an app, you have to specify the app's location. Only the app in that location will be permitted access to the protected folders - if the app (with the same name) is located in a different location, then it will not be added to the allow list and may be blocked by controlled folder access. +An allowed application or service only has write access to a controlled flder after it starts. For example, if you allow an update service that is already running, the update service will continue to trigger events until the service is stopped and restarted. + + ### Use the Windows Defender Security app to allow specific apps 1. Open the Windows Security by clicking the shield icon in the task bar or searching the start menu for **Defender**. diff --git a/windows/security/threat-protection/windows-defender-exploit-guard/enable-attack-surface-reduction.md b/windows/security/threat-protection/windows-defender-exploit-guard/enable-attack-surface-reduction.md index 1a68651c4f..3b305feed9 100644 --- a/windows/security/threat-protection/windows-defender-exploit-guard/enable-attack-surface-reduction.md +++ b/windows/security/threat-protection/windows-defender-exploit-guard/enable-attack-surface-reduction.md @@ -11,7 +11,7 @@ ms.pagetype: security ms.localizationpriority: medium author: andreabichsel ms.author: v-anbic -ms.date: 04/29/2019 +ms.date: 05/13/2019 --- # Enable attack surface reduction rules @@ -51,7 +51,7 @@ You can exclude files and folders from being evaluated by most attack surface re >- Block process creations originating from PSExec and WMI commands >- Block JavaScript or VBScript from launching downloaded executable content -You can specify individual files or folders (using folder paths or fully qualified resource names) but you can't specify which rules the exclusions apply to. +You can specify individual files or folders (using folder paths or fully qualified resource names) but you can't specify which rules the exclusions apply to. An exclusion is applied only when when the excluded application or service starts. For example, if you add an exclusion for an update service that is already running, the update service will continue to trigger events until the service is stopped and restarted. ASR rules support environment variables and wildcards. For information about using wildcards, see [Use wildcards in the file name and folder path or extension exclusion lists](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/configure-extension-file-exclusions-windows-defender-antivirus#use-wildcards-in-the-file-name-and-folder-path-or-extension-exclusion-lists). diff --git a/windows/security/threat-protection/windows-defender-exploit-guard/enable-controlled-folders-exploit-guard.md b/windows/security/threat-protection/windows-defender-exploit-guard/enable-controlled-folders-exploit-guard.md index d761ebfc85..f6e6986c98 100644 --- a/windows/security/threat-protection/windows-defender-exploit-guard/enable-controlled-folders-exploit-guard.md +++ b/windows/security/threat-protection/windows-defender-exploit-guard/enable-controlled-folders-exploit-guard.md @@ -11,7 +11,7 @@ ms.pagetype: security ms.localizationpriority: medium author: andreabichsel ms.author: v-anbic -ms.date: 04/29/2019 +ms.date: 05/13/2019 --- # Enable controlled folder access @@ -61,7 +61,7 @@ For more information about disabling local list merging, see [Prevent or allow u 1. Type the path to each application that has access to protected folders and the path to any additional folder that needs protection and click **Add**. ![Enable controlled folder access in Intune](images/enable-cfa-intune.png) >[!NOTE] - >Wilcard is supported for applications, but not for folders. Subfolders are not protected. + >Wilcard is supported for applications, but not for folders. Subfolders are not protected. Allowed apps will continue to trigger events until they are restarted. 1. Click **OK** to save each open blade and click **Create**. 1. Click the profile **Assignments**, assign to **All Users & All Devices**, and click **Save**. @@ -76,7 +76,7 @@ Use the [./Vendor/MSFT/Policy/Config/ControlledFolderAccessProtectedFolders](htt 1. Enter a name and a description, click **Controlled folder access**, and click **Next**. 1. Choose whether block or audit changes, allow other apps, or add other folders, and click **Next**. >[!NOTE] - >Wilcard is supported for applications, but not for folders. Subfolders are not protected. + >Wilcard is supported for applications, but not for folders. Subfolders are not protected. Allowed apps will continue to trigger events until they are restarted. 1. Review the settings and click **Next** to create the policy. 1. After the policy is created, click **Close**. From ddddfbbf4d4a8080cdf8e9cb625dd020253d2917 Mon Sep 17 00:00:00 2001 From: Justin Hall Date: Mon, 13 May 2019 15:16:26 -0700 Subject: [PATCH 53/67] edits --- .../customize-attack-surface-reduction.md | 4 ++-- .../customize-controlled-folders-exploit-guard.md | 6 +++--- .../enable-attack-surface-reduction.md | 4 ++-- .../enable-controlled-folders-exploit-guard.md | 4 ++-- .../enable-exploit-protection.md | 2 +- .../enable-network-protection.md | 3 ++- 6 files changed, 12 insertions(+), 11 deletions(-) diff --git a/windows/security/threat-protection/windows-defender-exploit-guard/customize-attack-surface-reduction.md b/windows/security/threat-protection/windows-defender-exploit-guard/customize-attack-surface-reduction.md index fe9741366e..20e1ca5eda 100644 --- a/windows/security/threat-protection/windows-defender-exploit-guard/customize-attack-surface-reduction.md +++ b/windows/security/threat-protection/windows-defender-exploit-guard/customize-attack-surface-reduction.md @@ -74,9 +74,9 @@ See the [attack surface reduction](attack-surface-reduction-exploit-guard.md) to 4. Double-click the **Exclude files and paths from Attack surface reduction Rules** setting and set the option to **Enabled**. Click **Show** and enter each file or folder in the **Value name** column. Enter **0** in the **Value** column for each item. -### Use PowerShell to exclude files and folderss +### Use PowerShell to exclude files and folders -1. Type **powershell** in the Start menu, right click **Windows PowerShell** and click **Run as administrator** +1. Type **powershell** in the Start menu, right-click **Windows PowerShell** and click **Run as administrator** 2. Enter the following cmdlet: ```PowerShell diff --git a/windows/security/threat-protection/windows-defender-exploit-guard/customize-controlled-folders-exploit-guard.md b/windows/security/threat-protection/windows-defender-exploit-guard/customize-controlled-folders-exploit-guard.md index deed0e6c2e..28a78453b2 100644 --- a/windows/security/threat-protection/windows-defender-exploit-guard/customize-controlled-folders-exploit-guard.md +++ b/windows/security/threat-protection/windows-defender-exploit-guard/customize-controlled-folders-exploit-guard.md @@ -94,7 +94,7 @@ You can specify if certain apps should always be considered safe and given write When you add an app, you have to specify the app's location. Only the app in that location will be permitted access to the protected folders - if the app (with the same name) is located in a different location, then it will not be added to the allow list and may be blocked by controlled folder access. -An allowed application or service only has write access to a controlled flder after it starts. For example, if you allow an update service that is already running, the update service will continue to trigger events until the service is stopped and restarted. +An allowed application or service only has write access to a controlled folder after it starts. For example, if you allow an update service that is already running, the update service will continue to trigger events until the service is stopped and restarted. ### Use the Windows Defender Security app to allow specific apps @@ -107,7 +107,7 @@ An allowed application or service only has write access to a controlled flder af 4. Click **Add an allowed app** and follow the prompts to add apps. - ![Screenshot of the add an allowed app button](images/cfa-allow-app.png) + ![Screenshot of how to add an allowed app button](images/cfa-allow-app.png) ### Use Group Policy to allow specific apps @@ -121,7 +121,7 @@ An allowed application or service only has write access to a controlled flder af ### Use PowerShell to allow specific apps -1. Type **powershell** in the Start menu, right click **Windows PowerShell** and click **Run as administrator** +1. Type **powershell** in the Start menu, right-click **Windows PowerShell** and click **Run as administrator** 2. Enter the following cmdlet: ```PowerShell diff --git a/windows/security/threat-protection/windows-defender-exploit-guard/enable-attack-surface-reduction.md b/windows/security/threat-protection/windows-defender-exploit-guard/enable-attack-surface-reduction.md index 3b305feed9..57d6a0abd8 100644 --- a/windows/security/threat-protection/windows-defender-exploit-guard/enable-attack-surface-reduction.md +++ b/windows/security/threat-protection/windows-defender-exploit-guard/enable-attack-surface-reduction.md @@ -26,7 +26,7 @@ Each ASR rule contains three settings: To use ASR rules, you need either a Windows 10 Enterprise E3 or E5 license. We recommend an E5 license so you can take advantage of the advanced monitoring and reporting capabilities available in Windows Defender Advanced Threat Protection (Windows Defender ATP). These advanced capabilities aren't available with an E3 license, but you can develop your own monitoring and reporting tools to use in conjunction with ASR rules. -You can enable attack surface reduction rules by using any of the these methods: +You can enable attack surface reduction rules by using any of these methods: - [Microsoft Intune](#intune) - [Mobile Device Management (MDM)](#mdm) @@ -131,7 +131,7 @@ Value: c:\path|e:\path|c:\Whitelisted.exe >[!WARNING] >If you manage your computers and devices with Intune, SCCM, or other enterprise-level management platform, the management software will overwrite any conflicting PowerShell settings on startup. -1. Type **powershell** in the Start menu, right click **Windows PowerShell** and click **Run as administrator**. +1. Type **powershell** in the Start menu, right-click **Windows PowerShell** and click **Run as administrator**. 2. Enter the following cmdlet: diff --git a/windows/security/threat-protection/windows-defender-exploit-guard/enable-controlled-folders-exploit-guard.md b/windows/security/threat-protection/windows-defender-exploit-guard/enable-controlled-folders-exploit-guard.md index f6e6986c98..0f4dcde83d 100644 --- a/windows/security/threat-protection/windows-defender-exploit-guard/enable-controlled-folders-exploit-guard.md +++ b/windows/security/threat-protection/windows-defender-exploit-guard/enable-controlled-folders-exploit-guard.md @@ -22,7 +22,7 @@ ms.date: 05/13/2019 [Controlled folder access](controlled-folders-exploit-guard.md) helps you protect valuable data from malicious apps and threats, such as ransomware. It is part of [Windows Defender Exploit Guard](windows-defender-exploit-guard.md). Controlled folder access is included with Windows 10 and Windows Server 2019. -You can enable controlled folder access by using any of the these methods: +You can enable controlled folder access by using any of these methods: - [Windows Security app](#windows-security-app) - [Microsoft Intune](#intune) @@ -100,7 +100,7 @@ Use the [./Vendor/MSFT/Policy/Config/ControlledFolderAccessProtectedFolders](htt ## PowerShell -1. Type **powershell** in the Start menu, right click **Windows PowerShell** and click **Run as administrator**. +1. Type **powershell** in the Start menu, right-click **Windows PowerShell** and click **Run as administrator**. 2. Enter the following cmdlet: diff --git a/windows/security/threat-protection/windows-defender-exploit-guard/enable-exploit-protection.md b/windows/security/threat-protection/windows-defender-exploit-guard/enable-exploit-protection.md index 58cb4ad00c..56932bf8a1 100644 --- a/windows/security/threat-protection/windows-defender-exploit-guard/enable-exploit-protection.md +++ b/windows/security/threat-protection/windows-defender-exploit-guard/enable-exploit-protection.md @@ -26,7 +26,7 @@ Many features from the Enhanced Mitigation Experience Toolkit (EMET) are include You can also set mitigations to [audit mode](evaluate-exploit-protection.md). Audit mode allows you to test how the mitigations would work (and review events) without impacting the normal use of the machine. -You can enable each mitigation separately by using any of the these methods: +You can enable each mitigation separately by using any of these methods: - [Windows Security app](#windows-security-app) - [Microsoft Intune](#intune) diff --git a/windows/security/threat-protection/windows-defender-exploit-guard/enable-network-protection.md b/windows/security/threat-protection/windows-defender-exploit-guard/enable-network-protection.md index 8df4d37da6..75c4d76f00 100644 --- a/windows/security/threat-protection/windows-defender-exploit-guard/enable-network-protection.md +++ b/windows/security/threat-protection/windows-defender-exploit-guard/enable-network-protection.md @@ -22,7 +22,8 @@ ms.date: 04/22/2019 [Network protection](network-protection-exploit-guard.md) helps to prevent employees from using any application to access dangerous domains that may host phishing scams, exploits, and other malicious content on the Internet. You can [audit network protection](evaluate-network-protection.md) in a test environment to see which apps would be blocked before you enable it. -You can enable network protection by using any of the these methods: + +You can enable network protection by using any of these methods: - [Microsoft Intune](#intune) - [Mobile Device Management (MDM)](#mdm) From 4a8b2dc1f690a7f0edfce207b4608dd30d5de124 Mon Sep 17 00:00:00 2001 From: Justin Hall Date: Mon, 13 May 2019 15:17:29 -0700 Subject: [PATCH 54/67] edits --- .../enable-network-protection.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/windows-defender-exploit-guard/enable-network-protection.md b/windows/security/threat-protection/windows-defender-exploit-guard/enable-network-protection.md index 75c4d76f00..a3cad38060 100644 --- a/windows/security/threat-protection/windows-defender-exploit-guard/enable-network-protection.md +++ b/windows/security/threat-protection/windows-defender-exploit-guard/enable-network-protection.md @@ -11,7 +11,7 @@ ms.pagetype: security ms.localizationpriority: medium author: andreabichsel ms.author: v-anbic -ms.date: 04/22/2019 +ms.date: 05/13/2019 --- # Enable network protection @@ -88,7 +88,7 @@ You can confirm network protection is enabled on a local computer by using Regis ## PowerShell -1. Type **powershell** in the Start menu, right click **Windows PowerShell** and click **Run as administrator** +1. Type **powershell** in the Start menu, right-click **Windows PowerShell** and click **Run as administrator** 2. Enter the following cmdlet: ``` From 5dc8cb6c1852377314ebaac4ae1f4e8b1db9afa5 Mon Sep 17 00:00:00 2001 From: Jose Gabriel Ortega Castro Date: Mon, 13 May 2019 20:36:14 -0500 Subject: [PATCH 55/67] Update windows/deployment/deploy-enterprise-licenses.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/deployment/deploy-enterprise-licenses.md | 1 - 1 file changed, 1 deletion(-) diff --git a/windows/deployment/deploy-enterprise-licenses.md b/windows/deployment/deploy-enterprise-licenses.md index c202b6f22e..353bb97445 100644 --- a/windows/deployment/deploy-enterprise-licenses.md +++ b/windows/deployment/deploy-enterprise-licenses.md @@ -13,7 +13,6 @@ ms.topic: article --- - # Deploy Windows 10 Enterprise licenses >[!IMPORTANT] From 6040e1162d7e9720e47d80be71d545ff288f0b50 Mon Sep 17 00:00:00 2001 From: Jose Gabriel Ortega Castro Date: Mon, 13 May 2019 20:36:22 -0500 Subject: [PATCH 56/67] Update windows/deployment/deploy-enterprise-licenses.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/deployment/deploy-enterprise-licenses.md | 1 - 1 file changed, 1 deletion(-) diff --git a/windows/deployment/deploy-enterprise-licenses.md b/windows/deployment/deploy-enterprise-licenses.md index 353bb97445..1c21ee3718 100644 --- a/windows/deployment/deploy-enterprise-licenses.md +++ b/windows/deployment/deploy-enterprise-licenses.md @@ -224,7 +224,6 @@ Use the following figures to help you troubleshoot when users experience these c **Figure 10 - Windows 10 Pro, version 1703 edition not activated in Settings** - Windows 10 activated and subscription not active **Figure 11 - Windows 10 Enterprise subscription lapsed or removed in Settings** From 528382e2207c4d93ef968cce2d6fbc579998ec64 Mon Sep 17 00:00:00 2001 From: Jose Gabriel Ortega Castro Date: Mon, 13 May 2019 20:36:31 -0500 Subject: [PATCH 57/67] Update windows/deployment/deploy-enterprise-licenses.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/deployment/deploy-enterprise-licenses.md | 1 - 1 file changed, 1 deletion(-) diff --git a/windows/deployment/deploy-enterprise-licenses.md b/windows/deployment/deploy-enterprise-licenses.md index 1c21ee3718..f2bf17ad13 100644 --- a/windows/deployment/deploy-enterprise-licenses.md +++ b/windows/deployment/deploy-enterprise-licenses.md @@ -229,7 +229,6 @@ Use the following figures to help you troubleshoot when users experience these c **Figure 11 - Windows 10 Enterprise subscription lapsed or removed in Settings** - Windows 10 not activated and subscription not active **Figure 12 - Windows 10 Pro, version 1703 edition not activated and Windows 10 Enterprise subscription lapsed or removed in Settings** From de56796a975c25c688fc74917111f6b3b1c795d7 Mon Sep 17 00:00:00 2001 From: Jose Gabriel Ortega Castro Date: Mon, 13 May 2019 21:28:02 -0500 Subject: [PATCH 58/67] Update windows/deployment/deploy-enterprise-licenses.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/deployment/deploy-enterprise-licenses.md | 1 - 1 file changed, 1 deletion(-) diff --git a/windows/deployment/deploy-enterprise-licenses.md b/windows/deployment/deploy-enterprise-licenses.md index f2bf17ad13..25a638d45a 100644 --- a/windows/deployment/deploy-enterprise-licenses.md +++ b/windows/deployment/deploy-enterprise-licenses.md @@ -12,7 +12,6 @@ author: greg-lindsay ms.topic: article --- - # Deploy Windows 10 Enterprise licenses >[!IMPORTANT] From c9e0b1d57e0067291f01e82ca694727663379631 Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Tue, 14 May 2019 11:13:08 +0500 Subject: [PATCH 59/67] update windows-upgrade-and-migration-considerations.md --- .../upgrade/windows-upgrade-and-migration-considerations.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/windows/deployment/upgrade/windows-upgrade-and-migration-considerations.md b/windows/deployment/upgrade/windows-upgrade-and-migration-considerations.md index d5eff8daa4..b2bade848b 100644 --- a/windows/deployment/upgrade/windows-upgrade-and-migration-considerations.md +++ b/windows/deployment/upgrade/windows-upgrade-and-migration-considerations.md @@ -28,6 +28,9 @@ Windows Easy Transfer is a software wizard for transferring files and settings With Windows Easy Transfer, files and settings can be transferred using a network share, a USB flash drive (UFD), or the Easy Transfer cable. However, you cannot use a regular universal serial bus (USB) cable to transfer files and settings with Windows Easy Transfer. An Easy Transfer cable can be purchased on the Web, from your computer manufacturer, or at an electronics store. +> [!NOTE] +> Windows Easy Transfer [is not available in Windows 10](https://support.microsoft.com/help/4026265/windows-windows-easy-transfer-is-not-available-in-windows-10). + ### Migrate with the User State Migration Tool You can use USMT to automate migration during large deployments of the Windows operating system. USMT uses configurable migration rule (.xml) files to control exactly which user accounts, user files, operating system settings, and application settings are migrated and how they are migrated. You can use USMT for both *side-by-side* migrations, where one piece of hardware is being replaced, or *wipe-and-load* (or *refresh*) migrations, when only the operating system is being upgraded. From e0e5aa64c2648a982296f756133a5912e01d4a09 Mon Sep 17 00:00:00 2001 From: Nicole Turner <39884432+nenonix@users.noreply.github.com> Date: Tue, 14 May 2019 13:25:19 +0200 Subject: [PATCH 60/67] Update waas-quick-start.md Link added under Learn More. Resolves https://github.com/MicrosoftDocs/windows-itpro-docs/issues/1576 --- windows/deployment/update/waas-quick-start.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/update/waas-quick-start.md b/windows/deployment/update/waas-quick-start.md index 9ef541fce2..af88e40987 100644 --- a/windows/deployment/update/waas-quick-start.md +++ b/windows/deployment/update/waas-quick-start.md @@ -69,8 +69,8 @@ Click the following Microsoft Mechanics video for an overview of the updated rel ## Learn more -[Adopting Windows as a service at Microsoft](https://www.microsoft.com/itshowcase/Article/Content/851/Adopting-Windows-as-a-service-at-Microsoft) - +- [Adopting Windows as a service at Microsoft](https://www.microsoft.com/itshowcase/Article/Content/851/Adopting-Windows-as-a-service-at-Microsoft) +- [Windows lifecycle fact sheet](https://support.microsoft.com/help/13853/windows-lifecycle-fact-sheet) ## Related topics From f066c23a3f08fe7488e8ba2a31922ea69343c763 Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Tue, 14 May 2019 11:14:34 -0700 Subject: [PATCH 61/67] Added preview mode info --- .../mdm/new-in-windows-mdm-enrollment-management.md | 8 ++++---- .../mdm/policy-configuration-service-provider.md | 4 ++-- .../client-management/mdm/policy-csp-authentication.md | 10 ++++++++-- 3 files changed, 14 insertions(+), 8 deletions(-) diff --git a/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md b/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md index b7d977b310..d652e7d5f2 100644 --- a/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md +++ b/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md @@ -1398,8 +1398,8 @@ For details about Microsoft mobile device management protocols for Windows 10 s
  • ApplicationManagement/LaunchAppAfterLogOn
  • ApplicationManagement/ScheduleForceRestartForUpdateFailures
    • -
  • Authentication/EnableFastFirstSignIn
    • -
  • Authentication/EnableWebSignIn
    • +
  • Authentication/EnableFastFirstSignIn (Preview mode only)
    • +
  • Authentication/EnableWebSignIn (Preview mode only)
  • Authentication/PreferredAadTenantDomainName
  • Browser/AllowFullScreenMode
  • Browser/AllowPrelaunch
    • @@ -1943,8 +1943,8 @@ The DM agent for [push-button reset](https://msdn.microsoft.com/windows/hardware
    • ApplicationManagement/LaunchAppAfterLogOn
    • ApplicationManagement/ScheduleForceRestartForUpdateFailures
      • -
    • Authentication/EnableFastFirstSignIn
      • -
    • Authentication/EnableWebSignIn
      • +
    • Authentication/EnableFastFirstSignIn (Preview mode only)
      • +
    • Authentication/EnableWebSignIn (Preview mode only)
    • Authentication/PreferredAadTenantDomainName
    • Defender/CheckForSignaturesBeforeRunningScan
    • Defender/DisableCatchupFullScan
      • diff --git a/windows/client-management/mdm/policy-configuration-service-provider.md b/windows/client-management/mdm/policy-configuration-service-provider.md index 91c6cd7f66..4dcc76c9fc 100644 --- a/windows/client-management/mdm/policy-configuration-service-provider.md +++ b/windows/client-management/mdm/policy-configuration-service-provider.md @@ -364,10 +364,10 @@ The following diagram shows the Policy configuration service provider in tree fo Authentication/AllowSecondaryAuthenticationDevice
      - Authentication/EnableFastFirstSignIn + Authentication/EnableFastFirstSignIn (Preview mode only)
      - Authentication/EnableWebSignIn + Authentication/EnableWebSignIn (Preview mode only)
      Authentication/PreferredAadTenantDomainName diff --git a/windows/client-management/mdm/policy-csp-authentication.md b/windows/client-management/mdm/policy-csp-authentication.md index 7708a220e7..89e6c6a809 100644 --- a/windows/client-management/mdm/policy-csp-authentication.md +++ b/windows/client-management/mdm/policy-csp-authentication.md @@ -354,6 +354,9 @@ The following list shows the supported values: +> [!Warning] +> This is policy is in preview mode and therefore not meant or recommended for production purposes. + This policy is intended for use on Shared PCs to enable a quick first sign-in experience for a user. It works by automatically connecting new non-admin Azure Active Directory (Azure AD) accounts to the pre-configured candidate local accounts. Value type is integer. Supported values: @@ -412,9 +415,12 @@ Value type is integer. Supported values: +> [!Warning] +> This is policy is in preview mode and therefore not meant or recommended for production purposes. + "Web Sign-in" is a new way of signing into a Windows PC. It enables Windows logon support for non-ADFS federated providers (e.g. SAML). -> [!Note] +> [!Note] > Web Sign-in is only supported on Azure AD Joined PCs. Value type is integer. Supported values: @@ -514,4 +520,4 @@ Footnotes: - 3 - Added in Windows 10, version 1709. - 4 - Added in Windows 10, version 1803. - 5 - Added in Windows 10, version 1809. -- 6 - Added in the next major release of Windows 10. \ No newline at end of file +- 6 - Added in Windows 10, version 1903. \ No newline at end of file From 2c927d925b48bdd57f6af159e41773d0e4b08c41 Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Tue, 14 May 2019 11:29:02 -0700 Subject: [PATCH 62/67] minor update --- windows/client-management/mdm/policy-csp-authentication.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/client-management/mdm/policy-csp-authentication.md b/windows/client-management/mdm/policy-csp-authentication.md index 89e6c6a809..58790db16d 100644 --- a/windows/client-management/mdm/policy-csp-authentication.md +++ b/windows/client-management/mdm/policy-csp-authentication.md @@ -355,7 +355,7 @@ The following list shows the supported values: > [!Warning] -> This is policy is in preview mode and therefore not meant or recommended for production purposes. +> This policy is only in preview mode and therefore not meant or recommended for production purposes. This policy is intended for use on Shared PCs to enable a quick first sign-in experience for a user. It works by automatically connecting new non-admin Azure Active Directory (Azure AD) accounts to the pre-configured candidate local accounts. @@ -416,7 +416,7 @@ Value type is integer. Supported values: > [!Warning] -> This is policy is in preview mode and therefore not meant or recommended for production purposes. +> This policy is only in preview mode and therefore not meant or recommended for production purposes. "Web Sign-in" is a new way of signing into a Windows PC. It enables Windows logon support for non-ADFS federated providers (e.g. SAML). From a576583cdafdca9dddee1a34a8862aa10fc47dbf Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 14 May 2019 11:51:00 -0700 Subject: [PATCH 63/67] fix link errors --- .../update/waas-delivery-optimization-reference.md | 10 +++++----- .../deployment/update/waas-delivery-optimization.md | 4 ++-- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/windows/deployment/update/waas-delivery-optimization-reference.md b/windows/deployment/update/waas-delivery-optimization-reference.md index 57bdd0311c..7fbacf8aee 100644 --- a/windows/deployment/update/waas-delivery-optimization-reference.md +++ b/windows/deployment/update/waas-delivery-optimization-reference.md @@ -5,9 +5,9 @@ keywords: oms, operations management suite, wdav, updates, downloads, log analyt ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library -author: JaimeO +author: greg-lindsay ms.localizationpriority: medium -ms.author: jaimeo +ms.author: greglin ms.collection: M365-modern-desktop ms.topic: article --- @@ -37,7 +37,7 @@ In MDM, the same settings are under **.Vendor/MSFT/Policy/Config/DeliveryOptimiz | --- | --- | --- | | [Download mode](#download-mode) | DODownloadMode | 1511 | | [Group ID](#group-id) | DOGroupID | 1511 | -| [Minimum RAM (inclusive) allowed to use Peer Caching](#minimum-ram-allowed-to-use-peer-caching) | DOMinRAMAllowedToPeer | 1703 | +| [Minimum RAM (inclusive) allowed to use Peer Caching](#minimum-ram-inclusive-allowed-to-use-peer-caching) | DOMinRAMAllowedToPeer | 1703 | | [Minimum disk size allowed to use Peer Caching](#minimum-disk-size-allowed-to-use-peer-caching) | DOMinDiskSizeAllowedToPeer | 1703 | | [Max Cache Age](#max-cache-age) | DOMaxCacheAge | 1511 | | [Max Cache Size](#max-cache-size) | DOMaxCacheSize | 1511 | @@ -70,7 +70,7 @@ Delivery Optimization uses locally cached updates. In cases where devices have a - The system drive is the default location for the Delivery Optimization cache. [Modify Cache Drive](#modify-cache-drive) allows administrators to change that location. >[!NOTE] ->It is possible to configure preferred cache devices. For more information, see [Set “preferred” cache devices for Delivery Optimization](#set-preferred-cache-devices). +>It is possible to configure preferred cache devices. For more information, see [Group ID](#group-id). All cached files have to be above a set minimum size. This size is automatically set by the Delivery Optimization cloud services, but when local storage is sufficient and the network isn't strained or congested, administrators might choose to change it to obtain increased performance. You can set the minimum size of files to cache by adjusting [Minimum Peer Caching Content File Size](#minimum-peer-caching-content-file-size). @@ -89,7 +89,7 @@ Additional options available that control the impact Delivery Optimization has o - [Delay foreground download from http (in secs)](#delay-foreground-download-from-http-in-secs) allows you to delay the use of an HTTP source in a foreground (interactive) download that is allowed to use P2P. Administrators can further customize scenarios where Delivery Optimization will be used with the following settings: -- [Minimum RAM (inclusive) allowed to use Peer Caching](#minimum-ram-allowed-to-use-peer-caching) sets the minimum RAM required for peer caching to be enabled. +- [Minimum RAM (inclusive) allowed to use Peer Caching](#minimum-ram-inclusive-allowed-to-use-peer-caching) sets the minimum RAM required for peer caching to be enabled. - [Minimum disk size allowed to use Peer Caching](#minimum-disk-size-allowed-to-use-peer-caching) sets the minimum disk size required for peer caching to be enabled. - [Enable Peer Caching while the device connects via VPN](#enable-peer-caching-while-the-device-connects-via-vpn) allows clients connected through VPN to use peer caching. - [Allow uploads while the device is on battery while under set Battery level](#allow-uploads-while-the-device-is-on-battery-while-under-set-battery-level) controls the minimum battery level required for uploads to occur. You must enable this policy to allow upload while on battery. diff --git a/windows/deployment/update/waas-delivery-optimization.md b/windows/deployment/update/waas-delivery-optimization.md index 1c13688e4e..178f964ce4 100644 --- a/windows/deployment/update/waas-delivery-optimization.md +++ b/windows/deployment/update/waas-delivery-optimization.md @@ -5,9 +5,9 @@ keywords: oms, operations management suite, wdav, updates, downloads, log analyt ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library -author: JaimeO +author: greg-lindsay ms.localizationpriority: medium -ms.author: jaimeo +ms.author: greglin ms.collection: M365-modern-desktop ms.topic: article --- From e4d3a2642cb7501a337cd4c3996569574335b741 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 14 May 2019 11:53:41 -0700 Subject: [PATCH 64/67] fix link errors --- .../windows-autopilot/windows-autopilot-reset-local.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/windows-autopilot/windows-autopilot-reset-local.md b/windows/deployment/windows-autopilot/windows-autopilot-reset-local.md index c94be655bb..c6b59a7df4 100644 --- a/windows/deployment/windows-autopilot/windows-autopilot-reset-local.md +++ b/windows/deployment/windows-autopilot/windows-autopilot-reset-local.md @@ -25,8 +25,8 @@ IT admins can perform a local Windows Autopilot Reset to quickly remove personal To enable local Autopilot Reset in Windows 10: -1. [Enable the policy for the feature](#enable-autopilot-reset) -2. [Trigger a reset for each device](#trigger-autopilot-reset) +1. [Enable the policy for the feature](#enable-local-autopilot-reset) +2. [Trigger a reset for each device](#trigger-local-autopilot-reset) ## Enable local Windows Autopilot Reset From 0cb8608ce75b22e80c3102665760d741ed47b9ae Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 14 May 2019 12:03:37 -0700 Subject: [PATCH 65/67] fix link errors --- .../hello-for-business/hello-cert-trust-deploy-mfa.md | 6 +++--- .../hello-for-business/hello-hybrid-cert-new-install.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-cert-trust-deploy-mfa.md b/windows/security/identity-protection/hello-for-business/hello-cert-trust-deploy-mfa.md index 3c90a6c465..cc631cea1a 100644 --- a/windows/security/identity-protection/hello-for-business/hello-cert-trust-deploy-mfa.md +++ b/windows/security/identity-protection/hello-for-business/hello-cert-trust-deploy-mfa.md @@ -80,7 +80,7 @@ The following services are required: Update the server using Windows Update until the server has no required or optional updates as the Azure MFA Server software may require one or more of these updates for the installation and software to correctly work. These procedures install additional components that may need to be updated. -#### Configure the IIS Server’s Certificate +#### Configure the IIS Server Certificate The TLS protocol protects all the communication to and from the MFA server. To enable this protection, you must configure the default web site to use the previously enrolled server authentication certificate. @@ -171,9 +171,9 @@ To do this, please follow the instructions mentioned in the previous [Install th Update the server using Windows Update until the server has no required or optional updates as the Azure MFA Server software may require one or more of these updates for the installation and software to correctly work. These procedures install additional components that may need to be updated. -#### Configure the IIS Server’s Certificate +#### Set the IIS Server Certificate -To do this, please follow the instructions mentioned in the previous [Configure the IIS Server’s Certificate](#configure-the-iis-server’s-certificate) section. +To do this, please follow the instructions mentioned in the previous [Configure the IIS Server’s Certificate](#configure-the-iis-server-certificate) section. #### Create WebServices SDK user account diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-new-install.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-new-install.md index 81a325489b..a1981cd9c2 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-new-install.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-new-install.md @@ -28,7 +28,7 @@ Windows Hello for Business involves configuring distributed technologies that ma * [Active Directory](#active-directory) * [Public Key Infrastructure](#public-key-infrastructure) * [Azure Active Directory](#azure-active-directory) -* [Multi-factor Authentication Services](#multi-factor-authentication-services) +* [Multifactor Authentication Services](#multifactor-authentication-services) New installations are considerably more involved than existing implementations because you are building the entire infrastructure. Microsoft recommends you review the new installation baseline to validate your existing environment has all the needed configurations to support your hybrid certificate trust Windows Hello for Business deployment. If your environment meets these needs, you can read the [Configure Azure Device Registration](hello-hybrid-cert-trust-devreg.md) section to prepare your Windows Hello for Business deployment by configuring Azure device registration. From 38dbc683bb88791ab520dcbed5aef8f3e322f689 Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Tue, 14 May 2019 15:10:58 -0700 Subject: [PATCH 66/67] Incorporated dev feedback --- windows/client-management/mdm/policy-csp-experience.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/client-management/mdm/policy-csp-experience.md b/windows/client-management/mdm/policy-csp-experience.md index cbc286da97..4db9f3f778 100644 --- a/windows/client-management/mdm/policy-csp-experience.md +++ b/windows/client-management/mdm/policy-csp-experience.md @@ -6,7 +6,7 @@ ms.topic: article ms.prod: w10 ms.technology: windows author: MariciaAlforque -ms.date: 05/01/2019 +ms.date: 05/14/2019 --- # Policy CSP - Experience @@ -1629,8 +1629,8 @@ ADMX Info: Supported values: -- false (default) - The lock option is not displayed in the User Tile menu. -- true - The lock option is displayed in the User Tile menu. +- false - The lock option is not displayed in the User Tile menu. +- true (default) - The lock option is displayed in the User Tile menu. @@ -1664,4 +1664,4 @@ Footnotes: - 3 - Added in Windows 10, version 1709. - 4 - Added in Windows 10, version 1803. - 5 - Added in Windows 10, version 1809. -- 6 - Added in the next major release of Windows 10. \ No newline at end of file +- 6 - Added in Windows 10, version 1903. \ No newline at end of file From e9f610c05bbd524afccbcc44af408068d290a7fa Mon Sep 17 00:00:00 2001 From: DocsPreview <49669258+DocsPreview@users.noreply.github.com> Date: Tue, 14 May 2019 16:02:25 -0700 Subject: [PATCH 67/67] Release info preview (#183) * Latest changes for 1809 issues * New Announcement Added * Latest Change for announcement * Updated link for japanese era content * Made some change in Announcement. * Latest changes done for few issues * Added new line to one of message * New Issue added to known issues of 1809 product version --- .../resolved-issues-windows-10-1607.yml | 20 ++++++++++++++++ .../resolved-issues-windows-10-1703.yml | 10 ++++++++ .../resolved-issues-windows-10-1709.yml | 20 ++++++++++++++++ .../resolved-issues-windows-10-1803.yml | 20 ++++++++++++++++ ...indows-10-1809-and-windows-server-2019.yml | 4 ++++ ...ndows-7-and-windows-server-2008-r2-sp1.yml | 18 ++++++++++++++ ...windows-8.1-and-windows-server-2012-r2.yml | 16 +++++++++++++ ...esolved-issues-windows-server-2008-sp2.yml | 24 +++++++++++++++++++ .../resolved-issues-windows-server-2012.yml | 22 +++++++++++++++++ ...indows-10-1607-and-windows-server-2016.yml | 8 +++---- .../status-windows-10-1703.yml | 4 ++-- .../status-windows-10-1709.yml | 8 +++---- .../status-windows-10-1803.yml | 8 +++---- ...indows-10-1809-and-windows-server-2019.yml | 8 +++++-- ...ndows-7-and-windows-server-2008-r2-sp1.yml | 20 ++++++++-------- ...windows-8.1-and-windows-server-2012-r2.yml | 16 ++++++------- .../status-windows-server-2008-sp2.yml | 22 ++++++++++++----- .../status-windows-server-2012.yml | 12 +++++----- .../windows-message-center.yml | 15 ++++++++++-- 19 files changed, 227 insertions(+), 48 deletions(-) diff --git a/windows/release-information/resolved-issues-windows-10-1607.yml b/windows/release-information/resolved-issues-windows-10-1607.yml index 72407b6ba9..046eea9c71 100644 --- a/windows/release-information/resolved-issues-windows-10-1607.yml +++ b/windows/release-information/resolved-issues-windows-10-1607.yml @@ -32,6 +32,8 @@ sections: - type: markdown text: " + + @@ -60,6 +62,24 @@ sections:
      " +- title: May 2019 +- items: + - type: markdown + text: " +
      SummaryOriginating updateStatusDate resolved
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail.

      See details >      		OS Build 14393.2941

      April 25, 2019
      KB4493473      		Resolved
      KB4494440      		May 14, 2019
      01:18 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		OS Build 14393.2941

      April 25, 2019
      KB4493473      		Resolved
      KB4494440      		May 14, 2019
      01:18 PM PT
      Custom URI schemes may not start corresponding application
      Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

      See details >      		OS Build 14393.2848

      March 12, 2019
      KB4489882      		Resolved
      KB4493473      		April 25, 2019
      02:00 PM PT
      End-user-defined characters (EUDC) may cause blue screen at startup
      If you enable per font end-user-defined characters (EUDC), the system will stop working and a blue screen may appear at startup.

      See details >      		OS Build 14393.2879

      March 19, 2019
      KB4489889      		Resolved
      KB4493470      		April 09, 2019
      10:00 AM PT
      Internet Explorer 11 authentication issue with multiple concurrent logons
      Internet Explorer 11 users may encounter issues if two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine.

      See details >      		OS Build 14393.2724

      January 08, 2019
      KB4480961      		Resolved
      KB4493470      		April 09, 2019
      10:00 AM PT
      + +
      DetailsOriginating updateStatusHistory
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Resolution: This issue has been resolved.

      Back to top      		OS Build 14393.2941

      April 25, 2019
      KB4493473      		Resolved
      KB4494440      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      + " + +- title: April 2019 +- items: + - type: markdown + text: " + + +
      DetailsOriginating updateStatusHistory
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail after installing KB4493473. 
       
      Affected platforms:  
      • Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016 
      • Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016 
      Resolution: This issue was resolved in KB4494440.

      Back to top      		OS Build 14393.2941

      April 25, 2019
      KB4493473      		Resolved
      KB4494440      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      April 25, 2019
      02:00 PM PT
      + " + - title: March 2019 - items: - type: markdown diff --git a/windows/release-information/resolved-issues-windows-10-1703.yml b/windows/release-information/resolved-issues-windows-10-1703.yml index a32bfe383c..6d20195ba0 100644 --- a/windows/release-information/resolved-issues-windows-10-1703.yml +++ b/windows/release-information/resolved-issues-windows-10-1703.yml @@ -32,6 +32,7 @@ sections: - type: markdown text: " + @@ -57,6 +58,15 @@ sections:
      " +- title: May 2019 +- items: + - type: markdown + text: " +
      SummaryOriginating updateStatusDate resolved
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		OS Build 15063.1784

      April 25, 2019
      KB4493436      		Resolved
      KB4499181      		May 14, 2019
      01:18 PM PT
      Custom URI schemes may not start corresponding application
      Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

      See details >      		OS Build 15063.1689

      March 12, 2019
      KB4489871      		Resolved
      KB4493436      		April 25, 2019
      02:00 PM PT
      End-user-defined characters (EUDC) may cause blue screen at startup
      If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup.

      See details >      		OS Build 15063.1716

      March 19, 2019
      KB4489888      		Resolved
      KB4493474      		April 09, 2019
      10:00 AM PT
      MSXML6 may cause applications to stop responding
      MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

      See details >      		OS Build 15063.1563

      January 08, 2019
      KB4480973      		Resolved
      KB4493474      		April 09, 2019
      10:00 AM PT
      + +
      DetailsOriginating updateStatusHistory
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Resolution: This issue has been resolved.

      Back to top      		OS Build 15063.1784

      April 25, 2019
      KB4493436      		Resolved
      KB4499181      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      + " + - title: March 2019 - items: - type: markdown diff --git a/windows/release-information/resolved-issues-windows-10-1709.yml b/windows/release-information/resolved-issues-windows-10-1709.yml index 2893c090ed..2d33536532 100644 --- a/windows/release-information/resolved-issues-windows-10-1709.yml +++ b/windows/release-information/resolved-issues-windows-10-1709.yml @@ -32,6 +32,8 @@ sections: - type: markdown text: " + + @@ -57,6 +59,24 @@ sections:
      " +- title: May 2019 +- items: + - type: markdown + text: " +
      SummaryOriginating updateStatusDate resolved
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail.

      See details >      		OS Build 16299.1127

      April 25, 2019
      KB4493440      		Resolved
      KB4499179      		May 14, 2019
      01:18 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		OS Build 16299.1127

      April 25, 2019
      KB4493440      		Resolved
      KB4499179      		May 14, 2019
      01:18 PM PT
      Custom URI schemes may not start corresponding application
      Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

      See details >      		OS Build 16299.1029

      March 12, 2019
      KB4489886      		Resolved
      KB4493440      		April 25, 2019
      02:00 PM PT
      End-user-defined characters (EUDC) may cause blue screen at startup
      If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup.

      See details >      		OS Build 16299.1059

      March 19, 2019
      KB4489890      		Resolved
      KB4493441      		April 09, 2019
      10:00 AM PT
      MSXML6 causes applications to stop responding if an exception was thrown
      MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

      See details >      		OS Build 16299.904

      January 08, 2019
      KB4480978      		Resolved
      KB4493441      		April 09, 2019
      10:00 AM PT
      + +
      DetailsOriginating updateStatusHistory
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Resolution: This issue has been resolved.

      Back to top      		OS Build 16299.1127

      April 25, 2019
      KB4493440      		Resolved
      KB4499179      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      + " + +- title: April 2019 +- items: + - type: markdown + text: " + + +
      DetailsOriginating updateStatusHistory
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail after installing KB4493440. 
       
      Affected platforms:  
      • Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016 
      • Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016 
      Resolution: This issue was resolved in KB4499179.

      Back to top      		OS Build 16299.1127

      April 25, 2019
      KB4493440      		Resolved
      KB4499179      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      April 25, 2019
      02:00 PM PT
      + " + - title: March 2019 - items: - type: markdown diff --git a/windows/release-information/resolved-issues-windows-10-1803.yml b/windows/release-information/resolved-issues-windows-10-1803.yml index 8eaaa3f3c9..1899a16774 100644 --- a/windows/release-information/resolved-issues-windows-10-1803.yml +++ b/windows/release-information/resolved-issues-windows-10-1803.yml @@ -32,6 +32,8 @@ sections: - type: markdown text: " + + @@ -62,6 +64,24 @@ sections:
      " +- title: May 2019 +- items: + - type: markdown + text: " +
      SummaryOriginating updateStatusDate resolved
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail.

      See details >      		OS Build 17134.753

      April 25, 2019
      KB4493437      		Resolved
      KB4499167      		May 14, 2019
      01:19 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		OS Build 17134.753

      April 25, 2019
      KB4493437      		Resolved
      KB4499167      		May 14, 2019
      01:18 PM PT
      Custom URI schemes may not start corresponding application
      Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

      See details >      		OS Build 17134.648

      March 12, 2019
      KB4489868      		Resolved
      KB4493437      		April 25, 2019
      02:00 PM PT
      End-user-defined characters (EUDC) may cause blue screen at startup
      If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup.

      See details >      		OS Build 17134.677

      March 19, 2019
      KB4489894      		Resolved
      KB4493464      		April 09, 2019
      10:00 AM PT
      First character of the Japanese era name not recognized
      The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

      See details >      		OS Build 17134.556

      January 15, 2019
      KB4480976      		Resolved
      KB4487029      		April 09, 2019
      10:00 AM PT
      + +
      DetailsOriginating updateStatusHistory
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Resolution: This issue has been resolved.

      Back to top      		OS Build 17134.753

      April 25, 2019
      KB4493437      		Resolved
      KB4499167      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      + " + +- title: April 2019 +- items: + - type: markdown + text: " + + +
      DetailsOriginating updateStatusHistory
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail after installing KB4493437. 
       
      Affected platforms:  
      • Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016 
      • Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016 
      Resolution: This issue was resolved in KB4499167.

      Back to top      		OS Build 17134.753

      April 25, 2019
      KB4493437      		Resolved
      KB4499167      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      April 25, 2019
      02:00 PM PT
      + " + - title: March 2019 - items: - type: markdown diff --git a/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml b/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml index b0d3c9f294..7e3ded548f 100644 --- a/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml +++ b/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml @@ -32,6 +32,8 @@ sections: - type: markdown text: " + + @@ -73,6 +75,8 @@ sections: - type: markdown text: "
      SummaryOriginating updateStatusDate resolved
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail.

      See details >      		OS Build 17763.475

      May 03, 2019
      KB4495667      		Resolved
      KB4494441      		May 14, 2019
      01:19 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		OS Build 17763.475

      May 03, 2019
      KB4495667      		Resolved
      KB4494441      		May 14, 2019
      01:18 PM PT
      Latest cumulative update (KB 4495667) installs automatically
      Reports that the optional cumulative update (KB 4495667) installs automatically.

      See details >      		OS Build 17763.475

      May 03, 2019
      KB4495667      		Resolved
      		May 08, 2019
      03:37 PM PT
      System may be unresponsive after restart if ArcaBit antivirus software installed
      After further investigation ArcaBit has confirmed this issue is not applicable to Windows 10, version 1809

      See details >      		OS Build 17763.437

      April 09, 2019
      KB4493509      		Resolved
      		May 08, 2019
      03:30 PM PT
      Custom URI schemes may not start corresponding application
      Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

      See details >      		OS Build 17763.379

      March 12, 2019
      KB4489899      		Resolved
      KB4495667      		May 03, 2019
      12:40 PM PT
      + +
      DetailsOriginating updateStatusHistory
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail after installing KB4495667. 
       
      Affected platforms:  
      • Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016 
      • Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016 
      Resolution: This issue was resolved in KB4494441.

      Back to top      		OS Build 17763.475

      May 03, 2019
      KB4495667      		Resolved
      KB4494441      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      May 14, 2019
      01:19 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Resolution: This issue has been resolved.

      Back to top      		OS Build 17763.475

      May 03, 2019
      KB4495667      		Resolved
      KB4494441      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      Latest cumulative update (KB 4495667) installs automatically
      Due to a servicing side issue some users were offered KB4495667 (optional update) automatically and rebooted devices. This issue has been mitigated.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
      • Server: Windows Server, version 1809; Windows Server 2019
      Resolution:: This issue has been mitigated on the servicing side to prevent auto installing of this update. Customers do not need to take any action.

      Back to top      		OS Build 17763.475

      May 03, 2019
      KB4495667      		Resolved
      		Resolved:
      May 08, 2019
      03:37 PM PT

      Opened:
      May 05, 2019
      12:01 PM PT
      " diff --git a/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml b/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml index d034127b65..cb278e2cc4 100644 --- a/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml +++ b/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml @@ -32,6 +32,11 @@ sections: - type: markdown text: " + + + + + @@ -55,11 +60,23 @@ sections:
      " +- title: May 2019 +- items: + - type: markdown + text: " +
      SummaryOriginating updateStatusDate resolved
      System may be unresponsive after restart if ArcaBit antivirus software installed
      Devices with ArcaBit antivirus software installed may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493472      		Resolved
      		May 14, 2019
      01:23 PM PT
      System unresponsive after restart if Sophos Endpoint Protection installed
      Devices with Sophos Endpoint Protection installed and managed by Sophos Central or Sophos Enterprise Console (SEC) may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493472      		Resolved
      		May 14, 2019
      01:22 PM PT
      System may be unresponsive after restart if Avira antivirus software installed
      Devices with Avira antivirus software installed may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493472      		Resolved
      		May 14, 2019
      01:21 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		April 25, 2019
      KB4493453      		Resolved
      KB4499164      		May 14, 2019
      01:18 PM PT
      Authentication may fail for services after the Kerberos ticket expires
      Authentication may fail for services that require unconstrained delegation after the Kerberos ticket expires.

      See details >      		March 12, 2019
      KB4489878      		Resolved
      KB4499164      		May 14, 2019
      01:17 PM PT
      Devices may not respond at login or Welcome screen if running certain Avast software
      Devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software may become unresponsive after restart.

      See details >      		April 09, 2019
      KB4493472      		Resolved
      		April 25, 2019
      02:00 PM PT
      Internet Explorer 11 authentication issue with multiple concurrent logons
      Internet Explorer 11 users may encounter issues if two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine.

      See details >      		January 08, 2019
      KB4480970      		Resolved
      KB4493472      		April 09, 2019
      10:00 AM PT
      Custom URI schemes may not start corresponding application
      Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

      See details >      		March 12, 2019
      KB4489878      		Resolved
      KB4493472      		April 09, 2019
      10:00 AM PT
      + +
      DetailsOriginating updateStatusHistory
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Resolution: This issue has been resolved.

      Back to top      		April 25, 2019
      KB4493453      		Resolved
      KB4499164      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      + " + - title: April 2019 - items: - type: markdown text: " + + +
      DetailsOriginating updateStatusHistory
      System may be unresponsive after restart if ArcaBit antivirus software installed
      Microsoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493472.

      Affected platforms:
      • Client: Windows 8.1; Windows 7 SP1
      • Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1
      Resolution: This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. ArcaBit has released an update to address this issue. For more information, see the Arcabit support article.

      Back to top      		April 09, 2019
      KB4493472      		Resolved
      		Resolved:
      May 14, 2019
      01:23 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System unresponsive after restart if Sophos Endpoint Protection installed
      Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing KB4493472.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Resolution: This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Sophos has released an update to address this issue. Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.

      Back to top      		April 09, 2019
      KB4493472      		Resolved
      		Resolved:
      May 14, 2019
      01:22 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System may be unresponsive after restart if Avira antivirus software installed
      Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493472.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1 
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Resolution: This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article.

      Back to top      		April 09, 2019
      KB4493472      		Resolved
      		Resolved:
      May 14, 2019
      01:21 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      Devices may not respond at login or Welcome screen if running certain Avast software
      Microsoft and Avast have identified an issue on devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software after you install KB4493472 and restart. Devices may become unresponsive at the login or Welcome screen. Additionally, you may be unable to log in or log in after an extended period of time.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1 
      • Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1 
      Resolution: Avast has released emergency updates to address this issue. For more information and AV update schedule, see the Avast support KB article.

      Back to top      		April 09, 2019
      KB4493472      		Resolved
      		Resolved:
      April 25, 2019
      02:00 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      " @@ -69,6 +86,7 @@ sections: - type: markdown text: " +
      DetailsOriginating updateStatusHistory
      Authentication may fail for services after the Kerberos ticket expires
      After installing KB4489878, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails.

      Affected platforms: 
      • Client: Windows 7 SP1
      • Server: Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Resolution: This issue was resolved in KB4499164.

      Back to top      		March 12, 2019
      KB4489878      		Resolved
      KB4499164      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      March 12, 2019
      10:00 AM PT
      Custom URI schemes may not start corresponding application
      After installing KB4489878, custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites on Internet Explorer.

      Affected platforms: 
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1 
      Resolution: This issue is resolved in KB4493472.

      Back to top      		March 12, 2019
      KB4489878      		Resolved
      KB4493472      		Resolved:
      April 09, 2019
      10:00 AM PT

      Opened:
      March 12, 2019
      10:00 AM PT
      NETDOM.EXE fails to run
      After installing KB4489878, NETDOM.EXE fails to run, and the on-screen error, “The command failed to complete successfully.” appears.

      Affected platforms: 
      • Client: Windows 7 SP1
      • Server: Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Resolution: This issue is resolved in KB4493472.

      Back to top      		March 12, 2019
      KB4489878      		Resolved
      KB4493472      		Resolved:
      April 09, 2019
      10:00 AM PT

      Opened:
      March 12, 2019
      10:00 AM PT
      diff --git a/windows/release-information/resolved-issues-windows-8.1-and-windows-server-2012-r2.yml b/windows/release-information/resolved-issues-windows-8.1-and-windows-server-2012-r2.yml index 1ef62bfe75..2a62a3f335 100644 --- a/windows/release-information/resolved-issues-windows-8.1-and-windows-server-2012-r2.yml +++ b/windows/release-information/resolved-issues-windows-8.1-and-windows-server-2012-r2.yml @@ -32,6 +32,10 @@ sections: - type: markdown text: " + + + + @@ -55,11 +59,23 @@ sections:
      " +- title: May 2019 +- items: + - type: markdown + text: " +
      SummaryOriginating updateStatusDate resolved
      System may be unresponsive after restart if ArcaBit antivirus software installed
      Devices with ArcaBit antivirus software installed may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493446      		Resolved
      		May 14, 2019
      01:22 PM PT
      System unresponsive after restart if Sophos Endpoint Protection installed
      Devices with Sophos Endpoint Protection installed and managed by Sophos Central or Sophos Enterprise Console (SEC) may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493446      		Resolved
      		May 14, 2019
      01:22 PM PT
      System may be unresponsive after restart if Avira antivirus software installed
      Devices with Avira antivirus software installed may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493446      		Resolved
      		May 14, 2019
      01:21 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		April 25, 2019
      KB4493443      		Resolved
      KB4499151      		May 14, 2019
      01:18 PM PT
      Devices may not respond at login or Welcome screen if running certain Avast software
      Devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software may become unresponsive after restart.

      See details >      		April 09, 2019
      KB4493446      		Resolved
      		April 25, 2019
      02:00 PM PT
      Internet Explorer 11 authentication issue with multiple concurrent logons
      Internet Explorer 11 users may encounter issues if two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine.

      See details >      		January 08, 2019
      KB4480963      		Resolved
      KB4493446      		April 09, 2019
      10:00 AM PT
      MSXML6 may cause applications to stop responding.
      MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

      See details >      		January 08, 2019
      KB4480963      		Resolved
      KB4493446      		April 09, 2019
      10:00 AM PT
      + +
      DetailsOriginating updateStatusHistory
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Resolution: This issue has been resolved.

      Back to top      		April 25, 2019
      KB4493443      		Resolved
      KB4499151      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      + " + - title: April 2019 - items: - type: markdown text: " + + +
      DetailsOriginating updateStatusHistory
      System may be unresponsive after restart if ArcaBit antivirus software installed
      Microsoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493446.

      Affected platforms:
      • Client: Windows 8.1; Windows 7 SP1
      • Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1
      Resolution: This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. ArcaBit has released an update to address this issue. For more information, see the Arcabit support article.

      Back to top      		April 09, 2019
      KB4493446      		Resolved
      		Resolved:
      May 14, 2019
      01:22 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System unresponsive after restart if Sophos Endpoint Protection installed
      Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing KB4493446.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Resolution: This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Sophos has released an update to address this issue. Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.

      Back to top      		April 09, 2019
      KB4493446      		Resolved
      		Resolved:
      May 14, 2019
      01:22 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System may be unresponsive after restart if Avira antivirus software installed
      Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493446.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1 
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Resolution: This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article.

      Back to top      		April 09, 2019
      KB4493446      		Resolved
      		Resolved:
      May 14, 2019
      01:21 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      Devices may not respond at login or Welcome screen if running certain Avast software
      Microsoft and Avast have identified an issue on devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software after you install KB4493446 and restart. Devices may become unresponsive at the login or Welcome screen. Additionally, you may be unable to log in or log in after an extended period of time.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1 
      • Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1 
      Resolution: Avast has released emergency updates to address this issue. For more information and AV update schedule, see the Avast support KB article.

      Back to top      		April 09, 2019
      KB4493446      		Resolved
      		Resolved:
      April 25, 2019
      02:00 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      " diff --git a/windows/release-information/resolved-issues-windows-server-2008-sp2.yml b/windows/release-information/resolved-issues-windows-server-2008-sp2.yml index fe19c4b36e..36c4a276c4 100644 --- a/windows/release-information/resolved-issues-windows-server-2008-sp2.yml +++ b/windows/release-information/resolved-issues-windows-server-2008-sp2.yml @@ -32,6 +32,10 @@ sections: - type: markdown text: " + + + + @@ -50,11 +54,31 @@ sections:
      " +- title: May 2019 +- items: + - type: markdown + text: " +
      SummaryOriginating updateStatusDate resolved
      System unresponsive after restart if Sophos Endpoint Protection installed
      Devices with Sophos Endpoint Protection installed and managed by Sophos Central or Sophos Enterprise Console (SEC) may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493471      		Resolved
      		May 14, 2019
      01:21 PM PT
      System may be unresponsive after restart if Avira antivirus software installed
      Devices with Avira antivirus software installed may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493471      		Resolved
      		May 14, 2019
      01:19 PM PT
      Authentication may fail for services after the Kerberos ticket expires
      Authentication may fail for services that require unconstrained delegation after the Kerberos ticket expires.

      See details >      		March 12, 2019
      KB4489880      		Resolved
      KB4499149      		May 14, 2019
      01:18 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		April 25, 2019
      KB4493460      		Resolved
      KB4499149      		May 14, 2019
      01:18 PM PT
      Embedded objects may display incorrectly
      Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly.

      See details >      		February 12, 2019
      KB4487023      		Resolved
      KB4493471      		April 09, 2019
      10:00 AM PT
      NETDOM.EXE fails to run
      NETDOM.EXE fails to run and the error, “The command failed to complete successfully.” appears on screen.

      See details >      		March 12, 2019
      KB4489880      		Resolved
      KB4493471      		April 09, 2019
      10:00 AM PT
      First character of the Japanese era name not recognized as an abbreviation
      The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

      See details >      		January 17, 2019
      KB4480974      		Resolved
      KB4489880      		March 12, 2019
      10:00 AM PT
      + +
      DetailsOriginating updateStatusHistory
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Resolution: This issue has been resolved.

      Back to top      		April 25, 2019
      KB4493460      		Resolved
      KB4499149      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      + " + +- title: April 2019 +- items: + - type: markdown + text: " + + + +
      DetailsOriginating updateStatusHistory
      System unresponsive after restart if Sophos Endpoint Protection installed
      Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing KB4493471.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Resolution: This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Sophos has released an update to address this issue. Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.

      Back to top      		April 09, 2019
      KB4493471      		Resolved
      		Resolved:
      May 14, 2019
      01:21 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System may be unresponsive after restart if Avira antivirus software installed
      Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493471.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1 
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Resolution: This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article.

      Back to top      		April 09, 2019
      KB4493471      		Resolved
      		Resolved:
      May 14, 2019
      01:19 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      + " + - title: March 2019 - items: - type: markdown text: " +
      DetailsOriginating updateStatusHistory
      Authentication may fail for services after the Kerberos ticket expires
      After installing KB4489880, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails.

      Affected platforms: 
      • Client: Windows 7 SP1
      • Server: Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Resolution: This issue was resolved in KB4499149.

      Back to top      		March 12, 2019
      KB4489880      		Resolved
      KB4499149      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      March 12, 2019
      10:00 AM PT
      NETDOM.EXE fails to run
      After installing KB4489880, NETDOM.EXE fails to run, and the on-screen error, “The command failed to complete successfully.” appears.

      Affected platforms: 
      • Client: Windows 7 SP1
      • Server: Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Resolution: This issue is resolved in KB4493471.

      Back to top      		March 12, 2019
      KB4489880      		Resolved
      KB4493471      		Resolved:
      April 09, 2019
      10:00 AM PT

      Opened:
      March 12, 2019
      10:00 AM PT
      " diff --git a/windows/release-information/resolved-issues-windows-server-2012.yml b/windows/release-information/resolved-issues-windows-server-2012.yml index b2a7ce07c1..a18dd90804 100644 --- a/windows/release-information/resolved-issues-windows-server-2012.yml +++ b/windows/release-information/resolved-issues-windows-server-2012.yml @@ -32,6 +32,9 @@ sections: - type: markdown text: " + + + @@ -53,6 +56,25 @@ sections:
      " +- title: May 2019 +- items: + - type: markdown + text: " +
      SummaryOriginating updateStatusDate resolved
      System unresponsive after restart if Sophos Endpoint Protection installed
      Devices with Sophos Endpoint Protection installed and managed by Sophos Central or Sophos Enterprise Console (SEC) may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493451      		Resolved
      		May 14, 2019
      01:21 PM PT
      System may be unresponsive after restart if Avira antivirus software installed
      Devices with Avira antivirus software installed may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493451      		Resolved
      		May 14, 2019
      01:19 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		April 25, 2019
      KB4493462      		Resolved
      KB4499171      		May 14, 2019
      01:18 PM PT
      Internet Explorer 11 authentication issue with multiple concurrent logons
      Internet Explorer 11 users may encounter issues if two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine.

      See details >      		January 08, 2019
      KB4480975      		Resolved
      KB4493451      		April 09, 2019
      10:00 AM PT
      MSXML6 may cause applications to stop responding
      MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

      See details >      		January 08, 2019
      KB4480975      		Resolved
      KB4493451      		April 09, 2019
      10:00 AM PT
      Embedded objects may display incorrectly
      Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly.

      See details >      		February 12, 2019
      KB4487025      		Resolved
      KB4493451      		April 09, 2019
      10:00 AM PT
      + +
      DetailsOriginating updateStatusHistory
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Resolution: This issue has been resolved.

      Back to top      		April 25, 2019
      KB4493462      		Resolved
      KB4499171      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      + " + +- title: April 2019 +- items: + - type: markdown + text: " + + + +
      DetailsOriginating updateStatusHistory
      System unresponsive after restart if Sophos Endpoint Protection installed
      Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing KB4493451.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Resolution: This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Sophos has released an update to address this issue. Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.

      Back to top      		April 09, 2019
      KB4493451      		Resolved
      		Resolved:
      May 14, 2019
      01:21 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System may be unresponsive after restart if Avira antivirus software installed
      Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493451.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1 
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Resolution: This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article.

      Back to top      		April 09, 2019
      KB4493451      		Resolved
      		Resolved:
      May 14, 2019
      01:19 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      + " + - title: February 2019 - items: - type: markdown diff --git a/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml b/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml index d444c69dac..a892f9ad48 100644 --- a/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml +++ b/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml @@ -60,13 +60,13 @@ sections: - type: markdown text: "
      This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

      - - + +
      SummaryOriginating updateStatusLast updated
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail.

      See details >      		OS Build 14393.2941

      April 25, 2019
      KB4493473      		Investigating
      		April 25, 2019
      02:00 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		OS Build 14393.2931

      April 25, 2019
      KB4492241      		Mitigated
      		May 10, 2019
      10:35 AM PT
      Cluster service may fail if the minimum password length is set to greater than 14
      The cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the Group Policy “Minimum Password Length” is configured with greater than 14 characters.

      See details >      		OS Build 14393.2639

      November 27, 2018
      KB4467684      		Mitigated
      		April 25, 2019
      02:00 PM PT
      Issue using PXE to start a device from WDS
      There may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension.

      See details >      		OS Build 14393.2848

      March 12, 2019
      KB4489882      		Mitigated
      		April 25, 2019
      02:00 PM PT
      SCVMM cannot enumerate and manage logical switches deployed on the host
      For hosts managed by System Center Virtual Machine Manager (VMM), VMM cannot enumerate and manage logical switches deployed on the host.

      See details >      		OS Build 14393.2639

      November 27, 2018
      KB4467684      		Mitigated
      		April 25, 2019
      02:00 PM PT
      Certain operations performed on a Cluster Shared Volume may fail
      Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\".

      See details >      		OS Build 14393.2724

      January 08, 2019
      KB4480961      		Mitigated
      		April 25, 2019
      02:00 PM PT
      Windows may not start on certain Lenovo and Fujitsu laptops with less than 8GB of RAM
      Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM.

      See details >      		OS Build 14393.2608

      November 13, 2018
      KB4467691      		Mitigated
      		February 19, 2019
      10:00 AM PT
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail.

      See details >      		OS Build 14393.2941

      April 25, 2019
      KB4493473      		Resolved
      KB4494440      		May 14, 2019
      01:18 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		OS Build 14393.2941

      April 25, 2019
      KB4493473      		Resolved
      KB4494440      		May 14, 2019
      01:18 PM PT
      Custom URI schemes may not start corresponding application
      Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

      See details >      		OS Build 14393.2848

      March 12, 2019
      KB4489882      		Resolved
      KB4493473      		April 25, 2019
      02:00 PM PT
      " @@ -83,7 +83,7 @@ sections: - type: markdown text: " - +
      DetailsOriginating updateStatusHistory
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Workaround: Until a resolution is released, we recommend switching to a different Japanese font, such as Yu Gothic or MS Mincho. Alternatively, you can uninstall the optional update.

      Next steps: Microsoft is working on a resolution and estimates a solution will be available in mid-May.

      Back to top      		OS Build 14393.2931

      April 25, 2019
      KB4492241      		Mitigated
      		Last updated:
      May 10, 2019
      10:35 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Resolution: This issue has been resolved.

      Back to top      		OS Build 14393.2941

      April 25, 2019
      KB4493473      		Resolved
      KB4494440      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      " @@ -92,7 +92,7 @@ sections: - type: markdown text: " - +
      DetailsOriginating updateStatusHistory
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail after installing KB4493473. 
       
      Affected platforms:  
      • Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016 
      • Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016 
      Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release. 

      Back to top      		OS Build 14393.2941

      April 25, 2019
      KB4493473      		Investigating
      		Last updated:
      April 25, 2019
      02:00 PM PT

      Opened:
      April 25, 2019
      02:00 PM PT
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail after installing KB4493473. 
       
      Affected platforms:  
      • Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016 
      • Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016 
      Resolution: This issue was resolved in KB4494440.

      Back to top      		OS Build 14393.2941

      April 25, 2019
      KB4493473      		Resolved
      KB4494440      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      April 25, 2019
      02:00 PM PT
      " diff --git a/windows/release-information/status-windows-10-1703.yml b/windows/release-information/status-windows-10-1703.yml index c0cfa4ac36..6d7e9ed3ed 100644 --- a/windows/release-information/status-windows-10-1703.yml +++ b/windows/release-information/status-windows-10-1703.yml @@ -60,8 +60,8 @@ sections: - type: markdown text: "
      This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

      - +
      SummaryOriginating updateStatusLast updated
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		OS Build 15063.1771

      April 25, 2019
      KB4492242      		Mitigated
      		May 10, 2019
      10:35 AM PT
      Certain operations performed on a Cluster Shared Volume may fail
      Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\".

      See details >      		OS Build 15063.1563

      January 08, 2019
      KB4480973      		Mitigated
      		April 25, 2019
      02:00 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		OS Build 15063.1784

      April 25, 2019
      KB4493436      		Resolved
      KB4499181      		May 14, 2019
      01:18 PM PT
      Custom URI schemes may not start corresponding application
      Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

      See details >      		OS Build 15063.1689

      March 12, 2019
      KB4489871      		Resolved
      KB4493436      		April 25, 2019
      02:00 PM PT
      " @@ -78,7 +78,7 @@ sections: - type: markdown text: " - +
      DetailsOriginating updateStatusHistory
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Workaround: Until a resolution is released, we recommend switching to a different Japanese font, such as Yu Gothic or MS Mincho. Alternatively, you can uninstall the optional update.

      Next steps: Microsoft is working on a resolution and estimates a solution will be available in mid-May.

      Back to top      		OS Build 15063.1771

      April 25, 2019
      KB4492242      		Mitigated
      		Last updated:
      May 10, 2019
      10:35 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Resolution: This issue has been resolved.

      Back to top      		OS Build 15063.1784

      April 25, 2019
      KB4493436      		Resolved
      KB4499181      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      " diff --git a/windows/release-information/status-windows-10-1709.yml b/windows/release-information/status-windows-10-1709.yml index 2618d42ebf..432a4cc2de 100644 --- a/windows/release-information/status-windows-10-1709.yml +++ b/windows/release-information/status-windows-10-1709.yml @@ -60,9 +60,9 @@ sections: - type: markdown text: "
      This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

      - - + +
      SummaryOriginating updateStatusLast updated
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail.

      See details >      		OS Build 16299.1127

      April 25, 2019
      KB4493440      		Investigating
      		April 25, 2019
      02:00 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		OS Build 16299.1111

      April 25, 2019
      KB4492243      		Mitigated
      		May 10, 2019
      10:35 AM PT
      Certain operations performed on a Cluster Shared Volume may fail
      Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\".

      See details >      		OS Build 16299.904

      January 08, 2019
      KB4480978      		Mitigated
      		April 25, 2019
      02:00 PM PT
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail.

      See details >      		OS Build 16299.1127

      April 25, 2019
      KB4493440      		Resolved
      KB4499179      		May 14, 2019
      01:18 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		OS Build 16299.1127

      April 25, 2019
      KB4493440      		Resolved
      KB4499179      		May 14, 2019
      01:18 PM PT
      Custom URI schemes may not start corresponding application
      Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

      See details >      		OS Build 16299.1029

      March 12, 2019
      KB4489886      		Resolved
      KB4493440      		April 25, 2019
      02:00 PM PT
      " @@ -79,7 +79,7 @@ sections: - type: markdown text: " - +
      DetailsOriginating updateStatusHistory
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Workaround: Until a resolution is released, we recommend switching to a different Japanese font, such as Yu Gothic or MS Mincho. Alternatively, you can uninstall the optional update.

      Next steps: Microsoft is working on a resolution and estimates a solution will be available in mid-May.

      Back to top      		OS Build 16299.1111

      April 25, 2019
      KB4492243      		Mitigated
      		Last updated:
      May 10, 2019
      10:35 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Resolution: This issue has been resolved.

      Back to top      		OS Build 16299.1127

      April 25, 2019
      KB4493440      		Resolved
      KB4499179      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      " @@ -88,7 +88,7 @@ sections: - type: markdown text: " - +
      DetailsOriginating updateStatusHistory
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail after installing KB4493440. 
       
      Affected platforms:  
      • Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016 
      • Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016 
      Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release. 

      Back to top      		OS Build 16299.1127

      April 25, 2019
      KB4493440      		Investigating
      		Last updated:
      April 25, 2019
      02:00 PM PT

      Opened:
      April 25, 2019
      02:00 PM PT
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail after installing KB4493440. 
       
      Affected platforms:  
      • Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016 
      • Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016 
      Resolution: This issue was resolved in KB4499179.

      Back to top      		OS Build 16299.1127

      April 25, 2019
      KB4493440      		Resolved
      KB4499179      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      April 25, 2019
      02:00 PM PT
      " diff --git a/windows/release-information/status-windows-10-1803.yml b/windows/release-information/status-windows-10-1803.yml index 9fea9cbeb3..b410878b1a 100644 --- a/windows/release-information/status-windows-10-1803.yml +++ b/windows/release-information/status-windows-10-1803.yml @@ -60,10 +60,10 @@ sections: - type: markdown text: "
      This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

      - - + +
      SummaryOriginating updateStatusLast updated
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail.

      See details >      		OS Build 17134.753

      April 25, 2019
      KB4493437      		Investigating
      		April 25, 2019
      02:00 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		OS Build 17134.730

      April 25, 2019
      KB4492245      		Mitigated
      		May 10, 2019
      10:35 AM PT
      Issue using PXE to start a device from WDS
      Using PXE to start a device from a WDS server configured to use Variable Window Extension may cause the connection to the WDS server to terminate prematurely.

      See details >      		OS Build 17134.648

      March 12, 2019
      KB4489868      		Mitigated
      		April 25, 2019
      02:00 PM PT
      Certain operations performed on a Cluster Shared Volume may fail
      Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\".

      See details >      		OS Build 17134.523

      January 08, 2019
      KB4480966      		Mitigated
      		April 25, 2019
      02:00 PM PT
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail.

      See details >      		OS Build 17134.753

      April 25, 2019
      KB4493437      		Resolved
      KB4499167      		May 14, 2019
      01:19 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		OS Build 17134.753

      April 25, 2019
      KB4493437      		Resolved
      KB4499167      		May 14, 2019
      01:18 PM PT
      Custom URI schemes may not start corresponding application
      Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

      See details >      		OS Build 17134.648

      March 12, 2019
      KB4489868      		Resolved
      KB4493437      		April 25, 2019
      02:00 PM PT
      " @@ -80,7 +80,7 @@ sections: - type: markdown text: " - +
      DetailsOriginating updateStatusHistory
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Workaround: Until a resolution is released, we recommend switching to a different Japanese font, such as Yu Gothic or MS Mincho. Alternatively, you can uninstall the optional update.

      Next steps: Microsoft is working on a resolution and estimates a solution will be available in mid-May.

      Back to top      		OS Build 17134.730

      April 25, 2019
      KB4492245      		Mitigated
      		Last updated:
      May 10, 2019
      10:35 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Resolution: This issue has been resolved.

      Back to top      		OS Build 17134.753

      April 25, 2019
      KB4493437      		Resolved
      KB4499167      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      " @@ -89,7 +89,7 @@ sections: - type: markdown text: " - +
      DetailsOriginating updateStatusHistory
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail after installing KB4493437. 
       
      Affected platforms:  
      • Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016 
      • Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016 
      Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release. 

      Back to top      		OS Build 17134.753

      April 25, 2019
      KB4493437      		Investigating
      		Last updated:
      April 25, 2019
      02:00 PM PT

      Opened:
      April 25, 2019
      02:00 PM PT
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail after installing KB4493437. 
       
      Affected platforms:  
      • Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016 
      • Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016 
      Resolution: This issue was resolved in KB4499167.

      Back to top      		OS Build 17134.753

      April 25, 2019
      KB4493437      		Resolved
      KB4499167      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      April 25, 2019
      02:00 PM PT
      " diff --git a/windows/release-information/status-windows-10-1809-and-windows-server-2019.yml b/windows/release-information/status-windows-10-1809-and-windows-server-2019.yml index afb53b80c9..957fd88deb 100644 --- a/windows/release-information/status-windows-10-1809-and-windows-server-2019.yml +++ b/windows/release-information/status-windows-10-1809-and-windows-server-2019.yml @@ -65,12 +65,14 @@ sections: - type: markdown text: "
      This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

      - + + + @@ -89,9 +91,11 @@ sections: - type: markdown text: "
      SummaryOriginating updateStatusLast updated
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		OS Build 17763.475

      May 03, 2019
      KB4495667      		Mitigated
      		May 10, 2019
      10:35 AM PT
      Windows 10, version 1809 Update Tuesday update may install twice
      Some customers are reporting that KB4494441 installs twice

      See details >      		OS Build 17763.502

      May 14, 2019
      KB4494441      		Acknowledged
      		May 14, 2019
      02:56 PM PT
      Devices with some Asian language packs installed may receive an error
      After installing the KB4493509 devices with some Asian language packs installed may receive the error, \"0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_F

      See details >      		OS Build 17763.437

      April 09, 2019
      KB4493509      		Mitigated
      		May 03, 2019
      10:59 AM PT
      Printing from Microsoft Edge or other UWP apps, you may receive the error 0x80070007
      Attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications, you may receive an error.

      See details >      		OS Build 17763.379

      March 12, 2019
      KB4489899      		Mitigated
      		May 02, 2019
      04:47 PM PT
      Issue using PXE to start a device from WDS
      Using PXE to start a device from a WDS server configured to use Variable Window Extension may cause the connection to the WDS server to terminate prematurely.

      See details >      		OS Build 17763.379

      March 12, 2019
      KB4489899      		Mitigated
      		April 09, 2019
      10:00 AM PT
      Certain operations performed on a Cluster Shared Volume may fail
      Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\".

      See details >      		OS Build 17763.253

      January 08, 2019
      KB4480116      		Mitigated
      		April 09, 2019
      10:00 AM PT
      Audio not working on monitors or TV connected to a PC via HDMI, USB, or DisplayPort
      Upgrade block: Microsoft has identified issues with certain new Intel display drivers, which accidentally turn on unsupported features in Windows.

      See details >      		OS Build 17763.134

      November 13, 2018
      KB4467708      		Mitigated
      		March 15, 2019
      12:00 PM PT
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail.

      See details >      		OS Build 17763.475

      May 03, 2019
      KB4495667      		Resolved
      KB4494441      		May 14, 2019
      01:19 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		OS Build 17763.475

      May 03, 2019
      KB4495667      		Resolved
      KB4494441      		May 14, 2019
      01:18 PM PT
      Latest cumulative update (KB 4495667) installs automatically
      Reports that the optional cumulative update (KB 4495667) installs automatically.

      See details >      		OS Build 17763.475

      May 03, 2019
      KB4495667      		Resolved
      		May 08, 2019
      03:37 PM PT
      System may be unresponsive after restart if ArcaBit antivirus software installed
      After further investigation ArcaBit has confirmed this issue is not applicable to Windows 10, version 1809

      See details >      		OS Build 17763.437

      April 09, 2019
      KB4493509      		Resolved
      		May 08, 2019
      03:30 PM PT
      Custom URI schemes may not start corresponding application
      Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

      See details >      		OS Build 17763.379

      March 12, 2019
      KB4489899      		Resolved
      KB4495667      		May 03, 2019
      12:40 PM PT
      - + + +
      DetailsOriginating updateStatusHistory
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Workaround: Until a resolution is released, we recommend switching to a different Japanese font, such as Yu Gothic or MS Mincho. Alternatively, you can uninstall the optional update.

      Next steps: Microsoft is working on a resolution and estimates a solution will be available in mid-May.

      Back to top      		OS Build 17763.475

      May 03, 2019
      KB4495667      		Mitigated
      		Last updated:
      May 10, 2019
      10:35 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      Windows 10, version 1809 Update Tuesday update may install twice
      We are presently investigating and will provide an update when available.

      Affected platforms:
      • Client: Windows 10, version 1809
      • Server: TBD


      Back to top      		OS Build 17763.502

      May 14, 2019
      KB4494441      		Acknowledged
      		Last updated:
      May 14, 2019
      02:56 PM PT

      Opened:
      May 14, 2019
      02:56 PM PT
      Devices with some Asian language packs installed may receive an error
      After installing the April 2019 Cumulative Update (KB4493509), devices with some Asian language packs installed may receive the error, \"0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.\"

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
      • Server: Windows Server, version 1809; Windows Server 2019
      Workaround:
      1. Uninstall and reinstall any recently added language packs. For instructions, see \"Manage the input and display language settings in Windows 10\".
      2. Click Check for Updates and install the April 2019 Cumulative Update. For instructions, see \"Update Windows 10\".
      Note: If reinstalling the language pack does not mitigate the issue, reset your PC as follows:
      1. Go to Settings app -> Recovery.
      2. Click on Get Started under \"Reset this PC\" recovery option.
      3. Select \"Keep my Files\".
      Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.

      Back to top      		OS Build 17763.437

      April 09, 2019
      KB4493509      		Mitigated
      		Last updated:
      May 03, 2019
      10:59 AM PT

      Opened:
      May 02, 2019
      04:36 PM PT
      Printing from Microsoft Edge or other UWP apps, you may receive the error 0x80070007
      When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications you may receive the error, \"Your printer has experienced an unexpected configuration problem. 0x80070007e.\"
       
      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
      • Server: Windows Server, version 1809; Windows Server 2019
      Workaround: You can use another browser, such as Internet Explorer to print your documents.
       
      Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.

      Back to top      		OS Build 17763.379

      March 12, 2019
      KB4489899      		Mitigated
      		Last updated:
      May 02, 2019
      04:47 PM PT

      Opened:
      May 02, 2019
      04:47 PM PT
      Zone transfers over TCP may fail
      Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail after installing KB4495667. 
       
      Affected platforms:  
      • Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016 
      • Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016 
      Resolution: This issue was resolved in KB4494441.

      Back to top      		OS Build 17763.475

      May 03, 2019
      KB4495667      		Resolved
      KB4494441      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      May 14, 2019
      01:19 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Resolution: This issue has been resolved.

      Back to top      		OS Build 17763.475

      May 03, 2019
      KB4495667      		Resolved
      KB4494441      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      Latest cumulative update (KB 4495667) installs automatically
      Due to a servicing side issue some users were offered KB4495667 (optional update) automatically and rebooted devices. This issue has been mitigated.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
      • Server: Windows Server, version 1809; Windows Server 2019
      Resolution:: This issue has been mitigated on the servicing side to prevent auto installing of this update. Customers do not need to take any action.

      Back to top      		OS Build 17763.475

      May 03, 2019
      KB4495667      		Resolved
      		Resolved:
      May 08, 2019
      03:37 PM PT

      Opened:
      May 05, 2019
      12:01 PM PT
      " diff --git a/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml b/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml index 0ce3cb79c0..6f79cac2fd 100644 --- a/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml +++ b/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml @@ -60,12 +60,12 @@ sections: - type: markdown text: "
      This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

      - - - - - + + + + +
      SummaryOriginating updateStatusLast updated
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		April 25, 2019
      KB4493453      		Mitigated
      		May 10, 2019
      10:35 AM PT
      System may be unresponsive after restart if ArcaBit antivirus software installed
      Devices with ArcaBit antivirus software installed may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493472      		Mitigated
      		May 08, 2019
      03:29 PM PT
      System may be unresponsive after restart if Avira antivirus software installed
      Devices with Avira antivirus software installed may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493472      		Mitigated
      		May 03, 2019
      08:50 AM PT
      Authentication may fail for services after the Kerberos ticket expires
      Authentication may fail for services that require unconstrained delegation after the Kerberos ticket expires.

      See details >      		March 12, 2019
      KB4489878      		Mitigated
      		April 25, 2019
      02:00 PM PT
      System unresponsive after restart if Sophos Endpoint Protection installed
      Devices with Sophos Endpoint Protection installed and managed by Sophos Central or Sophos Enterprise Console (SEC) may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493472      		Mitigated
      		April 25, 2019
      02:00 PM PT
      System may be unresponsive after restart with certain McAfee antivirus products
      Devices with McAfee Endpoint Security Threat Prevention 10.x, Host Intrusion Prevention 8.0, or VirusScan Enterprise 8.8 may be slow or unresponsive at startup.

      See details >      		April 09, 2019
      KB4493472      		Mitigated
      		April 25, 2019
      02:00 PM PT
      System may be unresponsive after restart if ArcaBit antivirus software installed
      Devices with ArcaBit antivirus software installed may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493472      		Resolved
      		May 14, 2019
      01:23 PM PT
      System unresponsive after restart if Sophos Endpoint Protection installed
      Devices with Sophos Endpoint Protection installed and managed by Sophos Central or Sophos Enterprise Console (SEC) may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493472      		Resolved
      		May 14, 2019
      01:22 PM PT
      System may be unresponsive after restart if Avira antivirus software installed
      Devices with Avira antivirus software installed may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493472      		Resolved
      		May 14, 2019
      01:21 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		April 25, 2019
      KB4493453      		Resolved
      KB4499164      		May 14, 2019
      01:18 PM PT
      Authentication may fail for services after the Kerberos ticket expires
      Authentication may fail for services that require unconstrained delegation after the Kerberos ticket expires.

      See details >      		March 12, 2019
      KB4489878      		Resolved
      KB4499164      		May 14, 2019
      01:17 PM PT
      Devices may not respond at login or Welcome screen if running certain Avast software
      Devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software may become unresponsive after restart.

      See details >      		April 09, 2019
      KB4493472      		Resolved
      		April 25, 2019
      02:00 PM PT
      " @@ -82,7 +82,7 @@ sections: - type: markdown text: " - +
      DetailsOriginating updateStatusHistory
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Workaround: Until a resolution is released, we recommend switching to a different Japanese font, such as Yu Gothic or MS Mincho. Alternatively, you can uninstall the optional update.

      Next steps: Microsoft is working on a resolution and estimates a solution will be available in mid-May.

      Back to top      		April 25, 2019
      KB4493453      		Mitigated
      		Last updated:
      May 10, 2019
      10:35 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Resolution: This issue has been resolved.

      Back to top      		April 25, 2019
      KB4493453      		Resolved
      KB4499164      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      " @@ -91,10 +91,10 @@ sections: - type: markdown text: " - - - + + +
      DetailsOriginating updateStatusHistory
      System may be unresponsive after restart if ArcaBit antivirus software installed
      Microsoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493472.

      Microsoft has temporarily blocked devices from receiving this update if ArcaBit antivirus software is installed.

      Affected platforms:
      • Client: Windows 8.1; Windows 7 SP1
      • Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1
      Workaround: ArcaBit has released an update to address this issue. For more information, see the Arcabit support article.

      Back to top      		April 09, 2019
      KB4493472      		Mitigated
      		Last updated:
      May 08, 2019
      03:29 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System may be unresponsive after restart if Avira antivirus software installed
      Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493472.

      Microsoft has temporarily blocked devices from receiving this update if Avira antivirus software is installed.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1 
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Next steps: Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article.

      Back to top      		April 09, 2019
      KB4493472      		Mitigated
      		Last updated:
      May 03, 2019
      08:50 AM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System unresponsive after restart if Sophos Endpoint Protection installed
      Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing KB4493472.

      Microsoft has temporarily blocked devices from receiving this update if the Sophos Endpoint is installed until a solution is available.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.

      Back to top      		April 09, 2019
      KB4493472      		Mitigated
      		Last updated:
      April 25, 2019
      02:00 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System may be unresponsive after restart with certain McAfee antivirus products
      Microsoft and McAfee have identified an issue on devices with McAfee Endpoint Security (ENS) Threat Prevention 10.x or McAfee Host Intrusion Prevention (Host IPS) 8.0 or McAfee VirusScan Enterprise (VSE) 8.8 installed. It may cause the system to have slow startup or become unresponsive at restart after installing this update. 

      Affected platforms:
      • Client:  Windows 8.1; Windows 7 SP1
      • Server:  Windows Server 2012 R2; Windows Server 2008 R2 SP1
      Workaround: Guidance for McAfee customers can be found in the following McAfee support articles: 
      Next steps: We are presently investigating this issue with McAfee. We will provide an update once we have more information.

      Back to top      		April 09, 2019
      KB4493472      		Mitigated
      		Last updated:
      April 25, 2019
      02:00 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System may be unresponsive after restart if ArcaBit antivirus software installed
      Microsoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493472.

      Affected platforms:
      • Client: Windows 8.1; Windows 7 SP1
      • Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1
      Resolution: This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. ArcaBit has released an update to address this issue. For more information, see the Arcabit support article.

      Back to top      		April 09, 2019
      KB4493472      		Resolved
      		Resolved:
      May 14, 2019
      01:23 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System unresponsive after restart if Sophos Endpoint Protection installed
      Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing KB4493472.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Resolution: This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Sophos has released an update to address this issue. Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.

      Back to top      		April 09, 2019
      KB4493472      		Resolved
      		Resolved:
      May 14, 2019
      01:22 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System may be unresponsive after restart if Avira antivirus software installed
      Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493472.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1 
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Resolution: This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article.

      Back to top      		April 09, 2019
      KB4493472      		Resolved
      		Resolved:
      May 14, 2019
      01:21 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      Devices may not respond at login or Welcome screen if running certain Avast software
      Microsoft and Avast have identified an issue on devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software after you install KB4493472 and restart. Devices may become unresponsive at the login or Welcome screen. Additionally, you may be unable to log in or log in after an extended period of time.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1 
      • Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1 
      Resolution: Avast has released emergency updates to address this issue. For more information and AV update schedule, see the Avast support KB article.

      Back to top      		April 09, 2019
      KB4493472      		Resolved
      		Resolved:
      April 25, 2019
      02:00 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      " @@ -104,6 +104,6 @@ sections: - type: markdown text: " - +
      DetailsOriginating updateStatusHistory
      Authentication may fail for services after the Kerberos ticket expires
      After installing KB4489878, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails.

      Affected platforms: 
      • Client: Windows 7 SP1
      • Server: Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Workaround: To mitigate this issue, use one of the following options:
      • Option 1: Purge the Kerberos tickets on the application server. After the Kerberos ticket expires, the issue will occur again, and you must purge the tickets again.
      • Option 2: If purging does not mitigate the issue, restart the application; for example, restart the Internet Information Services (IIS) app pool associated with the SQL server.
      • Option 3: Use constrained delegation.
      Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.

      Back to top      		March 12, 2019
      KB4489878      		Mitigated
      		Last updated:
      April 25, 2019
      02:00 PM PT

      Opened:
      March 12, 2019
      10:00 AM PT
      Authentication may fail for services after the Kerberos ticket expires
      After installing KB4489878, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails.

      Affected platforms: 
      • Client: Windows 7 SP1
      • Server: Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Resolution: This issue was resolved in KB4499164.

      Back to top      		March 12, 2019
      KB4489878      		Resolved
      KB4499164      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      March 12, 2019
      10:00 AM PT
      " diff --git a/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml b/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml index a16b0e0d20..95db74d05b 100644 --- a/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml +++ b/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml @@ -60,13 +60,13 @@ sections: - type: markdown text: "
      This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

      - - - - + + + +
      SummaryOriginating updateStatusLast updated
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		April 25, 2019
      KB4493443      		Mitigated
      		May 10, 2019
      10:35 AM PT
      System may be unresponsive after restart if ArcaBit antivirus software installed
      Devices with ArcaBit antivirus software installed may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493446      		Mitigated
      		May 08, 2019
      03:29 PM PT
      System may be unresponsive after restart if Avira antivirus software installed
      Devices with Avira antivirus software installed may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493446      		Mitigated
      		May 03, 2019
      08:50 AM PT
      Issue using PXE to start a device from WDS
      There may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension.

      See details >      		March 12, 2019
      KB4489881      		Mitigated
      		April 25, 2019
      02:00 PM PT
      System unresponsive after restart if Sophos Endpoint Protection installed
      Devices with Sophos Endpoint Protection installed and managed by Sophos Central or Sophos Enterprise Console (SEC) may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493446      		Mitigated
      		April 25, 2019
      02:00 PM PT
      Certain operations performed on a Cluster Shared Volume may fail
      Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”.

      See details >      		January 08, 2019
      KB4480963      		Mitigated
      		April 25, 2019
      02:00 PM PT
      System may be unresponsive after restart with certain McAfee antivirus products
      Devices with McAfee Endpoint Security Threat Prevention 10.x, Host Intrusion Prevention 8.0, or VirusScan Enterprise 8.8 may be slow or unresponsive at startup.

      See details >      		April 09, 2019
      KB4493446      		Mitigated
      		April 18, 2019
      05:00 PM PT
      System may be unresponsive after restart if ArcaBit antivirus software installed
      Devices with ArcaBit antivirus software installed may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493446      		Resolved
      		May 14, 2019
      01:22 PM PT
      System unresponsive after restart if Sophos Endpoint Protection installed
      Devices with Sophos Endpoint Protection installed and managed by Sophos Central or Sophos Enterprise Console (SEC) may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493446      		Resolved
      		May 14, 2019
      01:22 PM PT
      System may be unresponsive after restart if Avira antivirus software installed
      Devices with Avira antivirus software installed may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493446      		Resolved
      		May 14, 2019
      01:21 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		April 25, 2019
      KB4493443      		Resolved
      KB4499151      		May 14, 2019
      01:18 PM PT
      Devices may not respond at login or Welcome screen if running certain Avast software
      Devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software may become unresponsive after restart.

      See details >      		April 09, 2019
      KB4493446      		Resolved
      		April 25, 2019
      02:00 PM PT
      " @@ -83,7 +83,7 @@ sections: - type: markdown text: " - +
      DetailsOriginating updateStatusHistory
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Workaround: Until a resolution is released, we recommend switching to a different Japanese font, such as Yu Gothic or MS Mincho. Alternatively, you can uninstall the optional update.

      Next steps: Microsoft is working on a resolution and estimates a solution will be available in mid-May.

      Back to top      		April 25, 2019
      KB4493443      		Mitigated
      		Last updated:
      May 10, 2019
      10:35 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Resolution: This issue has been resolved.

      Back to top      		April 25, 2019
      KB4493443      		Resolved
      KB4499151      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      " @@ -92,10 +92,10 @@ sections: - type: markdown text: " - - - + + +
      DetailsOriginating updateStatusHistory
      System may be unresponsive after restart if ArcaBit antivirus software installed
      Microsoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493446.

      Microsoft has temporarily blocked devices from receiving this update if ArcaBit antivirus software is installed.

      Affected platforms:
      • Client: Windows 8.1; Windows 7 SP1
      • Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1
      Workaround: ArcaBit has released an update to address this issue. For more information, see the Arcabit support article.

      Back to top      		April 09, 2019
      KB4493446      		Mitigated
      		Last updated:
      May 08, 2019
      03:29 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System may be unresponsive after restart if Avira antivirus software installed
      Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493446.

      Microsoft has temporarily blocked devices from receiving this update if Avira antivirus software is installed.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1 
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Next steps: Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article.

      Back to top      		April 09, 2019
      KB4493446      		Mitigated
      		Last updated:
      May 03, 2019
      08:50 AM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System unresponsive after restart if Sophos Endpoint Protection installed
      Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing KB4493446.

      Microsoft has temporarily blocked devices from receiving this update if the Sophos Endpoint is installed until a solution is available.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.

      Back to top      		April 09, 2019
      KB4493446      		Mitigated
      		Last updated:
      April 25, 2019
      02:00 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System may be unresponsive after restart with certain McAfee antivirus products
      Microsoft and McAfee have identified an issue on devices with McAfee Endpoint Security (ENS) Threat Prevention 10.x or McAfee Host Intrusion Prevention (Host IPS) 8.0 or McAfee VirusScan Enterprise (VSE) 8.8 installed. It may cause the system to have slow startup or become unresponsive at restart after installing this update. 

      Affected platforms:
      • Client:  Windows 8.1; Windows 7 SP1
      • Server:  Windows Server 2012 R2; Windows Server 2008 R2 SP1
      Workaround: Guidance for McAfee customers can be found in the following McAfee support articles:  
      Next steps: We are presently investigating this issue with McAfee. We will provide an update once we have more information. 

      Back to top      		April 09, 2019
      KB4493446      		Mitigated
      		Last updated:
      April 18, 2019
      05:00 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System may be unresponsive after restart if ArcaBit antivirus software installed
      Microsoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493446.

      Affected platforms:
      • Client: Windows 8.1; Windows 7 SP1
      • Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1
      Resolution: This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. ArcaBit has released an update to address this issue. For more information, see the Arcabit support article.

      Back to top      		April 09, 2019
      KB4493446      		Resolved
      		Resolved:
      May 14, 2019
      01:22 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System unresponsive after restart if Sophos Endpoint Protection installed
      Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing KB4493446.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Resolution: This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Sophos has released an update to address this issue. Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.

      Back to top      		April 09, 2019
      KB4493446      		Resolved
      		Resolved:
      May 14, 2019
      01:22 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System may be unresponsive after restart if Avira antivirus software installed
      Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493446.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1 
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Resolution: This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article.

      Back to top      		April 09, 2019
      KB4493446      		Resolved
      		Resolved:
      May 14, 2019
      01:21 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      Devices may not respond at login or Welcome screen if running certain Avast software
      Microsoft and Avast have identified an issue on devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software after you install KB4493446 and restart. Devices may become unresponsive at the login or Welcome screen. Additionally, you may be unable to log in or log in after an extended period of time.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1 
      • Server: Windows Server 2012 R2; Windows Server 2008 R2 SP1 
      Resolution: Avast has released emergency updates to address this issue. For more information and AV update schedule, see the Avast support KB article.

      Back to top      		April 09, 2019
      KB4493446      		Resolved
      		Resolved:
      April 25, 2019
      02:00 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      " diff --git a/windows/release-information/status-windows-server-2008-sp2.yml b/windows/release-information/status-windows-server-2008-sp2.yml index 689abfde38..b87565393b 100644 --- a/windows/release-information/status-windows-server-2008-sp2.yml +++ b/windows/release-information/status-windows-server-2008-sp2.yml @@ -60,9 +60,10 @@ sections: - type: markdown text: "
      This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

      - - - + + + +
      SummaryOriginating updateStatusLast updated
      System may be unresponsive after restart if Avira antivirus software installed
      Devices with Avira antivirus software installed may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493471      		Mitigated
      		May 03, 2019
      08:51 AM PT
      System unresponsive after restart if Sophos Endpoint Protection installed
      Devices with Sophos Endpoint Protection installed and managed by Sophos Central or Sophos Enterprise Console (SEC) may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493471      		Mitigated
      		April 25, 2019
      02:00 PM PT
      Authentication may fail for services after the Kerberos ticket expires
      Authentication may fail for services that require unconstrained delegation after the Kerberos ticket expires.

      See details >      		March 12, 2019
      KB4489880      		Mitigated
      		April 25, 2019
      02:00 PM PT
      System unresponsive after restart if Sophos Endpoint Protection installed
      Devices with Sophos Endpoint Protection installed and managed by Sophos Central or Sophos Enterprise Console (SEC) may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493471      		Resolved
      		May 14, 2019
      01:21 PM PT
      System may be unresponsive after restart if Avira antivirus software installed
      Devices with Avira antivirus software installed may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493471      		Resolved
      		May 14, 2019
      01:19 PM PT
      Authentication may fail for services after the Kerberos ticket expires
      Authentication may fail for services that require unconstrained delegation after the Kerberos ticket expires.

      See details >      		March 12, 2019
      KB4489880      		Resolved
      KB4499149      		May 14, 2019
      01:18 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		April 25, 2019
      KB4493460      		Resolved
      KB4499149      		May 14, 2019
      01:18 PM PT
      " @@ -73,13 +74,22 @@ sections:
      " +- title: May 2019 +- items: + - type: markdown + text: " + + +
      DetailsOriginating updateStatusHistory
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Resolution: This issue has been resolved.

      Back to top      		April 25, 2019
      KB4493460      		Resolved
      KB4499149      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      + " + - title: April 2019 - items: - type: markdown text: " - - + +
      DetailsOriginating updateStatusHistory
      System may be unresponsive after restart if Avira antivirus software installed
      Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493471.

      Microsoft has temporarily blocked devices from receiving this update if Avira antivirus software is installed.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1 
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Next steps: Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article

      Back to top      		April 09, 2019
      KB4493471      		Mitigated
      		Last updated:
      May 03, 2019
      08:51 AM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System unresponsive after restart if Sophos Endpoint Protection installed
      Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing KB4493471.

      Microsoft has temporarily blocked devices from receiving this update if the Sophos Endpoint is installed until a solution is available.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.

      Back to top      		April 09, 2019
      KB4493471      		Mitigated
      		Last updated:
      April 25, 2019
      02:00 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System unresponsive after restart if Sophos Endpoint Protection installed
      Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing KB4493471.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Resolution: This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Sophos has released an update to address this issue. Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.

      Back to top      		April 09, 2019
      KB4493471      		Resolved
      		Resolved:
      May 14, 2019
      01:21 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System may be unresponsive after restart if Avira antivirus software installed
      Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493471.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1 
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Resolution: This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article.

      Back to top      		April 09, 2019
      KB4493471      		Resolved
      		Resolved:
      May 14, 2019
      01:19 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      " @@ -88,6 +98,6 @@ sections: - type: markdown text: " - +
      DetailsOriginating updateStatusHistory
      Authentication may fail for services after the Kerberos ticket expires
      After installing KB4489880, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails.

      Affected platforms: 
      • Client: Windows 7 SP1
      • Server: Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Workaround: To mitigate this issue, use one of the following options:
      • Option 1: Purge the Kerberos tickets on the application server. After the Kerberos ticket expires, the issue will occur again, and you must purge the tickets again.
      • Option 2: If purging does not mitigate the issue, restart the application; for example, restart the Internet Information Services (IIS) app pool associated with the SQL server.
      • Option 3: Use constrained delegation.
      Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.

      Back to top      		March 12, 2019
      KB4489880      		Mitigated
      		Last updated:
      April 25, 2019
      02:00 PM PT

      Opened:
      March 12, 2019
      10:00 AM PT
      Authentication may fail for services after the Kerberos ticket expires
      After installing KB4489880, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails.

      Affected platforms: 
      • Client: Windows 7 SP1
      • Server: Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Resolution: This issue was resolved in KB4499149.

      Back to top      		March 12, 2019
      KB4489880      		Resolved
      KB4499149      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      March 12, 2019
      10:00 AM PT
      " diff --git a/windows/release-information/status-windows-server-2012.yml b/windows/release-information/status-windows-server-2012.yml index be5f206c02..3ad111d345 100644 --- a/windows/release-information/status-windows-server-2012.yml +++ b/windows/release-information/status-windows-server-2012.yml @@ -60,11 +60,11 @@ sections: - type: markdown text: "
      This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

      - - - + + +
      SummaryOriginating updateStatusLast updated
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		April 25, 2019
      KB4493462      		Mitigated
      		May 10, 2019
      10:35 AM PT
      System may be unresponsive after restart if Avira antivirus software installed
      Devices with Avira antivirus software installed may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493451      		Mitigated
      		May 03, 2019
      08:51 AM PT
      Issue using PXE to start a device from WDS
      There may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension.

      See details >      		March 12, 2019
      KB4489891      		Mitigated
      		April 25, 2019
      02:00 PM PT
      System unresponsive after restart if Sophos Endpoint Protection installed
      Devices with Sophos Endpoint Protection installed and managed by Sophos Central or Sophos Enterprise Console (SEC) may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493451      		Mitigated
      		April 25, 2019
      02:00 PM PT
      Certain operations performed on a Cluster Shared Volume may fail
      Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”.

      See details >      		January 08, 2019
      KB4480975      		Mitigated
      		April 25, 2019
      02:00 PM PT
      System unresponsive after restart if Sophos Endpoint Protection installed
      Devices with Sophos Endpoint Protection installed and managed by Sophos Central or Sophos Enterprise Console (SEC) may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493451      		Resolved
      		May 14, 2019
      01:21 PM PT
      System may be unresponsive after restart if Avira antivirus software installed
      Devices with Avira antivirus software installed may become unresponsive upon restart.

      See details >      		April 09, 2019
      KB4493451      		Resolved
      		May 14, 2019
      01:19 PM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

      See details >      		April 25, 2019
      KB4493462      		Resolved
      KB4499171      		May 14, 2019
      01:18 PM PT
      " @@ -80,7 +80,7 @@ sections: - type: markdown text: " - +
      DetailsOriginating updateStatusHistory
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Workaround: Until a resolution is released, we recommend switching to a different Japanese font, such as Yu Gothic or MS Mincho. Alternatively, you can uninstall the optional update.

      Next steps: Microsoft is working on a resolution and estimates a solution will be available in mid-May.

      Back to top      		April 25, 2019
      KB4493462      		Mitigated
      		Last updated:
      May 10, 2019
      10:35 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      Layout and cell size of Excel sheets may change when using MS UI Gothic
      When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.

      Affected platforms:
      • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
      • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
      Resolution: This issue has been resolved.

      Back to top      		April 25, 2019
      KB4493462      		Resolved
      KB4499171      		Resolved:
      May 14, 2019
      10:00 AM PT

      Opened:
      May 10, 2019
      10:35 AM PT
      " @@ -89,8 +89,8 @@ sections: - type: markdown text: " - - + +
      DetailsOriginating updateStatusHistory
      System may be unresponsive after restart if Avira antivirus software installed
      Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493451.

      Microsoft has temporarily blocked devices from receiving this update if Avira antivirus software is installed.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1 
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Next steps: Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article.

      Back to top      		April 09, 2019
      KB4493451      		Mitigated
      		Last updated:
      May 03, 2019
      08:51 AM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System unresponsive after restart if Sophos Endpoint Protection installed
      Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing KB4493451.

      Microsoft has temporarily blocked devices from receiving this update if the Sophos Endpoint is installed until a solution is available.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.

      Back to top      		April 09, 2019
      KB4493451      		Mitigated
      		Last updated:
      April 25, 2019
      02:00 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System unresponsive after restart if Sophos Endpoint Protection installed
      Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to become unresponsive upon restart after installing KB4493451.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Resolution: This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Sophos has released an update to address this issue. Guidance for Sophos Endpoint and Sophos Enterprise Console customers can be found in the Sophos support article.

      Back to top      		April 09, 2019
      KB4493451      		Resolved
      		Resolved:
      May 14, 2019
      01:21 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      System may be unresponsive after restart if Avira antivirus software installed
      Microsoft and Avira have identified an issue on devices with Avira antivirus software installed that may cause the system to become unresponsive upon restart after installing KB4493451.

      Affected platforms: 
      • Client: Windows 8.1; Windows 7 SP1 
      • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
      Resolution: This issue has been resolved. Microsoft has removed the temporary block for all affected Windows updates. Avira has released an automatic update to address this issue. Guidance for Avira customers can be found in the Avira support article.

      Back to top      		April 09, 2019
      KB4493451      		Resolved
      		Resolved:
      May 14, 2019
      01:19 PM PT

      Opened:
      April 09, 2019
      10:00 AM PT
      " diff --git a/windows/release-information/windows-message-center.yml b/windows/release-information/windows-message-center.yml index bcea3b01d7..65b9ab4d01 100644 --- a/windows/release-information/windows-message-center.yml +++ b/windows/release-information/windows-message-center.yml @@ -50,13 +50,24 @@ sections: text: " + + + For more information about the Windows 10 update servicing cadence, please see the Window IT Pro blog. +
      MessageDate
      Reminder: Install the latest SSU for a smoother update experience
      We strongly recommend that you install the latest servicing stack update (SSU) before installing any Windows update; especially as an SSU may be a prerequisite for some updates. If you have difficulty installing Windows updates, verify that you have installed the latest SSU package for your version of Windows and then try installing the update again. Links to the latest SSU are always provided in the “How to get this update” section of each update KB article (e.g., KB4494441). For more information about SSUs, see our Servicing stack updates guidance.
      		May 14, 2019
      10:00 AM PT
      Take action: Update Remote Desktop Services on older versions of Windows
      Today, we released fixes for a critical wormable, remote code execution vulnerability (CVE-2019-0708) in Remote Desktop Services—formerly known as Terminal Services. This vulnerability affects Windows 7, Windows Server 2008 R2, and earlier versions of Windows nearing end of support. It does not affect Windows 8, Windows Server 2012, or newer operating systems. While we have not observed attacks exploiting this vulnerability, affected systems should be patched with priority. Here is what you need to know:

      +Call to action: +
        +
      • If you are running a supported version of Windows and have automatic updates enabled, you are automatically protected and do not need to take any action.
        • +
      • If you are managing updates on behalf of your organization, you should download the latest updates from the Microsoft Security Update Guide and apply them to your Windows 7, Windows Server 2008 R2, and Windows Server 2008 devices as soon as possible.
        • +
      +Given the potential impact to customers and their businesses, we have also released security updates for Windows XP and Windows Server 2003, even though these operating systems have reached end of support (except by custom support agreements). While we recommend that you upgrade to the current version of Windows to benefit from the latest security protections, these updates are available from the Microsoft Update Catalog only. For more information, see KB4500705. +
      +      		May 14, 2019
      10:00 AM PT
      Reminder: Windows 10 update servicing cadence
      This month we received questions about the cadence of updates we released in April and May 2019. Here's a quick recap of our releases and servicing cadence:
      • April 9, 2019 was the regular Update Tuesday release for all versions of Windows.
        • -
      • May 1, 2019 was an \"optional,\" out of band non-security update (OOB) for Windows 10, version 1809. It was released to Microsoft Catalog and WSUS, providing a critical fix for our OEM partners.
        • +
      • May 1, 2019 was an \"optional,\" out of band non-security update (OOB) for Windows 10, version 1809. It was released to Microsoft Catalog and WSUS, providing a critical fix for our OEM partners.
      • May 3, 2019 was the \"optional\" Windows 10, version 1809 \"C\" release for April. This update contained important Japanese era packages for commercial customers to preview. It was released later than expected and mistakenly targeted as \"required\" (instead of \"optional\") for consumers, which pushed the update out to customers and required a reboot. Within 24 hours of receiving customer reports, we corrected the targeting logic and mitigated the issue.
      - For more information about the Windows 10 update servicing cadence, please see the Window IT Pro blog.
      		May 10, 2019
      10:00 AM PT
      May 10, 2019
      10:00 AM PT
      Take action: Install servicing stack update for Windows Server 2008 SP2 for SHA-2 code sign support
      A standalone update, KB4493730, that introduce SHA-2 code sign support for the servicing stack (SSU) was released today as a security update.      		April 19, 2019
      10:00 AM PT
      The benefits of Windows 10 Dynamic Update
      Dynamic Update can help organizations and end users alike ensure that their Windows 10 devices have the latest feature update content (as part of an in-place upgrade)—and preserve precious features on demand (FODs) and language packs (LPs) that may have been previously installed.