resolved warnings

This commit is contained in:
Siddarth Mandalika
2021-10-20 16:19:37 +05:30
parent 7e436a1ff9
commit 50a8050dd5
4 changed files with 6 additions and 6 deletions

View File

@ -696,7 +696,7 @@ In this procedure, the workstations are dedicated to domain administrators. By s
1. Right-click **Windows Firewall with Advanced Security LDAP://path**, and > **Properties**. 1. Right-click **Windows Firewall with Advanced Security LDAP://path**, and > **Properties**.
![Local accounts for an Active Directory](images/adlocalaccounts-proc1-sample6.png) ![Local accounts for Active Directory](images/adlocalaccounts-proc1-sample6.png)
2. On each profile, ensure that the firewall is enabled and that inbound connections are set to **Block all connections**. 2. On each profile, ensure that the firewall is enabled and that inbound connections are set to **Block all connections**.
@ -791,7 +791,7 @@ For this procedure, do not link accounts to the OU that contain workstations for
6. Click **Add User or Group** > **Browse**, type **Domain Admins**, and > **OK**. 6. Click **Add User or Group** > **Browse**, type **Domain Admins**, and > **OK**.
![Local accounts for an AD](images/adlocalaccounts-proc2-sample5.png) ![Local accounts for AD](images/adlocalaccounts-proc2-sample5.png)
**Note** **Note**
You can optionally add any groups that contain server administrators who you want to restrict from signing in to workstations. You can optionally add any groups that contain server administrators who you want to restrict from signing in to workstations.
@ -804,7 +804,7 @@ For this procedure, do not link accounts to the OU that contain workstations for
1. Right-click the workstation OU, and then > **Link an Existing GPO**. 1. Right-click the workstation OU, and then > **Link an Existing GPO**.
![Local accounts for an Active Directory](images/adlocalaccounts-proc2-sample6.png) ![Local accounts representation for an Active Directory](images/adlocalaccounts-proc2-sample6.png)
2. Select the GPO that you just created, and > **OK**. 2. Select the GPO that you just created, and > **OK**.

View File

@ -16,7 +16,7 @@ localizationpriority: medium
ms.date: 08/19/2018 ms.date: 08/19/2018
ms.reviewer: ms.reviewer:
--- ---
# Validate and Deploy Multifactor Authentication # Validate and Deploy Multifactor Authentication feature
**Applies to** **Applies to**

View File

@ -16,7 +16,7 @@ localizationpriority: medium
ms.date: 08/19/2018 ms.date: 08/19/2018
ms.reviewer: ms.reviewer:
--- ---
# Validate and Deploy Multifactor Authentication # Validate and Deploy Multifactor Authentication (MFA)
> [!IMPORTANT] > [!IMPORTANT]
> As of July 1, 2019, Microsoft will no longer offer MFA Server for new deployments. New customers who would like to require multifactor authentication from their users should use cloud-based Azure AD Multi-Factor Authentication. Existing customers who have activated MFA Server prior to July 1 will be able to download the latest version, future updates and generate activation credentials as usual. > As of July 1, 2019, Microsoft will no longer offer MFA Server for new deployments. New customers who would like to require multifactor authentication from their users should use cloud-based Azure AD Multi-Factor Authentication. Existing customers who have activated MFA Server prior to July 1 will be able to download the latest version, future updates and generate activation credentials as usual.

View File

@ -2,7 +2,7 @@
title: Guidelines for troubleshooting BitLocker title: Guidelines for troubleshooting BitLocker
description: Describes approaches for investigating BitLocker issues, including how to gather diagnostic information description: Describes approaches for investigating BitLocker issues, including how to gather diagnostic information
ms.reviewer: kaushika ms.reviewer: kaushika
ms.technology: windows ms.technology: windows-sec
ms.prod: m365-security ms.prod: m365-security
ms.sitesec: library ms.sitesec: library
ms.localizationpriority: medium ms.localizationpriority: medium