diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index 64e5ee645b..56172647cf 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -6,8 +6,8 @@ "redirect_document_id": true }, { -"source_path": "windows/devices/surface/surface-device-compatibility-with-windows-10-ltsb.md", -"redirect_url": "/windows/devices/surface/surface-device-compatibility-with-windows-10-ltsc", +"source_path": "devices/surface/surface-device-compatibility-with-windows-10-ltsb.md", +"redirect_url": "/devices/surface/surface-device-compatibility-with-windows-10-ltsc", "redirect_document_id": true }, { diff --git a/devices/surface/TOC.md b/devices/surface/TOC.md index 27d7b79e79..5dd7130ea6 100644 --- a/devices/surface/TOC.md +++ b/devices/surface/TOC.md @@ -1,6 +1,6 @@ # [Surface](index.md) ## [Deploy Surface devices](deploy.md) -### [Surface device compatibility with Windows 10 Long-Term Servicing Branch](surface-device-compatibility-with-windows-10-ltsb.md) +### [Surface device compatibility with Windows 10 Long-Term Servicing Branch](surface-device-compatibility-with-windows-10-ltsc.md) #### [Long-Term Servicing Branch for Surface devices](ltsb-for-surface.md) ### [Deploy Windows 10 to Surface devices with MDT](deploy-windows-10-to-surface-devices-with-mdt.md) ### [Upgrade Surface devices to Windows 10 with MDT](upgrade-surface-devices-to-windows-10-with-mdt.md) diff --git a/devices/surface/change-history-for-surface.md b/devices/surface/change-history-for-surface.md index 9aa9194b2a..a18646b616 100644 --- a/devices/surface/change-history-for-surface.md +++ b/devices/surface/change-history-for-surface.md @@ -57,7 +57,7 @@ New or changed topic | Description |New or changed topic | Description | | --- | --- | -|[Surface device compatibility with Windows 10 Long-Term Servicing Branch](surface-device-compatibility-with-windows-10-ltsb.md) | New (supersedes [Long-Term Servicing Branch for Surface devices](ltsb-for-surface.md))| +|[Surface device compatibility with Windows 10 Long-Term Servicing Branch](surface-device-compatibility-with-windows-10-ltsc.md) | New (supersedes [Long-Term Servicing Branch for Surface devices](ltsb-for-surface.md))| ## January 2017 diff --git a/devices/surface/deploy.md b/devices/surface/deploy.md index a05b2ce399..d76f67bec8 100644 --- a/devices/surface/deploy.md +++ b/devices/surface/deploy.md @@ -17,7 +17,7 @@ Get deployment guidance for your Surface devices including information about MDT | Topic | Description | | --- | --- | -| [Surface device compatibility with Windows 10 Long-Term Servicing Branch](surface-device-compatibility-with-windows-10-ltsb.md) | Find out about compatibility and limitations of Surface devices running Windows 10 Enterprise LTSB edition. | +| [Surface device compatibility with Windows 10 Long-Term Servicing Channel](surface-device-compatibility-with-windows-10-ltsc.md) | Find out about compatibility and limitations of Surface devices running Windows 10 Enterprise LTSB edition. | | [Deploy Windows 10 to Surface devices with MDT](deploy-windows-10-to-surface-devices-with-mdt.md) | Walk through the recommended process of how to deploy Windows 10 to your Surface devices with the Microsoft Deployment Toolkit.| | [Upgrade Surface devices to Windows 10 with MDT](upgrade-surface-devices-to-windows-10-with-mdt.md)| Find out how to perform a Windows 10 upgrade deployment to your Surface devices. | | [Customize the OOBE for Surface deployments](customize-the-oobe-for-surface-deployments.md)| Walk through the process of customizing the Surface out-of-box experience for end users in your organization.| diff --git a/devices/surface/ltsb-for-surface.md b/devices/surface/ltsb-for-surface.md index fdb52daf8f..a4c9d85f83 100644 --- a/devices/surface/ltsb-for-surface.md +++ b/devices/surface/ltsb-for-surface.md @@ -12,7 +12,7 @@ ms.date: 04/25/2017 # Long-Term Servicing Branch (LTSB) for Surface devices >[!WARNING] ->For updated information on this topic, see [Surface device compatibility with Windows 10 Long-Term Servicing Branch](surface-device-compatibility-with-windows-10-ltsb.md). For additional information on this update, see the [Documentation Updates for Surface and Windows 10 LTSB Compatibility](https://blogs.technet.microsoft.com/surface/2017/04/11/documentation-updates-for-surface-and-windows-10-ltsb-compatibility) post on the Surface Blog for IT Pros. +>For updated information on this topic, see [Surface device compatibility with Windows 10 Long-Term Servicing Channel](surface-device-compatibility-with-windows-10-ltsc.md). For additional information on this update, see the [Documentation Updates for Surface and Windows 10 LTSB Compatibility](https://blogs.technet.microsoft.com/surface/2017/04/11/documentation-updates-for-surface-and-windows-10-ltsb-compatibility) post on the Surface Blog for IT Pros. General-purpose Surface devices running Long-Term Servicing Branch (LTSB) are not supported. As a general guideline, if a Surface device runs productivity software, such as Microsoft Office, it is a general-purpose device that does not qualify for LTSB and should instead run Current Branch (CB) or Current Branch for Business (CBB). diff --git a/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md b/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md index 127887c17e..76543bd50f 100644 --- a/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md +++ b/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md @@ -10,7 +10,7 @@ ms.topic: article ms.prod: w10 ms.technology: windows author: nickbrower -ms.date: 12/05/2017 +ms.date: 01/08/2018 --- # What's new in MDM enrollment and management @@ -26,6 +26,7 @@ For details about Microsoft mobile device management protocols for Windows 10 s - [What's new in Windows 10, version 1607](#whatsnew1607) - [What's new in Windows 10, version 1703](#whatsnew10) - [What's new in Windows 10, version 1709](#whatsnew1709) +- [Change history in MDM documentation](#change-history-in-mdm-documentation) - [Breaking changes and known issues](#breaking-changes-and-known-issues) - [Get command inside an atomic command is not supported](#getcommand) - [Notification channel URI not preserved during upgrade from Windows 8.1 to Windows 10](#notification) @@ -44,7 +45,6 @@ For details about Microsoft mobile device management protocols for Windows 10 s - [User provisioning failure in Azure Active Directory joined Windows 10 PC](#userprovisioning) - [Requirements to note for VPN certificates also used for Kerberos Authentication](#kerberos) - [Device management agent for the push-button reset is not working](#pushbuttonreset) -- [Change history in MDM documentation](#change-history-in-mdm-documentation) - [FAQ](#faq) ## What's new in Windows 10, version 1511 @@ -1382,6 +1382,122 @@ The DM agent for [push-button reset](https://msdn.microsoft.com/windows/hardware ## Change history in MDM documentation +### January 2018 + +
New or updated topic | +Description | +
---|---|
[Policy CSP](policy-configuration-service-provider.md) | +Added the following new policies for Windows 10, next major update: +
|
New or updated topic | -Description | -
---|---|
[VPNv2 CSP](vpnv2-csp.md) | -Added DeviceTunnel profile in Windows 10, version 1709. - |
[BitLocker CSP](bitlocker-csp.md) | -Added the following statements:.
-
|
[Policy CSP](policy-configuration-service-provider.md) | -
- Added the following new policies for Windows 10, version 1709: -
Experience/AllowFindMyDevice - updated the description to include active digitizers. - |
[EnterpriseDesktopAppManagement CSP](enterprisedesktopappmanagement-csp.md) | -Added the following statement to [MSI/ProductID/DownloadInstall](enterprisedesktopappmanagement-csp.md#msi-productid-downloadinstall):
-
|
[EnterpriseAssignedAccess CSP](enterpriseassignedaccess-csp.md) | -Added the following information about the settings pages in AssigneAccessXML:
-
|
[DeviceStatus CSP](devicestatus-csp.md) | -Added the following settings in Windows 10, version 1709: -
|
[AssignedAccess CSP](assignedaccess-csp.md) | -Here are the changes in Windows 10, version 1709. -
Starting in Windows 10, version 1709, AssignedAccess CSP is supported in Windows 10 Pro. - |
[SurfaceHub CSP](surfacehub-csp.md) | -Changed PasswordRotationPeriod to PasswordRotationEnabled. - |
New or updated topic | -Description | -
---|---|
[Win32 and Desktop Bridge app policy configuration](win32-and-centennial-app-policy-configuration.md) | -Added a list of registry locations that ingested policies are allowed to write to. | -
[Firewall CSP](firewall-csp.md) | -Added the following nodes:
-
|
[TPMPolicy CSP](tpmpolicy-csp.md) | -New CSP added in Windows 10, version 1703. | -
[Policy CSP](policy-configuration-service-provider.md) | -
- Added the following new policies for Windows 10, version 1703: -
Added the following new policies for Windows 10, version 1709: -
EnterpriseCloudPrint/DiscoveryMaxPrinterLimit is only supported in Windows 10 Mobile and Mobile Enterprise. - |
[WindowsAdvancedThreatProtection CSP](windowsadvancedthreatprotection-csp.md) | -Updated the CSP in Windows 10, version 1709. Added the following settings:
-
|
[WindowsDefenderApplicationGuard CSP](windowsdefenderapplicationguard-csp.md) | -New CSP added in Windows 10, version 1709. Also added the DDF topic [WindowsDefenderApplicationGuard DDF file](windowsdefenderapplicationguard-ddf-file.md). | -
[DynamicManagement CSP](dynamicmanagement-csp.md) | -The DynamicManagement CSP is not supported in Windows 10 Mobile and Mobile Enterprise. The table of SKU information in the [Configuration service provider reference](configuration-service-provider-reference.md) was updated. | -
[CM_ProxyEntries CSP](cm-proxyentries-csp.md) and [CMPolicy CSP](cmpolicy-csp.md) | -In Windows 10, version 1709, support for desktop SKUs were added to these CSPs. The table of SKU information in the [Configuration service provider reference](configuration-service-provider-reference.md) was updated. | -
New or updated topic | -Description | -
---|---|
[Policy CSP](policy-configuration-service-provider.md) | -
- Added the following new policies for Windows 10, version 1703: -
Starting in Windows 10, version 1703, the maximum value of Update/DeferFeatureUpdatesPeriodInDays has been increased from 180 days, to 365 days. -Added a statment that the following policies must target ./User. -
|
[Understanding ADMX-backed policies](understanding-admx-backed-policies.md) | -Added a section describing SyncML examples of various ADMX elements. - |
[BitLocker CSP](bitlocker-csp.md) | -
- Added the following setting: -
Note that SystemDrivesMinimumPINLength is 6 digits instead of 4. - |
[Reporting CSP](reporting-csp.md) | -Added new settings in Windows 10, version 1703. -
|
[Connecting your Windows 10-based device to work using a deep link](mdm-enrollment-of-windows-devices.md#connecting-your-windows-10-based-device-to-work-using-a-deep-link) | -Added following deep link parameters to the table: -
|
[Firewall CSP](firewall-csp.md) | -Added new CSP in Windows 10, version 1709. - |
MDM support for Windows 10 S | -Updated the following topics to indicate MDM support in Windows 10 S. -
|
New or updated topic | -Description | -
---|---|
[Policy CSP](policy-configuration-service-provider.md) | -Added the following new policies for Windows 10, version 1703: -
DeviceLock/EnforceLockScreenAndLogonImage is not supported in Windows 10 Pro edition. - |
[DMSessionActions CSP](sharedpc-csp.md) | -Added new CSP for Windows 10, version 1703. - |
[CertificateStore CSP](certificatestore-csp.md) |
-Updated in Windows 10, version 1703. Added the following setting: -
|
-
[ClientCertificateInstall CSP](clientcertificateinstall-csp.md) |
-Updated in Windows 10, version 1703. Added the following setting: -
|
-
[DMAcc CSP](dmacc-csp.md) |
-Updated in Windows 10, version 1703. Added the following setting: -
|
-
[DMClient CSP](dmclient-csp.md) |
-Updated in Windows 10, version 1703. Added the following nodes and settings: -
|
-
[SharedPC CSP](dmsessionactions-csp.md) | -Added new settings in Windows 10, version 1703. -
The default value for SetEduPolicies changed to false. The default value for SleepTimeout changed to 300. - |
[RemoteLock CSP](remotelock-csp.md) | -Added following setting: -
|
[NodeCache CSP](nodecache-csp.md) | -Added following settings: -
|
[Download all the DDF files for Windows 10, version 1703](http://download.microsoft.com/download/C/7/C/C7C94663-44CF-4221-ABCA-BC895F42B6C2/Windows10_1703_DDF_download.zip) | -Added a zip file containing the DDF XML files of the CSPs. The link to the download is available in the DDF topics of various CSPs. - |
[RemoteWipe CSP](remotewipe-csp.md) | -Added new setting in Windows 10, version 1703. -
|
[EnterpriseDesktopAppManagement CSP](enterprisedesktopappmanagement-csp.md) | -Added new setting in the March service release of Windows 10, version 1607. -
|
[MDM Bridge WMI Provider](https://msdnstage.redmond.corp.microsoft.com/en-us/library/windows/desktop/dn905224(v=vs.85).aspx) | -Updated for Windows 10, version 1703. Added new classes and properties. - | [Deploy and configure App-V apps using MDM](appv-deploy-and-config.md) | -Added a new topic describing how to deploy and configure App-V apps using MDM. - |
-
-
New or updated topic | -Description | -
---|---|
[Policy CSP](policy-configuration-service-provider.md) | -Added the following new policies for Windows 10, version 1703: -
For Windows 10, version 1703, added the ConfigOperations/ADMXInstall node and setting, which is used to ingest ADMX files. - |
-
[DeviceLock/DevicePasswordEnabled](policy-configuration-service-provider.md#devicelock-devicepasswordenabled) in Policy CSP | -Added the following note: -**DevicePasswordEnabled** should not be set to Enabled (0) when WMI is used to set the EAS DeviceLock policies given that it is Enabled by default in Policy CSP for back compat with Windows 8.x. If **DevicePasswordEnabled** is set to Enabled(0) then Policy CSP will return an error stating that **DevicePasswordEnabled** already exists. Windows 8.x did not support DevicePassword policy. When disabling **DevicePasswordEnabled** (1) then this should be the only policy set from the DeviceLock group of policies listed below: -
|
-
[Personalization CSP](personalization-csp.md) | -Added new CSP for Windows 10, version 1703. |
-
[EnterpriseAppVManagement CSP](enterpriseappvmanagement-csp.md) | -Added new CSP for Windows 10, version 1703. |
-
[HealthAttestation CSP](healthattestation-csp.md) | -Added the following settings:. -
|
-
[SurfaceHub CSP](surfacehub-csp.md) |
-Updated in Windows 10, version 1703. Added the following nodes and settings: -
|
-
[NetworkQoSPolicy CSP](networkqospolicy-csp.md) | -Added new CSP for Windows 10, version 1703. |
-
[EnterpriseAPN CSP](enterpriseapn-csp.md) | -Added the following setting: -
|
-
[WindowsLicensing CSP](windowslicensing-csp.md) |
-Added the following setting for Windows 10, version 1703: -
Added the following new node and settings in Windows 10, version 1607, but not previously documented: -
|
-
[EnterpriseDataProtection CSP](enterprisedataprotection-csp.md) | -Added the following settings: -
|
-
[WindowsAdvancedThreatProtection CSP](windowsadvancedthreatprotection-csp.md) | -Updated in Windows 10, version 1703. Added the following setting: -
|
-
New or updated topic | -Description | -
---|---|
[SecureAssessment CSP](secureassessment-csp.md) | -Updated the following setting names: -
|
[EnterpriseDataProtection CSP](enterprisedataprotection-csp.md) | -Added the following statement to [Settings/EDPShowIcons](enterprisedataprotection-csp.md#settings-edpshowicons):
|
[Policy CSP](policy-configuration-service-provider.md) | -Added the following new policies for Windows 10, version 1703: -
Starting in Windows 10, version 1703, Update/UpdateServiceUrl is not supported in Windows 10 Mobile Enteprise and IoT Enterprise -Starting in Windows 10, version 1703, in Browser/HomePages you can use the "<about:blank>" value if you don’t want to send traffic to Microsoft. -Starting in Windows 10, version 1703, Start/StartLayout can now be set on a per-device basis in addition to the pre-existing per-user basis. - |
-
[NetworkProxy CSP](networkproxy-csp.md) | -Added new CSP for Windows 10, version 1703. |
-
[BitLocker CSP](bitlocker-csp.md) | -Added new CSP for Windows 10, version 1703. |
-
[EnterpriseDataProtection CSP](enterprisedataprotection-csp.md) | -Starting in Windows 10, version 1703, AllowUserDecryption is no longer supported. |
-
[DynamicManagement CSP](dynamicmanagement-csp.md) | -Added new CSP for Windows 10, version 1703. |
-
[Implement server-side support for mobile application management on Windows](implement-server-side-mobile-application-management.md) | -New mobile application management (MAM) support added in Windows 10, version 1703. |
-
[PassportForWork CSP](passportforwork-csp.md) |
-Updated in Windows 10, version 1703. Added the following new node and settings: -
|
-
[Office CSP](office-csp.md) | -Added new CSP for Windows 10, version 1703. |
-
New or updated topic | -Description | -
---|---|
[Reboot CSP](reboot-csp.md) | -RebootNow triggers a reboot within 5 minutes to allow the user to wrap up any active work. Also updated the Note in RebootNow. - |
-
[Device update management](device-update-management.md) | -Updated the following section: -
|
-
[SecureAssessment CSP](secureassessment-csp.md) | -Updated in Windows 10, version 1703. Added the following settings -
|
-
[DevDetail CSP](devdetail-csp.md) | -Updated in Windows 10, version 1703. Added the following setting: DeviceHardwareData |
-
[Messaging CSP](messaging-csp.md) | -Added new CSP for Windows 10, version 1703. This CSP is only supported in Windows 10 Mobile and Mobile Enteprise editions. - |
-
[Policy CSP](policy-configuration-service-provider.md) | -Added the following new policies for Windows 10, version 1703: -
Added the following new policy for the January service release of Windows 10, version 1607: Update/UpdateServiceUrlAlternate -Removed TextInput/AllowLinguisticDataCollection from Policy CSP in Windows 10 version 1703. - |
[CleanPC CSP](cleanpc-csp.md) | -Added new CSP for Windows 10, version 1703. |
-
[DeveloperSetup CSP](developersetup-csp.md) | -Added new CSP for Windows 10, version 1703. |
-
Added a download of Windows 10 version 1607 DDF files | -You can download the Windows 10 version 1607 DDF files from [here](http://download.microsoft.com/download/2/3/E/23E27D6B-6E23-4833-B143-915EDA3BDD44/Windows10_1607_DDF.zip). - |
-
[DeviceStatus CSP](devicestatus-csp.md) | -Added the following values for DeviceStatus/NetworkIdentifiers/MacAddress/Type setting: -
|
-
New or updated topic | -Description | -
---|---|
[Update CSP](update-csp.md) | -Added the following nodes: -
|
-
[AppLocker CSP](applocker-csp.md) | -Added information about exempt applications list to the EnterpriseDataProtection setting. - |
[EnterpriseDataProtection CSP](enterprisedataprotection-csp.md) | -To Settings/RequireProtectionUnderLockConfig, added supported values. - |
[CM_CellularEntries CSP](cm-cellularentries-csp.md) | -To PurposeGroups setting, added the following values Windows 10, version 1709: -
|
[CellularSettings CSP](cellularsettings-csp.md) [CM_CellularEntries CSP](cm-cellularentries-csp.md) [EnterpriseAPN CSP](enterpriseapn-csp.md) |
-In the Windows 10, version 1709, support was added for Windows 10 Home, Pro, Enterprise, and Education editions. - |
Updated the DDF topics. | -The following DDF topics were updated:
-
|
[Reporting CSP](reporting-csp.md) | -Reporting/SecurityAuditing setting is not supported in Windows 10, version 1607 in the desktop editions. - |
New or updated topic | -Description | -
---|---|
[EnterpriseAPN CSP](enterpriseapn-csp.md) | -The EnterpriseAPN configuration service provider (CSP) is not supported in Windows 10 for desktop editions (Home, Pro, Enterprise, and Education), versions 1511 and 1607. - |
-
[Defender CSP](defender-csp.md) | -Added the following values for Defender/Scan setting: -
|
-
[EnterpriseDataProtection CSP](enterprisedataprotection-csp.md) | -Added data recovery agent (DRA) information to Settings/DataRecoveryCertificate. - |
-
[Disconnecting from the management infrastructure (unenrollment)](disconnecting-from-mdm-unenrollment.md) | -Added information about unenrollment from Azure Active Directory Join. - |
-
[Policy CSP](policy-configuration-service-provider.md) | -Updated the description of the following policies.
|
-
New or updated topic | -Description | -
---|---|
[CM_ProxyEntries CSP](cm-proxyentries-csp.md) | -Support for OMA DM was added in Windows 10, version 1607 - |
[AppLocker CSP](applocker-csp.md) | -[Recommended deny list for Windows Information Protection](applocker-csp.md#recommended-deny-list-for-windows-information-protection) - example for Windows 10, version 1607 that denies known unenlightened Microsoft apps from accessing enterprise data as an allowed app. This ensures an administrator does not accidentally make these apps Windows Information Protection allowed, and avoid known compatibility issues related to automatic file encryption with these applications. - - |
-
New or updated topic | -Description | -
---|---|
[Policy CSP](policy-configuration-service-provider.md) | -Updated the most restricted values for the following policies: -
|
-
New or updated topic | -Description | -
---|---|
WindowsTeam CSP |
-Deleted the WindowsTeam CSP topic. You should use [SurfaceHub](surfacehub-csp.md) instead. |
-
[Policy CSP](policy-configuration-service-provider.md) | -Added the following policies: -
|
-
New or updated topic | -Description | -
---|---|
[Policy CSP](policy-configuration-service-provider.md) | -Updated the following policy: -
|
-
New or updated topic | -Description | -
---|---|
[AppLocker CSP](applocker-csp.md) | -Added the following note the the list of [Inbox apps and components](applocker-csp.md#inboxappsandcomponents): -
-Note This list identifies system apps that ship as part of Windows that you can add to your AppLocker policy to ensure proper functioning of the operating system. If you decide to block some of these apps, we recommend a thorough testing before deploying to your production environment. Failure to do so may result in unexpected failures and can significantly degrade the user experience.
-
- |
-
[ComputerName](https://msdn.microsoft.com/library/windows/hardware/mt188590) in Windows Provisioning settings reference |
-ComputerName does not support asterisk (*) and does not support empty string. |
-
[Policy CSP](policy-configuration-service-provider.md) | -Updated the supported values for [Update/BranchReadinessLevel](policy-configuration-service-provider.md#update-branchreadinesslevel) |
-
[Device update management](device-update-management.md) | -Updated the following section: -
|
-
New or updated topic | -Description | -
---|---|
[Policy CSP](policy-configuration-service-provider.md) | -Added the following statement to Update/DeferUpdatePeriod policy: -In Windows 10 Mobile Enterprise version 1511 devices set to automatic updates, for DeferUpdatePeriod to work, you must set the following: -
Added new policy Experience/AllowThirdPartySuggestionsInWindowsSpotlight in Windows 10, version 1607. |
-
New or updated topic | -Description | -
---|---|
[EnterpriseModernAppManagement CSP](enterprisemodernappmanagement-csp.md) | -Updated the names for the following settings: -
|
-
[Policy CSP](policy-configuration-service-provider.md) | -Updated the following policy description: - -
|
-
[OMA DM protocol support](oma-dm-protocol-support.md) | -Updated the following description: -
|
-
[VPNv2 CSP](vpnv2-csp.md) | -Updated the following description: -
|
-
[MDM Bridge WMI Provider](https://msdn.microsoft.com/library/windows/hardware/dn905224) | -Replaced the descriptions for each class member with links to the corresponding node in the CSP topic. The CSP topics contain the most up-to-date information. |
-
New or updated topic | -Description | -
---|---|
[Policy CSP](policy-configuration-service-provider.md)
- [PolicyManager CSP](policymanager-csp.md) |
-Added the following note: -
|
-
[PassportForWork CSP](passportforwork-csp.md) | -Added the following note: -
-Important Starting with Windows 10, version 1607 all devices only have one PIN associated with Windows Hello for Business. This means that any PIN on a device will be subject to the policies specified in the PassportForWork CSP. The values specified take precedence over any complexity rules set via Exchange ActiveSync (EAS) or the DeviceLock CSP.
-
- |
-
[ProfileXML XSD](vpnv2-profile-xsd.md) | -Updated the [Native profile example](vpnv2-profile-xsd.md#native-profile-example) example. |
-
[Policy CSP](policy-configuration-service-provider.md)
- [Device update management](device-update-management.md) |
-The following policies are not supported in Windows 10 Mobile Enterprise: -
-Note Since these policies are not blocked, you will not get a failure message when you use them to configure a Windows 10 Mobile Enterprise device. However, the policies will not take effect.
-
-Added additional information about update policies supported for Windows Update for Business in [Changes in Windows 10, version 1607 for update management](device-update-management.md#windows10version1607forupdatemanagement). |
-
[DevDetail CSP](devdetail-csp.md) | -In Ext/Microsoft/DeviceName node, the Replace operation is only supported in Windows 10 Mobile, and not supported in the desktop. |
-
New or updated topic | -Description | -
---|---|
[Policy DDF file](policy-ddf-file.md) | -Updated version for Windows 10, version 1607 |
-
[MDM enrollment of Windows devices](mdm-enrollment-of-windows-devices.md) | -Updated the section about enrolling in MDM on a desktop. Added a new section for enrolling in MDM on a phone. |
-
New or updated topic | -Description | -
---|---|
[CertificateStore CSP](certificatestore-csp.md)
- [CertificateStore DDF file](certificatestore-ddf-file.md) |
-Added the following new settings in Windows 10, version 1607: -
|
-
New or updated topic | -Description | -
---|---|
[Bulk enrollment](bulk-enrollment-using-windows-provisioning-tool.md) | -Added new section: -
|
-
[Azure Active Directory integration with MDM](azure-active-directory-integration-with-mdm.md) | -Added a link to MDM enrollment templates and CSS files: -
|
-
New or updated topic | -Description | -
---|---|
[OMA DM protocol support](oma-dm-protocol-support.md) | -Added a table of common SyncML response codes that occur during OMA DM sessions. |
-
[Mobile device enrollment](mobile-device-enrollment.md) | -Updated the following section: -
|
-
[SUPL CSP](supl-csp.md) | -LocMasterSwitchDependencyNII setting is not deprecated. Removed the note that it's deprecated in Windows 10. |
-
[Push notification support for device management](push-notification-windows-mdm.md) | -Added the following section: -
|
-
[RemoteWipe CSP](remotewipe-csp.md) | -Updated [The Remote Wipe Process](remotewipe-csp.md#the-remote-wipe-process) section. Added the following note: -
-Note On the desktop, the remote wipe effectively performs a factory reset and the PC does not retain any information about the command once the wipe completes. Any response from the device about the actual status or result of the command may be inconsistent and unreliable because the MDM information has been removed.
-
- |
-
[Bulk enrollment](bulk-enrollment-using-windows-provisioning-tool.md) | -Added new step-by-step guide for creating and applying provisioning packages. |
-
Home | -Pro | -Business | -Enterprise | -Education | -Mobile | -Mobile Enterprise | -
---|---|---|---|---|---|---|
![]() |
- ![]() |
- ![]() |
- ![]() |
- ![]() |
- ![]() |
- ![]() |
-
Home | +Pro | +Business | +Enterprise | +Education | +Mobile | +Mobile Enterprise | +
---|---|---|---|---|---|---|
![]() |
+ ![]() |
+ ![]() |
+ ![]() |
+ ![]() |
+ ![]() |
+ ![]() |
+
Home | +Pro | +Business | +Enterprise | +Education | +
---|---|---|---|---|
![]() |
+ ![]() |
+ ![]() |
+ ![]() |
+ ![]() |
+
Mitigation + | |||||||||||||||||||||||||||||||||||||||
-OS requirements:
- +[Analyze log files](#analyze-log-files) in order to determine the files or registry entires that are blocking data migration. -
->[!NOTE] ->There is no pre-existing OS in the Windows AutoPilot or bare metal scenarios, so apps and settings are not migrated. In all other scenarios the existing apps and user settings are typically migrated to the new operating system. -## Windows AutoPilot +>[!IMPORTANT] +>The Windows AutoPilot and Subscription Activation scenarios require that the beginning OS be Windows 10 version 1703, or later. +>Except for clean install scenarios such as traditional bare metal and Windows AutoPilot, all the methods described can optionally migrate apps and settings to the new OS. + +## Modern deployment methods + +Modern deployment methods embrace both traditional on-prem and cloud services to deliver a simple, streamlined, cost effective deployment experience. + +### Windows AutoPilot Windows AutoPilot is a new suite of capabilities designed to simplify and modernize the deployment and management of new Windows 10 PCs. Windows AutoPilot enables IT professionals to customize the Out of Box Experience (OOBE) for Windows 10 PCs and provide end users with a fully configured new Windows 10 device after just a few clicks. There are no images to deploy, no drivers to inject, and no infrastructure to manage. Users can go through the deployment process independently, without the need consult their IT administrator. For more information about Windows AutoPilot, see [Overview of Windows AutoPilot](https://docs.microsoft.com/en-us/windows/deployment/windows-10-auto-pilot) and [Modernizing Windows deployment with Windows AutoPilot](https://blogs.technet.microsoft.com/windowsitpro/2017/06/29/modernizing-windows-deployment-with-windows-autopilot/). -## Windows 10 Subscription Activation - -Windows 10 Subscription Activation is a modern deployment method that enables you to change the SKU from Pro to Enterprise with no keys and no reboots. For more information about Subscription Activation, see [Windows 10 Subscription Activation](https://docs.microsoft.com/en-us/windows/deployment/windows-10-enterprise-subscription-activation). - -## In-place upgrade +### In-place upgrade For existing computers running Windows 7, Windows 8, or Windows 8.1, the recommended path for organizations deploying Windows 10 leverages the Windows installation program (Setup.exe) to perform an in-place upgrade, which automatically preserves all data, settings, applications, and drivers from the existing operating system version. This requires the least IT effort, because there is no need for any complex deployment infrastructure. @@ -188,26 +188,27 @@ There are some situations where you cannot use in-place upgrade; in these situat - Updating existing images. While it might be tempting to try to upgrade existing Windows 7, Windows 8, or Windows 8.1 images to Windows 10 by installing the old image, upgrading it, and then recapturing the new Windows 10 image, this is not supported – preparing an upgraded OS for imaging (using Sysprep.exe) is not supported and will not work when it detects the upgraded OS. - Dual-boot and multi-boot systems. The upgrade process is designed for devices running a single OS; if using dual-boot or multi-boot systems with multiple operating systems (not leveraging virtual machines for the second and subsequent operating systems), additional care should be taken. + ## Dynamic provisioning For new PCs, organizations have historically replaced the version of Windows included on the device with their own custom Windows image, because this was often faster and easier than leveraging the preinstalled version. But this is an added expense due to the time and effort required. With the new dynamic provisioning capabilities and tools provided with Windows 10, it is now possible to avoid this. The goal of dynamic provisioning is to take a new PC out of the box, turn it on, and transform it into a productive organization device, with minimal time and effort. The types of transformations that are available include: -- Changing the Windows edition with a single reboot. For organizations that have Software Assurance for Windows, it is easy to change a device from Windows 10 Pro to Windows 10 Enterprise, just by specifying an appropriate product or setup key. When the device restarts, all of the Windows 10 Enterprise features will be enabled. +### Windows 10 Subscription Activation -- Configuring the device with VPN and Wi-Fi connections that may be needed to gain access to organization resources. -- Installation of additional apps needed for organization functions. -- Configuration of common Windows settings to ensure compliance with organization policies. -- Enrollment of the device in a mobile device management (MDM) solution, such as Microsoft Intune. +Windows 10 Subscription Activation is a modern deployment method that enables you to change the SKU from Pro to Enterprise with no keys and no reboots. For more information about Subscription Activation, see [Windows 10 Subscription Activation](https://docs.microsoft.com/en-us/windows/deployment/windows-10-enterprise-subscription-activation). -There are two primary dynamic provisioning scenarios: -- **Azure Active Directory (Azure AD) Join with automatic mobile device management (MDM) enrollment.** In this scenario, the organization member just needs to provide their work or school user ID and password; the device can then be automatically joined to Azure Active Directory and enrolled in a mobile device management (MDM) solution with no additional user interaction. Once done, the MDM solution can finish configuring the device as needed. +### Azure Active Directory (AAD) join with automatic mobile device management (MDM) enrollment -- **Provisioning package configuration.** Using the [Windows Imaging and Configuration Designer (ICD)](https://go.microsoft.com/fwlink/p/?LinkId=619358), IT administrators can create a self-contained package that contains all of the configuration, settings, and apps that need to be applied to a machine. These packages can then be deployed to new PCs through a variety of means, typically by IT professionals. For more information, see [Configure devices without MDM](/windows/configuration/configure-devices-without-mdm). +In this scenario, the organization member just needs to provide their work or school user ID and password; the device can then be automatically joined to Azure Active Directory and enrolled in a mobile device management (MDM) solution with no additional user interaction. Once done, the MDM solution can finish configuring the device as needed. For more information, see [Azure Active Directory integration with MDM](https://docs.microsoft.com/en-us/windows/client-management/mdm/azure-active-directory-integration-with-mdm). -Either way, these scenarios can be used to enable “choose your own device” (CYOD) programs where the organization’s users can pick their own PC and not be restricted to a small list of approved or certified models (programs that are difficult to implement using traditional deployment scenarios). +### Provisioning package configuration + +Using the [Windows Imaging and Configuration Designer (ICD)](https://go.microsoft.com/fwlink/p/?LinkId=619358), IT administrators can create a self-contained package that contains all of the configuration, settings, and apps that need to be applied to a machine. These packages can then be deployed to new PCs through a variety of means, typically by IT professionals. For more information, see [Configure devices without MDM](/windows/configuration/configure-devices-without-mdm). + +These scenarios can be used to enable “choose your own device” (CYOD) programs where the organization’s users can pick their own PC and not be restricted to a small list of approved or certified models (programs that are difficult to implement using traditional deployment scenarios). While the initial Windows 10 release includes a variety of provisioning settings and deployment mechanisms, these will continue to be enhanced and extended based on feedback from organizations. As with all Windows features, organizations can submit suggestions for additional features through the Windows Feedback app or through their Microsoft Support contacts. @@ -226,6 +227,7 @@ The traditional deployment scenario can be divided into different sub-scenarios. - **Computer replace.** A replacement of the old machine with a new machine (with user-state migration and an optional full WIM image backup). ### New computer + This scenario occurs when you have a blank machine you need to deploy, or an existing machine you want to wipe and redeploy without needing to preserve any existing data. The setup starts from a boot media, using CD, USB, ISO, or Pre-Boot Execution Environment (PXE). You can also generate a full offline media that includes all the files needed for a client deployment, allowing you to deploy without having to connect to a central deployment share. The target can be a physical computer, a virtual machine, or a Virtual Hard Disk (VHD) running on a physical computer (boot from VHD). The deployment process for the new machine scenario is as follows: @@ -241,6 +243,7 @@ The deployment process for the new machine scenario is as follows: After taking these steps, the computer is ready for use. ### Computer refresh + A refresh is sometimes called wipe-and-load. The process is normally initiated in the running operating system. User data and settings are backed up and restored later as part of the deployment process. The target can be the same as for the new computer scenario. The deployment process for the wipe-and-load scenario is as follows: @@ -260,6 +263,7 @@ The deployment process for the wipe-and-load scenario is as follows: After taking these steps, the machine is ready for use. ### Computer replace + A computer replace is similar to the refresh scenario. However, since we are replacing the machine, we divide this scenario into two main tasks: backup of the old client and bare-metal deployment of the new client. As with the refresh scenario, user data and settings are backed up and restored. The deployment process for the replace scenario is as follows: @@ -271,6 +275,7 @@ The deployment process for the replace scenario is as follows: **Note** In some situations, you can use the replace scenario even if the target is the same machine. For example, you can use replace if you want to modify the disk layout from the master boot record (MBR) to the GUID partition table (GPT), which will allow you to take advantage of the Unified Extensible Firmware Interface (UEFI) functionality. You can also use replace if the disk needs to be repartitioned since user data needs to be transferred off the disk. ## Related topics + - [Upgrade to Windows 10 with the Microsoft Deployment Toolkit](upgrade/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md) - [Upgrade to Windows 10 with System Center Configuration Manager](upgrade/upgrade-to-windows-10-with-system-center-configuraton-manager.md) - [Deploy Windows 10 with System Center 2012 R2 Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=620230) |