mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-15 14:57:23 +00:00
Merge branch 'master' into patch-1
This commit is contained in:
commit
ceded06014
@ -24,12 +24,29 @@ Please refer to the “[Surface Hub Important Information](https://support.micro
|
|||||||
|
|
||||||
## Windows 10 Team Creators Update 1703
|
## Windows 10 Team Creators Update 1703
|
||||||
|
|
||||||
|
<details>
|
||||||
|
<summary>September 24, 2019—update for Team edition based on KB4516059* (OS Build 15063.2078)</summary>
|
||||||
|
|
||||||
|
This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
|
||||||
|
|
||||||
|
* Update to Surface Hub 2S Recovery Settings page to accurately reflect recovery options.
|
||||||
|
* Update to Surface Hub 2S Welcome screen to improve device recognizability.
|
||||||
|
* Addressed an issue with the Windows Team Edition shell background displaying incorrectly.
|
||||||
|
* Addressed an issue with Start Menu layout persistence when configured using MDM policy.
|
||||||
|
* Fixed an issue in Microsoft Edge that occurs when browsing some internal websites.
|
||||||
|
* Fixed an issue in Skype for Business that occurs when presenting in full-screen mode.
|
||||||
|
|
||||||
|
Please refer to the [Surface Hub Admin guide](https://docs.microsoft.com/surface-hub/) for enabling/disabling device features and services.
|
||||||
|
*[KB4503289](https://support.microsoft.com/help/4503289)
|
||||||
|
</details>
|
||||||
|
|
||||||
<details>
|
<details>
|
||||||
<summary>August 17, 2019—update for Team edition based on KB4512474* (OS Build 15063.2021)</summary>
|
<summary>August 17, 2019—update for Team edition based on KB4512474* (OS Build 15063.2021)</summary>
|
||||||
|
|
||||||
This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
|
This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
|
||||||
|
|
||||||
* Ensures that Video Out on Hub 2S defaults to "Duplicate" mode.
|
* Ensures that Video Out on Hub 2S defaults to "Duplicate" mode.
|
||||||
|
* Improves reliability for some Arabic language usage scenarios on Surface Hub.
|
||||||
|
|
||||||
Please refer to the [Surface Hub Admin guide](https://docs.microsoft.com/surface-hub/) for enabling/disabling device features and services.
|
Please refer to the [Surface Hub Admin guide](https://docs.microsoft.com/surface-hub/) for enabling/disabling device features and services.
|
||||||
*[KB4503289](https://support.microsoft.com/help/4503289)
|
*[KB4503289](https://support.microsoft.com/help/4503289)
|
||||||
|
@ -36,6 +36,7 @@ Compatible Surface devices include:
|
|||||||
* Surface Pro (Model 1796)
|
* Surface Pro (Model 1796)
|
||||||
* Surface Laptop
|
* Surface Laptop
|
||||||
* Surface Studio
|
* Surface Studio
|
||||||
|
* Surface Studio 2
|
||||||
* Surface Book
|
* Surface Book
|
||||||
* Surface Pro 4
|
* Surface Pro 4
|
||||||
* Surface 3 LTE
|
* Surface 3 LTE
|
||||||
|
@ -36,8 +36,7 @@ You can set the policy using one of these methods:
|
|||||||
|
|
||||||
- MDM provider
|
- MDM provider
|
||||||
|
|
||||||
- Autopilot Reset in Intune for Education is coming soon. In a future update of Intune for Education, new tenants will automatically have the Autopilot Reset setting enabled by default on the **All devices** group as part of initial tenant configuration. You will also be able to manage this setting to target different groups in the admin console.
|
-Check your MDM provider documentation on how to set this policy. If your MDM provider doesn't explicitly support this policy, you can manually set this policy if your MDM provider allows specific OMA-URIs to be manually set.
|
||||||
- If you're using an MDM provider other than Intune for Education, check your MDM provider documentation on how to set this policy. If your MDM provider doesn't explicitly support this policy, you can manually set this policy if your MDM provider allows specific OMA-URIs to be manually set.
|
|
||||||
|
|
||||||
For example, in Intune, create a new configuration policy and add an OMA-URI.
|
For example, in Intune, create a new configuration policy and add an OMA-URI.
|
||||||
- OMA-URI: ./Vendor/MSFT/Policy/Config/CredentialProviders/DisableAutomaticReDeploymentCredentials
|
- OMA-URI: ./Vendor/MSFT/Policy/Config/CredentialProviders/DisableAutomaticReDeploymentCredentials
|
||||||
@ -93,6 +92,7 @@ Autopilot Reset is a two-step process: trigger it and then authenticate. Once yo
|
|||||||
Once provisioning is complete, the device is again ready for use.
|
Once provisioning is complete, the device is again ready for use.
|
||||||
|
|
||||||
<span id="winre"/>
|
<span id="winre"/>
|
||||||
|
|
||||||
## Troubleshoot Autopilot Reset
|
## Troubleshoot Autopilot Reset
|
||||||
|
|
||||||
Autopilot Reset will fail when the [Windows Recovery Environment (WinRE)](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference) is not enabled on the device. You will see `Error code: ERROR_NOT_SUPPORTED (0x80070032)`.
|
Autopilot Reset will fail when the [Windows Recovery Environment (WinRE)](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference) is not enabled on the device. You will see `Error code: ERROR_NOT_SUPPORTED (0x80070032)`.
|
||||||
|
@ -165,13 +165,17 @@ Requirements:
|
|||||||
> If you do not see the policy, it may be because you don’t have the ADMX installed for Windows 10, version 1803, version 1809, or version 1903. To fix the issue, follow these steps (Note: the latest MDM.admx is backwards compatible):
|
> If you do not see the policy, it may be because you don’t have the ADMX installed for Windows 10, version 1803, version 1809, or version 1903. To fix the issue, follow these steps (Note: the latest MDM.admx is backwards compatible):
|
||||||
> 1. Download:
|
> 1. Download:
|
||||||
> 1803 -->[Administrative Templates (.admx) for Windows 10 April 2018 Update (1803)](https://www.microsoft.com/download/details.aspx?id=56880) or
|
> 1803 -->[Administrative Templates (.admx) for Windows 10 April 2018 Update (1803)](https://www.microsoft.com/download/details.aspx?id=56880) or
|
||||||
> 1809 --> [Administrative Templates for Windows 10 October 2018 Update (1809)](https://www.microsoft.com/download/details.aspx?id=57576).
|
> 1809 --> [Administrative Templates for Windows 10 October 2018 Update (1809)](https://www.microsoft.com/download/details.aspx?id=57576) or
|
||||||
> 1903 --> [Administrative Templates for Windows 10 May 2019 Update (1903)](https://www.microsoft.com/download/details.aspx?id=58495&WT.mc_id=rss_alldownloads_all) (recommended).
|
> 1903 --> [Administrative Templates (.admx) for Windows 10 May 2019 Update (1903)](https://www.microsoft.com/download/details.aspx?id=58495&WT.mc_id=rss_alldownloads_all)
|
||||||
> 2. Install the package on the Primary Domain Controller (PDC).
|
> 2. Install the package on the Primary Domain Controller (PDC).
|
||||||
> 3. Navigate, depending on the version to the folder:
|
> 3. Navigate, depending on the version to the folder:
|
||||||
> **C:\Program Files (x86)\Microsoft Group Policy\Windows 10 \<month\> \<year\> Update (\<feature release\>) \<policy version\>**
|
> 1803 --> **C:\Program Files (x86)\Microsoft Group Policy\Windows 10 April 2018 Update (1803) v2**, or
|
||||||
> 4. Copy policy definitions folder to **C:\Windows\SYSVOL\domain\Policies** (N.B. If this folder does not exist, then be aware that you will be switching to a [central policy store](https://support.microsoft.com/help/3087759/how-to-create-and-manage-the-central-store-for-group-policy-administra) for your entire domain).
|
> 1809 --> **C:\Program Files (x86)\Microsoft Group Policy\Windows 10 October 2018 Update (1809) v2**, or
|
||||||
> 5. Restart the Primary Domain Controller for the policy to be available.
|
> 1903 --> **C:\Program Files (x86)\Microsoft Group Policy\Windows 10 May 2019 Update (1903) v3**
|
||||||
|
> 4. Rename the extracted Policy Definitions folder to **PolicyDefinitions**.
|
||||||
|
> 5. Copy PolicyDefinitions folder to **C:\Windows\SYSVOL\domain\Policies**.
|
||||||
|
> (N.B. If this folder does not exist, then be aware that you will be switching to a [central policy store](https://support.microsoft.com/help/3087759/how-to-create-and-manage-the-central-store-for-group-policy-administra) for your entire domain).
|
||||||
|
> 6. Restart the Primary Domain Controller for the policy to be available.
|
||||||
> This procedure will work for any future version as well.
|
> This procedure will work for any future version as well.
|
||||||
|
|
||||||
1. Create a Group Policy Object (GPO) and enable the Group Policy **Computer Configuration** > **Policies** > **Administrative Templates** > **Windows Components** > **MDM** > **Enable automatic MDM enrollment using default Azure AD credentials**.
|
1. Create a Group Policy Object (GPO) and enable the Group Policy **Computer Configuration** > **Policies** > **Administrative Templates** > **Windows Components** > **MDM** > **Enable automatic MDM enrollment using default Azure AD credentials**.
|
||||||
|
@ -77,7 +77,7 @@ In addition to the settings in the table, you may want to set up **automatic log
|
|||||||
|
|
||||||
2. Go to
|
2. Go to
|
||||||
|
|
||||||
**HKEY\_LOCAL\_MACHINE\SOFTWARE\\Microsoft\WindowsNT\CurrentVersion\Winlogon**
|
**HKEY\_LOCAL\_MACHINE\SOFTWARE\\Microsoft\Windows NT\CurrentVersion\Winlogon**
|
||||||
|
|
||||||
3. Set the values for the following keys.
|
3. Set the values for the following keys.
|
||||||
|
|
||||||
|
@ -151,7 +151,7 @@ Certain Windows Analytics features have additional settings you can use.
|
|||||||
|
|
||||||
- For devices running Windows 10, version 1607 or earlier, Windows diagnostic data must also be set to Enhanced (see [Configure Windows diagnostic data in your organization](https://docs.microsoft.com/windows/configuration/configure-windows-diagnostic-data-in-your-organization#enhanced-level)) in order to be compatible with Windows Defender Antivirus. See the [Windows Defender Antivirus in Windows 10 and Windows Server 2016](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/windows-defender-antivirus-in-windows-10) for more information about enabling, configuring, and validating Windows Defender AV.
|
- For devices running Windows 10, version 1607 or earlier, Windows diagnostic data must also be set to Enhanced (see [Configure Windows diagnostic data in your organization](https://docs.microsoft.com/windows/configuration/configure-windows-diagnostic-data-in-your-organization#enhanced-level)) in order to be compatible with Windows Defender Antivirus. See the [Windows Defender Antivirus in Windows 10 and Windows Server 2016](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/windows-defender-antivirus-in-windows-10) for more information about enabling, configuring, and validating Windows Defender AV.
|
||||||
|
|
||||||
- **Device Health** is only compatible with Windows 10 desktop devices (workstations and laptops) and Windows Server 2016. The solution requires that at least the Enhanced level of diagnostic data is enabled on all devices that are intended to be displayed in the solution. In Windows 10, version 1709, a new policy was added to "limit enhanced telemetry to the minimum required by Windows Analytics". To learn more about Windows diagnostic data, see [Configure Windows diagnostic data in your organization](https://docs.microsoft.com/windows/configuration/configure-windows-diagnostic-data-in-your-organization).
|
- **Device Health** is only compatible with Windows 10 desktop devices (workstations and laptops). The solution requires that at least the Enhanced level of diagnostic data is enabled on all devices that are intended to be displayed in the solution. In Windows 10, version 1709, a new policy was added to "limit enhanced telemetry to the minimum required by Windows Analytics". To learn more about Windows diagnostic data, see [Configure Windows diagnostic data in your organization](https://docs.microsoft.com/windows/configuration/configure-windows-diagnostic-data-in-your-organization).
|
||||||
|
|
||||||
- **IE site discovery** is an optional feature of Upgrade Readiness that provides an inventory of websites that are accessed by client devices using Internet Explorer on Windows 7, Windows 8.1, and Windows 10. To enable IE site discovery, make sure the required updates are installed (per previous section) and enable IE site discovery in the deployment script batch file.
|
- **IE site discovery** is an optional feature of Upgrade Readiness that provides an inventory of websites that are accessed by client devices using Internet Explorer on Windows 7, Windows 8.1, and Windows 10. To enable IE site discovery, make sure the required updates are installed (per previous section) and enable IE site discovery in the deployment script batch file.
|
||||||
|
|
||||||
|
@ -8,8 +8,10 @@ ms.prod: w10
|
|||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.pagetype: deploy
|
ms.pagetype: deploy
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itpro
|
||||||
ms.audience: itpro
author: greg-lindsay
|
author: greg-lindsay
|
||||||
|
ms.audience: itpro
|
||||||
|
author: greg-lindsay
|
||||||
ms.localizationpriority: high
|
ms.localizationpriority: high
|
||||||
ms.collection: M365-analytics
|
ms.collection: M365-analytics
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
@ -43,6 +45,7 @@ See these topics for additional background information about related privacy iss
|
|||||||
- [Windows 10 and the GDPR for IT Decision Makers](https://docs.microsoft.com/windows/privacy/gdpr-it-guidance)
|
- [Windows 10 and the GDPR for IT Decision Makers](https://docs.microsoft.com/windows/privacy/gdpr-it-guidance)
|
||||||
- [Configure Windows diagnostic data in your organization](https://docs.microsoft.com/windows/configuration/configure-windows-diagnostic-data-in-your-organization)
|
- [Configure Windows diagnostic data in your organization](https://docs.microsoft.com/windows/configuration/configure-windows-diagnostic-data-in-your-organization)
|
||||||
- [Windows 7, Windows 8, and Windows 8.1 Appraiser Telemetry Events, and Fields](https://go.microsoft.com/fwlink/?LinkID=822965)
|
- [Windows 7, Windows 8, and Windows 8.1 Appraiser Telemetry Events, and Fields](https://go.microsoft.com/fwlink/?LinkID=822965)
|
||||||
|
- [Windows 10, version 1903 basic level Windows diagnostic events and fields](https://docs.microsoft.com/en-us/windows/privacy/basic-level-windows-diagnostic-events-and-fields-1903)
|
||||||
- [Windows 10, version 1809 basic level Windows diagnostic events and fields](https://docs.microsoft.com/windows/privacy/basic-level-windows-diagnostic-events-and-fields-1809)
|
- [Windows 10, version 1809 basic level Windows diagnostic events and fields](https://docs.microsoft.com/windows/privacy/basic-level-windows-diagnostic-events-and-fields-1809)
|
||||||
- [Windows 10, version 1803 basic level Windows diagnostic events and fields](https://docs.microsoft.com/windows/privacy/basic-level-windows-diagnostic-events-and-fields-1803)
|
- [Windows 10, version 1803 basic level Windows diagnostic events and fields](https://docs.microsoft.com/windows/privacy/basic-level-windows-diagnostic-events-and-fields-1803)
|
||||||
- [Windows 10, version 1709 basic level Windows diagnostic events and fields](https://docs.microsoft.com/windows/privacy/basic-level-windows-diagnostic-events-and-fields-1709)
|
- [Windows 10, version 1709 basic level Windows diagnostic events and fields](https://docs.microsoft.com/windows/privacy/basic-level-windows-diagnostic-events-and-fields-1709)
|
||||||
|
@ -8,7 +8,8 @@ ms.author: greglin
|
|||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itpro
|
||||||
|
author: greg-lindsay
|
||||||
ms.date: 04/19/2017
|
ms.date: 04/19/2017
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
---
|
---
|
||||||
@ -247,7 +248,7 @@ USMT provides several command-line options that you can use to analyze problems
|
|||||||
<td align="left"><p><strong>/progress:</strong>[<em>Path</em>]<em>FileName</em></p></td>
|
<td align="left"><p><strong>/progress:</strong>[<em>Path</em>]<em>FileName</em></p></td>
|
||||||
<td align="left"><p>Creates the optional progress log. You cannot store any of the log files in <em>StorePath</em>. <em>Path</em> can be either a relative or full path. If you do not specify the <em>Path</em> variable, then <em>FileName</em> will be created in the current directory.</p>
|
<td align="left"><p>Creates the optional progress log. You cannot store any of the log files in <em>StorePath</em>. <em>Path</em> can be either a relative or full path. If you do not specify the <em>Path</em> variable, then <em>FileName</em> will be created in the current directory.</p>
|
||||||
<p>For example:</p>
|
<p>For example:</p>
|
||||||
<p><code>loadstate /i:migapp.xml /i:migdocs.xml \server\share\migration\mystore /progress:prog.log /l:scanlog.log</code></p></td>
|
<p><code>loadstate /i:migapp.xml /i:migdocs.xml \server\share\migration\mystore /progress:prog.log /l:loadlog.log</code></p></td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr class="even">
|
<tr class="even">
|
||||||
<td align="left"><p><strong>/c</strong></p></td>
|
<td align="left"><p><strong>/c</strong></p></td>
|
||||||
|
@ -9,7 +9,8 @@ ms.mktglfcycl: deploy
|
|||||||
ms.localizationpriority: low
|
ms.localizationpriority: low
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.pagetype: deploy
|
ms.pagetype: deploy
|
||||||
audience: itpro
author: greg-lindsay
|
audience: itpro
|
||||||
|
author: greg-lindsay
|
||||||
ms.author: greglin
|
ms.author: greglin
|
||||||
ms.collection: M365-modern-desktop
|
ms.collection: M365-modern-desktop
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
@ -109,7 +110,7 @@ A [glossary](#glossary) of abbreviations used in this topic is provided at the e
|
|||||||
| --- | --- |
|
| --- | --- |
|
||||||
| Must we use Intune for our MDM? | No. No, any MDM will work with Autopilot, but others probably won’t have the same full suite of Windows Autopilot features as Intune. You’ll get the best experience from Intune. |
|
| Must we use Intune for our MDM? | No. No, any MDM will work with Autopilot, but others probably won’t have the same full suite of Windows Autopilot features as Intune. You’ll get the best experience from Intune. |
|
||||||
| Can Intune support Win32 app preinstalls? | Yes. Starting with the Windows 10 October Update (version 1809), Intune supports Win32 apps using .msi (and .msix) wrappers. |
|
| Can Intune support Win32 app preinstalls? | Yes. Starting with the Windows 10 October Update (version 1809), Intune supports Win32 apps using .msi (and .msix) wrappers. |
|
||||||
| What is co-management? | Co-management is when you use a combination of a cloud MDM tool (Intune) and an on-premise configuration tool like System Center Configuration Manager (SCCM). You only need to use SCCM if Intune can’t support what you want to do with your profile. If you choose to co-manage using Intune + SCCM, you do it by including an SCCM agent in your Intune profile. When that profile is pushed to the device, the device will see the SCCM agent and go out to SCCM to pull down any additional profile settings. |
|
| What is co-management? | Co-management is when you use a combination of a cloud MDM tool (Intune) and an on-premises configuration tool like System Center Configuration Manager (SCCM). You only need to use SCCM if Intune can’t support what you want to do with your profile. If you choose to co-manage using Intune + SCCM, you do it by including an SCCM agent in your Intune profile. When that profile is pushed to the device, the device will see the SCCM agent and go out to SCCM to pull down any additional profile settings. |
|
||||||
| Must we use System Center Configuration Manager (SCCM) for Windows Autopilot | No. Co-management (described above) is optional. |
|
| Must we use System Center Configuration Manager (SCCM) for Windows Autopilot | No. Co-management (described above) is optional. |
|
||||||
|
|
||||||
|
|
||||||
@ -118,7 +119,7 @@ A [glossary](#glossary) of abbreviations used in this topic is provided at the e
|
|||||||
| Question | Answer |
|
| Question | Answer |
|
||||||
| --- | --- |
|
| --- | --- |
|
||||||
| Self-deploying mode | A new version of Windows Autopilot where the user only turns on the device, and nothing else. It’s useful for scenarios where a standard user account isn’t needed (e.g., shared devices, or KIOSK devices). |
|
| Self-deploying mode | A new version of Windows Autopilot where the user only turns on the device, and nothing else. It’s useful for scenarios where a standard user account isn’t needed (e.g., shared devices, or KIOSK devices). |
|
||||||
| Hybrid Azure Active Directory join | Allows Windows Autopilot devices to connect to an on-premise Active Directory domain controller (in addition to being Azure AD joined). |
|
| Hybrid Azure Active Directory join | Allows Windows Autopilot devices to connect to an on-premises Active Directory domain controller (in addition to being Azure AD joined). |
|
||||||
| Windows Autopilot reset | Removes user apps and settings from a device, but maintains AAD domain join and MDM enrollment. Useful for when transferring a device from one user to another. |
|
| Windows Autopilot reset | Removes user apps and settings from a device, but maintains AAD domain join and MDM enrollment. Useful for when transferring a device from one user to another. |
|
||||||
| Personalization | Adds the following to the OOBE experience: A personalized welcome message can be created A username hint can be added Sign-in page text can be personalized The company’s logo can be included |
|
| Personalization | Adds the following to the OOBE experience: A personalized welcome message can be created A username hint can be added Sign-in page text can be personalized The company’s logo can be included |
|
||||||
| [Autopilot for existing devices](existing-devices.md) | Offers an upgrade path to Windows Autopilot for all existing Win 7/8 devices. |
|
| [Autopilot for existing devices](existing-devices.md) | Offers an upgrade path to Windows Autopilot for all existing Win 7/8 devices. |
|
||||||
|
@ -78,6 +78,10 @@ If the Microsoft Store is not accessible, the AutoPilot process will still conti
|
|||||||
<tr><td><b>Office 365<b><td>As part of the Intune device configuration, installation of Office 365 ProPlus may be required. For more information, see <a href="https://support.office.com/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2">Office 365 URLs and IP address ranges</a> (includes all Office services, DNS names, IP addresses; includes Azure AD and other services that may overlap with those listed above).
|
<tr><td><b>Office 365<b><td>As part of the Intune device configuration, installation of Office 365 ProPlus may be required. For more information, see <a href="https://support.office.com/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2">Office 365 URLs and IP address ranges</a> (includes all Office services, DNS names, IP addresses; includes Azure AD and other services that may overlap with those listed above).
|
||||||
<tr><td><b>Certificate revocation lists (CRLs)<b><td>Some of these services will also need to check certificate revocation lists (CRLs) for certificates used in the services. A full list of these is documented at <a href="https://support.office.com/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2#bkmk_crl">Office 365 URLs and IP address ranges</a> and <a href="https://aka.ms/o365chains">Office 365 Certificate Chains</a>.
|
<tr><td><b>Certificate revocation lists (CRLs)<b><td>Some of these services will also need to check certificate revocation lists (CRLs) for certificates used in the services. A full list of these is documented at <a href="https://support.office.com/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2#bkmk_crl">Office 365 URLs and IP address ranges</a> and <a href="https://aka.ms/o365chains">Office 365 Certificate Chains</a>.
|
||||||
<tr><td><b>Hybrid AAD join<b><td>The device can be hybrid AAD joined. The computer should be on corporate network for hybrid AAD join to work. See details at <a href="https://docs.microsoft.com/windows/deployment/windows-autopilot/user-driven-hybrid">Windows Autopilot user-driven mode</a>
|
<tr><td><b>Hybrid AAD join<b><td>The device can be hybrid AAD joined. The computer should be on corporate network for hybrid AAD join to work. See details at <a href="https://docs.microsoft.com/windows/deployment/windows-autopilot/user-driven-hybrid">Windows Autopilot user-driven mode</a>
|
||||||
|
<tr><td><b>Autopilot Self-Deploying mode and Autopilot White Glove<b><td>Firmware TPM devices, which are only provided by Intel, AMD, or Qualcomm, do not include all needed certificates at boot time and must be able to retrieve them from the manufacturer on first use. Devices with discrete TPM chips(including ones from any other manufacturer) come with these certificates preinstalled. Make sure that these URLs are accessible for each firmware TPM provider so that certificates can be successfully requested:
|
||||||
|
<br>Intel- https://ekop.intel.com/ekcertservice
|
||||||
|
<br>Qualcomm- https://ekcert.spserv.microsoft.com/EKCertificate/GetEKCertificate/v1
|
||||||
|
<br>AMD- http://ftpm.amd.com/pki/aia
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
## Licensing requirements
|
## Licensing requirements
|
||||||
|
@ -69,7 +69,13 @@ For security reasons, the package used to Offboard machines will expire 30 days
|
|||||||
|
|
||||||
2. Extract the contents of the .zip file to a shared, read-only location that can be accessed by the network administrators who will deploy the package. You should have a file named *WindowsDefenderATP_valid_until_YYYY-MM-DD.offboarding*.
|
2. Extract the contents of the .zip file to a shared, read-only location that can be accessed by the network administrators who will deploy the package. You should have a file named *WindowsDefenderATP_valid_until_YYYY-MM-DD.offboarding*.
|
||||||
|
|
||||||
3. Use the Microsoft Intune custom configuration policy to deploy the following supported OMA-URI settings. For more information on Microsoft Intune policy settings see, [Windows 10 policy settings in Microsoft Intune](https://docs.microsoft.com/intune/deploy-use/windows-10-policy-settings-in-microsoft-intune).
|
3. Use the Microsoft Intune custom configuration policy to deploy the following supported OMA-URI settings.
|
||||||
|
|
||||||
|
OMA-URI: ./Device/Vendor/MSFT/WindowsAdvancedThreatProtection/Offboarding
|
||||||
|
Date type: String
|
||||||
|
Value: [Copy and paste the value from the content of the WindowsDefenderATP_valid_until_YYYY-MM-DD.offboarding file]
|
||||||
|
|
||||||
|
For more information on Microsoft Intune policy settings see, [Windows 10 policy settings in Microsoft Intune](https://docs.microsoft.com/intune/deploy-use/windows-10-policy-settings-in-microsoft-intune).
|
||||||
|
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
|
@ -19,15 +19,19 @@ ms.date: 04/19/2017
|
|||||||
|
|
||||||
# Interactive logon: Message text for users attempting to log on
|
# Interactive logon: Message text for users attempting to log on
|
||||||
|
|
||||||
**Applies to**
|
**Applies to:**
|
||||||
|
|
||||||
- Windows 10
|
- Windows 10
|
||||||
|
|
||||||
Describes the best practices, location, values, management, and security considerations for the **Interactive logon: Message text for users attempting to log on** security policy setting.
|
Describes the best practices, location, values, management, and security considerations for the **Interactive logon: Message text for users attempting to log on** security policy setting.
|
||||||
|
|
||||||
## Reference
|
## Reference
|
||||||
|
|
||||||
The **Interactive logon: Message text for users attempting to log on** and [Interactive logon: Message title for users attempting to log on](interactive-logon-message-title-for-users-attempting-to-log-on.md) policy settings are closely related. **Interactive logon: Message text for users attempting to log on** specifies a text message to be displayed to users when they log on. Interactive logon: Message title for users attempting to log on specifies a title to appear in the title bar of the window that contains the text message. This text is often used for legal reasons—for example, to warn
|
The **Interactive logon: Message text for users attempting to log on** and [Interactive logon: Message title for users attempting to log on](interactive-logon-message-title-for-users-attempting-to-log-on.md) policy settings are closely related.
|
||||||
users about the ramifications of misusing company information, or to warn them that their actions might be audited.
|
|
||||||
|
**Interactive logon: Message text for users attempting to log on** specifies a text message to be displayed to users when they log on.
|
||||||
|
|
||||||
|
**Interactive logon: Message title for users attempting to log on** specifies a title to appear in the title bar of the window that contains the text message. This text is often used for legal reasons — for example, to warn users about the ramifications of misusing company information, or to warn them that their actions might be audited.
|
||||||
|
|
||||||
Not using this warning-message policy setting leaves your organization legally vulnerable to trespassers who unlawfully penetrate your network. Legal precedents have established that organizations that display warnings to users who connect to their servers over a network have a higher rate of successfully prosecuting trespassers.
|
Not using this warning-message policy setting leaves your organization legally vulnerable to trespassers who unlawfully penetrate your network. Legal precedents have established that organizations that display warnings to users who connect to their servers over a network have a higher rate of successfully prosecuting trespassers.
|
||||||
|
|
||||||
@ -46,7 +50,8 @@ The possible values for this setting are:
|
|||||||
|
|
||||||
1. IT IS AN OFFENSE TO CONTINUE WITHOUT PROPER AUTHORIZATION.
|
1. IT IS AN OFFENSE TO CONTINUE WITHOUT PROPER AUTHORIZATION.
|
||||||
2. This system is restricted to authorized users. Individuals who attempt unauthorized access will be prosecuted. If you are unauthorized, terminate access now. Click OK to indicate your acceptance of this information.
|
2. This system is restricted to authorized users. Individuals who attempt unauthorized access will be prosecuted. If you are unauthorized, terminate access now. Click OK to indicate your acceptance of this information.
|
||||||
>**Important:** Any warning that you display in the title or text should be approved by representatives from your organization's legal and human resources departments.
|
> [!IMPORTANT]
|
||||||
|
> Any warning that you display in the title or text should be approved by representatives from your organization's legal and human resources departments.
|
||||||
|
|
||||||
### Location
|
### Location
|
||||||
|
|
||||||
@ -92,12 +97,10 @@ Users often do not understand the importance of security practices. However, the
|
|||||||
|
|
||||||
Configure the **Interactive logon: Message text for users attempting to log on** and [Interactive logon: Message title for users attempting to log on](interactive-logon-message-title-for-users-attempting-to-log-on.md) settings to an appropriate value for your organization.
|
Configure the **Interactive logon: Message text for users attempting to log on** and [Interactive logon: Message title for users attempting to log on](interactive-logon-message-title-for-users-attempting-to-log-on.md) settings to an appropriate value for your organization.
|
||||||
|
|
||||||
>**Note:** Any warning message that displays should be approved by your organization's legal and human resources representatives.
|
|
||||||
|
|
||||||
### Potential impact
|
### Potential impact
|
||||||
|
|
||||||
Users see a message in a dialog box before they can log on to the server console.
|
Users see a message in a dialog box before they can log on to the server console.
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
- [Security Options](security-options.md)
|
- [Security Options](security-options.md)
|
||||||
|
@ -88,7 +88,7 @@ Microsoft recommends that you block the following Microsoft-signed applications
|
|||||||
- msxml6.dll
|
- msxml6.dll
|
||||||
- jscript9.dll
|
- jscript9.dll
|
||||||
|
|
||||||
Pick the correct version of each .dll for the Windows release you plan to support, and remove the other versions.
|
Pick the correct version of each .dll for the Windows release you plan to support, and remove the other versions. Ensure that you also uncomment them in the signing scenarios section.
|
||||||
|
|
||||||
```xml
|
```xml
|
||||||
<?xml version="1.0" encoding="utf-8" ?>
|
<?xml version="1.0" encoding="utf-8" ?>
|
||||||
@ -888,9 +888,11 @@ Pick the correct version of each .dll for the Windows release you plan to suppor
|
|||||||
<FileRuleRef RuleID="ID_DENY_WMIC"/>
|
<FileRuleRef RuleID="ID_DENY_WMIC"/>
|
||||||
<FileRuleRef RuleID="ID_DENY_MWFC" />
|
<FileRuleRef RuleID="ID_DENY_MWFC" />
|
||||||
<FileRuleRef RuleID="ID_DENY_WFC" />
|
<FileRuleRef RuleID="ID_DENY_WFC" />
|
||||||
|
<!-- Uncomment the relevant line(s) below if you have uncommented them in the rule definitions above.
|
||||||
<FileRuleRef RuleID="ID_DENY_MSXML3" />
|
<FileRuleRef RuleID="ID_DENY_MSXML3" />
|
||||||
<FileRuleRef RuleID="ID_DENY_MSXML6" />
|
<FileRuleRef RuleID="ID_DENY_MSXML6" />
|
||||||
<FileRuleRef RuleID="ID_DENY_JSCRIPT9" />
|
<FileRuleRef RuleID="ID_DENY_JSCRIPT9" />
|
||||||
|
-->
|
||||||
<FileRuleRef RuleID="ID_DENY_MSBUILD_DLL" />
|
<FileRuleRef RuleID="ID_DENY_MSBUILD_DLL" />
|
||||||
<FileRuleRef RuleID="ID_DENY_DOTNET" />
|
<FileRuleRef RuleID="ID_DENY_DOTNET" />
|
||||||
<FileRuleRef RuleID="ID_DENY_MS_BUILD" />
|
<FileRuleRef RuleID="ID_DENY_MS_BUILD" />
|
||||||
|
@ -28,6 +28,8 @@ These settings, located at **Computer Configuration\Administrative Templates\Net
|
|||||||
>[!NOTE]
|
>[!NOTE]
|
||||||
>You must configure either the Enterprise resource domains hosted in the cloud or Private network ranges for apps settings on your employee devices to successfully turn on Application Guard using enterprise mode.
|
>You must configure either the Enterprise resource domains hosted in the cloud or Private network ranges for apps settings on your employee devices to successfully turn on Application Guard using enterprise mode.
|
||||||
|
|
||||||
|
>Proxy servers must be a neutral resource listed in the "Domains categorized as both work and personal" policy.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|Policy name|Supported versions|Description|
|
|Policy name|Supported versions|Description|
|
||||||
|
@ -68,7 +68,7 @@ Answering frequently asked questions about Windows Defender Application Guard (A
|
|||||||
| | |
|
| | |
|
||||||
|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||||
| **Q:** | How do I configure WDAG to work with my network proxy (IP-Literal Addresses)? |
|
| **Q:** | How do I configure WDAG to work with my network proxy (IP-Literal Addresses)? |
|
||||||
| **A:** | WDAG requires proxies to have a symbolic name, not just an IP address. IP-Literal proxy settings such as “192.168.1.4:81” can be annotated as “itproxy:81” or using a record such as “P19216810010” for a proxy with an IP address of 192.168.100.10. This applies to Windows 10 Enterprise edition, 1709 or higher. |
|
| **A:** | WDAG requires proxies to have a symbolic name, not just an IP address. IP-Literal proxy settings such as “192.168.1.4:81” can be annotated as “itproxy:81” or using a record such as “P19216810010” for a proxy with an IP address of 192.168.100.10. This applies to Windows 10 Enterprise edition, 1709 or higher. These would be for the proxy policies under Network Isolation in Group Policy or Intune. |
|
||||||
|
|
||||||
<br>
|
<br>
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user