Merge pull request #2472 from MicrosoftDocs/troubleshoot-sccm
Troubleshoot sccm onboarding
After Width: | Height: | Size: 162 KiB |
After Width: | Height: | Size: 75 KiB |
After Width: | Height: | Size: 116 KiB |
After Width: | Height: | Size: 110 KiB |
After Width: | Height: | Size: 97 KiB |
After Width: | Height: | Size: 99 KiB |
After Width: | Height: | Size: 130 KiB |
After Width: | Height: | Size: 150 KiB |
After Width: | Height: | Size: 104 KiB |
After Width: | Height: | Size: 100 KiB |
After Width: | Height: | Size: 46 KiB |
After Width: | Height: | Size: 95 KiB |
After Width: | Height: | Size: 126 KiB |
After Width: | Height: | Size: 120 KiB |
After Width: | Height: | Size: 85 KiB |
After Width: | Height: | Size: 91 KiB |
After Width: | Height: | Size: 93 KiB |
After Width: | Height: | Size: 114 KiB |
After Width: | Height: | Size: 129 KiB |
After Width: | Height: | Size: 125 KiB |
After Width: | Height: | Size: 187 KiB |
After Width: | Height: | Size: 48 KiB |
After Width: | Height: | Size: 98 KiB |
After Width: | Height: | Size: 170 KiB |
After Width: | Height: | Size: 111 KiB |
After Width: | Height: | Size: 104 KiB |
After Width: | Height: | Size: 95 KiB |
After Width: | Height: | Size: 95 KiB |
After Width: | Height: | Size: 126 KiB |
After Width: | Height: | Size: 115 KiB |
@ -292,18 +292,115 @@ You might also need to check the following:
|
||||
|
||||
- Check to see that machines are reflected in the **Machines list** in the portal.
|
||||
|
||||
## Confirming onboarding of newly built machines
|
||||
There may be instances when onboarding is deployed on a newly built machine but not completed.
|
||||
|
||||
## Licensing requirements
|
||||
Microsoft Defender Advanced Threat Protection requires one of the following Microsoft Volume Licensing offers:
|
||||
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 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
|
||||
|
||||
- Windows 10 Enterprise E5
|
||||
- Windows 10 Education E5
|
||||
- Microsoft 365 Enterprise E5 which includes Windows 10 Enterprise E5
|
||||
|
||||
For more information, see [Windows 10 Licensing](https://www.microsoft.com/Licensing/product-licensing/windows10.aspx#tab=2).
|
||||
>[!NOTE]
|
||||
>The following steps are only relevant when using Microsoft Endpoint Configuration Manager (current branch)
|
||||
|
||||
|
||||
>Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/microsoft-365/windows/microsoft-defender-atp?ocid=docs-wdatp-troubleshootonboarding-belowfoldlink)
|
||||
1. Create an application in Microsoft Endpoint Configuration Manager current branch.
|
||||
|
||||

|
||||
|
||||
2. Select **Manually specify the application information**.
|
||||

|
||||
|
||||
3. Specify information about the application, then select **Next**.
|
||||

|
||||
|
||||
4. Specify information about the software center, then select **Next**.
|
||||

|
||||
|
||||
5. In **Deployment types** select **Add**.
|
||||

|
||||
|
||||
6. Select **Manually specify the deployment type information**, then select **Next**.
|
||||

|
||||
|
||||
7. Specify information about the deployment type, then select **Next**.
|
||||

|
||||
|
||||
8. In **Content** > **Installation program** specify the command: `net start sense`.
|
||||

|
||||
|
||||
9. In **Detection method**, select **Configure rules to detect the presence of this deployment type**, then select **Add Clause**.
|
||||
|
||||

|
||||
|
||||
10. Specify the following detection rule details, then select **OK**:
|
||||

|
||||
|
||||
11. In **Detection method** select **Next**.
|
||||

|
||||
|
||||
12. In **User Experience**, specify the following information, then select **Next**:
|
||||

|
||||
|
||||
13. In **Requirements**, select **Next**.
|
||||

|
||||
|
||||
14. In **Dependencies**, select **Next**.
|
||||

|
||||
|
||||
15. In **Summary**, select **Next**.
|
||||

|
||||
|
||||
16. In **Completion**, select **Close**.
|
||||
|
||||

|
||||
|
||||
17. In **Deployment types**, select **Next**.
|
||||
|
||||

|
||||
|
||||
18. In **Summary**, select **Next**.
|
||||

|
||||
|
||||
The status is then displayed
|
||||

|
||||
|
||||
19. In **Completion**, select **Close**.
|
||||
|
||||

|
||||
|
||||
20. You can now deploy the application by right-clicking the app and selecting **Deploy**.
|
||||
|
||||

|
||||
|
||||
21. In **General** select **Automatically distribute content for dependencies** and **Browse**.
|
||||

|
||||
|
||||
22. In **Content** select **Next**.
|
||||

|
||||
|
||||
23. In **Deployment settings**, select **Next**.
|
||||

|
||||
|
||||
24. In **Scheduling** select **As soon as possible after the available time**, then select **Next**.
|
||||

|
||||
|
||||
25. In **User experience**, select **Commit changes at deadline or during a maintenance window (requires restarts)**, then select **Next**.
|
||||

|
||||
|
||||
26. In **Alerts** select **Next**.
|
||||

|
||||
|
||||
27. In **Summary**, select **Next**.
|
||||

|
||||
|
||||
The status is then displayed
|
||||

|
||||
|
||||
28. In **Completion**, select **Close**.
|
||||

|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|