mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-13 05:47:23 +00:00
Merge branch 'public' into repo_sync_working_branch
This commit is contained in:
Tina Burden
GitHub
commit
6a99ba1ee7
@ -20,7 +20,7 @@ In Windows 10, version 1803, you can configure your HoloLens devices to run as m
|
||||
|
||||
When HoloLens is configured as a multi-app kiosk, only the allowed apps are available to the user. The benefit of a multi-app kiosk, or fixed-purpose device, is to provide an easy-to-understand experience for individuals by putting in front of them only the things they need to use, and removing from their view the things they don’t need to access.
|
||||
|
||||
Single-app kiosk mode starts the specified app when the user signs in, and restricts the user's ability to launch new apps or change the running app. When single-app kiosk mode is enabled for HoloLens, the bloom gesture and Cortana are disabled, and placed apps aren't shown in the user's surroundings.
|
||||
Single-app kiosk mode starts the specified app when the user signs in, and restricts the user's ability to launch new apps or change the running app. When single-app kiosk mode is enabled for HoloLens, the [start gestures](https://docs.microsoft.com/hololens/hololens2-basic-usage#start-gesture) (including [Bloom](https://docs.microsoft.com/hololens/hololens1-basic-usage) on HoloLens (1st Gen)) and Cortana are disabled, and placed apps aren't shown in the user's surroundings.
|
||||
|
||||
The following table lists the device capabilities in the different kiosk modes.
|
||||
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Use HoloLens offline
|
||||
title: Manage connection endpoints for HoloLens
|
||||
description: To set up HoloLens, you'll need to connect to a Wi-Fi network
|
||||
keywords: hololens, offline, OOBE
|
||||
audience: ITPro
|
||||
@ -17,13 +17,11 @@ appliesto:
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# Use HoloLens offline
|
||||
|
||||
HoloLens support a limited set of offline experiences for connectivity conscious customers and for customers who have environmental limits on connectivity.
|
||||
Some HoloLens components, apps, and related services transfer data to Microsoft network endpoints. This article lists different endpoints and URLs that need to be whitelisted in your network configuratiion (e.g. proxy or firewall) for those components to be functional.
|
||||
|
||||
## Near-offline setup
|
||||
|
||||
HoloLens need a network connection to go through initial device set up. If your corporate network has network restrictions, the following URLs will need to be available:
|
||||
HoloLens supports a limited set of offline experiences for customers who have network environment restrictions. However, HoloLens needs network connection to go through initial device set up and the following URLs have to be enabled:
|
||||
|
||||
| Purpose | URL |
|
||||
|------|------|
|
||||
@ -35,9 +33,125 @@ HoloLens need a network connection to go through initial device set up. If your
|
||||
| MSA | https://login.live.com/ppsecure/inlineconnect.srf?id=80600 |
|
||||
| MSA Pin | https://account.live.com/msangc?fl=enroll |
|
||||
|
||||
Additional references:
|
||||
## Endpoint configuration
|
||||
|
||||
In addition to the list above, to take full advantage of HoloLens functionality, the following endpoints need to be enabled in your network configuration.
|
||||
|
||||
|
||||
| Purpose | URL |
|
||||
|------|------|
|
||||
| Azure | wd-prod-fe.cloudapp.azure.com | | |
|
||||
| | ris-prod-atm.trafficmanager.net | | | |
|
||||
| | validation-v2.sls.trafficmanager.net | | | |
|
||||
| Azure AD Multi-Factor Authentication | https://secure.aadcdn.microsoftonline-p.com | | | |
|
||||
| Intune and MDM Configurations | activation-v2.sls.microsoft.com/* | | | |
|
||||
| | cdn.onenote.net | | | |
|
||||
| | client.wns.windows.com | | | |
|
||||
| | crl.microsoft.com/pki/crl/* | | | |
|
||||
| | ctldl.windowsupdate.com | | | |
|
||||
| | *displaycatalog.mp.microsoft.com | | | |
|
||||
| | dm3p.wns.windows.com | | | |
|
||||
| | *microsoft.com/pkiops/* | | | |
|
||||
| | ocsp.digicert.com/* | | | |
|
||||
| | r.manage.microsoft.com | | | |
|
||||
| | tile-service.weather.microsoft.com | | | |
|
||||
| | settings-win.data.microsoft.com | | | |
|
||||
| Certificates | activation-v2.sls.microsoft.com/* | | | |
|
||||
| | crl.microsoft.com/pki/crl/* | | | |
|
||||
| | ocsp.digicert.com/* | | | |
|
||||
| | www.microsoft.com/pkiops/* | | | |
|
||||
| Cortana and Search | store-images.*microsoft.com | | | |
|
||||
| | www.bing.com/client | | | |
|
||||
| | www.bing.com | | | |
|
||||
| | www.bing.com/proactive | | | |
|
||||
| | www.bing.com/threshold/xls.aspx | | | |
|
||||
| | exo-ring.msedge.net | | | |
|
||||
| | fp.msedge.net | | | |
|
||||
| | fp-vp.azureedge.net | | | |
|
||||
| | odinvzc.azureedge.net | | | |
|
||||
| | spo-ring.msedge.net | | | |
|
||||
| Device Authentication | login.live.com* | | | |
|
||||
| Device metadata | dmd.metaservices.microsoft.com | | | |
|
||||
| Location | inference.location.live.net | | | |
|
||||
| | location-inference-westus.cloudapp.net | | | |
|
||||
| Diagnostic Data | v10.events.data.microsoft.com | | | |
|
||||
| | v10.vortex-win.data.microsoft.com/collect/v1 | | | |
|
||||
| | www.microsoft.com | | | |
|
||||
| | co4.telecommand.telemetry.microsoft.com | | | |
|
||||
| | cs11.wpc.v0cdn.net | | | |
|
||||
| | cs1137.wpc.gammacdn.net | | | |
|
||||
| | modern.watson.data.microsoft.com* | | | |
|
||||
| | watson.telemetry.microsoft.com | | | |
|
||||
| Licensing | licensing.mp.microsoft.com | | | |
|
||||
| Microsoft Account | login.msa.akadns6.net | | | |
|
||||
| | us.configsvc1.live.com.akadns.net | | | |
|
||||
| Microsoft Edge | iecvlist.microsoft.com | | | |
|
||||
| Microsoft forward link redirection service (FWLink) | go.microsoft.com | | | |
|
||||
| Microsoft Store | *.wns.windows.com | | | |
|
||||
| | storecatalogrevocation.storequality.microsoft.com | | | |
|
||||
| | img-prod-cms-rt-microsoft-com* | | | |
|
||||
| | store-images.microsoft.com | | | |
|
||||
| | .md.mp.microsoft.com | | |
|
||||
| | *displaycatalog.mp.microsoft.com | | | |
|
||||
| | pti.store.microsoft.com | | | |
|
||||
| | storeedgefd.dsx.mp.microsoft.com | | | |
|
||||
| | markets.books.microsoft.com | | | |
|
||||
| | share.microsoft.com | | | |
|
||||
| Network Connection Status Indicator (NCSI) | www.msftconnecttest.com* | | | |
|
||||
| Office | *.c-msedge.net | | | |
|
||||
| | *.e-msedge.net | | | |
|
||||
| | *.s-msedge.net | | | |
|
||||
| | nexusrules.officeapps.live.com | | | |
|
||||
| | ocos-office365-s2s.msedge.net | | | |
|
||||
| | officeclient.microsoft.com | | | |
|
||||
| | outlook.office365.com | | | |
|
||||
| | client-office365-tas.msedge.net | | | |
|
||||
| | www.office.com | | | |
|
||||
| | onecollector.cloudapp.aria | | | |
|
||||
| | v10.events.data.microsoft.com/onecollector/1.0/ | | | |
|
||||
| | self.events.data.microsoft.com | | | |
|
||||
| | to-do.microsoft.com | | | |
|
||||
| OneDrive | g.live.com/1rewlive5skydrive/* | | | |
|
||||
| | msagfx.live.com | | | |
|
||||
| | oneclient.sfx.ms | | | |
|
||||
| Photos App | evoke-windowsservices-tas.msedge.net | | | |
|
||||
| Settings | cy2.settings.data.microsoft.com.akadns.net | | | |
|
||||
| | settings.data.microsoft.com | | | |
|
||||
| | settings-win.data.microsoft.com | | | |
|
||||
| Windows Defender | wdcp.microsoft.com | | | |
|
||||
| | definitionupdates.microsoft.com | | | |
|
||||
| | go.microsoft.com | | | |
|
||||
| | *smartscreen.microsoft.com | | | |
|
||||
| | smartscreen-sn3p.smartscreen.microsoft.com | | | |
|
||||
| | unitedstates.smartscreen-prod.microsoft.com | | | |
|
||||
| Windows Spotlight | *.search.msn.com | | | |
|
||||
| | arc.msn.com | | | |
|
||||
| | g.msn.com* | | | |
|
||||
| | query.prod.cms.rt.microsoft.com | | | |
|
||||
| | ris.api.iris.microsoft.com | | | |
|
||||
| Windows Update | *.prod.do.dsp.mp.microsoft.com | | | |
|
||||
| | cs9.wac.phicdn.net | | | |
|
||||
| | emdl.ws.microsoft.com | | | |
|
||||
| | *.dl.delivery.mp.microsoft.com | | | |
|
||||
| | *.windowsupdate.com | | | |
|
||||
| | *.delivery.mp.microsoft.com | | | |
|
||||
| | *.update.microsoft.com | | | |
|
||||
|
||||
|
||||
|
||||
## References
|
||||
|
||||
> [!NOTE]
|
||||
> If you are deploying D365 Remote Assist, you will have to enable the endpoints on this [list](https://docs.microsoft.com/office365/enterprise/urls-and-ip-address-ranges#skype-for-business-online-and-microsoft-teams)
|
||||
- [Configure Windows diagnostic data in your organization](https://docs.microsoft.com/windows/privacy/configure-windows-diagnostic-data-in-your-organization)
|
||||
- [Manage connection endpoints for Windows 10 Enterprise, version 1903](https://docs.microsoft.com/windows/privacy/manage-windows-1903-endpoints)
|
||||
- [Manage connections from Windows 10 operating system components to Microsoft services](https://docs.microsoft.com/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services)
|
||||
- [Manage connections from Windows 10 operating system components to Microsoft services using Microsoft Intune MDM Server](https://docs.microsoft.com/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-mdm)
|
||||
- [Intune network configuration requirements and bandwidth](https://docs.microsoft.com/intune/fundamentals/network-bandwidth-use#network-communication-requirements)
|
||||
- [Network endpoints for Microsoft Intune](https://docs.microsoft.com/intune/fundamentals/intune-endpoints)
|
||||
- [Office 365 URLs and IP address ranges](https://docs.microsoft.com/office365/enterprise/urls-and-ip-address-ranges)
|
||||
- [Prerequisites for Azure AD Connect](https://docs.microsoft.com/azure/active-directory/hybrid/how-to-connect-install-prerequisites)
|
||||
|
||||
- [Technical reference for AAD related IP ranges and URLs](https://docs.microsoft.com/office365/enterprise/urls-and-ip-address-ranges)
|
||||
|
||||
## HoloLens limitations
|
||||
|
||||
|
||||
@ -93,7 +93,7 @@ Internet Connectivity |Device does have Internet connectivity |Device does not h
|
||||
HTTP Version |1.1 |1.0 |If HTTP 1.0 found, it will cause issue with WU and Store |
|
||||
Direct Internet Connectivity |Device has a Proxy configured Device has no Proxy configured |N/A |Informational. Is your device behind a proxy? |
|
||||
Proxy Address | | |If configured, returns proxy address. |
|
||||
Proxy Authentication |Proxy does not require Authentication |Proxy requires Proxy Auth |Result may be a false positive if a user already has an open session in Edge and has authenticated thru the proxy. |[Configuring a proxy for your Surface Hub](https://blogs.technet.microsoft.com/y0av/2017/12/03/7/)
|
||||
Proxy Authentication |Proxy does not require Authentication |Proxy requires Proxy Auth |Result may be a false positive if a user already has an open session in Edge and has authenticated through the proxy. |[Configuring a proxy for your Surface Hub](https://blogs.technet.microsoft.com/y0av/2017/12/03/7/)
|
||||
Proxy Auth Types | | |If proxy authentication is used, return the Authentication methods advertised by the proxy. |
|
||||
|
||||
#### Environment
|
||||
|
||||
@ -29,10 +29,8 @@ Although the deployment and management of Surface devices is fundamentally the s
|
||||
|
||||
## Updating Surface device drivers and firmware
|
||||
|
||||
|
||||
For devices that recieve updates through Windows Update, drivers for Surface components (and even firmware updates) are applied automatically as part of the Windows Update process. For devices with managed updates, such as those updated through Windows Server Update Services (WSUS) or Configuration Manager, see [Manage Surface driver and firmware updates](https://docs.microsoft.com/surface/manage-surface-driver-and-firmware-updates/).
|
||||
|
||||
|
||||
> [!NOTE]
|
||||
> Surface device drivers and firmware are signed with SHA-256, which is not natively supported by Windows Server 2008 R2. A workaround is available for Configuration Manager environments running on Windows Server 2008 R2. For more information, see [Can't import drivers into Microsoft Endpoint Configuration Manager (KB3025419)](https://support.microsoft.com/kb/3025419).
|
||||
|
||||
|
||||
@ -33,9 +33,6 @@ The primary concern when selecting an Ethernet adapter is how that adapter will
|
||||
|
||||
Booting from the network (PXE boot) is only supported when you use an Ethernet adapter or docking station from Microsoft. To boot from the network, the chipset in the Ethernet adapter or dock must be detected and configured as a boot device in the firmware of the Surface device. Microsoft Ethernet adapters, such as the Surface Ethernet Adapter and the [Surface Dock](https://www.microsoft.com/surface/accessories/surface-dock) use a chipset that is compatible with the Surface firmware.
|
||||
|
||||
> [!NOTE]
|
||||
> PXE boot is not supported on Surface Pro X. For more information, refer to [Deploying, managing, and servicing Surface Pro X](surface-pro-arm-app-management.md)
|
||||
|
||||
The following Ethernet devices are supported for network boot with Surface devices:
|
||||
|
||||
- Surface USB-C to Ethernet and USB 3.0 Adapter
|
||||
|
||||
@ -19,7 +19,7 @@ ms.date: 08/30/2016
|
||||
|
||||
### Documents for download
|
||||
|
||||
- [Advanced Group Policy Management 4.0 documents](https://go.microsoft.com/fwlink/?LinkID=158931)
|
||||
- [Advanced Group Policy Management 4.0 documents](https://www.microsoft.com/download/details.aspx?id=13975)
|
||||
|
||||
### Microsoft Desktop Optimization Pack resources
|
||||
|
||||
|
||||
@ -335,7 +335,7 @@ The MBAM agent will be unable to post any updates to the database if connectivit
|
||||
User: SYSTEM
|
||||
Computer: TESTLABS.CONTOSO.COM
|
||||
Description:
|
||||
An error occured while applying MBAM policies.
|
||||
An error occurred while applying MBAM policies.
|
||||
Volume ID:\\?\Volume{871c5858-2467-4d0b-8c83-d68af8ce10e5}\
|
||||
Error code:
|
||||
0x803D0010
|
||||
@ -352,7 +352,7 @@ The MBAM agent will be unable to post any updates to the database if connectivit
|
||||
User: SYSTEM
|
||||
Computer: TESTLABS.CONTOSO.COM
|
||||
Description:
|
||||
An error occured while applying MBAM policies.
|
||||
An error occurred while applying MBAM policies.
|
||||
Volume ID:\\?\Volume{871c5858-2467-4d0b-8c83-d68af8ce10e5}\
|
||||
Error code:
|
||||
0x803D0006
|
||||
@ -420,7 +420,7 @@ The MBAM services may be unable to connect to the database server because of a n
|
||||
Computer: MBAM2-Admin.contoso.com
|
||||
Description:
|
||||
Event code: 100001
|
||||
Event message: SQL error occured
|
||||
Event message: SQL error occurred
|
||||
Event time: 7/11/2013 6:16:34 PM
|
||||
Event time (UTC): 7/11/2013 12:46:34 PM
|
||||
Event ID: 6615fb8eb9d54e778b933d5bb7ca91ed
|
||||
@ -552,7 +552,7 @@ Review the activity in the service trace log for any error or warning entries. B
|
||||
<Channel />
|
||||
<Computer>XXXXXXXXXXX</Computer>
|
||||
</System>
|
||||
<ApplicationData>AddUpdateVolume: While executing sql transaction for add volume to store exception occured Key Recovery Data Store processing error: Violation of UNIQUE KEY constraint 'UniqueRecoveryKeyId'. Cannot insert duplicate key in object 'RecoveryAndHardwareCore.Keys'. The duplicate key value is (8637036e-b379-4798-bd9e-5a0b36296de3).
|
||||
<ApplicationData>AddUpdateVolume: While executing sql transaction for add volume to store exception occurred Key Recovery Data Store processing error: Violation of UNIQUE KEY constraint 'UniqueRecoveryKeyId'. Cannot insert duplicate key in object 'RecoveryAndHardwareCore.Keys'. The duplicate key value is (8637036e-b379-4798-bd9e-5a0b36296de3).
|
||||
</ApplicationData>
|
||||
</E2ETraceEvent>
|
||||
|
||||
|
||||
@ -81,7 +81,7 @@ When you install updates to Windows XP, make sure that you remain on the version
|
||||
Although it is optional, we recommend that you install the following update for [hotfix KB972435](https://go.microsoft.com/fwlink/?LinkId=201077) (https://go.microsoft.com/fwlink/?LinkId=201077). This update increases the performance of shared folders in a Terminal Services session:
|
||||
|
||||
**Note**
|
||||
The update is publically available. However, you might be prompted to accept an agreement for Microsoft Services. Follow the prompts on the successive webpages to retrieve this hotfix.
|
||||
The update is publicly available. However, you might be prompted to accept an agreement for Microsoft Services. Follow the prompts on the successive webpages to retrieve this hotfix.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -29,7 +29,7 @@ If you are using System Center Configuration Manager 2007 SP2 and your MED-V wor
|
||||
|
||||
The [hotfix to improve the functionality for VMs that are managed by MED-V](https://go.microsoft.com/fwlink/?LinkId=201088) (https://go.microsoft.com/fwlink/?LinkId=201088) adds new functionality to virtual machines that are managed by MED-V and that are configured to operate in **NAT** mode. The new functionality lets virtual machines access the closest distribution points. Therefore, the administrator can manage the virtual machine and the host computer in the same manner. This hotfix must be installed first on the site server and then on the client.
|
||||
|
||||
The update is publically available. However, you might be prompted to accept an agreement for Microsoft Services. Follow the prompts on the successive webpages to retrieve this hotfix.
|
||||
The update is publicly available. However, you might be prompted to accept an agreement for Microsoft Services. Follow the prompts on the successive webpages to retrieve this hotfix.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -29,7 +29,7 @@ If you are using System Center Configuration Manager 2007 SP2 and your MED-V wor
|
||||
|
||||
The [hotfix to improve the functionality for VMs that are managed by MED-V](https://go.microsoft.com/fwlink/?LinkId=201088) (https://go.microsoft.com/fwlink/?LinkId=201088) adds new functionality to virtual machines that are managed by MED-V and that are configured to operate in **NAT** mode. The new functionality lets virtual machines access the closest distribution points. Therefore, the administrator can manage the virtual machine and the host computer in the same manner. This hotfix must be installed first on the site server and then on the client.
|
||||
|
||||
The update is publically available. However, you might be prompted to accept an agreement for Microsoft Services. Follow the prompts on the successive webpages to retrieve this hotfix.
|
||||
The update is publicly available. However, you might be prompted to accept an agreement for Microsoft Services. Follow the prompts on the successive webpages to retrieve this hotfix.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1806,7 +1806,7 @@ The content below are the latest versions of the DDF files:
|
||||
<Replace />
|
||||
</AccessType>
|
||||
<DefaultValue>4</DefaultValue>
|
||||
<Description>This node is used for setting or getting the block size (in Kilobytes) for the download of assoicated log file. The value range is 1~16. Default value is 4.</Description>
|
||||
<Description>This node is used for setting or getting the block size (in Kilobytes) for the download of associated log file. The value range is 1~16. Default value is 4.</Description>
|
||||
<DFFormat>
|
||||
<int />
|
||||
</DFFormat>
|
||||
|
||||
@ -957,7 +957,7 @@ The XML below is for Windows 10, version 1803.
|
||||
<Get />
|
||||
<Replace />
|
||||
</AccessType>
|
||||
<Description>Number of days after last sucessful sync to unenroll</Description>
|
||||
<Description>Number of days after last successful sync to unenroll</Description>
|
||||
<DFFormat>
|
||||
<int />
|
||||
</DFFormat>
|
||||
|
||||
@ -89,7 +89,7 @@ The following diagram shows the EnterpriseAppVManagement configuration service p
|
||||
- SYNC\_ERR\_PUBLISH\_GROUP_PACKAGES (3) - Publish group packages failed during publish.
|
||||
- SYNC\_ERR\_UNPUBLISH_PACKAGES (4) - Unpublish packages failed during publish.
|
||||
- SYNC\_ERR\_NEW_POLICY_WRITE (5) - New policy write failed during publish.
|
||||
- SYNC\_ERR\_MULTIPLE\_DURING_PUBLISH (6) - Multiple non-fatal errors occured during publish.
|
||||
- SYNC\_ERR\_MULTIPLE\_DURING_PUBLISH (6) - Multiple non-fatal errors occurred during publish.
|
||||
|
||||
<p style="margin-left: 20px">Value type is string. Supported operation is Get.</p>
|
||||
|
||||
|
||||
@ -5,7 +5,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: dansimp
|
||||
ms.localizationpriority: medium
|
||||
ms.localizationpriority: medium
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 04/30/2018
|
||||
@ -57,7 +57,7 @@ See [Dialer codes to launch diagnostic applications](https://docs.microsoft.com/
|
||||
|
||||
## PerSimSettings
|
||||
|
||||
Use to configure settings for each subscriber identification module (SIM) card. Enter the Integrated Circuit Card Identifier (ICCID) for the SIM card, select **Add**, and then configure the folowing settings.
|
||||
Use to configure settings for each subscriber identification module (SIM) card. Enter the Integrated Circuit Card Identifier (ICCID) for the SIM card, select **Add**, and then configure the following settings.
|
||||
|
||||
### Critical
|
||||
|
||||
|
||||
@ -81,7 +81,7 @@ SyncSender | Specify a value for SyncSender that is greater than 3 characters bu
|
||||
|
||||
## PerSimSettings
|
||||
|
||||
Use to configure settings for each subscriber identification module (SIM) card. Enter the Integrated Circuit Card Identifier (ICCID) for the SIM card, click **Add**, and then configure the folowing settings.
|
||||
Use to configure settings for each subscriber identification module (SIM) card. Enter the Integrated Circuit Card Identifier (ICCID) for the SIM card, click **Add**, and then configure the following settings.
|
||||
|
||||
### AllowMmsIfDataIsOff
|
||||
|
||||
|
||||
@ -272,7 +272,7 @@ For clients that should have their feature updates approved as soon as they’re
|
||||
Now, whenever Windows 10 feature updates are published to WSUS, they will automatically be approved for the **Ring 3 Broad IT** deployment ring with an installation deadline of 1 week.
|
||||
|
||||
> [!WARNING]
|
||||
> The auto approval rule runs after synchronization occurs. This means that the *next* upgrade for each Windows 10 version will be approved. If you select **Run Rule**, all possible updates that meet the criteria will be approved, potentially including older updates that you don't actualy want--which can be a problem when the download sizes are very large.
|
||||
> The auto approval rule runs after synchronization occurs. This means that the *next* upgrade for each Windows 10 version will be approved. If you select **Run Rule**, all possible updates that meet the criteria will be approved, potentially including older updates that you don't actually want--which can be a problem when the download sizes are very large.
|
||||
|
||||
## Manually approve and deploy feature updates
|
||||
|
||||
|
||||
@ -11,7 +11,8 @@ ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
audience: itpro
author: greg-lindsay
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
@ -24,7 +25,7 @@ The simplest path to upgrade PCs that are currently running Windows 7, Windows
|
||||
|
||||
## Proof-of-concept environment
|
||||
|
||||
For the purposes of this topic, we will use four machines: DC01, MDT01, and PC0001. DC01 is a domain controller and MDT01 is a Windows Server 2012 R2 standard machine, fully patched with the latest security updates, and configured as a member server in the fictional contoso.com domain. PC0001 is a machine with Windows 7 SP1, targeted for the Windows 10 upgrade. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](../deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit.md).
|
||||
For the purposes of this topic, we will use three machines: DC01, MDT01, and PC0001. DC01 is a domain controller and MDT01 is a Windows Server 2012 R2 standard machine, fully patched with the latest security updates, and configured as a member server in the fictional contoso.com domain. PC0001 is a machine with Windows 7 SP1, targeted for the Windows 10 upgrade. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](../deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit.md).
|
||||
|
||||
|
||||
|
||||
|
||||
@ -31,17 +31,16 @@ The Volume Activation Management Tool (VAMT) can be used to perform activations
|
||||
|
||||
The following table lists the system requirements for the VAMT host computer.
|
||||
|
||||
|Item |Minimum system requirement |
|
||||
|-----|---------------------------|
|
||||
|Computer and Processor |1 GHz x86 or x64 processor |
|
||||
|Memory |1 GB RAM for x86 or 2 GB RAM for x64 |
|
||||
|Hard Disk |16 GB available hard disk space for x86 or 20 GB for x64 |
|
||||
|External Drive|Removable media (Optional) |
|
||||
|Display |1024x768 or higher resolution monitor |
|
||||
|Network |Connectivity to remote computers via Windows® Management Instrumentation (TCP/IP) and Microsoft® Activation Web Service on the Internet via HTTPS |
|
||||
|Operating System |Windows 7, Windows 8, Windows 8.1, Windows 10, Windows Server 2008 R2, or Windows Server 2012. |
|
||||
|Additional Requirements |<ul><li>Connection to a SQL Server database. For more info, see [Install VAMT](install-vamt.md).</li><li>PowerShell 3.0: For Windows 8, Windows 8.1, Windows 10, and Windows Server® 2012, PowerShell is included in the installation. For previous versions of Windows and
|
||||
Windows Server, you must download PowerShell 3.0. To download PowerShell, go to [Download Windows PowerShell 3.0](https://go.microsoft.com/fwlink/p/?LinkId=218356).</li><li>If installing on Windows Server 2008 R2, you must also install .NET Framework 3.51.</li></ul> |
|
||||
| Item | Minimum system requirement |
|
||||
| ---- | ---------------------------|
|
||||
| Computer and Processor | 1 GHz x86 or x64 processor |
|
||||
| Memory | 1 GB RAM for x86 or 2 GB RAM for x64 |
|
||||
| Hard Disk | 16 GB available hard disk space for x86 or 20 GB for x64 |
|
||||
| External Drive | Removable media (Optional) |
|
||||
| Display | 1024x768 or higher resolution monitor |
|
||||
| Network | Connectivity to remote computers via Windows Management Instrumentation (TCP/IP) and Microsoft Activation Web Service on the Internet via HTTPS |
|
||||
| Operating System | Windows 7, Windows 8, Windows 8.1, Windows 10, Windows Server 2008 R2, Windows Server 2012, or later. |
|
||||
| Additional Requirements | <ul><li>Connection to a SQL Server database. For more info, see [Install VAMT](install-vamt.md).</li><li>PowerShell 3.0: For Windows 8, Windows 8.1, Windows 10, and Windows Server 2012, PowerShell is included in the installation. For previous versions of Windows and Windows Server, you must download PowerShell 3.0. To download PowerShell, go to [Download Windows PowerShell 3.0](https://go.microsoft.com/fwlink/p/?LinkId=218356).</li><li>If installing on Windows Server 2008 R2, you must also install .NET Framework 3.51.</li></ul> |
|
||||
|
||||
## Related topics
|
||||
- [Install and Configure VAMT](install-configure-vamt.md)
|
||||
|
||||
@ -215,7 +215,7 @@ See the following examples.
|
||||
- Click **Next**.
|
||||
|
||||
>[!NOTE]
|
||||
>The Autopilot for existing devices task sequence will result in an Azure Active Directory Domain (AAD) joined device. The User State Migration Toolkit (USMT) does not support AAD joined or hybrid AAD joined devices.
|
||||
>Because the Autopilot for existing devices task sequence completes while in Windows PE, User State Migration Toolkit (USMT) data migration is not supported as there is no way to restore the user state into the new OS. Also, the User State Migration Toolkit (USMT) does not support Azure AD-joined devices.
|
||||
|
||||
7. On the Include Updates page, choose one of the three available options. This selection is optional.
|
||||
8. On the Install applications page, add applications if desired. This is optional.
|
||||
|
||||
@ -121,8 +121,11 @@ Specific scenarios will then have additional requirements. Generally, there are
|
||||
See [Windows Autopilot Scenarios](windows-autopilot-scenarios.md) for additional details.
|
||||
|
||||
For a walkthrough for some of these and related steps, see this video:
|
||||
<br> <br>
|
||||
<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/KYVptkpsOqs" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
|
||||
|
||||
</br>
|
||||
|
||||
<iframe width="560" height="315" src="https://www.youtube.com/embed/KYVptkpsOqs" frameborder="0" allow="accelerometer; autoplay; encrypted-media" gyroscope; picture-in-picture" allowfullscreen></iframe>
|
||||
|
||||
|
||||
There are no additional hardware requirements to use Windows 10 Autopilot, beyond the [requirements to run Windows 10](https://www.microsoft.com/windows/windows-10-specifications).
|
||||
|
||||
|
||||
@ -334,7 +334,7 @@ A strong password is assigned to the KRBTGT and trust accounts automatically. Li
|
||||
|
||||
Resetting the password requires you either to be a member of the Domain Admins group, or to have been delegated with the appropriate authority. In addition, you must be a member of the local Administrators group, or you must have been delegated the appropriate authority.
|
||||
|
||||
After you reset the KRBTGT password, ensure that event ID 6 in the (Kerberos) Key-Distribution-Center event source is written to the System event log.
|
||||
After you reset the KRBTGT password, ensure that event ID 9 in the (Kerberos) Key-Distribution-Center event source is written to the System event log.
|
||||
|
||||
### Security considerations
|
||||
|
||||
|
||||
@ -78,9 +78,6 @@ Applications may cause performance issues when they attempt to hook the isolated
|
||||
|
||||
Services or protocols that rely on Kerberos, such as file shares, remote desktop, or BranchCache, continue to work and are not affected by Windows Defender Credential Guard.
|
||||
|
||||
See this video: [Credentials Protected by Windows Defender Credential Guard](https://mva.microsoft.com/en-us/training-courses/deep-dive-into-credential-guard-16651?l=pdc37LJyC_1204300474)
|
||||
|
||||
|
||||
## Security considerations
|
||||
|
||||
All computers that meet baseline protections for hardware, firmware, and software can use Windows Defender Credential Guard.
|
||||
|
||||
@ -55,6 +55,9 @@ Sign-in a certificate authority or management workstations with _Domain Admin_ e
|
||||
7. On the **Cryptography** tab, select **Key Storage Provider** from the **Provider Category** list. Select **RSA** from the **Algorithm name** list. Type **2048** in the **Minimum key size** text box. Select **SHA256** from the **Request hash** list. Click **OK**.
|
||||
8. Close the console.
|
||||
|
||||
>[!NOTE]
|
||||
>Don't confuse the **Request hash** algorithm with the hash argorithm of the certificate.
|
||||
|
||||
#### Configure Certificate Superseding for the Domain Controller Authentication (Kerberos) Certificate Template
|
||||
|
||||
Many domain controllers may have an existing domain controller certificate. The Active Directory Certificate Services provides a default certificate template for domain controllers--the domain controller certificate template. Later releases provided a new certificate template--the domain controller authentication certificate template. These certificate templates were provided prior to update of the Kerberos specification that stated Key Distribution Centers (KDCs) performing certificate authentication needed to include the **KDC Authentication** extension.
|
||||
|
||||
@ -47,7 +47,7 @@ Microsoft information protection technologies include:
|
||||
## How WIP protects sensitivity labels with endpoint data loss prevention
|
||||
|
||||
You can create and manage [sensitivity labels](https://docs.microsoft.com/office365/securitycompliance/labels) in the Microsoft 365 compliance center.
|
||||
When you create a sensitivity label, you can specify that endpoint data loss prevention applies to content with that label.
|
||||
When you [create a sensitivity label](https://docs.microsoft.com/microsoft-365/compliance/create-sensitivity-labels), you can specify that endpoint data loss prevention applies to content with that label.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -101,11 +101,13 @@ Use the [./Vendor/MSFT/Policy/Config/ControlledFolderAccessProtectedFolders](htt
|
||||
* **Enable** - Malicious and suspicious apps will not be allowed to make changes to files in protected folders. A notification will be provided in the Windows event log
|
||||
* **Disable (Default)** - The Controlled folder access feature will not work. All apps can make changes to files in protected folders.
|
||||
* **Audit Mode** - If a malicious or suspicious app attempts to make a change to a file in a protected folder, the change will be allowed but will be recorded in the Windows event log. This allows you to assess the impact of this feature on your organization.
|
||||
* **Block disk modification only** - Attempts by untrusted apps to write to disk sectors will be logged in Windows Event log. These logs can be found in **Applications and Services Logs** > Microsoft > Windows > Windows Defender > Operational > ID 1123.
|
||||
* **Audit disk modification only** - Only attempts to write to protected disk sectors will be recorded in the Windows event log (under **Applications and Services Logs** > **Microsoft** > **Windows** > **Windows Defender** > **Operational** > **ID 1124**). Attempts to modify or delete files in protected folders will not be recorded.
|
||||
|
||||
|
||||
|
||||
|
||||
> [!IMPORTANT]
|
||||
> To fully enable controlled folder access, you must set the Group Policy option to **Enabled** and also select **Enable** in the options drop-down menu.
|
||||
> To fully enable controlled folder access, you must set the Group Policy option to **Enabled** and select **Block** in the options drop-down menu.
|
||||
|
||||
## PowerShell
|
||||
|
||||
|
||||
@ -127,8 +127,8 @@ If you are looking for a pre-made simulation, you can use our ["Do It Yourself"
|
||||
|
||||
You can also use [Advanced hunting](advanced-hunting-query-language.md) to query data and [Threat analytics](threat-analytics.md) to view reports about emerging threats.
|
||||
|
||||
>[!NOTE]
|
||||
>The connection to the test machines is done using RDP. Make sure that your firewall settings allow RDP connections.
|
||||
> [!NOTE]
|
||||
> The connection to the test machines is done using RDP. Make sure that your firewall settings allow RDP connections.
|
||||
|
||||
1. Connect to your machine and run an attack simulation by selecting **Connect**.
|
||||
|
||||
@ -179,4 +179,3 @@ Your feedback helps us get better in protecting your environment from advanced a
|
||||
Let us know what you think, by selecting **Provide feedback**.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -119,11 +119,11 @@ The following commands are available for user roles that's been granted the abil
|
||||
Command | Description
|
||||
:---|:---
|
||||
analyze | Analyses the entity with various incrimination engines to reach a verdict.
|
||||
getfile | Gets a file from the machine. <br> NOTE: This command has a prerequisite command. You can use the `-auto` command in conjuction with `getfile` to automatically run the prerequisite command.
|
||||
getfile | Gets a file from the machine. <br> NOTE: This command has a prerequisite command. You can use the `-auto` command in conjunction with `getfile` to automatically run the prerequisite command.
|
||||
run | Runs a PowerShell script from the library on the machine.
|
||||
library | Lists files that were uploaded to the live response library.
|
||||
putfile | Puts a file from the library to the machine. Files are saved in a working folder and are deleted when the machine restarts by default.
|
||||
remediate | Remediates an entity on the machine. The remediation action will vary depending on the entity type:<br>- File: delete<br>- Process: stop, delete image file<br>- Service: stop, delete image file<br>- Registry entry: delete<br>- Scheduled task: remove<br>- Startup folder item: delete file <br> NOTE: This command has a prerequisite command. You can use the `-auto` command in conjuction with `remediate` to automatically run the prerequisite command.
|
||||
remediate | Remediates an entity on the machine. The remediation action will vary depending on the entity type:<br>- File: delete<br>- Process: stop, delete image file<br>- Service: stop, delete image file<br>- Registry entry: delete<br>- Scheduled task: remove<br>- Startup folder item: delete file <br> NOTE: This command has a prerequisite command. You can use the `-auto` command in conjunction with `remediate` to automatically run the prerequisite command.
|
||||
undo | Restores an entity that was remediated.
|
||||
|
||||
|
||||
|
||||
@ -41,7 +41,10 @@ The Security Compliance Toolkit consists of:
|
||||
- Windows Server 2012 R2
|
||||
|
||||
- Microsoft Office security baseline
|
||||
- Office365 ProPlus (Sept 2019)
|
||||
- Office 365 ProPlus (Sept 2019)
|
||||
|
||||
- Microsoft Edge security baseline
|
||||
- Version 79
|
||||
|
||||
- Tools
|
||||
- Policy Analyzer tool
|
||||
|
||||
@ -20,7 +20,7 @@ ms.date: 04/19/2017
|
||||
# Network security: Configure encryption types allowed for Kerberos
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows 2000 Server, Windows XP, Windows Server 2003, Windows Vista, Windows 7, Windows 8, Windows 8.1, Windows 10, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2
|
||||
|
||||
Describes the best practices, location, values and security considerations for the **Network security: Configure encryption types allowed for Kerberos** security policy setting.
|
||||
|
||||
@ -35,11 +35,11 @@ The following table lists and explains the allowed encryption types.
|
||||
|
||||
| Encryption type | Description and version support |
|
||||
| - | - |
|
||||
| DES_CBC_CRC | Data Encryption Standard with Cipher Block Chaining using the Cyclic Redundancy Check function<br/>Supported in Windows 2000 Server, Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008. The Windows 7, Windows 10 and Windows Server 2008 R2 operating systems do not support DES by default. |
|
||||
| DES_CBC_MD5| Data Encryption Standard with Cipher Block Chaining using the Message-Digest algorithm 5 checksum function<br/>Supported in Windows 2000 Server, Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008. The Windows 7, Windows 10 and Windows Server 2008 R2 operating systems do not support DES by default. |
|
||||
| RC4_HMAC_MD5| Rivest Cipher 4 with Hashed Message Authentication Code using the Message-Digest algorithm 5 checksum function<br/>Supported in Windows 2000 Server, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows 10 and Windows Server 2008 R2.|
|
||||
| AES128_HMAC_SHA1| Advanced Encryption Standard in 128 bit cipher block with Hashed Message Authentication Code using the Secure Hash Algorithm (1).<br/>Not supported in Windows 2000 Server, Windows XP, or Windows Server 2003. Supported in Windows Vista, Windows Server 2008, Windows 7, Windows 10 and Windows Server 2008 R2. |
|
||||
| AES256_HMAC_SHA1| Advanced Encryption Standard in 256 bit cipher block with Hashed Message Authentication Code using the Secure Hash Algorithm (1).<br/>Not supported in Windows 2000 Server, Windows XP, or Windows Server 2003. Supported in Windows Vista, Windows Server 2008, Windows 7, Windows 10 and Windows Server 2008 R2. |
|
||||
| DES_CBC_CRC | Data Encryption Standard with Cipher Block Chaining using the Cyclic Redundancy Check function<br/>Supported in Windows 2000 Server, Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008. The Windows 7, Windows 10, Windows Server 2008 R2 and later operating systems do not support DES by default. |
|
||||
| DES_CBC_MD5| Data Encryption Standard with Cipher Block Chaining using the Message-Digest algorithm 5 checksum function<br/>Supported in Windows 2000 Server, Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008. The Windows 7, Windows 10, Windows Server 2008 R2 and later operating systems do not support DES by default. |
|
||||
| RC4_HMAC_MD5| Rivest Cipher 4 with Hashed Message Authentication Code using the Message-Digest algorithm 5 checksum function<br/>Supported in Windows 2000 Server, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows 10, Windows Server 2008 R2, Windows Server 2012 and Windows Server 2012 R2.|
|
||||
| AES128_HMAC_SHA1| Advanced Encryption Standard in 128 bit cipher block with Hashed Message Authentication Code using the Secure Hash Algorithm (1).<br/>Not supported in Windows 2000 Server, Windows XP, or Windows Server 2003. Supported in Windows Vista, Windows Server 2008, Windows 7, Windows 10, Windows Server 2008 R2, Windows Server 2012 and Windows Server 2012 R2. |
|
||||
| AES256_HMAC_SHA1| Advanced Encryption Standard in 256 bit cipher block with Hashed Message Authentication Code using the Secure Hash Algorithm (1).<br/>Not supported in Windows 2000 Server, Windows XP, or Windows Server 2003. Supported in Windows Vista, Windows Server 2008, Windows 7, Windows 10, Windows Server 2008 R2, Windows Server 2012 and Windows Server 2012 R2. |
|
||||
| Future encryption types| Reserved by Microsoft for additional encryption types that might be implemented.|
|
||||
|
||||
### Possible values
|
||||
|
||||
@ -266,7 +266,7 @@ This section lists the exclusions that are delivered automatically when you inst
|
||||
|
||||
- %windir%\Ntds\ntds.pat
|
||||
|
||||
- The AD DS transaction log files. The transaction log files are specified in the registry key `HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters\Database Log Files`
|
||||
- The AD DS transaction log files. The transaction log files are specified in the registry key `HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters\Database Log Files Path`
|
||||
|
||||
- %windir%\Ntds\EDB*.log
|
||||
|
||||
|
||||
@ -121,7 +121,7 @@ Here's what you see in the Windows Security app:
|
||||
|
||||
If you are using Windows OS [1709](https://docs.microsoft.com/windows/release-information/status-windows-10-1709), [1803](https://docs.microsoft.com/windows/release-information/status-windows-10-1803), or [1809](https://docs.microsoft.com/windows/release-information/status-windows-10-1809-and-windows-server-2019), you won't see **Tamper Protection** in the Windows Security app. In this case, you can use PowerShell to determine whether tamper protection is enabled.
|
||||
|
||||
#### Use PowerShell to determine whether tamper protection is turned
|
||||
#### Use PowerShell to determine whether tamper protection is turned on
|
||||
|
||||
1. Open the Windows PowerShell app.
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Why you should use Windows Defender Antivirus together with Microsoft Defender Advanced Threat Protection
|
||||
description: For best results, use Windows Defender Antivirus together with your other Microsoft offerings.
|
||||
keywords: windows defender, antivirus
|
||||
keywords: windows defender, antivirus, third party av
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
ms.pagetype: security
|
||||
ms.prod: w10
|
||||
|
||||
@ -32,7 +32,8 @@ Refer to the below video for an overview and brief demo.
|
||||
|
||||
## Policy Authorization Process
|
||||
|
||||
The general steps for expanding the S mode base policy on your devices are to generate a supplemental policy, sign that policy, and then upload the signed policy to Intune and assign it to user or device groups.
|
||||
The general steps for expanding the S mode base policy on your Intune-managed devices are to generate a supplemental policy, sign that policy, and then upload the signed policy to Intune and assign it to user or device groups. Because you need access to WDAC PowerShell cmdlets to generate your supplemental policy, you should create and manage your policies on a non-S mode device. Once the policy has been uploaded to Intune, we recommend assigning it to a single test S-mode device to verify expected functioning before deploying the policy more broadly.
|
||||
|
||||
1. Generate a supplemental policy with WDAC tooling
|
||||
|
||||
This policy will expand the S mode base policy to authorize additional applications. Anything authorized by either the S mode base policy or your supplemental policy will be allowed to run. Your supplemental policies can specify filepath rules, trusted publishers, and more.
|
||||
@ -60,7 +61,7 @@ The general steps for expanding the S mode base policy on your devices are to ge
|
||||
- Since you'll be signing your policy, you must authorize the signing certificate you will use to sign the policy and optionally one or more additional signers that can be used to sign updates to the policy in the future. For more information, refer to Section 2, Sign policy. Use Add-SignerRule to add the signing certificate to the WDAC policy:
|
||||
|
||||
```powershell
|
||||
Add-SignerRule -FilePath <policypath> -CertificatePath <certpath> -User -Update`
|
||||
Add-SignerRule -FilePath <policypath> -CertificatePath <certpath> -User -Update
|
||||
```
|
||||
- Convert to .bin using [ConvertFrom-CIPolicy](https://docs.microsoft.com/powershell/module/configci/convertfrom-cipolicy?view=win10-ps)
|
||||
|
||||
@ -70,7 +71,7 @@ The general steps for expanding the S mode base policy on your devices are to ge
|
||||
|
||||
2. Sign policy
|
||||
|
||||
Supplemental S mode policies must be digitally signed. To sign your policy, you can choose to use the Device Guard Signing Service or your organization's custom Public Key Infrastructure (PKI). Refer to [Use the Device Guard Signing Portal in the Microsoft Store for Business](use-device-guard-signing-portal-in-microsoft-store-for-business.md) for guidance on using DGSS and [Create a code signing cert for WDAC](create-code-signing-cert-for-windows-defender-application-control.md) for guidance on signing using an internal CA.
|
||||
Supplemental S mode policies must be digitally signed. To sign your policy, you can choose to use the Device Guard Signing Service (DGSS) or your organization's custom Public Key Infrastructure (PKI). Refer to [Use the Device Guard Signing Portal in the Microsoft Store for Business](use-device-guard-signing-portal-in-microsoft-store-for-business.md) for guidance on using DGSS and [Create a code signing cert for WDAC](create-code-signing-cert-for-windows-defender-application-control.md) for guidance on signing using an internal CA.
|
||||
|
||||
Rename your policy to "{PolicyID}.p7b" after you've signed it. PolicyID can be found by inspecting the Supplemental Policy XML.
|
||||
|
||||
@ -91,7 +92,7 @@ Your supplemental policy can be used to significantly relax the S mode base poli
|
||||
|
||||
Instead of authorizing signers external to your organization, Intune has added new functionality to make it easier to authorize existing applications (without requiring repackaging or access to the source code) through the use of signed catalogs. This works for apps which may be unsigned or even signed apps when you don’t want to trust all apps that may share the same signing certificate.
|
||||
|
||||
The basic process is to generate a catalog file for each app using Package Inspector, then sign the catalog files using the DGSS or a custom PKI. After that, IT Pros can use the standard Intune app deployment process outlined above. Refer to [Deploy catalog files to support Windows Defender Application Control](deploy-catalog-files-to-support-windows-defender-application-control.md) for more in-depth guidance on generating catalogs.
|
||||
The basic process is to generate a catalog file for each app using Package Inspector, then sign the catalog files using the DGSS or a custom PKI. Use the Add-SignerRule PowerShell cmdlet as shown above to authorize the catalog signing certificate in the supplemental policy. After that, IT Pros can use the standard Intune app deployment process outlined above. Refer to [Deploy catalog files to support Windows Defender Application Control](deploy-catalog-files-to-support-windows-defender-application-control.md) for more in-depth guidance on generating catalogs.
|
||||
|
||||
> [!Note]
|
||||
> Every time an app updates, you will need to deploy an updated catalog. Because of this, IT Pros should try to avoid using catalog files for applications that auto-update and direct users not to update applications on their own.
|
||||
@ -180,8 +181,11 @@ Below is a sample policy that allows kernel debuggers, PowerShell ISE, and Regis
|
||||
</SiPolicy>
|
||||
```
|
||||
## Policy removal
|
||||
In order to revert users to an unmodified S mode policy, an IT Pro can remove a user or users from the targeted Intune group which received the policy, which will trigger a removal of both the policy and the authorization token from the device.
|
||||
|
||||
IT Pros also have the choice of deleting a supplemental policy through Intune.
|
||||
> [!Note]
|
||||
> This feature currently has a known a policy deletion bug, with a fix expected in the 2D update in late February 2020. Devices of users who are unenrolled will still have their WDAC policies removed. In the mentime, IT Pros are recommended to update their policy with the below 'empty' policy which makes no changes to S mode.
|
||||
> This feature currently has a known bug which occurs when an S mode supplemental policy is deleted through Intune, in which the policy is not immediately removed from the devices to which it was deployed. A fix is expected in the 2D update in late February 2020. In the meantime, IT Pros are recommended to update their policy with the below 'empty' policy which makes no changes to S mode.
|
||||
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
@ -233,3 +237,6 @@ Below is a sample policy that allows kernel debuggers, PowerShell ISE, and Regis
|
||||
</Settings>
|
||||
</SiPolicy>
|
||||
```
|
||||
|
||||
## Errata
|
||||
If an S-mode device with a policy authorization token and supplemental policy is rolled back from the 1909 update to the 1903 build, it will not revert to locked-down S mode until the next policy refresh. To achieve an immediate change to a locked-down S mode state, IT Pros should delete any tokens in %SystemRoot%\System32\CI\Tokens\Active.
|
||||
|
||||
@ -160,9 +160,8 @@ Pick the correct version of each .dll for the Windows release you plan to suppor
|
||||
<Deny ID="ID_DENY_MS_BUILD" FriendlyName="Microsoft.Build.dll" FileName="Microsoft.Build.dll" MinimumFileVersion="65535.65535.65535.65535" />
|
||||
<Deny ID="ID_DENY_MS_BUILD_FMWK" FriendlyName="Microsoft.Build.Framework.dll" FileName="Microsoft.Build.Framework.dll" MinimumFileVersion="65535.65535.65535.65535" />
|
||||
|
||||
<!-- msxml3.dll pick correct version based on release you are supporting -->
|
||||
<!-- msxml6.dll pick correct version based on release you are supporting -->
|
||||
<!-- jscript9.dll pick correct version based on release you are supporting -->
|
||||
<!-- pick the correct version of msxml3.dll, msxml6.dll, and jscript9.dll based on the release you are supporting -->
|
||||
<!-- the versions of these files in the 1903 release have this issue fixed, so they don’t need to be blocked -->
|
||||
<!-- RS1 Windows 1607
|
||||
<Deny ID="ID_DENY_MSXML3" FriendlyName="msxml3.dll" FileName="msxml3.dll" MinimumFileVersion ="8.110.14393.2550"/>
|
||||
<Deny ID="ID_DENY_MSXML6" FriendlyName="msxml6.dll" FileName="msxml6.dll" MinimumFileVersion ="6.30.14393.2550"/>
|
||||
@ -893,7 +892,7 @@ Pick the correct version of each .dll for the Windows release you plan to suppor
|
||||
<FileRuleRef RuleID="ID_DENY_WMIC"/>
|
||||
<FileRuleRef RuleID="ID_DENY_MWFC" />
|
||||
<FileRuleRef RuleID="ID_DENY_WFC" />
|
||||
<!-- Uncomment the relevant line(s) below if you have uncommented them in the rule definitions above.
|
||||
<!-- 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_MSXML6" />
|
||||
<FileRuleRef RuleID="ID_DENY_JSCRIPT9" />
|
||||
|
||||
@ -67,7 +67,7 @@ You can set several rule options within a WDAC policy. Table 1 describes each ru
|
||||
| **15 Enabled:Invalidate EAs on Reboot** | When the Intelligent Security Graph option (14) is used, WDAC sets an extended file attribute that indicates that the file was authorized to run. This option will cause WDAC to periodically re-validate the reputation for files that were authorized by the ISG.|
|
||||
| **16 Enabled:Update Policy No Reboot** | Use this option to allow future WDAC policy updates to apply without requiring a system reboot. |
|
||||
| **17 Enabled:Allow Supplemental Policies** | Use this option on a base policy to allow supplemental policies to expand it. |
|
||||
| **18 Disabled:Runtime FilePath Rule Protection** | Disable default FilePath rule protection (apps and executables allowed based on file path rules must come from a file path that’s only writable by an administrator) for the path specified in the FilePathRule parameter of the New-CIPolicyRule cmdlet. |
|
||||
| **18 Disabled:Runtime FilePath Rule Protection** | Disable default FilePath rule protection (apps and executables allowed based on file path rules must come from a file path that’s only writable by an administrator) for any FileRule that allows a file based on FilePath. |
|
||||
| **19 Enabled:Dynamic Code Security** | Enables policy enforcement for .NET applications and dynamically-loaded libraries. |
|
||||
|
||||
## Windows Defender Application Control file rule levels
|
||||
@ -83,11 +83,6 @@ Each file rule level has its benefit and disadvantage. Use Table 2 to select the
|
||||
| **Hash** | Specifies individual hash values for each discovered binary. Although this level is specific, it can cause additional administrative overhead to maintain the current product versions’ hash values. Each time a binary is updated, the hash value changes, therefore requiring a policy update. |
|
||||
| **FileName** | Specifies individual binary file names. Although the hash values for an application are modified when updated, the file names are typically not. This offers less specific security than the hash level but does not typically require a policy update when any binary is modified. |
|
||||
| **FilePath** | Beginning with Windows 10 version 1903, this specifies rules that allow execution of binaries contained under specific file path locations. Additional information about FilePath level rules can be found below. |
|
||||
> [!NOTE]
|
||||
> Due to an existing bug, you can not combine Path-based ALLOW rules with any DENY rules in a single policy. Instead, either separate DENY rules into a separate Base policy or move the Path-based ALLOW rules into a supplemental policy as described in [Deploy multiple WDAC policies.](deploy-multiple-windows-defender-application-control-policies.md)
|
||||
|
||||
| Rule level | Description |
|
||||
|----------- | ----------- |
|
||||
| **SignedVersion** | This combines the publisher rule with a version number. This option allows anything from the specified publisher, with a version at or above the specified version number, to run. |
|
||||
| **Publisher** | This is a combination of the PcaCertificate level (typically one certificate below the root) and the common name (CN) of the leaf certificate. This rule level allows organizations to trust a certificate from a major CA (such as Symantec), but only if the leaf certificate is from a specific company (such as Intel, for device drivers). |
|
||||
| **FilePublisher** | This is a combination of the “FileName” attribute of the signed file, plus “Publisher” (PCA certificate with CN of leaf), plus a minimum version number. This option trusts specific files from the specified publisher, with a version at or above the specified version number. |
|
||||
@ -101,6 +96,9 @@ Each file rule level has its benefit and disadvantage. Use Table 2 to select the
|
||||
> [!NOTE]
|
||||
> When you create WDAC policies with [New-CIPolicy](https://docs.microsoft.com/powershell/module/configci/new-cipolicy), you can specify a primary file rule level by including the **-Level** parameter. For discovered binaries that cannot be trusted based on the primary file rule criteria, use the **-Fallback** parameter. For example, if the primary file rule level is PCACertificate but you would like to trust the unsigned applications as well, using the Hash rule level as a fallback adds the hash values of binaries that did not have a signing certificate.
|
||||
|
||||
> [!NOTE]
|
||||
> WDAC only supports signer rules for RSA certificate signing keys with a maximum of 4096 bits.
|
||||
|
||||
## Example of file rule levels in use
|
||||
|
||||
For example, consider some IT professionals in a department that runs many servers. They decide they want their servers to run only software signed by the providers of their software and drivers, that is, the companies that provide their hardware, operating system, antivirus, and other important software. They know that their servers also run an internally written application that is unsigned but is rarely updated. They want to allow this application to run.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user