mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-07-03 03:03:43 +00:00
Merge branch 'master' into whfb-staging
This commit is contained in:
@ -20,6 +20,8 @@ This topic lists new and updated topics in the [Windows 10 for Education](index.
|
|||||||
| New or changed topic | Description |
|
| New or changed topic | Description |
|
||||||
| --- | ---- |
|
| --- | ---- |
|
||||||
| [Test Windows 10 S on existing Windows 10 education devices](test-windows10s-for-edu.md) | Updated the the list of device manufacturers. |
|
| [Test Windows 10 S on existing Windows 10 education devices](test-windows10s-for-edu.md) | Updated the the list of device manufacturers. |
|
||||||
|
| [Set up Take a Test on multiple PCs](take-a-test-multiple-pcs.md) | Updated instances of the parameter enablePrint, or enablePrinting, to requirePrinting. |
|
||||||
|
| [Set up Take a Test on a single PC](take-a-test-single-pc.md) | Updated instances of the parameter enablePrint, or enablePrinting, to requirePrinting. |
|
||||||
|
|
||||||
## RELEASE: Windows 10, version 1709 (Fall Creators Update)
|
## RELEASE: Windows 10, version 1709 (Fall Creators Update)
|
||||||
|
|
||||||
|
@ -233,9 +233,9 @@ One of the ways you can present content in a locked down manner is by embedding
|
|||||||
2. To enable printing, screen capture, or both, use the above link and append one of these parameters:
|
2. To enable printing, screen capture, or both, use the above link and append one of these parameters:
|
||||||
|
|
||||||
- `&enableTextSuggestions` - Enables text suggestions
|
- `&enableTextSuggestions` - Enables text suggestions
|
||||||
- `&enablePrint` - Enables printing
|
- `&requirePrinting` - Enables printing
|
||||||
- `&enableScreenCapture` - Enables screen capture
|
- `&enableScreenCapture` - Enables screen capture
|
||||||
- `&enablePrinting&enableScreenCapture` - Enables printing and screen capture; you can use a combination of `&enableTextSuggestions`, `&enablePrint`, and `&enableScreenCapture` if you want to enable more than one capability.
|
- `&requirePrinting&enableScreenCapture` - Enables printing and screen capture; you can use a combination of `&enableTextSuggestions`, `&requirePrinting`, and `&enableScreenCapture` if you want to enable more than one capability.
|
||||||
|
|
||||||
If you exclude these parameters, the default behavior is disabled.
|
If you exclude these parameters, the default behavior is disabled.
|
||||||
|
|
||||||
|
@ -97,9 +97,9 @@ One of the ways you can present content in a locked down manner is by embedding
|
|||||||
2. To enable printing, screen capture, or both, use the above link and append one of these parameters:
|
2. To enable printing, screen capture, or both, use the above link and append one of these parameters:
|
||||||
|
|
||||||
- `&enableTextSuggestions` - Enables text suggestions
|
- `&enableTextSuggestions` - Enables text suggestions
|
||||||
- `&enablePrint` - Enables printing
|
- `&requirePrinting` - Enables printing
|
||||||
- `&enableScreenCapture` - Enables screen capture
|
- `&enableScreenCapture` - Enables screen capture
|
||||||
- `&enablePrinting&enableScreenCapture` - Enables printing and screen capture; you can use a combination of `&enableTextSuggestions`, `&enablePrint`, and `&enableScreenCapture` if you want to enable more than one capability.
|
- `&requirePrinting&enableScreenCapture` - Enables printing and screen capture; you can use a combination of `&enableTextSuggestions`, `&requirePrinting`, and `&enableScreenCapture` if you want to enable more than one capability.
|
||||||
|
|
||||||
If you exclude these parameters, the default behavior is disabled.
|
If you exclude these parameters, the default behavior is disabled.
|
||||||
|
|
||||||
|
@ -7,6 +7,7 @@ ms.sitesec: library
|
|||||||
ms.author: elizapo
|
ms.author: elizapo
|
||||||
author: kaushika-msft
|
author: kaushika-msft
|
||||||
ms.localizationpriority: high
|
ms.localizationpriority: high
|
||||||
|
ms.date: 08/30/2017
|
||||||
---
|
---
|
||||||
# Top support solutions for Windows 10
|
# Top support solutions for Windows 10
|
||||||
|
|
||||||
|
@ -8,13 +8,19 @@ ms.sitesec: library
|
|||||||
ms.pagetype: security
|
ms.pagetype: security
|
||||||
ms.localizationpriority: high
|
ms.localizationpriority: high
|
||||||
author: jdeckerms
|
author: jdeckerms
|
||||||
ms.date: 10/20/2017
|
ms.date: 11/06/2017
|
||||||
---
|
---
|
||||||
|
|
||||||
# Change history for Configure Windows 10
|
# Change history for Configure Windows 10
|
||||||
|
|
||||||
This topic lists new and updated topics in the [Configure Windows 10](index.md) documentation for Windows 10 and Windows 10 Mobile.
|
This topic lists new and updated topics in the [Configure Windows 10](index.md) documentation for Windows 10 and Windows 10 Mobile.
|
||||||
|
|
||||||
|
## November 2017
|
||||||
|
|
||||||
|
New or changed topic | Description
|
||||||
|
--- | ---
|
||||||
|
[Create a provisioning package with multivariant settings](provisioning-packages/provisioning-multivariant.md) | Add support for desktop to [Conditions](provisioning-packages/provisioning-multivariant.md#conditions) table.
|
||||||
|
|
||||||
## October 2017
|
## October 2017
|
||||||
|
|
||||||
New or changed topic | Description
|
New or changed topic | Description
|
||||||
|
@ -6,6 +6,8 @@ ms.mktglfcycl: deploy
|
|||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
author: jdeckerms
|
author: jdeckerms
|
||||||
ms.localizationpriority: high
|
ms.localizationpriority: high
|
||||||
|
ms.date: 11/06/2017
|
||||||
|
ms.author: jdecker
|
||||||
---
|
---
|
||||||
|
|
||||||
# Create a provisioning package with multivariant settings
|
# Create a provisioning package with multivariant settings
|
||||||
@ -44,12 +46,12 @@ The following table shows the conditions supported in Windows 10 provisioning fo
|
|||||||
|
|
||||||
| Condition Name | Condition priority | Windows 10 Mobile | Windows 10 for desktop editions | Value type | Value description |
|
| Condition Name | Condition priority | Windows 10 Mobile | Windows 10 for desktop editions | Value type | Value description |
|
||||||
| --- | --- | --- | --- | --- | --- |
|
| --- | --- | --- | --- | --- | --- |
|
||||||
| MNC | P0 | Supported | N/A | Digit string | Use to target settings based on the Mobile Network Code (MNC) value. |
|
| MNC | P0 | Supported | Supported | Digit string | Use to target settings based on the Mobile Network Code (MNC) value. |
|
||||||
| MCC | P0 | Supported | N/A | Digit string | Use to target settings based on the Mobile Country Code (MCC) value. |
|
| MCC | P0 | Supported | Supported | Digit string | Use to target settings based on the Mobile Country Code (MCC) value. |
|
||||||
| SPN | P0 | Supported | N/A | String | Use to target settings based on the Service Provider Name (SPN) value. |
|
| SPN | P0 | Supported | Supported | String | Use to target settings based on the Service Provider Name (SPN) value. |
|
||||||
| PNN | P0 | Supported | N/A | String | Use to target settings based on public land mobile network (PLMN) Network Name value. |
|
| PNN | P0 | Supported | Supported | String | Use to target settings based on public land mobile network (PLMN) Network Name value. |
|
||||||
| GID1 | P0 | Supported | N/A | Digit string | Use to target settings based on the Group Identifier (level 1) value. |
|
| GID1 | P0 | Supported | Supported | Digit string | Use to target settings based on the Group Identifier (level 1) value. |
|
||||||
| ICCID | P0 | Supported | N/A | Digit string | Use to target settings based on the Integrated Circuit Card Identifier (ICCID) value. |
|
| ICCID | P0 | Supported | Supported | Digit string | Use to target settings based on the Integrated Circuit Card Identifier (ICCID) value. |
|
||||||
| Roaming | P0 | Supported | N/A | Boolean | Use to specify roaming. Set the value to **1** (roaming) or **0** (non-roaming). |
|
| Roaming | P0 | Supported | N/A | Boolean | Use to specify roaming. Set the value to **1** (roaming) or **0** (non-roaming). |
|
||||||
| UICC | P0 | Supported | N/A | Enumeration | Use to specify the Universal Integrated Circuit Card (UICC) state. Set the value to one of the following:</br></br></br>- 0 - Empty</br>- 1 - Ready</br>- 2 - Locked |
|
| UICC | P0 | Supported | N/A | Enumeration | Use to specify the Universal Integrated Circuit Card (UICC) state. Set the value to one of the following:</br></br></br>- 0 - Empty</br>- 1 - Ready</br>- 2 - Locked |
|
||||||
| UICCSLOT | P0 | Supported | N/A | Digit string | Use to specify the UICC slot. Set the value one of the following:</br></br></br>- 0 - Slot 0</br>- 1 - Slot 1 |
|
| UICCSLOT | P0 | Supported | N/A | Digit string | Use to specify the UICC slot. Set the value one of the following:</br></br></br>- 0 - Slot 0</br>- 1 - Slot 1 |
|
||||||
|
@ -6,12 +6,18 @@ ms.prod: w10
|
|||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
author: greg-lindsay
|
author: greg-lindsay
|
||||||
ms.date: 10/31/2017
|
ms.date: 11/08/2017
|
||||||
---
|
---
|
||||||
|
|
||||||
# Change history for Deploy Windows 10
|
# Change history for Deploy Windows 10
|
||||||
This topic lists new and updated topics in the [Deploy Windows 10](index.md) documentation for [Windows 10 and Windows 10 Mobile](/windows/windows-10).
|
This topic lists new and updated topics in the [Deploy Windows 10](index.md) documentation for [Windows 10 and Windows 10 Mobile](/windows/windows-10).
|
||||||
|
|
||||||
|
## November 2017
|
||||||
|
|
||||||
|
New or changed topic | Description
|
||||||
|
-- | ---
|
||||||
|
[Create a Windows 10 reference image](deploy-windows-mdt/create-a-windows-10-reference-image.md) | Added warning that you should not use **SkipMachineOOBE** or **SkipUserOOBE** in your Unattend.xml.
|
||||||
|
|
||||||
## RELEASE: Windows 10, version 1709
|
## RELEASE: Windows 10, version 1709
|
||||||
| New or changed topic | Description |
|
| New or changed topic | Description |
|
||||||
|----------------------|-------------|
|
|----------------------|-------------|
|
||||||
|
@ -9,6 +9,7 @@ ms.localizationpriority: high
|
|||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.pagetype: mdt
|
ms.pagetype: mdt
|
||||||
author: mtniehaus
|
author: mtniehaus
|
||||||
|
ms.date: 11/08/2017
|
||||||
---
|
---
|
||||||
|
|
||||||
# Create a Windows 10 reference image
|
# Create a Windows 10 reference image
|
||||||
@ -19,8 +20,8 @@ author: mtniehaus
|
|||||||
Creating a reference image is important because that image serves as the foundation for the devices in your organization. In this topic, you will learn how to create a Windows 10 reference image using the Microsoft Deployment Toolkit (MDT). You will create a deployment share, configure rules and settings, and import all the applications and operating system files required to build a Windows 10 reference image. After completing the steps outlined in this topic, you will have a Windows 10 reference image that can be used in your deployment solution.
|
Creating a reference image is important because that image serves as the foundation for the devices in your organization. In this topic, you will learn how to create a Windows 10 reference image using the Microsoft Deployment Toolkit (MDT). You will create a deployment share, configure rules and settings, and import all the applications and operating system files required to build a Windows 10 reference image. After completing the steps outlined in this topic, you will have a Windows 10 reference image that can be used in your deployment solution.
|
||||||
For the purposes of this topic, we will use four machines: DC01, MDT01, HV01, and PC0001. DC01 is a domain controller, PC0001 is a Windows 10 Enterprise x64 client, and MDT01 is a Windows Server 2012 R2 standard server. HV01 is a Hyper-V host server, but HV01 could be replaced by PC0001 as long as PC0001 has enough memory and is capable of running Hyper-V. MDT01, HV01, and PC0001 are members of the domain contoso.com for the fictitious Contoso Corporation.
|
For the purposes of this topic, we will use four machines: DC01, MDT01, HV01, and PC0001. DC01 is a domain controller, PC0001 is a Windows 10 Enterprise x64 client, and MDT01 is a Windows Server 2012 R2 standard server. HV01 is a Hyper-V host server, but HV01 could be replaced by PC0001 as long as PC0001 has enough memory and is capable of running Hyper-V. MDT01, HV01, and PC0001 are members of the domain contoso.com for the fictitious Contoso Corporation.
|
||||||
|
|
||||||
**Note**
|
>{!NOTE]}
|
||||||
For important details about the setup for the steps outlined in this article, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-10-with-the-microsoft-deployment-toolkit.md#proof).
|
>For important details about the setup for the steps outlined in this article, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-10-with-the-microsoft-deployment-toolkit.md#proof).
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
@ -75,8 +76,8 @@ This section will show you how to populate the MDT deployment share with the Win
|
|||||||
|
|
||||||
MDT supports adding both full source Windows 10 DVDs (ISOs) and custom images that you have created. In this case, you create a reference image, so you add the full source setup files from Microsoft.
|
MDT supports adding both full source Windows 10 DVDs (ISOs) and custom images that you have created. In this case, you create a reference image, so you add the full source setup files from Microsoft.
|
||||||
|
|
||||||
**Note**
|
>[!OTE]
|
||||||
Due to the Windows limits on path length, we are purposely keeping the operating system destination directory short, using the folder name W10EX64RTM rather than a more descriptive name like Windows 10 Enterprise x64 RTM.
|
>Due to the Windows limits on path length, we are purposely keeping the operating system destination directory short, using the folder name W10EX64RTM rather than a more descriptive name like Windows 10 Enterprise x64 RTM.
|
||||||
|
|
||||||
### Add Windows 10 Enterprise x64 (full source)
|
### Add Windows 10 Enterprise x64 (full source)
|
||||||
|
|
||||||
@ -115,8 +116,8 @@ By storing configuration items as MDT applications, it is easy to move these obj
|
|||||||
|
|
||||||
In these examples, we assume that you downloaded the software in this list to the E:\\Downloads folder. The first application is added using the UI, but because MDT supports Windows PowerShell, you add the other applications using Windows PowerShell.
|
In these examples, we assume that you downloaded the software in this list to the E:\\Downloads folder. The first application is added using the UI, but because MDT supports Windows PowerShell, you add the other applications using Windows PowerShell.
|
||||||
|
|
||||||
**Note**
|
>[!NOTE]
|
||||||
All the Microsoft Visual C++ downloads can be found on [The latest supported Visual C++ downloads](https://go.microsoft.com/fwlink/p/?LinkId=619523).
|
>All the Microsoft Visual C++ downloads can be found on [The latest supported Visual C++ downloads](https://go.microsoft.com/fwlink/p/?LinkId=619523).
|
||||||
|
|
||||||
### Create the install: Microsoft Office Professional Plus 2013 x86
|
### Create the install: Microsoft Office Professional Plus 2013 x86
|
||||||
|
|
||||||
@ -371,8 +372,11 @@ Figure 9. The Windows 10 desktop with the Resume Task Sequence shortcut.
|
|||||||
|
|
||||||
When using MDT, you don't need to edit the Unattend.xml file very often because most configurations are taken care of by MDT. However if, for example, you want to configure Internet Explorer 11 behavior, then you can edit the Unattend.xml for this. Editing the Unattend.xml for basic Internet Explorer settings is easy, but for more advanced settings, you will want to use Internet Explorer Administration Kit (IEAK).
|
When using MDT, you don't need to edit the Unattend.xml file very often because most configurations are taken care of by MDT. However if, for example, you want to configure Internet Explorer 11 behavior, then you can edit the Unattend.xml for this. Editing the Unattend.xml for basic Internet Explorer settings is easy, but for more advanced settings, you will want to use Internet Explorer Administration Kit (IEAK).
|
||||||
|
|
||||||
**Note**
|
>[!WARNING]
|
||||||
You also can use the Unattend.xml to enable components in Windows 10, like the Telnet Client or Hyper-V client. Normally we prefer to do this via the Install Roles and Features action, or using Deployment Image Servicing and Management (DISM) command-line tools, because then we can add that as an application, being dynamic, having conditions, and so forth. Also, if you are adding packages via Unattend.xml, it is version specific, so Unattend.xml must match the exact version of the operating system you are servicing.
|
>Do not use **SkipMachineOOBE** or **SkipUserOOBE** in your Unattend.xml
|
||||||
|
|
||||||
|
>[!NOTE]
|
||||||
|
>You also can use the Unattend.xml to enable components in Windows 10, like the Telnet Client or Hyper-V client. Normally we prefer to do this via the **Install Roles and Features** action, or using Deployment Image Servicing and Management (DISM) command-line tools, because then we can add that as an application, being dynamic, having conditions, and so forth. Also, if you are adding packages via Unattend.xml, it is version specific, so Unattend.xml must match the exact version of the operating system you are servicing.
|
||||||
|
|
||||||
Follow these steps to configure Internet Explorer settings in Unattend.xml for the Windows 10 Enterprise x64 RTM Default Image task sequence:
|
Follow these steps to configure Internet Explorer settings in Unattend.xml for the Windows 10 Enterprise x64 RTM Default Image task sequence:
|
||||||
|
|
||||||
|
@ -7,7 +7,7 @@ ms.prod: w10
|
|||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
ms.localizationpriority: high
|
ms.localizationpriority: high
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.date: 10/26/2017
|
ms.date: 11/7/2017
|
||||||
author: greg-lindsay
|
author: greg-lindsay
|
||||||
---
|
---
|
||||||
|
|
||||||
@ -18,7 +18,18 @@ author: greg-lindsay
|
|||||||
|
|
||||||
To successfully deploy the Windows 10 operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the key capabilities and limitations of each, is a key task.
|
To successfully deploy the Windows 10 operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the key capabilities and limitations of each, is a key task.
|
||||||
|
|
||||||
|
## Windows AutoPilot
|
||||||
|
|
||||||
|
Windows AutoPilot is a new suite of capabilities designed to simplify and modernize the deployment and management of new Windows 10 PCs. Windows AutoPilot enables IT professionals to customize the Out of Box Experience (OOBE) for Windows 10 PCs and provide end users with a fully configured new Windows 10 device after just a few clicks. There are no images to deploy, no drivers to inject, and no infrastructure to manage. Users can go through the deployment process independently, without the need consult their IT administrator.
|
||||||
|
|
||||||
|
For more information about Windows AutoPilot, see [Overview of Windows AutoPilot](https://docs.microsoft.com/en-us/windows/deployment/windows-10-auto-pilot) and [Modernizing Windows deployment with Windows AutoPilot](https://blogs.technet.microsoft.com/windowsitpro/2017/06/29/modernizing-windows-deployment-with-windows-autopilot/).
|
||||||
|
|
||||||
|
## Windows 10 Subscription Activation
|
||||||
|
|
||||||
|
Windows 10 Subscription Activation is a modern deployment method that enables you to change the SKU from Pro to Enterprise with no keys and no reboots. For more information about Subscription Activation, see [Windows 10 Subscription Activation](https://docs.microsoft.com/en-us/windows/deployment/windows-10-enterprise-subscription-activation).
|
||||||
|
|
||||||
## In-place upgrade
|
## In-place upgrade
|
||||||
|
|
||||||
For existing computers running Windows 7, Windows 8, or Windows 8.1, the recommended path for organizations deploying Windows 10 leverages the Windows installation program (Setup.exe) to perform an in-place upgrade, which automatically preserves all data, settings, applications, and drivers from the existing operating system version. This requires the least IT effort, because there is no need for any complex deployment infrastructure.
|
For existing computers running Windows 7, Windows 8, or Windows 8.1, the recommended path for organizations deploying Windows 10 leverages the Windows installation program (Setup.exe) to perform an in-place upgrade, which automatically preserves all data, settings, applications, and drivers from the existing operating system version. This requires the least IT effort, because there is no need for any complex deployment infrastructure.
|
||||||
|
|
||||||
Although consumer PCs will be upgraded using Windows Update, organizations want more control over the process. This is accomplished by leveraging tools like System Center Configuration Manager or the Microsoft Deployment Toolkit to completely automate the upgrade process through simple task sequences.
|
Although consumer PCs will be upgraded using Windows Update, organizations want more control over the process. This is accomplished by leveraging tools like System Center Configuration Manager or the Microsoft Deployment Toolkit to completely automate the upgrade process through simple task sequences.
|
||||||
@ -43,6 +54,7 @@ There are some situations where you cannot use in-place upgrade; in these situat
|
|||||||
- Dual-boot and multi-boot systems. The upgrade process is designed for devices running a single OS; if using dual-boot or multi-boot systems with multiple operating systems (not leveraging virtual machines for the second and subsequent operating systems), additional care should be taken.
|
- Dual-boot and multi-boot systems. The upgrade process is designed for devices running a single OS; if using dual-boot or multi-boot systems with multiple operating systems (not leveraging virtual machines for the second and subsequent operating systems), additional care should be taken.
|
||||||
|
|
||||||
## Dynamic provisioning
|
## Dynamic provisioning
|
||||||
|
|
||||||
For new PCs, organizations have historically replaced the version of Windows included on the device with their own custom Windows image, because this was often faster and easier than leveraging the preinstalled version. But this is an added expense due to the time and effort required. With the new dynamic provisioning capabilities and tools provided with Windows 10, it is now possible to avoid this.
|
For new PCs, organizations have historically replaced the version of Windows included on the device with their own custom Windows image, because this was often faster and easier than leveraging the preinstalled version. But this is an added expense due to the time and effort required. With the new dynamic provisioning capabilities and tools provided with Windows 10, it is now possible to avoid this.
|
||||||
|
|
||||||
The goal of dynamic provisioning is to take a new PC out of the box, turn it on, and transform it into a productive organization device, with minimal time and effort. The types of transformations that are available include:
|
The goal of dynamic provisioning is to take a new PC out of the box, turn it on, and transform it into a productive organization device, with minimal time and effort. The types of transformations that are available include:
|
||||||
@ -50,11 +62,8 @@ The goal of dynamic provisioning is to take a new PC out of the box, turn it on,
|
|||||||
- Changing the Windows edition with a single reboot. For organizations that have Software Assurance for Windows, it is easy to change a device from Windows 10 Pro to Windows 10 Enterprise, just by specifying an appropriate product or setup key. When the device restarts, all of the Windows 10 Enterprise features will be enabled.
|
- Changing the Windows edition with a single reboot. For organizations that have Software Assurance for Windows, it is easy to change a device from Windows 10 Pro to Windows 10 Enterprise, just by specifying an appropriate product or setup key. When the device restarts, all of the Windows 10 Enterprise features will be enabled.
|
||||||
|
|
||||||
- Configuring the device with VPN and Wi-Fi connections that may be needed to gain access to organization resources.
|
- Configuring the device with VPN and Wi-Fi connections that may be needed to gain access to organization resources.
|
||||||
|
|
||||||
- Installation of additional apps needed for organization functions.
|
- Installation of additional apps needed for organization functions.
|
||||||
|
|
||||||
- Configuration of common Windows settings to ensure compliance with organization policies.
|
- Configuration of common Windows settings to ensure compliance with organization policies.
|
||||||
|
|
||||||
- Enrollment of the device in a mobile device management (MDM) solution, such as Microsoft Intune.
|
- Enrollment of the device in a mobile device management (MDM) solution, such as Microsoft Intune.
|
||||||
|
|
||||||
There are two primary dynamic provisioning scenarios:
|
There are two primary dynamic provisioning scenarios:
|
||||||
@ -67,7 +76,8 @@ Either way, these scenarios can be used to enable “choose your own device” (
|
|||||||
|
|
||||||
While the initial Windows 10 release includes a variety of provisioning settings and deployment mechanisms, these will continue to be enhanced and extended based on feedback from organizations. As with all Windows features, organizations can submit suggestions for additional features through the Windows Feedback app or through their Microsoft Support contacts.
|
While the initial Windows 10 release includes a variety of provisioning settings and deployment mechanisms, these will continue to be enhanced and extended based on feedback from organizations. As with all Windows features, organizations can submit suggestions for additional features through the Windows Feedback app or through their Microsoft Support contacts.
|
||||||
|
|
||||||
## Traditional deployment
|
## Traditional deployment:
|
||||||
|
|
||||||
New versions of Windows have typically been deployed by organizations using an image-based process built on top of tools provided in the [Windows Assessment and Deployment Kit](windows-adk-scenarios-for-it-pros.md), Windows Deployment Services, the [Deploy Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit.md), and [System Center Configuration Manager](deploy-windows-sccm/deploy-windows-10-with-system-center-2012-r2-configuration-manager.md).
|
New versions of Windows have typically been deployed by organizations using an image-based process built on top of tools provided in the [Windows Assessment and Deployment Kit](windows-adk-scenarios-for-it-pros.md), Windows Deployment Services, the [Deploy Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit.md), and [System Center Configuration Manager](deploy-windows-sccm/deploy-windows-10-with-system-center-2012-r2-configuration-manager.md).
|
||||||
|
|
||||||
With the release of Windows 10, all of these tools are being updated to fully support Windows 10. Although newer scenarios such as in-place upgrade and dynamic provisioning may reduce the need for traditional deployment capabilities in some organizations, these traditional methods remain important and will continue to be available to organizations that need them.
|
With the release of Windows 10, all of these tools are being updated to fully support Windows 10. Although newer scenarios such as in-place upgrade and dynamic provisioning may reduce the need for traditional deployment capabilities in some organizations, these traditional methods remain important and will continue to be available to organizations that need them.
|
||||||
|
@ -30,6 +30,7 @@
|
|||||||
###### [Configure endpoints using Microsoft Intune](windows-defender-atp\configure-endpoints-mdm-windows-defender-advanced-threat-protection.md#configure-endpoints-using-microsoft-intune)
|
###### [Configure endpoints using Microsoft Intune](windows-defender-atp\configure-endpoints-mdm-windows-defender-advanced-threat-protection.md#configure-endpoints-using-microsoft-intune)
|
||||||
##### [Configure endpoints using a local script](windows-defender-atp\configure-endpoints-script-windows-defender-advanced-threat-protection.md)
|
##### [Configure endpoints using a local script](windows-defender-atp\configure-endpoints-script-windows-defender-advanced-threat-protection.md)
|
||||||
##### [Configure non-persistent virtual desktop infrastructure (VDI) machines](windows-defender-atp\configure-endpoints-vdi-windows-defender-advanced-threat-protection.md)
|
##### [Configure non-persistent virtual desktop infrastructure (VDI) machines](windows-defender-atp\configure-endpoints-vdi-windows-defender-advanced-threat-protection.md)
|
||||||
|
#### [Configure non-Windows endpoints](windows-defender-atp\configure-endpoints-non-windows-windows-defender-advanced-threat-protection.md)
|
||||||
#### [Configure server endpoints](windows-defender-atp\configure-server-endpoints-windows-defender-advanced-threat-protection.md)
|
#### [Configure server endpoints](windows-defender-atp\configure-server-endpoints-windows-defender-advanced-threat-protection.md)
|
||||||
#### [Run a detection test on a newly onboarded endpoint](windows-defender-atp\run-detection-test-windows-defender-advanced-threat-protection.md)
|
#### [Run a detection test on a newly onboarded endpoint](windows-defender-atp\run-detection-test-windows-defender-advanced-threat-protection.md)
|
||||||
#### [Configure proxy and Internet connectivity settings](windows-defender-atp\configure-proxy-internet-windows-defender-advanced-threat-protection.md)
|
#### [Configure proxy and Internet connectivity settings](windows-defender-atp\configure-proxy-internet-windows-defender-advanced-threat-protection.md)
|
||||||
|
@ -0,0 +1,70 @@
|
|||||||
|
---
|
||||||
|
title: Configure non-Windows endpoints in Windows Defender ATP
|
||||||
|
description: Configure non-Winodws endpoints so that they can send sensor data to the Windows Defender ATP service.
|
||||||
|
keywords: configure endpoints non-Windows endpoints, macos, linux, endpoint management, configure Windows ATP endpoints, configure Windows Defender Advanced Threat Protection endpoints
|
||||||
|
search.product: eADQiWindows 10XVcnh
|
||||||
|
ms.prod: w10
|
||||||
|
ms.mktglfcycl: deploy
|
||||||
|
ms.sitesec: library
|
||||||
|
ms.pagetype: security
|
||||||
|
author: mjcaparas
|
||||||
|
localizationpriority: high
|
||||||
|
ms.date: 11/07/2017
|
||||||
|
---
|
||||||
|
|
||||||
|
# Configure non-Windows endpoints
|
||||||
|
|
||||||
|
**Applies to:**
|
||||||
|
|
||||||
|
- Mac OS X
|
||||||
|
- Linux
|
||||||
|
- Windows Defender Advanced Threat Protection (Windows Defender ATP)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Windows Defender ATP provides a centralized security operations experience for Windows as well as non-Windows platforms. You'll be able to see alerts from various supported operating systems (OS) in the Windows Defender ATP portal and better protect your organization's network. This experience leverages on a third-party security products’ sensor data.
|
||||||
|
|
||||||
|
You'll need to know the exact Linux distros and Mac OS X versions that are compatible with Windows Defender ATP for the integration to work.
|
||||||
|
|
||||||
|
## Onboard non-Windows endpoints
|
||||||
|
You'll need to take the following steps to oboard non-Windows endpoints:
|
||||||
|
1. Turn on third-party integration
|
||||||
|
2. Run a detection test
|
||||||
|
|
||||||
|
### Turn on third-party integration
|
||||||
|
|
||||||
|
1. In Windows Defender Security Center portal, select **Endpoint management** > **Clients** > **Non-Windows**. Make sure the third-party solution is listed.
|
||||||
|
|
||||||
|
2. Toggle the third-party provider switch button to turn on the third-party solution integration.
|
||||||
|
|
||||||
|
3. Click **Generate access token** button and then **Copy**.
|
||||||
|
|
||||||
|
4. Depending on the third-party implementation you're using, the implementation might vary. Refer to the third-party solution documentation for guidance on how to use the token.
|
||||||
|
|
||||||
|
|
||||||
|
>[!WARNING]
|
||||||
|
>The access token has a limited validity period. If needed, regenerate the token close to the time you need to share it with the third-party solution.
|
||||||
|
|
||||||
|
### Run detection test
|
||||||
|
Create an EICAR test file by saving the string displayed on the portal in an empty text file. Then, introduce the test file to a machine running the third-party antivirus solution.
|
||||||
|
|
||||||
|
The file should trigger a detection and a corresponding alert on Windows Defender ATP.
|
||||||
|
|
||||||
|
### Offboard non-Windows endpoints
|
||||||
|
To effectively offboard the endpoints from the service, you'll need to disable the data push on the third-party portal first then switch the toggle to off in Windows Defender Security Center. The toggle in the portal only blocks the data inbound flow.
|
||||||
|
|
||||||
|
|
||||||
|
1. Follow the third-party documentation to opt-out on the third-party service side.
|
||||||
|
|
||||||
|
2. In Windows Defender Security Center portal, select **Endpoint management**> **Non-Windows**.
|
||||||
|
|
||||||
|
3. Toggle the third-party provider switch button to turn stop telemetry from endpoints.
|
||||||
|
|
||||||
|
>[!WARNING]
|
||||||
|
>If you decide to turn on the third-party integration again after disabling the integration, you'll need to regenerate the token and reapply it on endpoints.
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
- [Configure Windows Defender ATP client endpoints](configure-endpoints-windows-defender-advanced-threat-protection.md)
|
||||||
|
- [Configure server endpoints](configure-server-endpoints-windows-defender-advanced-threat-protection.md)
|
||||||
|
- [Configure proxy and Internet connectivity settings](configure-proxy-internet-windows-defender-advanced-threat-protection.md)
|
||||||
|
- [Troubleshooting Windows Defender Advanced Threat Protection onboarding issues](troubleshoot-onboarding-windows-defender-advanced-threat-protection.md)
|
@ -87,6 +87,7 @@ For more information, see [To disable an agent](https://docs.microsoft.com/en-us
|
|||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
- [Configure Windows Defender ATP client endpoints](configure-endpoints-windows-defender-advanced-threat-protection.md)
|
- [Configure Windows Defender ATP client endpoints](configure-endpoints-windows-defender-advanced-threat-protection.md)
|
||||||
|
- [Configure non-Windows endpoints](configure-endpoints-non-windows-windows-defender-advanced-threat-protection.md)
|
||||||
- [Configure proxy and Internet connectivity settings](configure-proxy-internet-windows-defender-advanced-threat-protection.md)
|
- [Configure proxy and Internet connectivity settings](configure-proxy-internet-windows-defender-advanced-threat-protection.md)
|
||||||
- [Run a detection test on a newly onboarded Windows Defender ATP endpoint](run-detection-test-windows-defender-advanced-threat-protection.md)
|
- [Run a detection test on a newly onboarded Windows Defender ATP endpoint](run-detection-test-windows-defender-advanced-threat-protection.md)
|
||||||
- [Troubleshooting Windows Defender Advanced Threat Protection onboarding issues](troubleshoot-onboarding-windows-defender-advanced-threat-protection.md)
|
- [Troubleshooting Windows Defender Advanced Threat Protection onboarding issues](troubleshoot-onboarding-windows-defender-advanced-threat-protection.md)
|
||||||
|
@ -54,6 +54,7 @@ For more information, see [Windows Defender Antivirus compatibility](../windows-
|
|||||||
Topic | Description
|
Topic | Description
|
||||||
:---|:---
|
:---|:---
|
||||||
[Configure client endpoints](configure-endpoints-windows-defender-advanced-threat-protection.md) | You'll need to configure endpoints for it to report to the Windows Defender ATP service. Learn about the tools and methods you can use to configure endpoints in your enterprise.
|
[Configure client endpoints](configure-endpoints-windows-defender-advanced-threat-protection.md) | You'll need to configure endpoints for it to report to the Windows Defender ATP service. Learn about the tools and methods you can use to configure endpoints in your enterprise.
|
||||||
|
[Configure non-Windows endpoints](configure-endpoints-non-windows-windows-defender-advanced-threat-protection.md) | Windows Defender ATP provides a centralized security operations experience for Windows as well as non-Windows platforms. You'll be able to see alerts from various supported operating systems (OS) in the Windows Defender ATP portal and better protect your organization's network. This experience leverages on a third-party security products<74> sensor data.
|
||||||
[Configure server endpoints](configure-server-endpoints-windows-defender-advanced-threat-protection.md) | Onboard Windows Server 2012 R2 and Windows Server 2016 to Windows Defender ATP
|
[Configure server endpoints](configure-server-endpoints-windows-defender-advanced-threat-protection.md) | Onboard Windows Server 2012 R2 and Windows Server 2016 to Windows Defender ATP
|
||||||
[Configure proxy and Internet settings](configure-proxy-internet-windows-defender-advanced-threat-protection.md)| Enable communication with the Windows Defender ATP cloud service by configuring the proxy and Internet connectivity settings.
|
[Configure proxy and Internet settings](configure-proxy-internet-windows-defender-advanced-threat-protection.md)| Enable communication with the Windows Defender ATP cloud service by configuring the proxy and Internet connectivity settings.
|
||||||
[Troubleshoot onboarding issues](troubleshoot-onboarding-windows-defender-advanced-threat-protection.md) | Learn about resolving issues that might arise during onboarding.
|
[Troubleshoot onboarding issues](troubleshoot-onboarding-windows-defender-advanced-threat-protection.md) | Learn about resolving issues that might arise during onboarding.
|
||||||
|
Reference in New Issue
Block a user