mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-20 12:53:38 +00:00
Merge branch 'master' into shared-pc-csp-update
This commit is contained in:
@ -1760,6 +1760,12 @@ The DM agent for [push-button reset](https://msdn.microsoft.com/windows/hardware
|
|||||||
|
|
||||||
## Change history in MDM documentation
|
## Change history in MDM documentation
|
||||||
|
|
||||||
|
### January 2019
|
||||||
|
|
||||||
|
|New or updated topic | Description|
|
||||||
|
|--- | ---|
|
||||||
|
|[Policy CSP - Storage](policy-csp-storage.md)|Added the following new policies: AllowStorageSenseGlobal, ConfigStorageSenseGlobalCadence, AllowStorageSenseTemporaryFilesCleanup, ConfigStorageSenseRecycleBinCleanupThreshold, ConfigStorageSenseDownloadsCleanupThreshold, and ConfigStorageSenseCloudContentCleanupThreshold.|
|
||||||
|
|
||||||
### December 2018
|
### December 2018
|
||||||
|
|
||||||
|New or updated topic | Description|
|
|New or updated topic | Description|
|
||||||
|
@ -6,7 +6,7 @@ ms.topic: article
|
|||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.technology: windows
|
ms.technology: windows
|
||||||
author: MariciaAlforque
|
author: MariciaAlforque
|
||||||
ms.date: 08/27/2018
|
ms.date: 01/14/2019
|
||||||
---
|
---
|
||||||
|
|
||||||
# Policy CSP - Storage
|
# Policy CSP - Storage
|
||||||
@ -24,6 +24,21 @@ ms.date: 08/27/2018
|
|||||||
<dd>
|
<dd>
|
||||||
<a href="#storage-allowdiskhealthmodelupdates">Storage/AllowDiskHealthModelUpdates</a>
|
<a href="#storage-allowdiskhealthmodelupdates">Storage/AllowDiskHealthModelUpdates</a>
|
||||||
</dd>
|
</dd>
|
||||||
|
<dd>
|
||||||
|
<a href="#storage-allowstoragesenseglobal">Storage/AllowStorageSenseGlobal</a>
|
||||||
|
</dd>
|
||||||
|
<dd>
|
||||||
|
<a href="#storage-allowstoragesensetemporaryfilescleanup">Storage/AllowStorageSenseTemporaryFilesCleanup</a>
|
||||||
|
</dd>
|
||||||
|
<dd>
|
||||||
|
<a href="#storage-configstoragesensecloudcontentdehydrationthreshold">Storage/ConfigStorageSenseCloudContentDehydrationThreshold</a>
|
||||||
|
</dd>
|
||||||
|
<dd>
|
||||||
|
<a href="#storage-configstoragesenseglobalcadence">Storage/ConfigStorageSenseGlobalCadence</a>
|
||||||
|
</dd>
|
||||||
|
<dd>
|
||||||
|
<a href="#storage-configstoragesenserecyclebincleanupthreshold">Storage/ConfigStorageSenseRecycleBinCleanupThreshold</a>
|
||||||
|
</dd>
|
||||||
<dd>
|
<dd>
|
||||||
<a href="#storage-enhancedstoragedevices">Storage/EnhancedStorageDevices</a>
|
<a href="#storage-enhancedstoragedevices">Storage/EnhancedStorageDevices</a>
|
||||||
</dd>
|
</dd>
|
||||||
@ -73,8 +88,6 @@ ms.date: 08/27/2018
|
|||||||
<!--Description-->
|
<!--Description-->
|
||||||
Added in Windows 10, version 1709. Allows disk health model updates.
|
Added in Windows 10, version 1709. Allows disk health model updates.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Value type is integer.
|
Value type is integer.
|
||||||
|
|
||||||
<!--/Description-->
|
<!--/Description-->
|
||||||
@ -97,6 +110,420 @@ The following list shows the supported values:
|
|||||||
|
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
|
<!--Policy-->
|
||||||
|
<a href="" id="storage-allowstoragesenseglobal"></a>**Storage/AllowStorageSenseGlobal**
|
||||||
|
|
||||||
|
<!--SupportedSKUs-->
|
||||||
|
<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></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td></td>
|
||||||
|
<td></td>
|
||||||
|
</tr>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
<!--/SupportedSKUs-->
|
||||||
|
<!--Scope-->
|
||||||
|
[Scope](./policy-configuration-service-provider.md#policy-scope):
|
||||||
|
|
||||||
|
> [!div class = "checklist"]
|
||||||
|
> * Device
|
||||||
|
|
||||||
|
<hr/>
|
||||||
|
|
||||||
|
<!--/Scope-->
|
||||||
|
<!--Description-->
|
||||||
|
Storage Sense can automatically clean some of the user’s files to free up disk space. By default, Storage Sense is automatically turned on when the machine runs into low disk space and is set to run whenever the machine runs into storage pressure. This cadence can be changed in Storage settings or set with the Storage/ConfigStorageSenseGlobalCadence group policy.
|
||||||
|
|
||||||
|
If you enable this policy setting without setting a cadence, Storage Sense is turned on for the machine with the default cadence of "during low free disk space." Users cannot disable Storage Sense, but they can adjust the cadence (unless you also configure the Storage/ConfigStorageSenseGlobalCadence group policy).
|
||||||
|
|
||||||
|
If you disable this policy setting, the machine will turn off Storage Sense. Users cannot enable Storage Sense.
|
||||||
|
|
||||||
|
If you do not configure this policy setting, Storage Sense is turned off by default until the user runs into low disk space or the user enables it manually. Users can configure this setting in Storage settings.
|
||||||
|
<!--/Description-->
|
||||||
|
<!--ADMXMapped-->
|
||||||
|
ADMX Info:
|
||||||
|
- GP English name: *Allow Storage Sense*
|
||||||
|
- GP name: *SS_AllowStorageSenseGlobal*
|
||||||
|
- GP path: *SOFTWARE/Policies/Microsoft/Windows/StorageSense*
|
||||||
|
- GP ADMX file name: *StorageSense.admx*
|
||||||
|
|
||||||
|
<!--/ADMXMapped-->
|
||||||
|
<!--SupportedValues-->
|
||||||
|
|
||||||
|
<!--/SupportedValues-->
|
||||||
|
<!--Example-->
|
||||||
|
|
||||||
|
<!--/Example-->
|
||||||
|
<!--Validation-->
|
||||||
|
|
||||||
|
<!--/Validation-->
|
||||||
|
<!--/Policy-->
|
||||||
|
|
||||||
|
<hr/>
|
||||||
|
|
||||||
|
<!--Policy-->
|
||||||
|
<a href="" id="storage-allowstoragesensetemporaryfilescleanup"></a>**Storage/AllowStorageSenseTemporaryFilesCleanup**
|
||||||
|
|
||||||
|
<!--SupportedSKUs-->
|
||||||
|
<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></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td></td>
|
||||||
|
<td></td>
|
||||||
|
</tr>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
<!--/SupportedSKUs-->
|
||||||
|
<!--Scope-->
|
||||||
|
[Scope](./policy-configuration-service-provider.md#policy-scope):
|
||||||
|
|
||||||
|
> [!div class = "checklist"]
|
||||||
|
> * Device
|
||||||
|
|
||||||
|
<hr/>
|
||||||
|
|
||||||
|
<!--/Scope-->
|
||||||
|
<!--Description-->
|
||||||
|
When Storage Sense runs, it can delete the user’s temporary files that are not in use.
|
||||||
|
|
||||||
|
If the Storage/AllowStorageSenseGlobal policy is disabled, then this policy does not have any effect.
|
||||||
|
|
||||||
|
If you enable this policy setting, Storage Sense will delete the user’s temporary files that are not in use. Users cannot disable this setting in Storage settings.
|
||||||
|
|
||||||
|
If you disable this policy setting, Storage Sense will not delete the user’s temporary files. Users cannot enable this setting in Storage settings.
|
||||||
|
|
||||||
|
If you do not configure this policy setting, Storage Sense will delete the user’s temporary files by default. Users can configure this setting in Storage settings.
|
||||||
|
|
||||||
|
<!--/Description-->
|
||||||
|
<!--ADMXMapped-->
|
||||||
|
ADMX Info:
|
||||||
|
- GP English name: *Allow Storage Sense Temporary Files cleanup*
|
||||||
|
- GP name: *SS_AllowStorageSenseTemporaryFilesCleanup*
|
||||||
|
- GP path: *System/StorageSense*
|
||||||
|
- GP ADMX file name: *StorageSense.admx*
|
||||||
|
|
||||||
|
<!--/ADMXMapped-->
|
||||||
|
<!--SupportedValues-->
|
||||||
|
|
||||||
|
<!--/SupportedValues-->
|
||||||
|
<!--Example-->
|
||||||
|
|
||||||
|
<!--/Example-->
|
||||||
|
<!--Validation-->
|
||||||
|
|
||||||
|
<!--/Validation-->
|
||||||
|
<!--/Policy-->
|
||||||
|
|
||||||
|
<hr/>
|
||||||
|
|
||||||
|
<!--Policy-->
|
||||||
|
<a href="" id="storage-configstoragesensecloudcontentdehydrationthreshold"></a>**Storage/ConfigStorageSenseCloudContentDehydrationThreshold**
|
||||||
|
|
||||||
|
<!--SupportedSKUs-->
|
||||||
|
<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></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td></td>
|
||||||
|
<td></td>
|
||||||
|
</tr>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
<!--/SupportedSKUs-->
|
||||||
|
<!--Scope-->
|
||||||
|
[Scope](./policy-configuration-service-provider.md#policy-scope):
|
||||||
|
|
||||||
|
> [!div class = "checklist"]
|
||||||
|
> * Device
|
||||||
|
|
||||||
|
<hr/>
|
||||||
|
|
||||||
|
<!--/Scope-->
|
||||||
|
<!--Description-->
|
||||||
|
When Storage Sense runs, it can dehydrate cloud-backed content that hasn’t been opened in a certain amount of days.
|
||||||
|
|
||||||
|
If the Storage/AllowStorageSenseGlobal policy is disabled, then this policy does not have any effect.
|
||||||
|
|
||||||
|
If you enable this policy setting, you must provide the number of days since a cloud-backed file has been opened before Storage Sense will dehydrate it. Supported values are: 0–365.
|
||||||
|
|
||||||
|
If you set this value to zero, Storage Sense will not dehydrate any cloud-backed content. The default value is 0, which never dehydrates cloud-backed content.
|
||||||
|
|
||||||
|
If you disable or do not configure this policy setting, then Storage Sense will not dehydrate any cloud-backed content by default. Users can configure this setting in Storage settings.
|
||||||
|
|
||||||
|
<!--/Description-->
|
||||||
|
<!--ADMXMapped-->
|
||||||
|
ADMX Info:
|
||||||
|
- GP English name: *Configure Storage Sense Cloud Content dehydration threshold*
|
||||||
|
- GP name: *SS_ConfigStorageSenseCloudContentDehydrationThreshold*
|
||||||
|
- GP path: *System/StorageSense*
|
||||||
|
- GP ADMX file name: *StorageSense.admx*
|
||||||
|
|
||||||
|
<!--/ADMXMapped-->
|
||||||
|
<!--SupportedValues-->
|
||||||
|
|
||||||
|
<!--/SupportedValues-->
|
||||||
|
<!--Example-->
|
||||||
|
|
||||||
|
<!--/Example-->
|
||||||
|
<!--Validation-->
|
||||||
|
|
||||||
|
<!--/Validation-->
|
||||||
|
<!--/Policy-->
|
||||||
|
|
||||||
|
<hr/>
|
||||||
|
|
||||||
|
|
||||||
|
<!--Policy-->
|
||||||
|
<a href="" id="storage-configstoragesensedownloadscleanupthreshold"></a>**Storage/ConfigStorageSenseDownloadsCleanupThreshold**
|
||||||
|
|
||||||
|
<!--SupportedSKUs-->
|
||||||
|
<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></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td></td>
|
||||||
|
<td></td>
|
||||||
|
</tr>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
<!--/SupportedSKUs-->
|
||||||
|
<!--Scope-->
|
||||||
|
[Scope](./policy-configuration-service-provider.md#policy-scope):
|
||||||
|
|
||||||
|
> [!div class = "checklist"]
|
||||||
|
> * Device
|
||||||
|
|
||||||
|
<hr/>
|
||||||
|
|
||||||
|
<!--/Scope-->
|
||||||
|
<!--Description-->
|
||||||
|
When Storage Sense runs, it can delete files in the user’s Downloads folder if they have been there for over a certain amount of days.
|
||||||
|
|
||||||
|
If the Storage/AllowStorageSenseGlobal policy is disabled, then this policy does not have any effect.
|
||||||
|
|
||||||
|
If you enable this policy setting, you must provide the minimum age threshold (in days) of a file in the Downloads folder before Storage Sense will delete it. Supported values are: 0–365.
|
||||||
|
|
||||||
|
If you set this value to zero, Storage Sense will not delete files in the user’s Downloads folder. The default is 0, or never deleting files in the Downloads folder.
|
||||||
|
|
||||||
|
If you disable or do not configure this policy setting, then Storage Sense will not delete files in the user’s Downloads folder by default. Users can configure this setting in Storage settings.
|
||||||
|
|
||||||
|
<!--/Description-->
|
||||||
|
<!--ADMXMapped-->
|
||||||
|
ADMX Info:
|
||||||
|
- GP English name: *Configure Storage Storage Downloads cleanup threshold*
|
||||||
|
- GP name: *SS_ConfigStorageSenseDownloadsCleanupThreshold*
|
||||||
|
- GP path: *System/StorageSense*
|
||||||
|
- GP ADMX file name: *StorageSense.admx*
|
||||||
|
|
||||||
|
<!--/ADMXMapped-->
|
||||||
|
<!--SupportedValues-->
|
||||||
|
|
||||||
|
<!--/SupportedValues-->
|
||||||
|
<!--Example-->
|
||||||
|
|
||||||
|
<!--/Example-->
|
||||||
|
<!--Validation-->
|
||||||
|
|
||||||
|
<!--/Validation-->
|
||||||
|
<!--/Policy-->
|
||||||
|
|
||||||
|
<hr/>
|
||||||
|
|
||||||
|
<!--Policy-->
|
||||||
|
<a href="" id="storage-configstoragesenseglobalcadence"></a>**Storage/ConfigStorageSenseGlobalCadence**
|
||||||
|
|
||||||
|
<!--SupportedSKUs-->
|
||||||
|
<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></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td></td>
|
||||||
|
<td></td>
|
||||||
|
</tr>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
<!--/SupportedSKUs-->
|
||||||
|
<!--Scope-->
|
||||||
|
[Scope](./policy-configuration-service-provider.md#policy-scope):
|
||||||
|
|
||||||
|
> [!div class = "checklist"]
|
||||||
|
> * Device
|
||||||
|
|
||||||
|
<hr/>
|
||||||
|
|
||||||
|
<!--/Scope-->
|
||||||
|
<!--Description-->
|
||||||
|
Storage Sense can automatically clean some of the user’s files to free up disk space.
|
||||||
|
If the Storage/AllowStorageSenseGlobal policy is disabled, then this policy does not have any effect.
|
||||||
|
|
||||||
|
If you enable this policy setting, you must provide the desired Storage Sense cadence.
|
||||||
|
|
||||||
|
The following are supported options:
|
||||||
|
|
||||||
|
- 1 – Daily
|
||||||
|
- 7 – Weekly
|
||||||
|
- 30 – Monthly
|
||||||
|
- 0 – During low free disk space
|
||||||
|
|
||||||
|
The default is 0 (during low free disk space).
|
||||||
|
|
||||||
|
If you do not configure this policy setting, then the Storage Sense cadence is set to “during low free disk space” by default. Users can configure this setting in Storage settings.
|
||||||
|
|
||||||
|
<!--/Description-->
|
||||||
|
<!--ADMXMapped-->
|
||||||
|
ADMX Info:
|
||||||
|
- GP English name: *Configure Storage Sense cadence*
|
||||||
|
- GP name: *RemovableDisks_DenyWrite_Access_2*
|
||||||
|
- GP path: *SOFTWARE/Policies/Microsoft/Windows/StorageSense*
|
||||||
|
- GP ADMX file name: *StorageSense.admx*
|
||||||
|
|
||||||
|
<!--/ADMXMapped-->
|
||||||
|
<!--SupportedValues-->
|
||||||
|
|
||||||
|
<!--/SupportedValues-->
|
||||||
|
<!--Example-->
|
||||||
|
|
||||||
|
<!--/Example-->
|
||||||
|
<!--Validation-->
|
||||||
|
|
||||||
|
<!--/Validation-->
|
||||||
|
<!--/Policy-->
|
||||||
|
|
||||||
|
<hr/>
|
||||||
|
|
||||||
|
<!--Policy-->
|
||||||
|
<a href="" id="storage-configstoragesenserecyclebincleanupthreshold"></a>**Storage/ConfigStorageSenseRecycleBinCleanupThreshold**
|
||||||
|
|
||||||
|
<!--SupportedSKUs-->
|
||||||
|
<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></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td><img src="images/checkmark.png" alt="check mark" /><sup>6</sup></td>
|
||||||
|
<td></td>
|
||||||
|
<td></td>
|
||||||
|
</tr>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
<!--/SupportedSKUs-->
|
||||||
|
<!--Scope-->
|
||||||
|
[Scope](./policy-configuration-service-provider.md#policy-scope):
|
||||||
|
|
||||||
|
> [!div class = "checklist"]
|
||||||
|
> * Device
|
||||||
|
|
||||||
|
<hr/>
|
||||||
|
|
||||||
|
<!--/Scope-->
|
||||||
|
<!--Description-->
|
||||||
|
When Storage Sense runs, it can delete files in the user’s Recycle Bin if they have been there for over a certain amount of days.
|
||||||
|
|
||||||
|
If the Storage/AllowStorageSenseGlobal policy is disabled, then this policy does not have any effect.
|
||||||
|
|
||||||
|
If you enable this policy setting, you must provide the minimum age threshold (in days) of a file in the Recycle Bin before Storage Sense will delete it. Supported values are: 0–365.
|
||||||
|
|
||||||
|
If you set this value to zero, Storage Sense will not delete files in the user’s Recycle Bin. The default is 30 days.
|
||||||
|
|
||||||
|
If you disable or do not configure this policy setting, Storage Sense will delete files in the user’s Recycle Bin that have been there for over 30 days by default. Users can configure this setting in Storage settings.
|
||||||
|
|
||||||
|
<!--/Description-->
|
||||||
|
<!--ADMXMapped-->
|
||||||
|
ADMX Info:
|
||||||
|
- GP English name: *Configure Storage Sense Recycle Bin cleanup threshold*
|
||||||
|
- GP name: *SS_ConfigStorageSenseRecycleBinCleanupThreshold*
|
||||||
|
- GP path: *System/StorageSense*
|
||||||
|
- GP ADMX file name: *StorageSense.admx*
|
||||||
|
|
||||||
|
<!--/ADMXMapped-->
|
||||||
|
<!--SupportedValues-->
|
||||||
|
|
||||||
|
<!--/SupportedValues-->
|
||||||
|
<!--Example-->
|
||||||
|
|
||||||
|
<!--/Example-->
|
||||||
|
<!--Validation-->
|
||||||
|
|
||||||
|
<!--/Validation-->
|
||||||
|
<!--/Policy-->
|
||||||
|
|
||||||
|
<hr/>
|
||||||
|
|
||||||
<!--Policy-->
|
<!--Policy-->
|
||||||
<a href="" id="storage-enhancedstoragedevices"></a>**Storage/EnhancedStorageDevices**
|
<a href="" id="storage-enhancedstoragedevices"></a>**Storage/EnhancedStorageDevices**
|
||||||
|
|
||||||
@ -221,6 +648,9 @@ ADMX Info:
|
|||||||
|
|
||||||
<!--/Validation-->
|
<!--/Validation-->
|
||||||
<!--/Policy-->
|
<!--/Policy-->
|
||||||
|
|
||||||
|
<!--/Policies-->
|
||||||
|
|
||||||
<hr/>
|
<hr/>
|
||||||
|
|
||||||
Footnote:
|
Footnote:
|
||||||
|
@ -18,6 +18,7 @@
|
|||||||
#### [Adding devices](add-devices.md)
|
#### [Adding devices](add-devices.md)
|
||||||
#### [Creating profiles](profiles.md)
|
#### [Creating profiles](profiles.md)
|
||||||
#### [Enrollment status page](enrollment-status.md)
|
#### [Enrollment status page](enrollment-status.md)
|
||||||
|
#### [BitLocker encryption](bitlocker.md)
|
||||||
### [Administering Autopilot via Microsoft Store for Business](https://docs.microsoft.com/microsoft-store/add-profile-to-devices#manage-autopilot-deployment-profiles)
|
### [Administering Autopilot via Microsoft Store for Business](https://docs.microsoft.com/microsoft-store/add-profile-to-devices#manage-autopilot-deployment-profiles)
|
||||||
### [Administering Autopilot via Microsoft Intune](https://docs.microsoft.com/intune/enrollment-autopilot)
|
### [Administering Autopilot via Microsoft Intune](https://docs.microsoft.com/intune/enrollment-autopilot)
|
||||||
### [Administering Autopilot via Microsoft 365 Business & Office 365 Admin portal](https://support.office.com/article/Create-and-edit-Autopilot-profiles-5cf7139e-cfa1-4765-8aad-001af1c74faa)
|
### [Administering Autopilot via Microsoft 365 Business & Office 365 Admin portal](https://support.office.com/article/Create-and-edit-Autopilot-profiles-5cf7139e-cfa1-4765-8aad-001af1c74faa)
|
||||||
|
40
windows/deployment/windows-autopilot/bitlocker.md
Normal file
40
windows/deployment/windows-autopilot/bitlocker.md
Normal file
@ -0,0 +1,40 @@
|
|||||||
|
---
|
||||||
|
title: Setting the BitLocker encryption algorithm for Autopilot devices
|
||||||
|
description: Microsoft Intune provides a comprehensive set of configuration options to manage BitLocker on Windows 10 devices.
|
||||||
|
keywords: Autopilot, BitLocker, encryption, 256-bit, Windows 10
|
||||||
|
ms.prod: w10
|
||||||
|
ms.technology: Windows
|
||||||
|
ms.mktglfcycl: deploy
|
||||||
|
ms.sitesec: library
|
||||||
|
ms.pagetype: deploy
|
||||||
|
ms.localizationpriority: medium
|
||||||
|
author: greg-lindsay
|
||||||
|
ms.author: greg-lindsay
|
||||||
|
---
|
||||||
|
|
||||||
|
# Setting the BitLocker encryption algorithm for Autopilot devices
|
||||||
|
|
||||||
|
With Windows Autopilot, you can configure the BitLocker encryption settings to be applied before automatic encryption is started. This ensures that the default encrytion algorithm is not applied automatically when this is not the desired setting. Other BitLocker policies that must be applied prior to encryption can also be delivered before automatic BitLocker encryption begins.
|
||||||
|
|
||||||
|
The BitLocker encryption algorithm is used when BitLocker is first enabled, and sets the strength to which full volume encryption should occur. Available encryption algorithms are: AES-CBC 128-bit, AES-CBC 256-bit, XTS-AES 128-bit or XTS-AES 256-bit encryption. The default value is XTS-AES 128-bit encryption. See [BitLocker CSP](https://docs.microsoft.com/en-us/windows/client-management/mdm/bitlocker-csp) for information about the recommended encryption algorithms to use.
|
||||||
|
|
||||||
|
An example of encryption settings is shown below.
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
Note that a device which is encrypted automatically will need to be decrypted prior to changing the encyption algorithm.
|
||||||
|
|
||||||
|
To ensure the desired BitLocker encryption algorithm is set before automatic encryption occurs for Autopilot devices:
|
||||||
|
|
||||||
|
1. Configure the [encryption method settings](https://docs.microsoft.com/intune/endpoint-protection-windows-10#windows-encryption) in the Windows 10 Endpoint Protection profile to the desired encryption algorithm.
|
||||||
|
2. [Assign the policy](https://docs.microsoft.com/intune/device-profile-assign) to your Autopilot device group.
|
||||||
|
- **IMPORTANT**: The encryption policy must be assigned to **devices** in the group, not users.
|
||||||
|
3. Enable the Autopilot [Enrollment Status Page](https://docs.microsoft.com/windows/deployment/windows-autopilot/enrollment-status) (ESP) for these devices. This is a critical step because if the ESP is not enabled, the policy will not apply when the device boots.
|
||||||
|
|
||||||
|
## Requirements
|
||||||
|
|
||||||
|
Windows 10, version 1809 or later.
|
||||||
|
|
||||||
|
## See also
|
||||||
|
|
||||||
|
[Bitlocker overview](https://docs.microsoft.com/en-us/windows/security/information-protection/bitlocker/bitlocker-overview)
|
Binary file not shown.
After Width: | Height: | Size: 14 KiB |
@ -10,6 +10,7 @@ ms.sitesec: library
|
|||||||
ms.pagetype: security
|
ms.pagetype: security
|
||||||
author: mjcaparas
|
author: mjcaparas
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
|
ms.date: 12/14/2018
|
||||||
---
|
---
|
||||||
|
|
||||||
# Onboard servers to the Windows Defender ATP service
|
# Onboard servers to the Windows Defender ATP service
|
||||||
@ -40,23 +41,7 @@ For a practical guidance on what needs to be in place for licensing and infrastr
|
|||||||
|
|
||||||
## Windows Server 2012 R2 and Windows Server 2016
|
## Windows Server 2012 R2 and Windows Server 2016
|
||||||
|
|
||||||
There are two options to onboard Windows Server 2012 R2 and Windows Server 2016 to Windows Defender ATP:
|
To onboard Windows Server 2012 R2 and Windows Server 2016 to Windows Defender ATP, you’ll need to:
|
||||||
- **Option 1**: Onboard through Azure Security Center
|
|
||||||
- **Option 2**: Onboard through Windows Defender Security Center
|
|
||||||
|
|
||||||
|
|
||||||
### Option 1: Onboard servers through Azure Security Center
|
|
||||||
1. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**.
|
|
||||||
|
|
||||||
2. Select **Windows server 2012R2 and 2016** as the operating system.
|
|
||||||
|
|
||||||
3. Click **Go to Azure Security Center to onboard servers**.
|
|
||||||
|
|
||||||
4. Follow the onboarding steps in Azure Security Center. For more information, see [Windows Defender Advanced Threat Protection with Azure Security Center](https://docs.microsoft.com/azure/security-center/security-center-wdatp).
|
|
||||||
|
|
||||||
|
|
||||||
### Option 2: Onboard servers through Windows Defender Security Center
|
|
||||||
You'll need to take the following steps if you opt to onboard servers through Windows Defender Security Center.
|
|
||||||
|
|
||||||
- For Windows Server 2012 R2: Configure and update System Center Endpoint Protection clients.
|
- For Windows Server 2012 R2: Configure and update System Center Endpoint Protection clients.
|
||||||
|
|
||||||
@ -69,18 +54,7 @@ You'll need to take the following steps if you opt to onboard servers through Wi
|
|||||||
>[!TIP]
|
>[!TIP]
|
||||||
> After onboarding the machine, you can choose to run a detection test to verify that it is properly onboarded to the service. For more information, see [Run a detection test on a newly onboarded Windows Defender ATP endpoint](run-detection-test-windows-defender-advanced-threat-protection.md).
|
> After onboarding the machine, you can choose to run a detection test to verify that it is properly onboarded to the service. For more information, see [Run a detection test on a newly onboarded Windows Defender ATP endpoint](run-detection-test-windows-defender-advanced-threat-protection.md).
|
||||||
|
|
||||||
|
### Configure and update System Center Endpoint Protection clients
|
||||||
#### Turn on Server monitoring from the Windows Defender Security Center portal
|
|
||||||
|
|
||||||
1. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**.
|
|
||||||
|
|
||||||
2. Select **Windows server 2012R2 and 2016** as the operating system.
|
|
||||||
|
|
||||||
3. Select **Onboard Servers through Windows Defender ATP**.
|
|
||||||
4. Click **Turn on server monitoring** and confirm that you'd like to proceed with the environment set up. When the set up completes, the **Workspace ID** and **Workspace key** fields are populated with unique values. You'll need to use these values to configure the MMA agent.
|
|
||||||
|
|
||||||
|
|
||||||
#### Configure and update System Center Endpoint Protection clients
|
|
||||||
>[!IMPORTANT]
|
>[!IMPORTANT]
|
||||||
>This step is required only if your organization uses System Center Endpoint Protection (SCEP) and you're onboarding Windows Server 2012 R2.
|
>This step is required only if your organization uses System Center Endpoint Protection (SCEP) and you're onboarding Windows Server 2012 R2.
|
||||||
|
|
||||||
@ -90,8 +64,17 @@ The following steps are required to enable this integration:
|
|||||||
- Install the [January 2017 anti-malware platform update for Endpoint Protection clients](https://support.microsoft.com/help/3209361/january-2017-anti-malware-platform-update-for-endpoint-protection-clie)
|
- Install the [January 2017 anti-malware platform update for Endpoint Protection clients](https://support.microsoft.com/help/3209361/january-2017-anti-malware-platform-update-for-endpoint-protection-clie)
|
||||||
- Configure the SCEP client Cloud Protection Service membership to the **Advanced** setting
|
- Configure the SCEP client Cloud Protection Service membership to the **Advanced** setting
|
||||||
|
|
||||||
|
|
||||||
|
### Turn on Server monitoring from the Windows Defender Security Center portal
|
||||||
|
|
||||||
|
1. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**.
|
||||||
|
|
||||||
|
2. Select Windows server 2012, 2012R2 and 2016 as the operating system.
|
||||||
|
|
||||||
|
3. Click **Turn on server monitoring** and confirm that you'd like to proceed with the environment set up. When the set up completes, the **Workspace ID** and **Workspace key** fields are populated with unique values. You'll need to use these values to configure the MMA agent.
|
||||||
|
|
||||||
<span id="server-mma"/>
|
<span id="server-mma"/>
|
||||||
#### Install and configure Microsoft Monitoring Agent (MMA) to report sensor data to Windows Defender ATP
|
### Install and configure Microsoft Monitoring Agent (MMA) to report sensor data to Windows Defender ATP
|
||||||
|
|
||||||
1. Download the agent setup file: [Windows 64-bit agent](https://go.microsoft.com/fwlink/?LinkId=828603).
|
1. Download the agent setup file: [Windows 64-bit agent](https://go.microsoft.com/fwlink/?LinkId=828603).
|
||||||
|
|
||||||
@ -105,7 +88,7 @@ The following steps are required to enable this integration:
|
|||||||
Once completed, you should see onboarded servers in the portal within an hour.
|
Once completed, you should see onboarded servers in the portal within an hour.
|
||||||
|
|
||||||
<span id="server-proxy"/>
|
<span id="server-proxy"/>
|
||||||
#### Configure server proxy and Internet connectivity settings
|
### Configure server proxy and Internet connectivity settings
|
||||||
|
|
||||||
- Each Windows server must be able to connect to the Internet using HTTPS. This connection can be direct, using a proxy, or through the [OMS Gateway](https://docs.microsoft.com/azure/log-analytics/log-analytics-oms-gateway).
|
- Each Windows server must be able to connect to the Internet using HTTPS. This connection can be direct, using a proxy, or through the [OMS Gateway](https://docs.microsoft.com/azure/log-analytics/log-analytics-oms-gateway).
|
||||||
- If a proxy or firewall is blocking all traffic by default and allowing only specific domains through or HTTPS scanning (SSL inspection) is enabled, make sure that the following URLs are white-listed to permit communication with Windows Defender ATP service:
|
- If a proxy or firewall is blocking all traffic by default and allowing only specific domains through or HTTPS scanning (SSL inspection) is enabled, make sure that the following URLs are white-listed to permit communication with Windows Defender ATP service:
|
||||||
@ -125,28 +108,6 @@ Agent Resource | Ports
|
|||||||
| winatp-gw-aus.microsoft.com | 443|
|
| winatp-gw-aus.microsoft.com | 443|
|
||||||
| winatp-gw-aue.microsoft.com |443 |
|
| winatp-gw-aue.microsoft.com |443 |
|
||||||
|
|
||||||
|
|
||||||
## Integration with Azure Security Center
|
|
||||||
Windows Defender ATP integrates with Azure Security Center to provide a comprehensive server protection solution. With this integration Azure Security Center can leverage the power of Windows Defender ATP to provide improved threat detection for Windows Servers.
|
|
||||||
|
|
||||||
>[!NOTE]
|
|
||||||
>You'll need to have the appropriate license to enable this feature.
|
|
||||||
|
|
||||||
The following capabilities are included in this integration:
|
|
||||||
- Automated onboarding - Windows Defender ATP sensor is automatically enabled on Windows Servers that are onboarded to Azure Security Center. For more information on Azure Security Center onboarding, see [Onboarding to Azure Security Center Standard for enhanced security](https://docs.microsoft.com/azure/security-center/security-center-onboarding).
|
|
||||||
|
|
||||||
>[!NOTE]
|
|
||||||
> Automated onboarding is only applicable for Windows Server 2012 R2 and Windows Server 2016.
|
|
||||||
|
|
||||||
- Servers monitored by Azure Security Center will also be available in Windows Defender ATP - Azure Security Center seamlessly connects to the Windows Defender ATP tenant, providing a single view across clients and servers. In addition, Windows Defender ATP alerts will be available in the Azure Security Center console.
|
|
||||||
- Server investigation - Azure Security Center customers can access Windows Defender Security Center to perform detailed investigation to uncover the scope of a potential breach
|
|
||||||
|
|
||||||
>[!IMPORTANT]
|
|
||||||
>- When you use Azure Security Center to monitor servers, a Windows Defender ATP tenant is automatically created. The Windows Defender ATP data is stored in Europe by default.
|
|
||||||
>- If you use Windows Defender ATP before using Azure Security Center, your data will be stored in the location you specified when you created your tenant even if you integrate with Azure Security Center at a later time.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Windows Server, version 1803 and Windows Server 2019
|
## Windows Server, version 1803 and Windows Server 2019
|
||||||
To onboard Windows Server, version 1803 or Windows Server 2019, use the same method used when onboarding Windows 10 machines.
|
To onboard Windows Server, version 1803 or Windows Server 2019, use the same method used when onboarding Windows 10 machines.
|
||||||
|
|
||||||
@ -182,6 +143,26 @@ Supported tools include:
|
|||||||
If the result is ‘The specified service does not exist as an installed service’, then you'll need to install Windows Defender AV. For more information, see [Windows Defender Antivirus in Windows 10](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/windows-defender-antivirus-in-windows-10).
|
If the result is ‘The specified service does not exist as an installed service’, then you'll need to install Windows Defender AV. For more information, see [Windows Defender Antivirus in Windows 10](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/windows-defender-antivirus-in-windows-10).
|
||||||
|
|
||||||
|
|
||||||
|
## Integration with Azure Security Center
|
||||||
|
Windows Defender ATP integrates with Azure Security Center to provide a comprehensive server protection solution. With this integration Azure Security Center can leverage the power of Windows Defender ATP to provide improved threat detection for Windows Servers.
|
||||||
|
|
||||||
|
>[!NOTE]
|
||||||
|
>You'll need to have the appropriate license to enable this feature.
|
||||||
|
|
||||||
|
The following capabilities are included in this integration:
|
||||||
|
- Automated onboarding - Windows Defender ATP sensor is automatically enabled on Windows Servers that are onboarded to Azure Security Center. For more information on Azure Security Center onboarding, see [Onboarding to Azure Security Center Standard for enhanced security](https://docs.microsoft.com/azure/security-center/security-center-onboarding).
|
||||||
|
|
||||||
|
>[!NOTE]
|
||||||
|
> Automated onboarding is only applicable for Windows Server 2012 R2 and Windows Server 2016.
|
||||||
|
|
||||||
|
- Servers monitored by Azure Security Center will also be available in Windows Defender ATP - Azure Security Center seamlessly connects to the Windows Defender ATP tenant, providing a single view across clients and servers. In addition, Windows Defender ATP alerts will be available in the Azure Security Center console.
|
||||||
|
- Server investigation - Azure Security Center customers can access Windows Defender Security Center to perform detailed investigation to uncover the scope of a potential breach
|
||||||
|
|
||||||
|
>[!IMPORTANT]
|
||||||
|
>- When you use Azure Security Center to monitor servers, a Windows Defender ATP tenant is automatically created. The Windows Defender ATP data is stored in Europe by default.
|
||||||
|
>- If you use Windows Defender ATP before using Azure Security Center, your data will be stored in the location you specified when you created your tenant even if you integrate with Azure Security Center at a later time.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Offboard servers
|
## Offboard servers
|
||||||
You can offboard Windows Server, version 1803 and Windows 2019 in the same method available for Windows 10 client machines.
|
You can offboard Windows Server, version 1803 and Windows 2019 in the same method available for Windows 10 client machines.
|
||||||
|
@ -16,7 +16,10 @@ ms.date: 1/26/2018
|
|||||||
- Windows 10
|
- Windows 10
|
||||||
- Windows 10 Mobile
|
- Windows 10 Mobile
|
||||||
|
|
||||||
Windows Defender SmartScreen works with Group Policy and mobile device management (MDM) settings to help you manage your organization's computer settings. Based on how you set up Windows Defender SmartScreen, you can show employees a warning page and let them continue to the site, or you can block the site entirely.
|
Windows Defender SmartScreen works with Intune, Group Policy, and mobile device management (MDM) settings to help you manage your organization's computer settings. Based on how you set up Windows Defender SmartScreen, you can show employees a warning page and let them continue to the site, or you can block the site entirely.
|
||||||
|
|
||||||
|
See [Windows 10 (and later) settings to protect devices using Intune](https://docs.microsoft.com/en-us/intune/endpoint-protection-windows-10#windows-defender-smartscreen-settings) for the controls you can use in Intune.
|
||||||
|
|
||||||
|
|
||||||
## Group Policy settings
|
## Group Policy settings
|
||||||
SmartScreen uses registry-based Administrative Template policy settings. For more info about Group Policy, see the [Group Policy TechCenter](https://go.microsoft.com/fwlink/p/?LinkId=214514). This site provides links to the latest technical documentation, videos, and downloads for Group Policy.
|
SmartScreen uses registry-based Administrative Template policy settings. For more info about Group Policy, see the [Group Policy TechCenter](https://go.microsoft.com/fwlink/p/?LinkId=214514). This site provides links to the latest technical documentation, videos, and downloads for Group Policy.
|
||||||
|
@ -286,20 +286,7 @@ For more information about updating Windows 10, see [Windows 10 servicing optio
|
|||||||
|
|
||||||
## Microsoft Edge
|
## Microsoft Edge
|
||||||
|
|
||||||
Microsoft Edge takes you beyond just browsing to actively engaging with the web through features like Web Note, Reading View, and Cortana.
|
Microsoft Edge is not available in the LTSC release of Windows 10.
|
||||||
|
|
||||||
- **Web Note.** Microsoft Edge lets you annotate, highlight, and call things out directly on webpages.
|
|
||||||
- **Reading view.** Microsoft Edge lets you enjoy and print online articles in a distraction-free layout that's optimized for your screen size. While in reading view, you can also save webpages or PDF files to your reading list, for later viewing.
|
|
||||||
- **Cortana.** Cortana is automatically enabled on Microsoft Edge. Microsoft Edge lets you highlight words for more info and gives you one-click access to things like restaurant reservations and reviews, without leaving the webpage.
|
|
||||||
- **Compatibility and security.** Microsoft Edge lets you continue to use IE11 for sites that are on your corporate intranet or that are included on your Enterprise Mode Site List. You must use IE11 to run older, less secure technology, such as ActiveX controls.
|
|
||||||
|
|
||||||
### Enterprise guidance
|
|
||||||
|
|
||||||
Microsoft Edge is the default browser experience for Windows 10 and Windows 10 Mobile. However, if you're running web apps that need ActiveX controls, we recommend that you continue to use Internet Explorer 11 for them. If you don't have IE11 installed anymore, you can download it from the Microsoft Store or from the [Internet Explorer 11 download page](https://go.microsoft.com/fwlink/p/?linkid=290956).
|
|
||||||
|
|
||||||
We also recommend that you upgrade to IE11 if you're running any earlier versions of Internet Explorer. IE11 is supported on Windows 7, Windows 8.1, and Windows 10. So any legacy apps that work with IE11 will continue to work even as you migrate to Windows 10.
|
|
||||||
|
|
||||||
[Learn more about using Microsoft Edge in the enterprise](https://technet.microsoft.com/itpro/microsoft-edge/enterprise-guidance-using-microsoft-edge-and-ie11)
|
|
||||||
|
|
||||||
## See Also
|
## See Also
|
||||||
|
|
||||||
|
@ -30,6 +30,11 @@ The Windows 10 Enterprise LTSC 2019 release is an important release for LTSC use
|
|||||||
>[!IMPORTANT]
|
>[!IMPORTANT]
|
||||||
>The LTSC release is [intended for special use devices](https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/LTSC-What-is-it-and-when-should-it-be-used/ba-p/293181). Support for LTSC by apps and tools that are designed for the semi-annual channel release of Windows 10 might be limited.
|
>The LTSC release is [intended for special use devices](https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/LTSC-What-is-it-and-when-should-it-be-used/ba-p/293181). Support for LTSC by apps and tools that are designed for the semi-annual channel release of Windows 10 might be limited.
|
||||||
|
|
||||||
|
## Microsoft Intune
|
||||||
|
|
||||||
|
>[!NOTE]
|
||||||
|
>Some features that are described on this page require Microsoft Intune. Currently, information about Microsoft Intune support for LTSC 2019 is pending.
|
||||||
|
|
||||||
## Security
|
## Security
|
||||||
|
|
||||||
This version of Window 10 includes security improvements for threat protection, information protection, and identity protection.
|
This version of Window 10 includes security improvements for threat protection, information protection, and identity protection.
|
||||||
@ -175,12 +180,6 @@ This release enables support for WIP with Files on Demand, allows file encryptio
|
|||||||
|
|
||||||
The minimum PIN length is being changed from 6 to 4, with a default of 6. For more information, see [BitLocker Group Policy settings](https://docs.microsoft.com/windows/device-security/bitlocker/bitlocker-group-policy-settings#bkmk-unlockpol3).
|
The minimum PIN length is being changed from 6 to 4, with a default of 6. For more information, see [BitLocker Group Policy settings](https://docs.microsoft.com/windows/device-security/bitlocker/bitlocker-group-policy-settings#bkmk-unlockpol3).
|
||||||
|
|
||||||
#### Delivering BitLocker policy to AutoPilot devices during OOBE
|
|
||||||
|
|
||||||
You can choose which encryption algorithm to apply automatic BitLocker encryption to capable devices, rather than automatically having those devices encrypt themselves with the default algorithm. This allows the encryption algorithm (and other BitLocker policies that must be applied prior to encryption), to be delivered before automatic BitLocker encryption begins.
|
|
||||||
|
|
||||||
For example, you can choose the XTS-AES 256 encryption algorithm, and have it applied to devices that would normally encrypt themselves automatically with the default XTS-AES 128 algorithm during OOBE.
|
|
||||||
|
|
||||||
#### Silent enforcement on fixed drives
|
#### Silent enforcement on fixed drives
|
||||||
|
|
||||||
Through a Modern Device Management (MDM) policy, BitLocker can be enabled silently for standard Azure Active Directory (AAD) joined users. In Windows 10, version 1803 automatic BitLocker encryption was enabled for standard AAD users, but this still required modern hardware that passed the Hardware Security Test Interface (HSTI). This new functionality enables BitLocker via policy even on devices that don’t pass the HSTI.
|
Through a Modern Device Management (MDM) policy, BitLocker can be enabled silently for standard Azure Active Directory (AAD) joined users. In Windows 10, version 1803 automatic BitLocker encryption was enabled for standard AAD users, but this still required modern hardware that passed the Hardware Security Test Interface (HSTI). This new functionality enables BitLocker via policy even on devices that don’t pass the HSTI.
|
||||||
@ -396,6 +395,13 @@ In the Feedback and Settings page under Privacy Settings you can now delete the
|
|||||||
|
|
||||||
## Configuration
|
## Configuration
|
||||||
|
|
||||||
|
<<<<<<< HEAD
|
||||||
|
### Kiosk configuration
|
||||||
|
|
||||||
|
Microsoft Edge has many improvements specifically targeted to Kiosks, however Edge is not available in the LTSC release of Windows 10. Internet Explorer is included in Windows 10 LTSC releases as its feature set is not changing, and it will continue to get security fixes for the life of a Windows 10 LTSC release.
|
||||||
|
|
||||||
|
If you wish to take advantage of [Kiosk capabilities in Edge](https://docs.microsoft.com/microsoft-edge/deploy/microsoft-edge-kiosk-mode-deploy), consider [Kiosk mode](https://docs.microsoft.com/windows/configuration/kiosk-methods) with a semi-annual release channel.
|
||||||
|
=======
|
||||||
### Kiosk Configuration
|
### Kiosk Configuration
|
||||||
|
|
||||||
We introduced a simplified assigned access configuration experience in **Settings** that allows device administrators to easily set up a PC as a kiosk or digital sign. A wizard experience walks you through kiosk setup including creating a kiosk account that will automatically sign in when a device starts.
|
We introduced a simplified assigned access configuration experience in **Settings** that allows device administrators to easily set up a PC as a kiosk or digital sign. A wizard experience walks you through kiosk setup including creating a kiosk account that will automatically sign in when a device starts.
|
||||||
@ -444,6 +450,7 @@ With this release you can easily deploy and manage kiosk devices with Microsoft
|
|||||||
For more information, see:
|
For more information, see:
|
||||||
- [Making IT simpler with a modern workplace](https://www.microsoft.com/en-us/microsoft-365/blog/2018/04/27/making-it-simpler-with-a-modern-workplace/)
|
- [Making IT simpler with a modern workplace](https://www.microsoft.com/en-us/microsoft-365/blog/2018/04/27/making-it-simpler-with-a-modern-workplace/)
|
||||||
- [Simplifying kiosk management for IT with Windows 10](https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Simplifying-kiosk-management-for-IT-with-Windows-10/ba-p/187691)
|
- [Simplifying kiosk management for IT with Windows 10](https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Simplifying-kiosk-management-for-IT-with-Windows-10/ba-p/187691)
|
||||||
|
>>>>>>> 29ecd8ba10cf9401b75cb72a382839f4b4becd26
|
||||||
|
|
||||||
### Co-management
|
### Co-management
|
||||||
|
|
||||||
@ -455,20 +462,6 @@ For more information, see [What's New in MDM enrollment and management](https://
|
|||||||
|
|
||||||
The OS uninstall period is a length of time that users are given when they can optionally roll back a Windows 10 update. With this release, administrators can use Intune or [DISM](#dism) to customize the length of the OS uninstall period.
|
The OS uninstall period is a length of time that users are given when they can optionally roll back a Windows 10 update. With this release, administrators can use Intune or [DISM](#dism) to customize the length of the OS uninstall period.
|
||||||
|
|
||||||
### Windows Configuration Designer
|
|
||||||
|
|
||||||
Previously known as *Windows Imaging and Configuration Designer (ICD)*, the tool for creating provisioning packages is renamed **Windows Configuration Designer**. The new Windows Configuration Designer is available in [Microsoft Store](https://www.microsoft.com/store/apps/9nblggh4tx22) as an app. To run Windows Configuration Designer on earlier versions of Windows, you can still install Windows Configuration Designer from the [Windows Assessment and Deployment Kit (ADK)](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit).
|
|
||||||
|
|
||||||
Windows Configuration Designer in Windows 10 Enterprise 2019 LTSC includes several new wizards to make it easier to create provisioning packages.
|
|
||||||
|
|
||||||

|
|
||||||
|
|
||||||
Both the desktop and kiosk wizards include an option to remove pre-installed software, based on the new [CleanPC configuration service provider (CSP)](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/cleanpc-csp).
|
|
||||||
|
|
||||||

|
|
||||||
|
|
||||||
[Learn more about Windows Configuration Designer.](/windows/configuration/provisioning-packages/provisioning-packages)
|
|
||||||
|
|
||||||
### Azure Active Directory join in bulk
|
### Azure Active Directory join in bulk
|
||||||
|
|
||||||
Using the new wizards in Windows Configuration Designer, you can [create provisioning packages to enroll devices in Azure Active Directory](/windows/configuration/provisioning-packages/provisioning-packages#configuration-designer-wizards). Azure AD join in bulk is available in the desktop, mobile, kiosk, and Surface Hub wizards.
|
Using the new wizards in Windows Configuration Designer, you can [create provisioning packages to enroll devices in Azure Active Directory](/windows/configuration/provisioning-packages/provisioning-packages#configuration-designer-wizards). Azure AD join in bulk is available in the desktop, mobile, kiosk, and Surface Hub wizards.
|
||||||
@ -495,25 +488,6 @@ Previously, the customized taskbar could only be deployed using Group Policy or
|
|||||||
- Settings for Power: [**Start/HidePowerButton**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#start-hidepowerbutton), [**Start/HideHibernate**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#start-hidehibernate), [**Start/HideRestart**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#start-hiderestart), [**Start/HideShutDown**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#start-hideshutdown), and [**Start/HideSleep**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#start-hidesleep)
|
- Settings for Power: [**Start/HidePowerButton**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#start-hidepowerbutton), [**Start/HideHibernate**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#start-hidehibernate), [**Start/HideRestart**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#start-hiderestart), [**Start/HideShutDown**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#start-hideshutdown), and [**Start/HideSleep**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#start-hidesleep)
|
||||||
- Additional new settings: [**Start/HideFrequentlyUsedApps**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#start-hidefrequentlyusedapps), [**Start/HideRecentlyAddedApps**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#start-hiderecentlyaddedapps), **AllowPinnedFolder**, **ImportEdgeAssets**, [**Start/HideRecentJumplists**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#start-hiderecentjumplists), [**Start/NoPinningToTaskbar**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#start-nopinningtotaskbar), [**Settings/PageVisibilityList**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#settings-pagevisibilitylist), and [**Start/HideAppsList**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#start-hideapplist).
|
- Additional new settings: [**Start/HideFrequentlyUsedApps**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#start-hidefrequentlyusedapps), [**Start/HideRecentlyAddedApps**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#start-hiderecentlyaddedapps), **AllowPinnedFolder**, **ImportEdgeAssets**, [**Start/HideRecentJumplists**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#start-hiderecentjumplists), [**Start/NoPinningToTaskbar**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#start-nopinningtotaskbar), [**Settings/PageVisibilityList**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#settings-pagevisibilitylist), and [**Start/HideAppsList**](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#start-hideapplist).
|
||||||
|
|
||||||
|
|
||||||
### Cortana at work
|
|
||||||
|
|
||||||
Cortana is Microsoft’s personal digital assistant, who helps busy people get things done, even while at work. Cortana has powerful configuration options, specifically optimized for your business. By signing in with an Azure Active Directory (Azure AD) account, your employees can give Cortana access to their enterprise/work identity, while getting all the functionality Cortana provides to them outside of work.
|
|
||||||
|
|
||||||
Using Azure AD also means that you can remove an employee’s profile (for example, when an employee leaves your organization) while respecting Windows Information Protection (WIP) policies and ignoring enterprise content, such as emails, calendar items, and people lists that are marked as enterprise data.
|
|
||||||
|
|
||||||
For more info about Cortana at work, see [Cortana integration in your business or enterprise](/windows/configuration/cortana-at-work/cortana-at-work-overview)
|
|
||||||
|
|
||||||
## Microsoft Edge
|
|
||||||
|
|
||||||
iOS and Android versions of Edge are now available. For more information, see [Microsoft Edge Tips](https://microsoftedgetips.microsoft.com/en-us?source=firstrunwip).
|
|
||||||
|
|
||||||
Support in [Windows Defender Application Guard](#windows-defender-application-guard) is also improved.
|
|
||||||
|
|
||||||
#### Microsoft Edge Group Policies
|
|
||||||
|
|
||||||
We introduced new group policies and Modern Device Management settings to manage Microsoft Edge. The new policies include enabling and disabling full-screen mode, printing, favorites bar, and saving history; preventing certificate error overrides; configuring the Home button and startup options; setting the New Tab page and Home button URL, and managing extensions. Learn more about the [new Microsoft Edge policies](https://aka.ms/new-microsoft-edge-group-policies).
|
|
||||||
|
|
||||||
## Windows Update
|
## Windows Update
|
||||||
|
|
||||||
### Windows Update for Business
|
### Windows Update for Business
|
||||||
|
@ -69,6 +69,14 @@ You can choose which encryption algorithm to apply automatic BitLocker encryptio
|
|||||||
|
|
||||||
For example, you can choose the XTS-AES 256 encryption algorithm, and have it applied to devices that would normally encrypt themselves automatically with the default XTS-AES 128 algorithm during OOBE.
|
For example, you can choose the XTS-AES 256 encryption algorithm, and have it applied to devices that would normally encrypt themselves automatically with the default XTS-AES 128 algorithm during OOBE.
|
||||||
|
|
||||||
|
To achieve this:
|
||||||
|
|
||||||
|
1. Configure the [encryption method settings](https://docs.microsoft.com/intune/endpoint-protection-windows-10#windows-encryption) in the Windows 10 Endpoint Protection profile to the desired encryption algorithm.
|
||||||
|
2. [Assign the policy](https://docs.microsoft.com/intune/device-profile-assign) to your Autopilot device group.
|
||||||
|
- **IMPORTANT**: The encryption policy must be assigned to **devices** in the group, not users.
|
||||||
|
1. Enable the Autopilot [Enrollment Status Page](https://docs.microsoft.com/windows/deployment/windows-autopilot/enrollment-status) (ESP) for these devices. This is also important because if the ESP is not enabled, the policy will not apply when the device boots.
|
||||||
|
|
||||||
|
|
||||||
### Windows Defender Application Guard Improvements
|
### Windows Defender Application Guard Improvements
|
||||||
|
|
||||||
Windows Defender Application Guard (WDAG) introduced a new user interface inside **Windows Security** in this release. Standalone users can now install and configure their Windows Defender Application Guard settings in Windows Security without needing to change registry key settings.
|
Windows Defender Application Guard (WDAG) introduced a new user interface inside **Windows Security** in this release. Standalone users can now install and configure their Windows Defender Application Guard settings in Windows Security without needing to change registry key settings.
|
||||||
|
Reference in New Issue
Block a user