From 43555d0839d40635a8c36d706b20521401feb6f8 Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Mon, 6 Apr 2020 10:52:29 -0700 Subject: [PATCH] update to bullet --- .../microsoft-defender-atp/troubleshoot-onboarding.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/troubleshoot-onboarding.md b/windows/security/threat-protection/microsoft-defender-atp/troubleshoot-onboarding.md index db55660b65..84dc110f5f 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/troubleshoot-onboarding.md +++ b/windows/security/threat-protection/microsoft-defender-atp/troubleshoot-onboarding.md @@ -298,7 +298,7 @@ There may be instances when onboarding is deployed on a newly built machine but The steps below provide guidance for the following scenario: - Onboarding package is deployed to newly built machines - Sensor does not start because the Out-of-box experience (OOBE) or first user logon has not been completed -- Machine is turned off and shipped to the end user +- Machine is turned off or restarted before the end user performs a first logon - In this scenario, the SENSE service will not start automatically even though onboarding package was deployed >[!NOTE]