mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-27 08:13:39 +00:00
Merge branch 'master' into jreeds-smartscreen-rebrand
This commit is contained in:
Jreeds001
GitHub
@ -7832,11 +7832,6 @@
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deploy/deploy-windows-10-with-system-center-2012-r2-configuration-manager.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-sccm/deploy-windows-10-with-system-center-2012-r2-configuration-manager",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deploy/deploy-windows-10-with-the-microsoft-deployment-toolkit.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit",
|
||||
"redirect_document_id": true
|
||||
@ -7887,16 +7882,6 @@
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deploy/integrate-configuration-manager-with-mdt-2013.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-mdt/integrate-configuration-manager-with-mdt-2013",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deploy/integrate-configuration-manager-with-mdt.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-mdt/integrate-configuration-manager-with-mdt",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deploy/introduction-vamt.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/volume-activation/introduction-vamt",
|
||||
"redirect_document_id": true
|
||||
@ -15778,7 +15763,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/deploy-windows-sccm/deploy-windows-10-with-system-center-2012-r2-configuration-manager.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-sccm/deploy-windows-10-with-configuration-manager",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
@ -15792,21 +15777,11 @@
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/deploy-windows-mdt/integrate-configuration-manager-with-mdt.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-sccm/integrate-configuration-manager-with-mdt",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/deploy-windows-mdt/deploy-windows-10-with-configuration-manager.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-sccm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/deploy-windows-sccm/integrate-configuration-manager-with-mdt.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-cm/integrate-configuration-manager-with-mdt",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/deploy-windows-sccm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager",
|
||||
"redirect_document_id": false
|
||||
@ -15875,6 +15850,10 @@
|
||||
"source_path": "windows/deployment/deploy-windows-sccm/deploy-windows-10-with-configuration-manager.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-cm/get-started-with-configuraton-manager",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/deploy-windows-sccm/integrate-configuration-manager-with-mdt.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager#integrate-configuration-manager-with-mdt", "redirect_document_id": false
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
@ -31,7 +31,7 @@ When a user starts the Autopilot self-deploying process, the process completes t
|
||||
> [!NOTE]
|
||||
> Autopilot for HoloLens does not support Active Directory join or Hybrid Azure AD join.
|
||||
1. Use Azure AD to enroll the device in Microsoft Intune (or another MDM service).
|
||||
1. Download the device-targeted policies, certificates, and networking profiles.
|
||||
1. Download the device-targeted policies, user-targeted apps, certificates, and networking profiles.
|
||||
1. Provision the device.
|
||||
1. Present the sign-in screen to the user.
|
||||
|
||||
@ -39,8 +39,8 @@ When a user starts the Autopilot self-deploying process, the process completes t
|
||||
|
||||
The following steps summarize the process of setting up your environment for the Windows Autopilot for HoloLens 2. The rest of this section provides the details of these steps.
|
||||
|
||||
1. Enroll in the Windows Autopilot for HoloLens 2 program.
|
||||
1. Make sure that you meet the requirements for Windows Autopilot for HoloLens.
|
||||
1. Enroll in the Windows Autopilot for HoloLens 2 program.
|
||||
1. Verify that your tenant is flighted (enrolled to participate in the program).
|
||||
1. Register devices in Windows Autopilot.
|
||||
1. Create a device group.
|
||||
@ -49,7 +49,36 @@ The following steps summarize the process of setting up your environment for the
|
||||
1. Configure a custom configuration profile for HoloLens devices (known issue).
|
||||
1. Verify the profile status of the HoloLens devices.
|
||||
|
||||
### 1. Enroll in the Windows Autopilot for HoloLens 2 program
|
||||
### 1. Make sure that you meet the requirements for Windows Autopilot for HoloLens
|
||||
For the latest information about how to participate in the program, review [Windows Insider Release Notes](hololens-insider.md#windows-insider-release-notes).
|
||||
|
||||
Review the following sections of the Windows Autopilot requirements article:
|
||||
|
||||
- [Network requirements](https://docs.microsoft.com/windows/deployment/windows-autopilot/windows-autopilot-requirements#networking-requirements)
|
||||
- [Licensing requirements](https://docs.microsoft.com/windows/deployment/windows-autopilot/windows-autopilot-requirements#licensing-requirements)
|
||||
- [Configuration requirements](https://docs.microsoft.com/windows/deployment/windows-autopilot/windows-autopilot-requirements#configuration-requirements)
|
||||
> [!IMPORTANT]
|
||||
> Unlike other Windows Autopilot programs, Windows Autopilot for HoloLens 2 has specific operating system requirements.
|
||||
|
||||
Review the "[Requirements](https://docs.microsoft.com/windows/deployment/windows-autopilot/self-deploying#requirements)" section of the Windows Autopilot Self-Deploying mode article. Your environment has to meet these requirements as well as the standard Windows Autopilot requirements.
|
||||
|
||||
> [!NOTE]
|
||||
> You do not have to review the "Step by step" and "Validation" sections of the article. The procedures later in this article provide corresponding steps that are specific to HoloLens.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> For information about how to register devices and configure profiles, see [4. Register devices in Windows Autopilot](#4-register-devices-in-windows-autopilot) and [6. Create a deployment profile](#6-create-a-deployment-profile) in this article. These sections provide steps that are specific to HoloLens.
|
||||
|
||||
Before you start the OOBE and provisioning process, make sure that the HoloLens devices meet the following requirements:
|
||||
|
||||
- The devices are not already members of Azure AD, and are not enrolled in Intune (or another MDM system). The Autopilot self-deploying process completes these steps. To make sure that all the device-related information is cleaned up, check the **Devices** pages in both Azure AD and Intune.
|
||||
- Every device can connect to the internet. You can use a wired or wireless connection.
|
||||
- Every device can connect to a computer by using a USB-C cable, and that computer has the following available:
|
||||
- Advanced Recovery Companion (ARC)
|
||||
- The latest Windows update: Windows 10, version 19041.1002.200107-0909 or a later version)
|
||||
|
||||
To configure and manage the Autopilot self-deploying mode profiles, make sure that you have access to [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com).
|
||||
|
||||
### 2. Enroll in the Windows Autopilot for HoloLens 2 program
|
||||
|
||||
To participate in the program, you have to use a tenant that is flighted for HoloLens. To do this, go to [Windows Autopilot for HoloLens Private Preview request](https://aka.ms/APHoloLensTAP) or use the following QR code to submit a request.
|
||||
|
||||
@ -62,36 +91,6 @@ In this request, provide the following information:
|
||||
- Number of HoloLens 2 devices that are participating in this evaluation
|
||||
- Number of HoloLens 2 devices that you plan to deploy by using Autopilot self-deploying mode
|
||||
|
||||
### 2. Make sure that you meet the requirements for Windows Autopilot for HoloLens
|
||||
|
||||
For the latest information about how to participate in the program, review [Windows Insider Release Notes](hololens-insider.md#windows-insider-release-notes).
|
||||
|
||||
Review the following sections of the Windows Autopilot requirements article:
|
||||
|
||||
- [Network requirements](https://docs.microsoft.com/windows/deployment/windows-autopilot/windows-autopilot-requirements#networking-requirements)
|
||||
- [Licensing requirements](https://docs.microsoft.com/windows/deployment/windows-autopilot/windows-autopilot-requirements#licensing-requirements)
|
||||
- [Configuration requirements](https://docs.microsoft.com/windows/deployment/windows-autopilot/windows-autopilot-requirements#configuration-requirements)
|
||||
> [!IMPORTANT]
|
||||
> For information about how to register devices and configure profiles, see [4. Register devices in Windows Autopilot](#4-register-devices-in-windows-autopilot) and [6. Create a deployment profile](#6-create-a-deployment-profile) in this article. These sections provide steps that are specific to HoloLens.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Unlike other Windows Autopilot programs, Windows Autopilot for HoloLens 2 has specific operating system requirements.
|
||||
|
||||
Review the "[Requirements](https://docs.microsoft.com/windows/deployment/windows-autopilot/self-deploying#requirements)" section of the Windows Autopilot Self-Deploying mode article. Your environment has to meet these requirements as well as the standard Windows Autopilot requirements.
|
||||
|
||||
> [!NOTE]
|
||||
> You do not have to review the "Step by step" and "Validation" sections of the article. The procedures later in this article provide corresponding steps that are specific to HoloLens.
|
||||
|
||||
Before you start the OOBE and provisioning process, make sure that the HoloLens devices meet the following requirements:
|
||||
|
||||
- The devices are not already members of Azure AD, and are not enrolled in Intune (or another MDM system). The Autopilot self-deploying process completes these steps. To make sure that all the device-related information is cleaned up, check the **Devices** pages in both Azure AD and Intune.
|
||||
- Every device can connect to the internet. You can use a wired or wireless connection.
|
||||
- Every device can connect to a computer by using a USB-C cable, and that computer has the following available:
|
||||
- Advanced Recovery Companion (ARC)
|
||||
- The latest Windows update: Windows 10, version 19041.1002.200107-0909 or a later version)
|
||||
|
||||
To configure and manage the Autopilot self-deploying mode profiles, make sure that you have access to [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com).
|
||||
|
||||
### 3. Verify that your tenant is flighted
|
||||
|
||||
To verify that your tenant is flighted for the Autopilot program after you submit your request, follow these steps:
|
||||
@ -108,7 +107,7 @@ To register a HoloLens device in the Windows Autopilot program, you have to obta
|
||||
|
||||
**Retrieve a device hardware hash**
|
||||
|
||||
1. Start the HoloLens 2 device, and make sure that you sign in by using an account that is the device owner.
|
||||
1. Start the HoloLens 2 device.
|
||||
1. On the device, press the Power and Volume Down buttons at the same time and then release them. The device collects diagnostic logs and the hardware hash, and stores them in a set of .zip files.
|
||||
1. Use a USB-C cable to connect the device to a computer.
|
||||
1. On the computer, open File Explorer. Open **This PC\\\<*HoloLens device name*>\\Internal Storage\\Documents**, and locate the AutopilotDiagnostics.zip file.
|
||||
|
||||
@ -90,7 +90,6 @@ Next, see [Add a Windows 10 operating system image using Configuration Manager](
|
||||
|
||||
## Related topics
|
||||
|
||||
[Integrate Configuration Manager with MDT](../deploy-windows-mdt/integrate-configuration-manager-with-mdt.md)<br>
|
||||
[Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)<br>
|
||||
[Add a Windows 10 operating system image using Configuration Manager](add-a-windows-10-operating-system-image-using-configuration-manager.md)<br>
|
||||
[Create an application to deploy with Windows 10 using Configuration Manager](create-an-application-to-deploy-with-windows-10-using-configuration-manager.md)<br>
|
||||
|
||||
@ -413,7 +413,7 @@
|
||||
### [Configure portal settings]()
|
||||
#### [Set up preferences](microsoft-defender-atp/preferences-setup.md)
|
||||
#### [General]()
|
||||
##### [Update data retention settings](microsoft-defender-atp/data-retention-settings.md)
|
||||
##### [Verify data storage location and update data retention settings](microsoft-defender-atp/data-retention-settings.md)
|
||||
##### [Configure alert notifications](microsoft-defender-atp/configure-email-notifications.md)
|
||||
##### [Enable and create Power BI reports using Windows Defender Security center data](microsoft-defender-atp/powerbi-reports.md)
|
||||
##### [Enable Secure score security controls](microsoft-defender-atp/enable-secure-score.md)
|
||||
@ -704,6 +704,7 @@
|
||||
#### [Microsoft Defender SmartScreen Group Policy and mobile device management (MDM) settings](microsoft-defender-smartscreen/microsoft-defender-smartscreen-available-settings.md)
|
||||
#### [Set up and use Microsft Defender SmartScreen on individual devices](microsoft-defender-smartscreen/microsoft-defender-smartscreen-set-individual-device.md)
|
||||
|
||||
|
||||
### [Windows Sandbox](windows-sandbox/windows-sandbox-overview.md)
|
||||
#### [Windows Sandbox architecture](windows-sandbox/windows-sandbox-architecture.md)
|
||||
#### [Windows Sandbox configuration](windows-sandbox/windows-sandbox-configure-using-wsb-file.md)
|
||||
|
||||
@ -17,8 +17,8 @@ ms.date: 04/19/2017
|
||||
# Audit Other Privilege Use Events
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows Server 2016
|
||||
- Windows 10
|
||||
- Windows Server 2016
|
||||
|
||||
|
||||
This auditing subcategory should not have any events in it, but for some reason Success auditing will enable generation of event 4985(S): The state of a transaction has changed.
|
||||
@ -31,7 +31,7 @@ This auditing subcategory should not have any events in it, but for some reason
|
||||
|
||||
**Events List:**
|
||||
|
||||
- [4985](event-4674.md)(S): The state of a transaction has changed.
|
||||
- [4985](event-4985.md)(S): The state of a transaction has changed.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Update how long data is stored by MDATP
|
||||
description: Update data retention settings for Microsoft Defender Advanced Threat Protection (MDATP) by selecting between 30 days to 180 days.
|
||||
title: Verify data storage location and update data retention settings
|
||||
description: Verify data storage location and update data retention settings for Microsoft Defender Advanced Threat Protection
|
||||
keywords: data, storage, settings, retention, update
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
@ -15,9 +15,8 @@ manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
ms.date: 04/24/2018
|
||||
---
|
||||
# Update data retention settings for Microsoft Defender ATP
|
||||
# Verify data storage location and update data retention settings for Microsoft Defender ATP
|
||||
|
||||
**Applies to:**
|
||||
|
||||
@ -25,10 +24,18 @@ ms.date: 04/24/2018
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
|
||||
|
||||
>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-gensettings-abovefoldlink)
|
||||
|
||||
During the onboarding process, a wizard takes you through the general settings of Microsoft Defender ATP. After onboarding, you might want to update the data retention settings.
|
||||
During the onboarding process, a wizard takes you through the data storage and retention settings of Microsoft Defender ATP.
|
||||
|
||||
After completing the onboarding, you can verify your selection in the data retention settings page.
|
||||
|
||||
## Verify data storage location
|
||||
During the [Set up phase](production-deployment.md), you would have selected the location to store your data.
|
||||
|
||||
You can verify the data location by navigating to **Settings** > **Data retention**.
|
||||
|
||||
## Update data retention settings
|
||||
|
||||
1. In the navigation pane, select **Settings** > **Data retention**.
|
||||
|
||||
|
||||
Binary file not shown.
Binary file not shown.
@ -19,6 +19,12 @@ ms.topic: conceptual
|
||||
|
||||
# Intune-based deployment for Microsoft Defender ATP for Mac
|
||||
|
||||
> [!NOTE]
|
||||
> This documentation explains the legacy method for deploying and configuring Microsoft Defender ATP on macOS devices. The native experience is now available in the MEM console. The release of the native UI in the MEM console provide admins with a much simpler way to configure and dfeploy the application and send it down to macOS devices.
|
||||
> This blog post explains the new features: https://techcommunity.microsoft.com/t5/microsoft-endpoint-manager-blog/microsoft-endpoint-manager-simplifies-deployment-of-microsoft/ba-p/1322995
|
||||
> To configure the app go here: https://docs.microsoft.com/mem/intune/protect/antivirus-microsoft-defender-settings-macos
|
||||
> To deploy the app go here: https://docs.microsoft.com/mem/intune/apps/apps-advanced-threat-protection-macos
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP) for Mac](microsoft-defender-atp-mac.md)
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Shadow protection in next-generation protection
|
||||
description: Learn about shadow protection in next-generation protection
|
||||
title: Shadow protection
|
||||
description: Learn about shadow protection
|
||||
keywords: Windows Defender Antivirus, shadow protection, passive mode
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
ms.pagetype: security
|
||||
@ -16,7 +16,7 @@ ms.custom: next-gen
|
||||
ms.collection:
|
||||
---
|
||||
|
||||
# Shadow protection in next-generation protection
|
||||
# Shadow protection
|
||||
|
||||
**Applies to:**
|
||||
|
||||
@ -67,7 +67,7 @@ The following images shows an instance of unwanted software that was detected an
|
||||
|Windows Defender Antivirus engine |To make sure your engine is up to date, using PowerShell, run the [Get-MpComputerStatus](https://docs.microsoft.com/powershell/module/defender/get-mpcomputerstatus?view=win10-ps) cmdlet as an administrator. In the **AMEngineVersion** line, you should see **1.1.16700.2** or above. |
|
||||
|
||||
> [!IMPORTANT]
|
||||
> To get the best protection value, make sure Windows Defender Antivirus is configured to receive regular updates and other essential features, such as behavioral monitoring, IOfficeAV, tamper protection, and more. See [Protect security settings with tamper protection](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/prevent-changes-to-security-settings-with-tamper-protection)
|
||||
> To get the best protection value, make sure Windows Defender Antivirus is configured to receive regular updates and other essential features, such as behavioral monitoring, IOfficeAV, tamper protection, and more. See [Protect security settings with tamper protection](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/prevent-changes-to-security-settings-with-tamper-protection).
|
||||
|
||||
|
||||
## Frequently asked questions
|
||||
@ -78,7 +78,7 @@ No. Shadow protection does not affect third-party antivirus protection running o
|
||||
|
||||
### Why do I need to keep Windows Defender Antivirus up to date?
|
||||
|
||||
The [Microsoft Defender ATP](https://docs.microsoft.com/windows/security/threat-protection) stack works in integration, and to get best protection value, you should keep Windows Defender Antivirus up to date.
|
||||
Because Windows Defender Antivirus detects and remediates malicious items, it’s important to keep it up to date to leverage the latest machine learning models, behavioral detections, and heuristics for best results. The [Microsoft Defender ATP](https://docs.microsoft.com/windows/security/threat-protection) stack of capabilities work in an integrated manner, and to get best protection value, you should keep Windows Defender Antivirus up to date.
|
||||
|
||||
### Why do we need cloud protection on?
|
||||
|
||||
|
||||
Reference in New Issue
Block a user