Update configure-server-endpoints.md

Clarifications to avoid customer confusion about requirements when onboarding via Azure Defender for Servers.
We've had support cases where this was not clear enough and customer did not add the workspace configuration so onboarding never happened.
This commit is contained in:
amirsc3 2020-11-17 14:10:32 +02:00 committed by GitHub
parent e30c197293
commit 207c534880
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -128,6 +128,10 @@ Once completed, you should see onboarded Windows servers in the portal within an
After completing the onboarding steps, you'll need to [Configure and update System Center Endpoint Protection clients](#configure-and-update-system-center-endpoint-protection-clients).
> [!NOTE]
> For onboarding via Azure Defender for Servers (previously Azure Security Center Standard Edition) to work as expected, the server must have an appropriate workspace and key configured within the Microsoft Monitoring Agent (MMA) settings. Once configured, the appropriate cloud management pack is deployed on the machine and the sensor process (MsSenseS.exe) will be deployed and started.
> This is also required if the server is configured to use an OMS Gateway server as proxy.
### Option 3: Onboard Windows servers through Microsoft Endpoint Configuration Manager version 2002 and later
You can onboard Windows Server 2012 R2 and Windows Server 2016 by using Microsoft Endpoint Configuration Manager version 2002 and later. For more information, see [Microsoft Defender for Endpoint
in Microsoft Endpoint Configuration Manager current branch](https://docs.microsoft.com/mem/configmgr/protect/deploy-use/defender-advanced-threat-protection).