Merge remote-tracking branch 'refs/remotes/origin/master' into jdsh
@ -142,6 +142,7 @@
|
|||||||
#### [EnterpriseModernAppManagement XSD](enterprisemodernappmanagement-xsd.md)
|
#### [EnterpriseModernAppManagement XSD](enterprisemodernappmanagement-xsd.md)
|
||||||
### [FileSystem CSP](filesystem-csp.md)
|
### [FileSystem CSP](filesystem-csp.md)
|
||||||
### [Firewall CSP](firewall-csp.md)
|
### [Firewall CSP](firewall-csp.md)
|
||||||
|
#### [Firewall DDF file](firewall-ddf-file.md)
|
||||||
### [HealthAttestation CSP](healthattestation-csp.md)
|
### [HealthAttestation CSP](healthattestation-csp.md)
|
||||||
#### [HealthAttestation DDF](healthattestation-ddf.md)
|
#### [HealthAttestation DDF](healthattestation-ddf.md)
|
||||||
### [HotSpot CSP](hotspot-csp.md)
|
### [HotSpot CSP](hotspot-csp.md)
|
||||||
|
@ -1148,6 +1148,34 @@ The following tables show the configuration service providers support in Windows
|
|||||||
<!--EndSKU-->
|
<!--EndSKU-->
|
||||||
<!--EndCSP-->
|
<!--EndCSP-->
|
||||||
|
|
||||||
|
<!--StartCSP-->
|
||||||
|
[Firewall CSP](firewall-csp.md)
|
||||||
|
|
||||||
|
<!--StartSKU-->
|
||||||
|
<table>
|
||||||
|
<tr>
|
||||||
|
<th>Home</th>
|
||||||
|
<th>Pro</th>
|
||||||
|
<th>Business</th>
|
||||||
|
<th>Enterprise</th>
|
||||||
|
<th>Education</th>
|
||||||
|
<th>Mobile</th>
|
||||||
|
<th>Mobile Enterprise</th>
|
||||||
|
</tr>
|
||||||
|
<tr>
|
||||||
|
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||||
|
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||||
|
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||||
|
</tr>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
<!--EndSKU-->
|
||||||
|
<!--EndCSP-->
|
||||||
|
|
||||||
<!--StartCSP-->
|
<!--StartCSP-->
|
||||||
[HealthAttestation CSP](healthattestation-csp.md)
|
[HealthAttestation CSP](healthattestation-csp.md)
|
||||||
|
|
||||||
|
@ -217,6 +217,11 @@ The following diagram shows the Firewall configuration service provider in tree
|
|||||||
If not specified - a new rule is disabled by default.</p>
|
If not specified - a new rule is disabled by default.</p>
|
||||||
<p style="margin-left: 20px">Boolean value. Supported operations are Add, Get, Replace, and Delete.</p>
|
<p style="margin-left: 20px">Boolean value. Supported operations are Add, Get, Replace, and Delete.</p>
|
||||||
|
|
||||||
|
<a href="" id="profiles"></a>**FirewallRules_FirewallRuleName_/Profiles**
|
||||||
|
<p style="margin-left: 20px">Specifies the profiles to which the rule belongs: Domain, Private, Public. . See FW_PROFILE_TYPE for the bitmasks that are used to identify profile types.</p>
|
||||||
|
|
||||||
|
<p style="margin-left: 20px">Value type is integer. Supported operations are Add, Get, Replace, and Delete.</p>
|
||||||
|
|
||||||
<a href="" id="action"></a>**FirewallRules/_FirewallRuleName_/Action**
|
<a href="" id="action"></a>**FirewallRules/_FirewallRuleName_/Action**
|
||||||
<p style="margin-left: 20px">Specifies the action for the rule.</p>
|
<p style="margin-left: 20px">Specifies the action for the rule.</p>
|
||||||
<p style="margin-left: 20px">Supported operation is Get.</p>
|
<p style="margin-left: 20px">Supported operation is Get.</p>
|
||||||
@ -229,14 +234,43 @@ If not specified - a new rule is disabled by default.</p>
|
|||||||
</ul>
|
</ul>
|
||||||
<p style="margin-left: 20px">Value type is integer. Supported operations are Add, Get, Replace, and Delete.</p>
|
<p style="margin-left: 20px">Value type is integer. Supported operations are Add, Get, Replace, and Delete.</p>
|
||||||
|
|
||||||
|
<a href="" id="direction"></a>**FirewallRules/_FirewallRuleName_/Direction**
|
||||||
|
<p style="margin-left: 20px">Comma separated list. The rule is enabled based on the traffic direction as following. Supported values:</p>
|
||||||
|
<ul>
|
||||||
|
<li>IN - the rule applies to inbound traffic.</li>
|
||||||
|
<li>OUT - the rule applies to outbound traffic.</li>
|
||||||
|
<li>If not specified, the default is IN.</li>
|
||||||
|
</ul>
|
||||||
|
<p style="margin-left: 20px">Value type is string. Supported operations are Add, Get, Replace, and Delete.</p>
|
||||||
|
|
||||||
|
<a href="" id="interfacetypes"></a>**FirewallRules/FirewallRuleName/InterfaceTypes**
|
||||||
|
<p style="margin-left: 20px">Comma separated list of interface types. Valid values:</p>
|
||||||
|
<ul>
|
||||||
|
<li>RemoteAccess</li>
|
||||||
|
<li>Wireless</li>
|
||||||
|
<li>MobileBroadband</li>
|
||||||
|
<li>All</li>
|
||||||
|
</ul>
|
||||||
|
<p style="margin-left: 20px">Value type is string. Supported operations are Add, Get, Replace, and Delete.</p>
|
||||||
|
|
||||||
<a href="" id="icmptypesandcodes"></a>**FirewallRules/_FirewallRuleName_/IcmpTypesAndCodes**
|
<a href="" id="icmptypesandcodes"></a>**FirewallRules/_FirewallRuleName_/IcmpTypesAndCodes**
|
||||||
<p style="margin-left: 20px">List of ICMP types and codes separated by semicolon. "\*" indicates all ICMP types and codes.<</p>
|
<p style="margin-left: 20px">List of ICMP types and codes separated by semicolon. "\*" indicates all ICMP types and codes.<</p>
|
||||||
<p style="margin-left: 20px">Value type is string. Supported operations are Add, Get, Replace, and Delete.</p>
|
<p style="margin-left: 20px">Value type is string. Supported operations are Add, Get, Replace, and Delete.</p>
|
||||||
|
|
||||||
|
<a href="" id="edgetraversal"></a>**FirewallRules/_FirewallRuleName_/EdgeTraversal**
|
||||||
|
<p style="margin-left: 20px">Indicates whether edge traversal is enabled or disabled for this rule.</p>
|
||||||
|
<p style="margin-left: 20px">The EdgeTraversal setting indicates that specific inbound traffic is allowed to tunnel through NATs and other edge devices using the Teredo tunneling technology. In order for this setting to work correctly, the application or service with the inbound firewall rule needs to support IPv6. The primary application of this setting allows listeners on the host to be globally addressable through a Teredo IPv6 address.</p>
|
||||||
|
<p style="margin-left: 20px">New rules have the EdgeTraversal property disabled by default.</p>
|
||||||
|
<p style="margin-left: 20px">Boolean value. Supported operations are Add, Get, Replace, and Delete.</p>
|
||||||
|
|
||||||
<a href="" id="localuserauthorizedlist"></a>**FirewallRules/_FirewallRuleName_/LocalUserAuthorizedList**
|
<a href="" id="localuserauthorizedlist"></a>**FirewallRules/_FirewallRuleName_/LocalUserAuthorizedList**
|
||||||
<p style="margin-left: 20px">Specifies the list of authorized local users for the app container. This is a string in Security Descriptor Definition Language (SDDL) format.</p>
|
<p style="margin-left: 20px">Specifies the list of authorized local users for the app container. This is a string in Security Descriptor Definition Language (SDDL) format.</p>
|
||||||
<p style="margin-left: 20px">Value type is string. Supported operations are Add, Get, Replace, and Delete.</p>
|
<p style="margin-left: 20px">Value type is string. Supported operations are Add, Get, Replace, and Delete.</p>
|
||||||
|
|
||||||
|
<a href="" id="status"></a>**FirewallRules/_FirewallRuleName_/Status**
|
||||||
|
<p style="margin-left: 20px">Provides information about the specific verrsion of the rule in deployment for monitoring purposes.</p>
|
||||||
|
<p style="margin-left: 20px">Value type is string. Supported operation is Get.</p>
|
||||||
|
|
||||||
<a href="" id="friendlyname"></a>**FirewallRules/_FirewallRuleName_/FriendlyName**
|
<a href="" id="friendlyname"></a>**FirewallRules/_FirewallRuleName_/FriendlyName**
|
||||||
<p style="margin-left: 20px">Specifies the friendly name of the rule. The string must not contain the "|" character.</p>
|
<p style="margin-left: 20px">Specifies the friendly name of the rule. The string must not contain the "|" character.</p>
|
||||||
<p style="margin-left: 20px">Value type is string. Supported operations are Add, Get, Replace, and Delete.</p>
|
<p style="margin-left: 20px">Value type is string. Supported operations are Add, Get, Replace, and Delete.</p>
|
||||||
|
1815
windows/client-management/mdm/firewall-ddf-file.md
Normal file
Before Width: | Height: | Size: 90 KiB After Width: | Height: | Size: 95 KiB |
@ -850,6 +850,10 @@ For details about Microsoft mobile device management protocols for Windows 10 s
|
|||||||
<td style="vertical-align:top"><p>Added a section describing SyncML examples of various ADMX elements.</p>
|
<td style="vertical-align:top"><p>Added a section describing SyncML examples of various ADMX elements.</p>
|
||||||
</td></tr>
|
</td></tr>
|
||||||
<tr class="odd">
|
<tr class="odd">
|
||||||
|
<td style="vertical-align:top">[Win32 and Desktop Bridge app policy configuration](win32-and-centennial-app-policy-configuration.md)</td>
|
||||||
|
<td style="vertical-align:top">New topic.</td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
<td style="vertical-align:top">[Deploy and configure App-V apps using MDM](appv-deploy-and-config.md)</td>
|
<td style="vertical-align:top">[Deploy and configure App-V apps using MDM](appv-deploy-and-config.md)</td>
|
||||||
<td style="vertical-align:top"><p>Added a new topic describing how to deploy and configure App-V apps using MDM.</p>
|
<td style="vertical-align:top"><p>Added a new topic describing how to deploy and configure App-V apps using MDM.</p>
|
||||||
</td></tr>
|
</td></tr>
|
||||||
@ -1158,6 +1162,38 @@ The DM agent for [push-button reset](https://msdn.microsoft.com/windows/hardware
|
|||||||
|
|
||||||
## Change history in MDM documentation
|
## Change history in MDM documentation
|
||||||
|
|
||||||
|
### June 2017
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="25%" />
|
||||||
|
<col width="75%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead>
|
||||||
|
<tr class="header">
|
||||||
|
<th>New or updated topic</th>
|
||||||
|
<th>Description</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<tr class="odd">
|
||||||
|
<td style="vertical-align:top">[Win32 and Desktop Bridge app policy configuration](win32-and-centennial-app-policy-configuration.md)</td>
|
||||||
|
<td style="vertical-align:top">Added a list of registry locations that ingested policies are allowed to write to.</td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td style="vertical-align:top">[Firewall CSP](firewall-csp.md)</td>
|
||||||
|
<td style="vertical-align:top">Added the following nodes:
|
||||||
|
<ul>
|
||||||
|
<li>Profiles</li>
|
||||||
|
<li>Direction</li>
|
||||||
|
<li>InterfaceTypes</li>
|
||||||
|
<li>EdgeTraversal</li>
|
||||||
|
<li>Status</li>
|
||||||
|
</ul>
|
||||||
|
Also Added [Firewall DDF file](firewall-ddf-file.md).</td></tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
### May 2017
|
### May 2017
|
||||||
|
|
||||||
<table>
|
<table>
|
||||||
|
@ -201,9 +201,9 @@ This cloud service encrypts a recovery secret, which is stored locally on the cl
|
|||||||
<a href="" id="biometrics-facialfeaturesuseenhancedantispoofing--only-for---device-vendor-msft-"></a>**Biometrics/FacialFeaturesUseEnhancedAntiSpoofing** (only for ./Device/Vendor/MSFT)
|
<a href="" id="biometrics-facialfeaturesuseenhancedantispoofing--only-for---device-vendor-msft-"></a>**Biometrics/FacialFeaturesUseEnhancedAntiSpoofing** (only for ./Device/Vendor/MSFT)
|
||||||
<p style="margin-left: 20px">Boolean value used to enable or disable enhanced anti-spoofing for facial feature recognition on Windows Hello face authentication. This node was added in Windows 10, version 1511.
|
<p style="margin-left: 20px">Boolean value used to enable or disable enhanced anti-spoofing for facial feature recognition on Windows Hello face authentication. This node was added in Windows 10, version 1511.
|
||||||
|
|
||||||
<p style="margin-left: 20px">Default value is false. If you set this policy to true or don't configure this setting, Windows requires all users on managed devices to use enhanced anti-spoofing for Windows Hello face authentication. Windows Hello face authentication is disabled on devices that do not support enhanced anti-spoofing.
|
<p style="margin-left: 20px">Default value is false. If you set this policy to false or don't configure this setting, Windows doesn't require enhanced anti-spoofing for Windows Hello face authentication.
|
||||||
|
|
||||||
<p style="margin-left: 20px">If you set this policy to false, Windows doesn't require enhanced anti-spoofing for Windows Hello face authentication.
|
<p style="margin-left: 20px">If you set this policy to true, Windows requires all users on managed devices to use enhanced anti-spoofing for Windows Hello face authentication. Windows Hello face authentication is disabled on devices that do not support enhanced anti-spoofing.
|
||||||
|
|
||||||
<p style="margin-left: 20px">Note that enhanced anti-spoofing for Windows Hello face authentication is not required on unmanaged devices.
|
<p style="margin-left: 20px">Note that enhanced anti-spoofing for Windows Hello face authentication is not required on unmanaged devices.
|
||||||
|
|
||||||
|
@ -240,17 +240,13 @@ This section describes sample SyncML for the various ADMX elements like Text, Mu
|
|||||||
|
|
||||||
### <a href="" id="how-a-group-policy-policy-category-path-and-name-are-mapped-to-a-mdm-area-and-policy-name"></a>How a Group Policy policy category path and name are mapped to a MDM area and policy name
|
### <a href="" id="how-a-group-policy-policy-category-path-and-name-are-mapped-to-a-mdm-area-and-policy-name"></a>How a Group Policy policy category path and name are mapped to a MDM area and policy name
|
||||||
|
|
||||||
Below is the internal OS mapping of a Group Policy to a MDM area and name. This is part of a set of Windows manifests (extension **wm.xml**) that when compiled parses out the associated ADMX file, finds the specified Group Policy policy and stores that definition (metadata) in the MDM Policy CSP client store. ADMX backed policies are organized hierarchically. Their scope can be **machine**, **user**, or have a scope of **both**. When the MDM policy is referred to through a SyncML command and the Policy CSP URI, as shown below, this metadata is referenced and determines what registry keys are set or removed. Machine-scope policies are referenced via .\Device and the user scope policies via .\User.
|
Below is the internal OS mapping of a Group Policy to a MDM area and name. This is part of a set of Windows manifest that when compiled parses out the associated ADMX file, finds the specified Group Policy policy and stores that definition (metadata) in the MDM Policy CSP client store. ADMX backed policies are organized hierarchically. Their scope can be **machine**, **user**, or have a scope of **both**. When the MDM policy is referred to through a SyncML command and the Policy CSP URI, as shown below, this metadata is referenced and determines what registry keys are set or removed. Machine-scope policies are referenced via .\Device and the user scope policies via .\User.
|
||||||
|
|
||||||
`./[Device|User]/Vendor/MSFT/Policy/Config/[config|result]/<area>/<policy>`
|
`./[Device|User]/Vendor/MSFT/Policy/Config/[config|result]/<area>/<policy>`
|
||||||
|
|
||||||
The **wm.xml** for each mapped area can be found in its own directory under:
|
|
||||||
|
|
||||||
`\\SDXROOT\onecoreuap\admin\enterprisemgmt\policymanager\policydefinition\`
|
|
||||||
|
|
||||||
Note that the data payload of the SyncML needs to be encoded so that it does not conflict with the boilerplate SyncML XML tags. Use this online tool for encoding and encoding the policy data [Coder's Toolbox](http://coderstoolbox.net/string/#!encoding=xml&action=encode&charset=us_ascii)
|
Note that the data payload of the SyncML needs to be encoded so that it does not conflict with the boilerplate SyncML XML tags. Use this online tool for encoding and encoding the policy data [Coder's Toolbox](http://coderstoolbox.net/string/#!encoding=xml&action=encode&charset=us_ascii)
|
||||||
|
|
||||||
**Snippet of wm.xml for AppVirtualization area:**
|
**Snippet of manifest for AppVirtualization area:**
|
||||||
|
|
||||||
```XML
|
```XML
|
||||||
<identity xmlns="urn:Microsoft.CompPlat/ManifestSchema.v1.00" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" owner="Microsoft" namespace="Windows-DeviceManagement-PolicyDefinition" name="AppVirtualization">
|
<identity xmlns="urn:Microsoft.CompPlat/ManifestSchema.v1.00" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" owner="Microsoft" namespace="Windows-DeviceManagement-PolicyDefinition" name="AppVirtualization">
|
||||||
|
@ -24,8 +24,27 @@ author: nickbrower
|
|||||||
|
|
||||||
Starting in Windows 10, version 1703, you can import ADMX files (also called ADMX ingestion) and set those ADMX-backed policies for Win32 and Desktop Bridge apps by using Windows 10 Mobile Device Management (MDM) on desktop SKUs. The ADMX files that define policy information can be ingested to your device by using the Policy CSP URI, `./Device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall`. The ingested ADMX file is then processed into MDM policies.
|
Starting in Windows 10, version 1703, you can import ADMX files (also called ADMX ingestion) and set those ADMX-backed policies for Win32 and Desktop Bridge apps by using Windows 10 Mobile Device Management (MDM) on desktop SKUs. The ADMX files that define policy information can be ingested to your device by using the Policy CSP URI, `./Device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall`. The ingested ADMX file is then processed into MDM policies.
|
||||||
|
|
||||||
When the ADMX policies are imported, the registry keys to which each policy is written are checked so that known system registry keys, or registry keys that are used by existing inbox policies or system components, are not overwritten. This precaution helps to avoid security concerns over opening the entire registry. Currently, the ingested policies are not allowed to write to locations within the **System**, **Software\Microsoft**, and **Software\Policies\Microsoft** keys.
|
When the ADMX policies are imported, the registry keys to which each policy is written are checked so that known system registry keys, or registry keys that are used by existing inbox policies or system components, are not overwritten. This precaution helps to avoid security concerns over opening the entire registry. Currently, the ingested policies are not allowed to write to locations within the **System**, **Software\Microsoft**, and **Software\Policies\Microsoft** keys, except for the following locations:
|
||||||
|
|
||||||
|
- Software\Policies\Microsoft\Office\
|
||||||
|
- Software\Microsoft\Office\
|
||||||
|
- Software\Microsoft\Windows\CurrentVersion\Explorer\
|
||||||
|
- Software\Microsoft\Internet Explorer\
|
||||||
|
- software\policies\microsoft\shared tools\proofing tools\
|
||||||
|
- software\policies\microsoft\imejp\
|
||||||
|
- software\policies\microsoft\ime\shared\
|
||||||
|
- software\policies\microsoft\shared tools\graphics filters\
|
||||||
|
- software\policies\microsoft\windows\currentversion\explorer\
|
||||||
|
- software\policies\microsoft\softwareprotectionplatform\
|
||||||
|
- software\policies\microsoft\officesoftwareprotectionplatform\
|
||||||
|
- software\policies\microsoft\windows\windows search\preferences\
|
||||||
|
- software\policies\microsoft\exchange\
|
||||||
|
- software\microsoft\shared tools\proofing tools\
|
||||||
|
- software\microsoft\shared tools\graphics filters\
|
||||||
|
- software\microsoft\windows\windows search\preferences\
|
||||||
|
- software\microsoft\exchange\
|
||||||
|
- software\policies\microsoft\vba\security\
|
||||||
|
- software\microsoft\onedrive
|
||||||
|
|
||||||
## <a href="" id="ingesting-an-app-admx-file"></a>Ingesting an app ADMX file
|
## <a href="" id="ingesting-an-app-admx-file"></a>Ingesting an app ADMX file
|
||||||
|
|
||||||
|
@ -122,6 +122,9 @@ When you have the Start layout that you want your users to see, use the [Export-
|
|||||||
</tbody>
|
</tbody>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
|
>[!IMPORTANT]
|
||||||
|
>If the Start layout that you export contains tiles for desktop (Win32) apps or .url links, **Export-StartLayout** will use **DesktopApplicationLinkPath** in the resulting file. Use a text or XML editor to change **DesktopApplicationLinkPath** to **DesktopApplicationID**. See [Specify Start tiles](start-layout-xml-desktop.md#specify-start-tiles) for details on using the app ID in place of the link path.
|
||||||
|
|
||||||
## Configure a partial Start layout
|
## Configure a partial Start layout
|
||||||
|
|
||||||
|
|
||||||
|
@ -160,6 +160,9 @@ You can use the **start:DesktopApplicationTile** tag to pin a Windows desktop ap
|
|||||||
|
|
||||||
- By using a path to a shortcut link (.lnk file) to a Windows desktop application.
|
- By using a path to a shortcut link (.lnk file) to a Windows desktop application.
|
||||||
|
|
||||||
|
>[!NOTE]
|
||||||
|
>In Start layouts for Windows 10, version 1703, you should use **DesktopApplicationID** rather than **DesktopApplicationLinkPath** if you are using Group Policy or MDM to apply the start layout and the application was installed after the user's first sign-in.
|
||||||
|
|
||||||
To pin a Windows desktop application through this method, you must first add the .lnk file in the specified location when the device first boots.
|
To pin a Windows desktop application through this method, you must first add the .lnk file in the specified location when the device first boots.
|
||||||
|
|
||||||
The following example shows how to pin the Command Prompt:
|
The following example shows how to pin the Command Prompt:
|
||||||
@ -174,10 +177,12 @@ You can use the **start:DesktopApplicationTile** tag to pin a Windows desktop ap
|
|||||||
|
|
||||||
You must set the **DesktopApplicationLinkPath** attribute to the .lnk file that points to the Windows desktop application. The path also supports environment variables.
|
You must set the **DesktopApplicationLinkPath** attribute to the .lnk file that points to the Windows desktop application. The path also supports environment variables.
|
||||||
|
|
||||||
If you are pointing to a third-party Windows desktop application, you must put the .lnk file in a legacy Start Menu directory before first boot; for example, "%APPDATA%\Microsoft\Windows\Start Menu\Programs\" or the all users profile "%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\".
|
If you are pointing to a third-party Windows desktop application and the layout is being applied before the first boot, you must put the .lnk file in a legacy Start Menu directory before first boot; for example, "%APPDATA%\Microsoft\Windows\Start Menu\Programs\" or the all users profile "%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\".
|
||||||
|
|
||||||
- By using the application's application user model ID, if this is known. If the Windows desktop application doesn't have one, use the shortcut link option.
|
- By using the application's application user model ID, if this is known. If the Windows desktop application doesn't have one, use the shortcut link option.
|
||||||
|
|
||||||
|
You can use the [Get-StartApps cmdlet](https://technet.microsoft.com/library/dn283402.aspx) on a PC that has the application pinned to Start to obtain the app ID.
|
||||||
|
|
||||||
To pin a Windows desktop application through this method, you must set the **DesktopApplicationID** attribute to the application user model ID that's associated with the corresponding app.
|
To pin a Windows desktop application through this method, you must set the **DesktopApplicationID** attribute to the application user model ID that's associated with the corresponding app.
|
||||||
|
|
||||||
The following example shows how to pin the Internet Explorer Windows desktop application:
|
The following example shows how to pin the Internet Explorer Windows desktop application:
|
||||||
@ -205,6 +210,9 @@ The following example shows how to create a tile of the Web site's URL, which yo
|
|||||||
Column="2"/>
|
Column="2"/>
|
||||||
```
|
```
|
||||||
|
|
||||||
|
>[!NOTE]
|
||||||
|
>In Windows 10, version 1703, **Export-StartLayout** will use **DesktopApplicationLinkPath** for the .url shortcut. You must change **DesktopApplicationLinkPath** to **DesktopApplicationID** and provide the URL.
|
||||||
|
|
||||||
#### start:SecondaryTile
|
#### start:SecondaryTile
|
||||||
|
|
||||||
You can use the **start:SecondaryTile** tag to pin a Web link through a Microsoft Edge secondary tile. This method doesn't require any additional action compared to the method of using legacy .url shortcuts (through the start:DesktopApplicationTile tag).
|
You can use the **start:SecondaryTile** tag to pin a Web link through a Microsoft Edge secondary tile. This method doesn't require any additional action compared to the method of using legacy .url shortcuts (through the start:DesktopApplicationTile tag).
|
||||||
@ -273,6 +281,9 @@ The following example shows how to modify your LayoutModification.xml file to ad
|
|||||||
|
|
||||||
You can use the **AppendOfficeSuite** tag to add the in-box installed Office suite of apps to Start.
|
You can use the **AppendOfficeSuite** tag to add the in-box installed Office suite of apps to Start.
|
||||||
|
|
||||||
|
>[!NOTE]
|
||||||
|
>The OEM must have installed Office for this tag to work.
|
||||||
|
|
||||||
The following example shows how to add the **AppendOfficeSuite** tag to your LayoutModification.xml file to append the full Universal Office suite to Start:
|
The following example shows how to add the **AppendOfficeSuite** tag to your LayoutModification.xml file to append the full Universal Office suite to Start:
|
||||||
|
|
||||||
```XML
|
```XML
|
||||||
@ -289,6 +300,9 @@ The following example shows how to add the **AppendOfficeSuite** tag to your Lay
|
|||||||
|
|
||||||
You can use the **AppendDownloadOfficeTile** tag to append the Office trial installer to Start. This tag adds the Download Office tile to Start and the download tile will appear at the bottom right-hand side of the second group.
|
You can use the **AppendDownloadOfficeTile** tag to append the Office trial installer to Start. This tag adds the Download Office tile to Start and the download tile will appear at the bottom right-hand side of the second group.
|
||||||
|
|
||||||
|
>[!NOTE]
|
||||||
|
>The OEM must have installed the Office trial installer for this tag to work.
|
||||||
|
|
||||||
The following example shows how to add the **AppendDownloadOfficeTile** tag to your LayoutModification.xml file:
|
The following example shows how to add the **AppendDownloadOfficeTile** tag to your LayoutModification.xml file:
|
||||||
|
|
||||||
```XML
|
```XML
|
||||||
|
BIN
windows/deployment/update/images/uc-01-wdav.png
Normal file
After Width: | Height: | Size: 56 KiB |
@ -1,6 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Get started with Update Compliance (Windows 10)
|
title: Get started with Update Compliance (Windows 10)
|
||||||
description: Explains how to configure Update Compliance.
|
description: Configure Update Compliance in OMS to see the status of updates and antimalware protection on devices in your network.
|
||||||
|
keywords: update compliance, oms, operations management suite, prerequisites, requirements, updates, upgrades, antivirus, antimalware, signature, log analytics, wdav
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
@ -14,91 +15,90 @@ This topic explains the steps necessary to configure your environment for Window
|
|||||||
|
|
||||||
Steps are provided in sections that follow the recommended setup process:
|
Steps are provided in sections that follow the recommended setup process:
|
||||||
1. Ensure that [prerequisites](#update-compliance-prerequisites) are met.
|
1. Ensure that [prerequisites](#update-compliance-prerequisites) are met.
|
||||||
2. [Add Update Compliance](#add-update-compliance-to-microsoft-operations-management-suite) to Microsoft Operations Management Suite
|
2. [Add Update Compliance](#add-update-compliance-to-microsoft-operations-management-suite) to Microsoft Operations Management Suite.
|
||||||
3. [Deploy your Commercial ID](#deploy-your-commercial-id-to-your-windows-10-devices) to your organization’s devices
|
3. [Deploy your Commercial ID](#deploy-your-commercial-id-to-your-windows-10-devices) to your organization’s devices.
|
||||||
|
|
||||||
## Update Compliance Prerequisites
|
## Update Compliance prerequisites
|
||||||
|
|
||||||
Update Compliance has the following requirements:
|
Update Compliance has the following requirements:
|
||||||
1. Update Compliance is currently only compatible with Windows 10 devices. The solution is intended to be used with desktop devices (Windows 10 workstations and laptops).
|
1. Update Compliance is currently only compatible with Windows 10 devices. The solution is intended to be used with desktop devices (Windows 10 workstations and laptops).
|
||||||
2. The solution requires that Windows 10 telemetry is enabled on all devices that are intended to be displayed in the solution. These devices must have at least the [basic level of telemetry](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization#basic-level) enabled. To learn more about Windows telemetry, see [Configure Windows telemetry in your organization](/windows/configuration/configure-windows-telemetry-in-your-organization).
|
2. The solution requires that Windows 10 telemetry is enabled on all devices that are intended to be displayed in the solution. These devices must have at least the [basic level of telemetry](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization#basic-level) enabled. To learn more about Windows telemetry, see [Configure Windows telemetry in your organization](/windows/configuration/configure-windows-telemetry-in-your-organization).
|
||||||
3. The telemetry of your organization’s Windows devices must be successfully transmitted to Microsoft. Microsoft has specified [endpoints for different aspects of telemetry](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization#endpoints), which must be whitelisted by your organization so the data can be transmitted. The following table is taken from the article on telemetry endpoints and summarizes the use of each endpoint:
|
3. The telemetry of your organization’s Windows devices must be successfully transmitted to Microsoft. Microsoft has specified [endpoints for each of the telemetry services](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization#endpoints), which must be whitelisted by your organization so the data can be transmitted. The following table is taken from the article on telemetry endpoints and summarizes the use of each endpoint:
|
||||||
|
|
||||||
<TABLE BORDER=1>
|
Service | Endpoint
|
||||||
<TR><TD BGCOLOR="#cceeff">Service<TD BGCOLOR="#cceeff">Endpoint
|
--- | ---
|
||||||
<TR><TD>Connected User Experience and Telemetry component<TD>v10.vortex-win.data.microsoft.com
|
Connected User Experience and Telemetry component | v10.vortex-win.data.microsoft.com<BR>settings-win.data.microsoft.com
|
||||||
<BR>settings-win.data.microsoft.com
|
Windows Error Reporting | watson.telemetry.microsoft.com
|
||||||
<TR><TD>Windows Error Reporting <TD>watson.telemetry.microsoft.com
|
Online Crash Analysis | oca.telemetry.microsoft.com
|
||||||
<TR><TD>Online Crash Analysis <TD>oca.telemetry.microsoft.com
|
|
||||||
</TABLE>
|
|
||||||
|
|
||||||
4. To use Windows Defender Antivirus Assessment, devices must be protected by Windows Defender AV (and not a 3rd party AV program), and must have enabled [cloud-delivered protection](/windows/threat-protection/windows-defender-antivirus/utilize-microsoft-cloud-protection-windows-defender-antivirus). See the [Windows Defender Antivirus in Windows 10](/windows/threat-protection/windows-defender-antivirus/windows-defender-antivirus-in-windows-10) content library for more information on enabling, configuring, and validating Windows Defender AV.
|
|
||||||
|
4. To use Windows Defender Antivirus Assessment, devices must be protected by Windows Defender AV (and not a 3rd party AV program), and must have enabled [cloud-delivered protection](/windows/threat-protection/windows-defender-antivirus/utilize-microsoft-cloud-protection-windows-defender-antivirus). See the [Windows Defender Antivirus in Windows 10](/windows/threat-protection/windows-defender-antivirus/windows-defender-antivirus-in-windows-10) content library for more information on enabling, configuring, and validating Windows Defender AV.
|
||||||
|
|
||||||
|
|
||||||
## Add Update Compliance to Microsoft Operations Management Suite
|
## Add Update Compliance to Microsoft Operations Management Suite
|
||||||
|
|
||||||
Update Compliance is offered as a solution in the Microsoft Operations Management Suite (OMS), a collection of cloud-based servicing for monitoring and automating your on-premises and cloud environments. For more information about OMS, see [Operations Management Suite overview](https://azure.microsoft.com/en-us/documentation/articles/operations-management-suite-overview/).
|
Update Compliance is offered as a solution in the Microsoft Operations Management Suite (OMS), a collection of cloud-based servicing for monitoring and automating your on-premise and cloud environments. For more information about OMS, see [Operations Management Suite overview](https://azure.microsoft.com/en-us/documentation/articles/operations-management-suite-overview/).
|
||||||
|
|
||||||
If you are already using OMS, you’ll find Update Compliance in the Solutions Gallery. Select the **Update Compliance** tile in the gallery and then click **Add** on the solution's details page. Update Compliance is now visible in your workspace.
|
If you are already using OMS, you’ll find Update Compliance in the Solutions Gallery. Select the **Update Compliance** tile in the gallery and then click **Add** on the solution's details page. Update Compliance is now visible in your workspace.
|
||||||
|
|
||||||
If you are not yet using OMS, use the following steps to subscribe to OMS Update Compliance:
|
If you are not yet using OMS, use the following steps to subscribe to OMS Update Compliance:
|
||||||
|
|
||||||
1. Go to [Operations Management Suite’s page](https://www.microsoft.com/en-us/cloud-platform/operations-management-suite) on Microsoft.com and click **Sign in**.
|
1. Go to [Operations Management Suite](https://www.microsoft.com/en-us/cloud-platform/operations-management-suite) on Microsoft.com and click **Sign in**.
|
||||||
|
|
||||||
|
|
||||||
|
[](images/uc-02.png)
|
||||||
|
|
||||||
<P><TABLE BORDER=1><TR><TD>
|
|
||||||
<A HREF="images/uc-02.png"><img src="images/uc-02a.png"></A>
|
|
||||||
<TABLE>
|
|
||||||
|
|
||||||
2. Sign in to Operations Management Suite (OMS). You can use either a Microsoft Account or a Work or School account to create a workspace. If your company is already using Azure Active Directory (Azure AD), use a Work or School account when you sign in to OMS. Using a Work or School account allows you to use identities from your Azure AD to manage permissions in OMS.
|
2. Sign in to Operations Management Suite (OMS). You can use either a Microsoft Account or a Work or School account to create a workspace. If your company is already using Azure Active Directory (Azure AD), use a Work or School account when you sign in to OMS. Using a Work or School account allows you to use identities from your Azure AD to manage permissions in OMS.
|
||||||
|
|
||||||
<P><TABLE BORDER=1><TR><TD>
|
|
||||||
<A HREF="images/uc-03.png"><img src="images/uc-03a.png"></A>
|
[](images/uc-03.png)
|
||||||
<TABLE>
|
|
||||||
|
|
||||||
3. Create a new OMS workspace.
|
3. Create a new OMS workspace.
|
||||||
|
|
||||||
<P><TABLE BORDER=1><TR><TD>
|
|
||||||
<A HREF="images/uc-04.png"><img src="images/uc-04a.png"></A>
|
[](images/uc-04.png)
|
||||||
<TABLE>
|
|
||||||
|
|
||||||
4. Enter a name for the workspace, select the workspace region, and provide the email address that you want associated with this workspace. Click **Create**.
|
4. Enter a name for the workspace, select the workspace region, and provide the email address that you want associated with this workspace. Click **Create**.
|
||||||
|
|
||||||
<P><TABLE BORDER=1><TR><TD>
|
|
||||||
<A HREF="images/uc-05.png"><img src="images/uc-05a.png"></A>
|
[](images/uc-05.png)
|
||||||
<TABLE>
|
|
||||||
|
|
||||||
5. If your organization already has an Azure subscription, you can link it to your workspace. Note that you may need to request access from your organization’s Azure administrator. If your organization does not have an Azure subscription, create a new one or select the default OMS Azure subscription from the list. If you do not yet have an Azure subscription, follow [this guide](https://blogs.technet.microsoft.com/upgradeanalytics/2016/11/08/linking-operations-management-suite-workspaces-to-microsoft-azure/) to create and link an Azure subscription to an OMS workspace.
|
5. If your organization already has an Azure subscription, you can link it to your workspace. Note that you may need to request access from your organization’s Azure administrator. If your organization does not have an Azure subscription, create a new one or select the default OMS Azure subscription from the list. If you do not yet have an Azure subscription, follow [this guide](https://blogs.technet.microsoft.com/upgradeanalytics/2016/11/08/linking-operations-management-suite-workspaces-to-microsoft-azure/) to create and link an Azure subscription to an OMS workspace.
|
||||||
|
|
||||||
<P><TABLE BORDER=1><TR><TD>
|
|
||||||
<A HREF="images/uc-06.png"><img src="images/uc-06a.png"></A>
|
[](images/uc-06.png)
|
||||||
<TABLE>
|
|
||||||
|
|
||||||
6. To add the Update Compliance solution to your workspace, go to the Solutions Gallery.
|
6. To add the Update Compliance solution to your workspace, go to the Solutions Gallery.
|
||||||
|
|
||||||
<P><TABLE BORDER=1><TR><TD>
|
|
||||||
<A HREF="images/uc-07.png"><img src="images/uc-07a.png"></A>
|
|
||||||
<TABLE>
|
|
||||||
|
|
||||||
7. Select the **Update Compliance** tile in the gallery and then select **Add** on the solution’s details page. You might need to scroll to find **Update Compliance**. The solution is now visible on your workspace.
|
[](images/uc-07.png)
|
||||||
|
|
||||||
|
|
||||||
|
7. Select the **Update Compliance** tile in the gallery and then select **Add** on the solution’s details page. You might need to scroll to find **Update Compliance**. The solution is now visible in your workspace.
|
||||||
|
|
||||||
|
|
||||||
|
[](images/uc-08.png)
|
||||||
|
|
||||||
<P><TABLE BORDER=1><TR><TD>
|
|
||||||
<A HREF="images/uc-08.png"><img src="images/uc-08a.png"></A>
|
|
||||||
<TABLE>
|
|
||||||
|
|
||||||
8. Click the **Update Compliance** tile to configure the solution. The **Settings Dashboard** opens.
|
8. Click the **Update Compliance** tile to configure the solution. The **Settings Dashboard** opens.
|
||||||
|
|
||||||
<P><TABLE BORDER=1><TR><TD>
|
|
||||||
<A HREF="images/uc-09.png"><img src="images/uc-09a.png"></A>
|
[](images/uc-09.png)
|
||||||
<TABLE>
|
|
||||||
|
|
||||||
9. Click **Subscribe** to subscribe to OMS Update Compliance. You will then need to distribute your Commercial ID across all your organization’s devices. More information on the Commercial ID is provided below.
|
9. Click **Subscribe** to subscribe to OMS Update Compliance. You will then need to distribute your Commercial ID across all your organization’s devices. More information on the Commercial ID is provided below.
|
||||||
|
|
||||||
<P><TABLE BORDER=1><TR><TD>
|
|
||||||
<A HREF="images/uc-10.png"><img src="images/uc-10a.png"></A>
|
[](images/uc-10.png)
|
||||||
<TABLE>
|
|
||||||
|
|
||||||
After you are subscribed to OMS Update Compliance and your devices have a Commercial ID, you will begin receiving data. It will typically take 24 hours for the first data to begin appearing. The following section explains how to deploy your Commercial ID to your Windows 10 devices.
|
After you are subscribed to OMS Update Compliance and your devices have a Commercial ID, you will begin receiving data. It will typically take 24 hours for the first data to begin appearing. The following section explains how to deploy your Commercial ID to your Windows 10 devices.
|
||||||
|
|
||||||
|
>[!NOTE]
|
||||||
>You can unsubscribe from the Update Compliance solution if you no longer want to monitor your organization’s devices. User device data will continue to be shared with Microsoft while the opt-in keys are set on user devices and the proxy allows traffic.
|
>You can unsubscribe from the Update Compliance solution if you no longer want to monitor your organization’s devices. User device data will continue to be shared with Microsoft while the opt-in keys are set on user devices and the proxy allows traffic.
|
||||||
|
|
||||||
## Deploy your Commercial ID to your Windows 10 devices
|
## Deploy your Commercial ID to your Windows 10 devices
|
||||||
|
@ -1,6 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Monitor Windows Updates with Update Compliance (Windows 10)
|
title: Monitor Windows Updates and Windows Defender AV with Update Compliance (Windows 10)
|
||||||
description: Introduction to Update Compliance.
|
description: You can use Update Compliance in OMS to monitor the progress of updates and key antimalware protection features on devices in your network.
|
||||||
|
keywords: oms, operations management suite, wdav, updates, upgrades, antivirus, antimalware, signature, log analytics
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
@ -8,26 +9,26 @@ ms.pagetype: deploy
|
|||||||
author: greg-lindsay
|
author: greg-lindsay
|
||||||
---
|
---
|
||||||
|
|
||||||
# Monitor Windows Updates with Update Compliance
|
# Monitor Windows Updates and Windows Defender Antivirus with Update Compliance
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
With Windows 10, organizations need to change the way they approach monitoring and deploying updates. Update Compliance is a powerful set of tools that enable organizations to monitor and track all important aspects of Microsoft’s new servicing strategy: [Windows as a Service](waas-overview.md).
|
With Windows 10, organizations need to change the way they approach monitoring and deploying updates. Update Compliance is a powerful set of tools that enable organizations to monitor and track all important aspects of the new servicing strategy from Microsoft: [Windows as a Service](waas-overview.md).
|
||||||
|
|
||||||
Update Compliance is a solution built within Operations Management Suite (OMS), a cloud-based monitoring and automation service which has a flexible servicing subscription based off data usage/retention. For more information about OMS, see [Operations Management Suite overview](http://azure.microsoft.com/en-us/documentation/articles/operations-management-suite-overview/).
|
Update Compliance is a solution built within Operations Management Suite (OMS), a cloud-based monitoring and automation service which has a flexible servicing subscription based off data usage/retention. For more information about OMS, see [Operations Management Suite overview](http://azure.microsoft.com/en-us/documentation/articles/operations-management-suite-overview/).
|
||||||
|
|
||||||
Update Compliance uses the Windows telemetry that is part of all Windows 10 devices. It collects system data including update installation progress, Windows Update for Business (WUfB) configuration data, and other update-specific information, and then sends this data privately to a secure cloud to be stored for analysis and usage within the solution.
|
Update Compliance uses the Windows telemetry that is part of all Windows 10 devices. It collects system data including update installation progress, Windows Update for Business (WUfB) configuration data, Windows Defender Antivirus data, and other update-specific information, and then sends this data privately to a secure cloud to be stored for analysis and usage within the solution.
|
||||||
|
|
||||||
Update Compliance provides the following:
|
Update Compliance provides the following:
|
||||||
|
|
||||||
- An overview of your organization’s devices that just works.
|
- Dedicated drill-downs for devices that might need attention
|
||||||
- Dedicated drill-downs for devices that might need attention.
|
- An inventory of devices, including the version of Windows they are running and their update status
|
||||||
- An inventory of devices, including the version of Windows they are running and their update status.
|
- The ability to track protection and threat status for Windows Defender Antivirus-enabled devices
|
||||||
- An overview of WUfB deferral configurations (Windows 10 Anniversary Update [1607] and later).
|
- An overview of WUfB deferral configurations (Windows 10 Anniversary Update [1607] and later)
|
||||||
- Powerful built-in [log analytics](https://www.microsoft.com/en-us/cloud-platform/insight-and-analytics?WT.srch=1&WT.mc_id=AID529558_SEM_%5B_uniqid%5D&utm_source=Bing&utm_medium=CPC&utm_term=log%20analytics&utm_campaign=Hybrid_Cloud_Management) to create useful custom queries.
|
- Powerful built-in [log analytics](https://www.microsoft.com/en-us/cloud-platform/insight-and-analytics?WT.srch=1&WT.mc_id=AID529558_SEM_%5B_uniqid%5D&utm_source=Bing&utm_medium=CPC&utm_term=log%20analytics&utm_campaign=Hybrid_Cloud_Management) to create useful custom queries
|
||||||
- Cloud-connected access utilizing Windows 10 telemetry means no need for new complex, customized infrastructure.
|
- Cloud-connected access utilizing Windows 10 telemetry means no need for new complex, customized infrastructure
|
||||||
|
|
||||||
See the following topics in this guide for detailed information about configuring and use the Update Compliance solution:
|
See the following topics in this guide for detailed information about configuring and using the Update Compliance solution:
|
||||||
|
|
||||||
- [Get started with Update Compliance](update-compliance-get-started.md): How to add Update Compliance to your environment.
|
- [Get started with Update Compliance](update-compliance-get-started.md): How to add Update Compliance to your environment.
|
||||||
- [Using Update Compliance](update-compliance-using.md): How to begin using Update Compliance.
|
- [Using Update Compliance](update-compliance-using.md): How to begin using Update Compliance.
|
||||||
@ -36,19 +37,20 @@ An overview of the processes used by the Update Compliance solution is provided
|
|||||||
|
|
||||||
## Update Compliance architecture
|
## Update Compliance architecture
|
||||||
|
|
||||||
The Update Compliance architecture and data flow is summarized by the following five step process:
|
The Update Compliance architecture and data flow is summarized by the following five-step process:
|
||||||
|
|
||||||
**(1)** User computers send telemetry data to a secure Microsoft data center using the Microsoft Data Management Service.<BR>
|
**(1)** User computers send telemetry data to a secure Microsoft data center using the Microsoft Data Management Service.<BR>
|
||||||
**(2)** Telemetry data is analyzed by the Update Compliance Data Service.<BR>
|
**(2)** Telemetry data is analyzed by the Update Compliance Data Service.<BR>
|
||||||
**(3)** Telemetry data is pushed from the Update Compliance Data Service to your OMS workspace.<BR>
|
**(3)** Telemetry data is pushed from the Update Compliance Data Service to your OMS workspace.<BR>
|
||||||
**(4)** Telemetry data is available in the Update Compliance solution.<BR>
|
**(4)** Telemetry data is available in the Update Compliance solution.<BR>
|
||||||
**(5)** You are able to monitor and troubleshoot Windows updates on your network.<BR>
|
**(5)** You are able to monitor and troubleshoot Windows updates and Windows Defender AV in your environment.<BR>
|
||||||
|
|
||||||
These steps are illustrated in following diagram:
|
These steps are illustrated in following diagram:
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
>This process assumes that Windows telemetry is enabled and devices are assigned your Commercial ID.
|
>[!NOTE]
|
||||||
|
>This process assumes that Windows telemetry is enabled and you [have assigned your Commercial ID to devices](update-compliance-get-started#deploy-your-commercial-id-to-your-windows-10-devices.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@ -19,6 +19,7 @@ Update Compliance:
|
|||||||
- Provides a workflow that can be used to quickly identify which devices require attention.
|
- Provides a workflow that can be used to quickly identify which devices require attention.
|
||||||
- Enables you to track deployment compliance targets for updates.
|
- Enables you to track deployment compliance targets for updates.
|
||||||
|
|
||||||
|
>[!NOTE]
|
||||||
>Information is refreshed daily so that update progress can be monitored. Changes will be displayed about 24 hours after their occurrence, so you always have a recent snapshot of your devices.
|
>Information is refreshed daily so that update progress can be monitored. Changes will be displayed about 24 hours after their occurrence, so you always have a recent snapshot of your devices.
|
||||||
|
|
||||||
In OMS, the aspects of a solution's dashboard are usually divided into <I>blades</I>. Blades are a slice of information, typically with a summarization tile and an enumeration of the items that makes up that data. All data is presented through <I>queries</I>. <I>Perspectives</I> are also possible, wherein a given query has a unique view designed to display custom data. The terminology of blades, tiles, and perspectives will be used in the sections that follow.
|
In OMS, the aspects of a solution's dashboard are usually divided into <I>blades</I>. Blades are a slice of information, typically with a summarization tile and an enumeration of the items that makes up that data. All data is presented through <I>queries</I>. <I>Perspectives</I> are also possible, wherein a given query has a unique view designed to display custom data. The terminology of blades, tiles, and perspectives will be used in the sections that follow.
|
||||||
|
@ -1,5 +1,5 @@
|
|||||||
# [Threat protection](index.md)
|
# [Threat protection](index.md)
|
||||||
|
## [Windows Defender Security Center](windows-defender-security-center\windows-defender-security-center.md)
|
||||||
## [Windows Defender Advanced Threat Protection](windows-defender-atp\windows-defender-advanced-threat-protection.md)
|
## [Windows Defender Advanced Threat Protection](windows-defender-atp\windows-defender-advanced-threat-protection.md)
|
||||||
### [Minimum requirements](windows-defender-atp\minimum-requirements-windows-defender-advanced-threat-protection.md)
|
### [Minimum requirements](windows-defender-atp\minimum-requirements-windows-defender-advanced-threat-protection.md)
|
||||||
### [Preview features](windows-defender-atp\preview-windows-defender-advanced-threat-protection.md)
|
### [Preview features](windows-defender-atp\preview-windows-defender-advanced-threat-protection.md)
|
||||||
|
@ -33,7 +33,7 @@ You'll also see additional links for:
|
|||||||
- Reporting on Windows Defender Antivirus protection
|
- Reporting on Windows Defender Antivirus protection
|
||||||
|
|
||||||
> [!IMPORTANT]
|
> [!IMPORTANT]
|
||||||
> In most cases, Windows 10 will disable Windows Defender Antivirus if it finds another antivirus product running and up-to-date. You must disable or uninstall third-party antivirus products before Windows Defender Antivirus will be functioning. If you re-enable or install third-part antivirus products, then Windows 10 will automatically disable Windows Defender Antivirus.
|
> In most cases, Windows 10 will disable Windows Defender Antivirus if it finds another antivirus product running and up-to-date. You must disable or uninstall third-party antivirus products before Windows Defender Antivirus will be functioning. If you re-enable or install third-party antivirus products, then Windows 10 will automatically disable Windows Defender Antivirus.
|
||||||
|
|
||||||
|
|
||||||
Tool|Deployment options (<a href="#fn2" id="ref2">2</a>)|Management options (network-wide configuration and policy or baseline deployment) ([3](#fn3))|Reporting options
|
Tool|Deployment options (<a href="#fn2" id="ref2">2</a>)|Management options (network-wide configuration and policy or baseline deployment) ([3](#fn3))|Reporting options
|
||||||
|
@ -31,11 +31,11 @@ See the [Windows Defender Advanced Threat Protection](../windows-defender-atp/wi
|
|||||||
|
|
||||||
If you are enrolled in Windows Defender ATP, and you are not using Windows Defender AV as your real-time protection service on your endpoints, Windows Defender will automatically enter into a passive mode. On Windows Server 2016 SKUs, Windows Defender AV will not enter into the passive mode and will run alongside your other antivirus product.
|
If you are enrolled in Windows Defender ATP, and you are not using Windows Defender AV as your real-time protection service on your endpoints, Windows Defender will automatically enter into a passive mode. On Windows Server 2016 SKUs, Windows Defender AV will not enter into the passive mode and will run alongside your other antivirus product.
|
||||||
|
|
||||||
In passive mode, Windows Defender will continue to run (using the *msmpeng.exe* process), and will continue to be updated, however there will be no Windows Defender user interface, scheduled scans won't run, and Windows Defender will not provide real-time protection from malware.
|
In passive mode, Windows Defender AV will continue to run (using the *msmpeng.exe* process), and will continue to be updated, however there will be no Windows Defender user interface, scheduled scans won't run, and Windows Defender AV will not provide real-time protection from malware.
|
||||||
|
|
||||||
You can still [manage updates for Windows Defender](manage-updates-baselines-windows-defender-antivirus.md), however you can't move Windows Defender into the normal active mode if your endpoints have an up-to-date third-party product providing real-time protection from malware.
|
You can still [manage updates for Windows Defender](manage-updates-baselines-windows-defender-antivirus.md), however you can't move Windows Defender AV into the normal active mode if your endpoints have an up-to-date third-party product providing real-time protection from malware.
|
||||||
|
|
||||||
If you uninstall the other product, and choose to use Windows Defender to provide protection to your endpoints, Windows Defender will automatically return to its normal active mode.
|
If you uninstall the other product, and choose to use Windows Defender AV to provide protection to your endpoints, Windows Defender AV will automatically return to its normal active mode.
|
||||||
|
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
@ -36,12 +36,12 @@ author: iaanw
|
|||||||
|
|
||||||
Windows Defender Antivirus is available on Windows Server 2016. In some instances it is referred to as Endpoint Protection - however, the protection engine is the same.
|
Windows Defender Antivirus is available on Windows Server 2016. In some instances it is referred to as Endpoint Protection - however, the protection engine is the same.
|
||||||
|
|
||||||
See [Windows Defender Overview for Windows Server](https://technet.microsoft.com/windows-server-docs/security/windows-defender/windows-defender-overview-windows-server) for more information on enabling the client interface and configuring roles and specific server features.
|
See the [Windows Defender Overview for Windows Server](https://technet.microsoft.com/windows-server-docs/security/windows-defender/windows-defender-overview-windows-server) for more information on enabling the client interface and configuring roles and specific server features.
|
||||||
|
|
||||||
While the functionality, configuration, and management is largely the same for Windows Defender AV either on Windows 10 or Windows Server 2016, there are a few key differences:
|
While the functionality, configuration, and management is largely the same for Windows Defender AV either on Windows 10 or Windows Server 2016, there are a few key differences:
|
||||||
|
|
||||||
- In Windows Server 2016, [automatic exclusions](configure-server-exclusions-windows-defender-antivirus.md) are applied based on your defined Server Role.
|
- In Windows Server 2016, [automatic exclusions](configure-server-exclusions-windows-defender-antivirus.md) are applied based on your defined Server Role.
|
||||||
- In Windows Server 2016, [Windows Defender AV will not disable itself if you are running another antivirus product](windows-defender-antivirus-on-windows-server-2016.md).
|
- In Windows Server 2016, Windows Defender AV will not disable itself if you are running another antivirus product.
|
||||||
|
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
@ -35,12 +35,16 @@ In Windows 10, version 1703 (also known as the Creators Update), the Windows Def
|
|||||||
|
|
||||||
Settings that were previously part of the Windows Defender client and main Windows Settings have been combined and moved to the new app, which is installed by default as part of Windows 10, version 1703.
|
Settings that were previously part of the Windows Defender client and main Windows Settings have been combined and moved to the new app, which is installed by default as part of Windows 10, version 1703.
|
||||||
|
|
||||||
The app also includes the settings and status of:
|
> [!IMPORTANT]
|
||||||
|
> Disabling the Windows Security Center service will not disable Windows Defender AV or [Windows Firewall](https://docs.microsoft.com/en-us/windows/access-protection/windows-firewall/windows-firewall-with-advanced-security). These will be disabled automatically when a 3rd party antivirus or firewall product is installed and kept up to date.
|
||||||
|
|
||||||
- The PC (as "device health")
|
> [!WARNING]
|
||||||
- Windows Firewall
|
> If you do disable the Windows Security Center service, or configure its associated Group Policy settings to prevent it from starting or running, the Windows Defender Security Center may display stale or inaccurate information about any antivirus or firewall products you have installed on the device.
|
||||||
- Windows Defender SmartScreen Filter
|
>It may also prevent Windows Defender AV from enabling itself if you have an old or outdated 3rd party antivirus, or if you uninstall any 3rd party antivirus products you may have previously installed.
|
||||||
- Parental and Family Controls
|
>This will significantly lower the protection of your device and could lead to malware infection.
|
||||||
|
|
||||||
|
|
||||||
|
See the [Windows Defender Security Center topic](/windows/threat-protection/windows-defender-security-center) for more information on other Windows security features that can be monitored in the app.
|
||||||
|
|
||||||
>[!NOTE]
|
>[!NOTE]
|
||||||
>The Windows Defender Security Center app is a client interface on Windows 10, version 1703. It is not the Windows Defender Security Center web portal that is used to review and manage [Windows Defender Advanced Threat Protection](../windows-defender-atp/windows-defender-advanced-threat-protection.md).
|
>The Windows Defender Security Center app is a client interface on Windows 10, version 1703. It is not the Windows Defender Security Center web portal that is used to review and manage [Windows Defender Advanced Threat Protection](../windows-defender-atp/windows-defender-advanced-threat-protection.md).
|
||||||
|
After Width: | Height: | Size: 39 KiB |
After Width: | Height: | Size: 49 KiB |
After Width: | Height: | Size: 2.2 KiB |
After Width: | Height: | Size: 40 KiB |
@ -0,0 +1,119 @@
|
|||||||
|
---
|
||||||
|
title: Windows Defender Security Center
|
||||||
|
description: The Windows Defender Security Center brings together common Windows security features into one place
|
||||||
|
keywords: wdav, smartscreen, antivirus, wdsc, firewall, device health, performance, Edge, browser, family, parental options, security, windows
|
||||||
|
search.product: eADQiWindows 10XVcnh
|
||||||
|
ms.pagetype: security
|
||||||
|
ms.prod: w10
|
||||||
|
ms.mktglfcycl: manage
|
||||||
|
ms.sitesec: library
|
||||||
|
ms.pagetype: security
|
||||||
|
localizationpriority: medium
|
||||||
|
author: iaanw
|
||||||
|
---
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
# The Windows Defender Security Center
|
||||||
|
|
||||||
|
**Applies to**
|
||||||
|
|
||||||
|
- Windows 10, version 1703
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
In Windows 10, version 1703 we introduced the new Windows Defender Security Center, which brings together common Windows security features into one, easy-to-use app.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Many settings that were previously part of the individual features and main Windows Settings have been combined and moved to the new app, which is installed out-of-the-box as part of Windows 10, version 1703.
|
||||||
|
|
||||||
|
The app includes the settings and status for the following security features:
|
||||||
|
|
||||||
|
- Virus & threat protection, including settings for Windows Defender Antivirus
|
||||||
|
- Device performance & health, which includes information about drivers, storage space, and general Windows Update issues
|
||||||
|
- Firewall & network protection, including Windows Firewall
|
||||||
|
- App & browser control, covering Windows Defender SmartScreen settings
|
||||||
|
- Family options, which include a number of parental controls along with tips and information for keeping kids safe online
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
The Windows Defender Security Center uses the [Windows Security Center service](https://technet.microsoft.com/en-us/library/bb457154.aspx#EDAA) to provide the status and information on 3rd party antivirus and firewall products that are installed on the device.
|
||||||
|
|
||||||
|
> [!IMPORTANT]
|
||||||
|
> Disabling the Windows Security Center service will not disable Windows Defender AV or [Windows Firewall](https://docs.microsoft.com/en-us/windows/access-protection/windows-firewall/windows-firewall-with-advanced-security). These will be disabled automatically when a 3rd party antivirus or firewall product is installed and kept up to date.
|
||||||
|
|
||||||
|
> [!WARNING]
|
||||||
|
> If you do disable the Windows Security Center service, or configure its associated Group Policy settings to prevent it from starting or running, the Windows Defender Security Center may display stale or inaccurate information about any antivirus or firewall products you have installed on the device.
|
||||||
|
>It may also prevent Windows Defender AV from enabling itself if you have an old or outdated 3rd party antivirus, or if you uninstall any 3rd party antivirus products you may have previously installed.
|
||||||
|
>This will significantly lower the protection of your device and could lead to malware infection.
|
||||||
|
|
||||||
|
|
||||||
|
## Open the Windows Defender Security Center
|
||||||
|
- Right-click the icon in the notification area on the taskbar and click **Open**.
|
||||||
|
|
||||||
|

|
||||||
|
- Search the Start menu for **Windows Defender Security Center**.
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
|
||||||
|
> [!NOTE]
|
||||||
|
> Settings configured with management tools, such as Group Policy, Microsoft Intune, or System Center Configuration Manager, will generally take precedence over the settings in the Windows Defender Security Center. Review the settings for each feature in its appropriate library. Links for both home user and enterprise or commercial audiences are listed below.
|
||||||
|
|
||||||
|
## How the Windows Defender Security Center works with Windows security features
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
The Windows Defender Security Center operates as a separate app or process from each of the individual features, and will display notifications through the Action Center.
|
||||||
|
|
||||||
|
It acts as a collector or single place to see the status and perform some configuration for each of the features.
|
||||||
|
|
||||||
|
Disabling any of the individual features (through Group Policy or other management tools, such as System Center Configuration Manager) will prevent that feature from reporting its status in the Windows Defender Security Center. The Windows Defender Security Center itself will still run and show status for the other security features.
|
||||||
|
|
||||||
|
> [!IMPORTANT]
|
||||||
|
> Individually disabling any of the services will not disable the other services or the Windows Defender Security Center itself.
|
||||||
|
|
||||||
|
For example, [using a 3rd party antivirus will disable Windows Defender Antivirus](https://docs.microsoft.com/en-us/windows/threat-protection/windows-defender-antivirus/deploy-manage-report-windows-defender-antivirus). However, the Windows Defender Security Center will still run, show its icon in the taskbar, and display information about the other features, such as Windows Defender SmartScreen and Windows Firewall.
|
||||||
|
|
||||||
|
The presence of the 3rd party antivirus will be indicated under the **Virus & threat protection** section in the Windows Defender Security Center.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## More information
|
||||||
|
|
||||||
|
See the following links for more information on the features in the Windows Defender Security Center:
|
||||||
|
- Windows Defender Antivirus
|
||||||
|
- IT administrators and IT pros can get configuration guidance from the [Windows Defender Antivirus in the Windows Defender Security Center topic](https://docs.microsoft.com/en-us/windows/threat-protection/windows-defender-antivirus/windows-defender-security-center-antivirus) and the [Windows Defender Antivirus documentation library](https://docs.microsoft.com/en-us/windows/threat-protection/windows-defender-antivirus/windows-defender-antivirus-in-windows-10)
|
||||||
|
- Home users can learn more at the [Virus & threat protection in Windows Defender Security Center topic at support.microsoft.com](https://support.microsoft.com/en-us/help/4012987/windows-10-virus-threat-protection-windows-defender-security-center)
|
||||||
|
- Device performance & health
|
||||||
|
- It administrators and IT pros can [configure the Load and unload device drivers security policy setting](https://docs.microsoft.com/en-us/windows/device-security/security-policy-settings/load-and-unload-device-drivers), and learn how to [deploy drivers during Windows 10 deployment using System Center Configuration Manager](https://docs.microsoft.com/en-us/windows/deployment/deploy-windows-sccm/add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager)
|
||||||
|
- Home users can learn more at the [Track your device and performance health in Windows Defender Security Center topic at support.microsoft.com](https://support.microsoft.com/en-us/help/4012986/windows-defender-track-your-device-performance-health)
|
||||||
|
- Windows Firewall
|
||||||
|
- IT administrators and IT pros can get configuration guidance from the [Windows Firewall with Advanced Security documentation library](https://docs.microsoft.com/en-us/windows/access-protection/windows-firewall/windows-firewall-with-advanced-security)
|
||||||
|
- Home users can learn more at the [Firewall & network protection in Windows Defender Security Center topic at support.microsoft.com](https://support.microsoft.com/en-us/help/4012988/windows-10-firewall-network-protection-windows-defender-security-center)
|
||||||
|
- Windows Defender SmartScreen
|
||||||
|
- IT administrators and IT pros can get configuration guidance from the [Windows Defender SmartScreen documentation library](https://docs.microsoft.com/en-us/windows/threat-protection/windows-defender-smartscreen/windows-defender-smartscreen-overview)
|
||||||
|
- Home users can learn more at the [App & browser control in Windows Defender Security Center topic at support.microsoft.com](https://support.microsoft.com/en-us/help/4013218/windows-10-app-browser-control-in-windows-defender)
|
||||||
|
- Family options, which include a number of parental controls along with tips and information for keeping kids safe online
|
||||||
|
- Home users can learn more at the [Help protection your family online in Windows Defender Security Center topic at support.microsoft.com](https://support.microsoft.com/en-us/help/4013209/windows-10-protect-your-family-online-in-windows-defender)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
>[!NOTE]
|
||||||
|
>The Windows Defender Security Center app is a client interface on Windows 10, version 1703. It is not the Windows Defender Security Center web portal that is used to review and manage [Windows Defender Advanced Threat Protection](https://docs.microsoft.com/en-us/windows/threat-protection/windows-defender-atp/windows-defender-advanced-threat-protection).
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|