mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-17 15:57:23 +00:00
Merged PR 11779: Fixed what's new merge issue - live publish
This commit is contained in:
parent
666d2b5cf8
commit
504c7bf68b
@ -8,7 +8,7 @@ ms.mktglfcycl: deploy
|
|||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.localizationpriority: none
|
ms.localizationpriority: none
|
||||||
author: Mir0sh
|
author: Mir0sh
|
||||||
ms.date: 04/19/2017
|
ms.date: 10/02/2018
|
||||||
---
|
---
|
||||||
|
|
||||||
# Audit IPsec Driver
|
# Audit IPsec Driver
|
||||||
@ -56,7 +56,7 @@ This subcategory is outside the scope of this document.
|
|||||||
|
|
||||||
## 5478(S): IPsec Services has started successfully.
|
## 5478(S): IPsec Services has started successfully.
|
||||||
|
|
||||||
## 5479(): IPsec Services has been shut down successfully. The shutdown of IPsec Services can put the computer at greater risk of network attack or expose the computer to potential security risks.
|
## 5479(S): IPsec Services has been shut down successfully. The shutdown of IPsec Services can put the computer at greater risk of network attack or expose the computer to potential security risks.
|
||||||
|
|
||||||
## 5480(F): IPsec Services failed to get the complete list of network interfaces on the computer. This poses a potential security risk because some of the network interfaces may not get the protection provided by the applied IPsec filters. Use the IP Security Monitor snap-in to diagnose the problem.
|
## 5480(F): IPsec Services failed to get the complete list of network interfaces on the computer. This poses a potential security risk because some of the network interfaces may not get the protection provided by the applied IPsec filters. Use the IP Security Monitor snap-in to diagnose the problem.
|
||||||
|
|
||||||
|
@ -8,7 +8,7 @@ ms.mktglfcycl: deploy
|
|||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.localizationpriority: none
|
ms.localizationpriority: none
|
||||||
author: Mir0sh
|
author: Mir0sh
|
||||||
ms.date: 04/19/2017
|
ms.date: 10/02/2018
|
||||||
---
|
---
|
||||||
|
|
||||||
# Audit IPsec Extended Mode
|
# Audit IPsec Extended Mode
|
||||||
@ -28,17 +28,17 @@ Audit IPsec Extended Mode subcategory is out of scope of this document, because
|
|||||||
| Member Server | IF | IF | IF | IF | IF - This subcategory is mainly used for IPsec Extended Mode troubleshooting, or for tracing or monitoring IPsec Extended Mode operations. |
|
| Member Server | IF | IF | IF | IF | IF - This subcategory is mainly used for IPsec Extended Mode troubleshooting, or for tracing or monitoring IPsec Extended Mode operations. |
|
||||||
| Workstation | IF | IF | IF | IF | IF - This subcategory is mainly used for IPsec Extended Mode troubleshooting, or for tracing or monitoring IPsec Extended Mode operations. |
|
| Workstation | IF | IF | IF | IF | IF - This subcategory is mainly used for IPsec Extended Mode troubleshooting, or for tracing or monitoring IPsec Extended Mode operations. |
|
||||||
|
|
||||||
## 4978: During Extended Mode negotiation, IPsec received an invalid negotiation packet. If this problem persists, it could indicate a network issue or an attempt to modify or replay this negotiation.
|
## 4978(S): During Extended Mode negotiation, IPsec received an invalid negotiation packet. If this problem persists, it could indicate a network issue or an attempt to modify or replay this negotiation.
|
||||||
|
|
||||||
## 4979: IPsec Main Mode and Extended Mode security associations were established.
|
## 4979(S): IPsec Main Mode and Extended Mode security associations were established.
|
||||||
|
|
||||||
## 4980: IPsec Main Mode and Extended Mode security associations were established.
|
## 4980(S): IPsec Main Mode and Extended Mode security associations were established.
|
||||||
|
|
||||||
## 4981: IPsec Main Mode and Extended Mode security associations were established.
|
## 4981(S): IPsec Main Mode and Extended Mode security associations were established.
|
||||||
|
|
||||||
## 4982: IPsec Main Mode and Extended Mode security associations were established.
|
## 4982(S): IPsec Main Mode and Extended Mode security associations were established.
|
||||||
|
|
||||||
## 4983: An IPsec Extended Mode negotiation failed. The corresponding Main Mode security association has been deleted.
|
## 4983(S): An IPsec Extended Mode negotiation failed. The corresponding Main Mode security association has been deleted.
|
||||||
|
|
||||||
## 4984: An IPsec Extended Mode negotiation failed. The corresponding Main Mode security association has been deleted.
|
## 4984(S): An IPsec Extended Mode negotiation failed. The corresponding Main Mode security association has been deleted.
|
||||||
|
|
||||||
|
@ -8,7 +8,7 @@ ms.mktglfcycl: deploy
|
|||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.localizationpriority: none
|
ms.localizationpriority: none
|
||||||
author: Mir0sh
|
author: Mir0sh
|
||||||
ms.date: 04/19/2017
|
ms.date: 10/02/2018
|
||||||
---
|
---
|
||||||
|
|
||||||
# Audit IPsec Main Mode
|
# Audit IPsec Main Mode
|
||||||
@ -28,21 +28,21 @@ Audit IPsec Main Mode subcategory is out of scope of this document, because this
|
|||||||
| Member Server | IF | IF | IF | IF | IF - This subcategory is mainly used for IPsec Main Mode troubleshooting, or for tracing or monitoring IPsec Main Mode operations. |
|
| Member Server | IF | IF | IF | IF | IF - This subcategory is mainly used for IPsec Main Mode troubleshooting, or for tracing or monitoring IPsec Main Mode operations. |
|
||||||
| Workstation | IF | IF | IF | IF | IF - This subcategory is mainly used for IPsec Main Mode troubleshooting, or for tracing or monitoring IPsec Main Mode operations. |
|
| Workstation | IF | IF | IF | IF | IF - This subcategory is mainly used for IPsec Main Mode troubleshooting, or for tracing or monitoring IPsec Main Mode operations. |
|
||||||
|
|
||||||
## 4646: Security ID: %1
|
## 4646(S): Security ID: %1
|
||||||
|
|
||||||
## 4650: An IPsec Main Mode security association was established. Extended Mode was not enabled. Certificate authentication was not used.
|
## 4650(S): An IPsec Main Mode security association was established. Extended Mode was not enabled. Certificate authentication was not used.
|
||||||
|
|
||||||
## 4651: An IPsec Main Mode security association was established. Extended Mode was not enabled. A certificate was used for authentication.
|
## 4651(S): An IPsec Main Mode security association was established. Extended Mode was not enabled. A certificate was used for authentication.
|
||||||
|
|
||||||
## 4652: An IPsec Main Mode negotiation failed.
|
## 4652(F): An IPsec Main Mode negotiation failed.
|
||||||
|
|
||||||
## 4653: An IPsec Main Mode negotiation failed.
|
## 4653(F): An IPsec Main Mode negotiation failed.
|
||||||
|
|
||||||
## 4655: An IPsec Main Mode security association ended.
|
## 4655(S): An IPsec Main Mode security association ended.
|
||||||
|
|
||||||
## 4976: During Main Mode negotiation, IPsec received an invalid negotiation packet. If this problem persists, it could indicate a network issue or an attempt to modify or replay this negotiation.
|
## 4976(S): During Main Mode negotiation, IPsec received an invalid negotiation packet. If this problem persists, it could indicate a network issue or an attempt to modify or replay this negotiation.
|
||||||
|
|
||||||
## 5049: An IPsec Security Association was deleted.
|
## 5049(S): An IPsec Security Association was deleted.
|
||||||
|
|
||||||
## 5453: An IPsec negotiation with a remote computer failed because the IKE and AuthIP IPsec Keying Modules (IKEEXT) service is not started.
|
## 5453(S): An IPsec negotiation with a remote computer failed because the IKE and AuthIP IPsec Keying Modules (IKEEXT) service is not started.
|
||||||
|
|
||||||
|
@ -8,7 +8,7 @@ ms.mktglfcycl: deploy
|
|||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.localizationpriority: none
|
ms.localizationpriority: none
|
||||||
author: Mir0sh
|
author: Mir0sh
|
||||||
ms.date: 04/19/2017
|
ms.date: 10/02/2018
|
||||||
---
|
---
|
||||||
|
|
||||||
# Audit IPsec Quick Mode
|
# Audit IPsec Quick Mode
|
||||||
@ -28,9 +28,9 @@ Audit IPsec Quick Mode subcategory is out of scope of this document, because thi
|
|||||||
| Member Server | IF | IF | IF | IF | IF - This subcategory is mainly used for IPsec Quick Mode troubleshooting, or for tracing or monitoring IPsec Quick Mode operations. |
|
| Member Server | IF | IF | IF | IF | IF - This subcategory is mainly used for IPsec Quick Mode troubleshooting, or for tracing or monitoring IPsec Quick Mode operations. |
|
||||||
| Workstation | IF | IF | IF | IF | IF - This subcategory is mainly used for IPsec Quick Mode troubleshooting, or for tracing or monitoring IPsec Quick Mode operations. |
|
| Workstation | IF | IF | IF | IF | IF - This subcategory is mainly used for IPsec Quick Mode troubleshooting, or for tracing or monitoring IPsec Quick Mode operations. |
|
||||||
|
|
||||||
## 4977: During Quick Mode negotiation, IPsec received an invalid negotiation packet. If this problem persists, it could indicate a network issue or an attempt to modify or replay this negotiation.
|
## 4977(S): During Quick Mode negotiation, IPsec received an invalid negotiation packet. If this problem persists, it could indicate a network issue or an attempt to modify or replay this negotiation.
|
||||||
|
|
||||||
## 5451: An IPsec Quick Mode security association was established.
|
## 5451(S): An IPsec Quick Mode security association was established.
|
||||||
|
|
||||||
## 5452: An IPsec Quick Mode security association ended.
|
## 5452(S): An IPsec Quick Mode security association ended.
|
||||||
|
|
||||||
|
@ -189,8 +189,6 @@ Windows Defender Credential Guard has always been an optional feature, but Windo
|
|||||||
|
|
||||||
A network connection is now required to set up a new device. As a result, we removed the “skip for now” option in the network setup page in Out Of Box Experience (OOBE).
|
A network connection is now required to set up a new device. As a result, we removed the “skip for now” option in the network setup page in Out Of Box Experience (OOBE).
|
||||||
|
|
||||||
<<<<<<< HEAD
|
|
||||||
=======
|
|
||||||
### Windows Defender ATP
|
### Windows Defender ATP
|
||||||
|
|
||||||
[Windows Defender ATP](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/windows-defender-advanced-threat-protection) has been enhanced with many new capabilities. For more information, see the following topics:
|
[Windows Defender ATP](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/windows-defender-advanced-threat-protection) has been enhanced with many new capabilities. For more information, see the following topics:
|
||||||
@ -220,7 +218,6 @@ Windows Defender ATP now adds support for Windows Server 2019. You'll be able to
|
|||||||
- [Onboard previous versions of Windows](https://docs.microsoft.com/windows/security/threat-protection/onboard-downlevel-windows-defender-advanced-threat-protection)<br>
|
- [Onboard previous versions of Windows](https://docs.microsoft.com/windows/security/threat-protection/onboard-downlevel-windows-defender-advanced-threat-protection)<br>
|
||||||
Onboard supported versions of Windows machines so that they can send sensor data to the Windows Defender ATP sensor
|
Onboard supported versions of Windows machines so that they can send sensor data to the Windows Defender ATP sensor
|
||||||
|
|
||||||
>>>>>>> 951a08abdd8a55231838c35a12890ed68af95f88
|
|
||||||
## Faster sign-in to a Windows 10 shared pc
|
## Faster sign-in to a Windows 10 shared pc
|
||||||
|
|
||||||
Do you have shared devices deployed in your work place? **Fast sign-in** enables users to sign in to a shared Windows 10 PC in a flash!
|
Do you have shared devices deployed in your work place? **Fast sign-in** enables users to sign in to a shared Windows 10 PC in a flash!
|
||||||
|
Loading…
x
Reference in New Issue
Block a user