mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 19:03:46 +00:00
Merge branch 'master' of https://github.com/Microsoft/win-cpub-itpro-docs into maricia-10027661
This commit is contained in:
Maricia Alforque
@ -44,7 +44,7 @@ This diagram shows the correct pinout used for an RJ-11 (6P6C) to DB9 cable.
|
||||
|
||||
Room control systems use common meeting-room scenarios for commands. Commands originate from the room control system, and are communicated over a serial connection to a Surface Hub. Commands are ASCII based, and the Surface Hub will acknowledge when state changes occur.
|
||||
|
||||
The following command modifiers are available. Commands terminate with a new line character (/n). Responses can come at any time in response to state changes not triggered directly by a management port command.
|
||||
The following command modifiers are available. Commands terminate with a new line character (\n). Responses can come at any time in response to state changes not triggered directly by a management port command.
|
||||
|
||||
| Modifier | Result |
|
||||
| --- | --- |
|
||||
|
||||
@ -44,7 +44,7 @@ author: CelesteDG
|
||||
<p><b>[Deploy Windows 10 in a school district](deploy-windows-10-in-a-school-district.md)</b><br />Get step-by-step guidance on how to deploy Windows 10 to PCs and devices across a school district.</p>
|
||||
<p><b><a href="https://technet.microsoft.com/en-us/windows/mt574244" target="_blank">Try it out: Windows 10 deployment (for education)</a></b><br />Learn how to upgrade devices running the Windows 7 operating system to Windows 10 Anniversary Update, and how to manage devices, apps, and users in Windows 10 Anniversary Update.<br /><br />For the best experience, use this guide in tandem with the <a href="https://vlabs.holsystems.com/vlabs/technet?eng=VLabs&auth=none&src=vlabs&altadd=true&labid=20949&lod=true" target="_blank">TechNet Virtual Lab: IT Pro Try-It-Out</a>.</p>
|
||||
|
||||
###  Switch
|
||||
##  Switch
|
||||
|
||||
<p><b>[Switch to Windows 10 Pro Education from Windows 10 Pro or Windows 10 S](switch-to-pro-education.md)</b><br />If you have an education tenant and use Windows 10 Pro or Windows 10 S in your schools, find out how you can opt-in to a free switch to Windows 10 Pro Education.</p>
|
||||
|
||||
|
||||
@ -70,7 +70,7 @@ To make this as seamless as possible, in your Azure AD tenant:
|
||||
|
||||
|
||||
|
||||
- Clear your Azure AD tokens from time to time. Your tenant can only have 50 automated Azure AD tokens active at any one time.
|
||||
- Clear your Azure AD tokens from time to time. Your tenant can only have 500 automated Azure AD tokens active at any one time.
|
||||
|
||||
In the Azure portal, select **Azure Active Directory**. Go to **Users and groups > All users** and look at the list of user names. User names that start with **package_** followed by a string of letters and numbers. These are the user accounts that are created automatically for the tokens and you can safely delete these.
|
||||
|
||||
|
||||
@ -159,7 +159,7 @@ Once you enable the setting to switch to Windows 10 Pro Education, the switch wi
|
||||
|
||||
**To turn on the automatic switch to Windows 10 Pro Education**
|
||||
|
||||
1. Sign in to [Microsoft Store for Education](https://businessstore.microsoft.com/) with your work or school account.
|
||||
1. Sign in to [Microsoft Store for Education](https://educationstore.microsoft.com/) with your work or school account.
|
||||
|
||||
If this is the first time you're signing into the Microsoft Store for Education, you'll be prompted to accept the Microsoft Store for Education Terms of Use.
|
||||
|
||||
@ -341,7 +341,7 @@ Once the automatic switch to Windows 10 Pro Education is turned off, the change
|
||||
|
||||
**To roll back Windows 10 Pro Education to Windows 10 Pro**
|
||||
|
||||
1. Log in to [Microsoft Store for Business](https://businessstore.microsoft.com/en-us/Store/Apps) with your school or work account, or follow the link from the notification email to turn off the automatic switch.
|
||||
1. Log in to [Microsoft Store for Education](https://educationstore.microsoft.com/) with your school or work account, or follow the link from the notification email to turn off the automatic switch.
|
||||
2. Select **Manage > Benefits** and locate the section **Windows 10 Pro Education** and follow the link.
|
||||
3. In the **Revert to Windows 10 Pro** page, click **Revert to Windows 10 Pro**.
|
||||
|
||||
|
||||
@ -71,141 +71,41 @@ Each PinRule element contains a sequence of one or more Site elements and a sequ
|
||||
The PinRules element can have the following attributes.
|
||||
For help with formatting Pin Rules, see [Representing a Date in XML](#representing-a-date-in-xml) or [Representing a Duration in XML](#representing-a-duration-in-xml).
|
||||
|
||||
- **Duration** or **NextUpdate**
|
||||
|
||||
Specifies when the Pin Rules will expire.
|
||||
Either is required.
|
||||
**NextUpdate** takes precedence if both are specified.
|
||||
|
||||
**Duration**, represented as an XML TimeSpan data type, does not allow years and months.
|
||||
You represent the **NextUpdate** attribute as a XML DateTime data type in UTC.
|
||||
|
||||
**Required?** Yes. At least one is required.
|
||||
|
||||
- **LogDuration** or **LogEndDate**
|
||||
|
||||
Configures auditing only to extend beyond the expiration of enforcing the Pin Rules.
|
||||
|
||||
**LogEndDate**, represented as an XML DateTime data type in UTC, takes precedence if both are specified.
|
||||
|
||||
You represent **LogDuration** as an XML TimeSpan data type, which does not allow years and months.
|
||||
|
||||
If neither attribute is specified, auditing expiration uses **Duration** or **NextUpdate** attributes.
|
||||
|
||||
**Required?** No.
|
||||
|
||||
- **ListIdentifier**
|
||||
|
||||
Provides a friendly name for the list of pin rules.
|
||||
Windows does not use this attribute for certificate pinning enforcement, however it is included when the pin rules are converted to a certificate trust list (CTL).
|
||||
|
||||
**Required?** No.
|
||||
| Attribute | Description | Required |
|
||||
|-----------|-------------|----------|
|
||||
| **Duration** or **NextUpdate** | Specifies when the Pin Rules will expire. Either is required. **NextUpdate** takes precedence if both are specified. <br> **Duration**, represented as an XML TimeSpan data type, does not allow years and months. You represent the **NextUpdate** attribute as a XML DateTime data type in UTC. | **Required?** Yes. At least one is required. |
|
||||
| **LogDuration** or **LogEndDate** | Configures auditing only to extend beyond the expiration of enforcing the Pin Rules. <br> **LogEndDate**, represented as an XML DateTime data type in UTC, takes precedence if both are specified. <br> You represent **LogDuration** as an XML TimeSpan data type, which does not allow years and months. <br> If neither attribute is specified, auditing expiration uses **Duration** or **NextUpdate** attributes. | No. |
|
||||
| **ListIdentifier** | Provides a friendly name for the list of pin rules. Windows does not use this attribute for certificate pinning enforcement, however it is included when the pin rules are converted to a certificate trust list (CTL). | No. |
|
||||
|
||||
#### PinRule Element
|
||||
|
||||
The **PinRule** element can have the following attributes:
|
||||
The **PinRule** element can have the following attributes.
|
||||
|
||||
- **Name**
|
||||
|
||||
Uniquely identifies the **PinRule**.
|
||||
Windows uses this attribute to identify the element for a parsing error or for verbose output.
|
||||
The attribute is not included in the generated certificate trust list (CTL).
|
||||
|
||||
**Required?** Yes.
|
||||
|
||||
- **Error**
|
||||
|
||||
Describes the action Windows performs when it encounters a PIN mismatch.
|
||||
You can choose from the following string values:
|
||||
- **Revoked** - Windows reports the certificate protecting the site as if it was revoked. This typically prevents the user from accessing the site.
|
||||
- **InvalidName** - Windows reports the certificate protecting the site as if the name on the certificate does not match the name of the site. This typically results in prompting the user before accessing the site.
|
||||
- **None** - The default value. No error is returned. You can use this setting to audit the pin rules without introducing any user friction.
|
||||
|
||||
**Required?** No.
|
||||
|
||||
- **Log**
|
||||
|
||||
A Boolean value represent as string that equals **true** or **false**.
|
||||
By default, logging is enabled (**true**).
|
||||
|
||||
**Required?** No.
|
||||
| Attribute | Description | Required |
|
||||
|-----------|-------------|----------|
|
||||
| **Name** | Uniquely identifies the **PinRule**. Windows uses this attribute to identify the element for a parsing error or for verbose output. The attribute is not included in the generated certificate trust list (CTL). | Yes.|
|
||||
| **Error** | Describes the action Windows performs when it encounters a PIN mismatch. You can choose from the following string values: <br>- **Revoked** - Windows reports the certificate protecting the site as if it was revoked. This typically prevents the user from accessing the site. <br>- **InvalidName** - Windows reports the certificate protecting the site as if the name on the certificate does not match the name of the site. This typically results in prompting the user before accessing the site. <br>- **None** - The default value. No error is returned. You can use this setting to audit the pin rules without introducing any user friction. | No. |
|
||||
| **Log** | A Boolean value represent as string that equals **true** or **false**. By default, logging is enabled (**true**). | No. |
|
||||
|
||||
#### Certificate element
|
||||
|
||||
The **Certificate** element can have the following attributes:
|
||||
The **Certificate** element can have the following attributes.
|
||||
|
||||
- **File**
|
||||
|
||||
Path to a file containing one or more certificates.
|
||||
Where the certificate(s) can be encoded as:
|
||||
- single certificate
|
||||
- p7b
|
||||
- sst.
|
||||
|
||||
These files can also be Base64 formatted.
|
||||
All **Site** elements included in the same **PinRule** element can match any of these certificates.
|
||||
|
||||
**Required?** Yes (File, Directory or Base64 must be present).
|
||||
|
||||
- **Directory**
|
||||
|
||||
Path to a directory containing one or more of the above certificate files.
|
||||
Skips any files not containing any certificates.
|
||||
|
||||
**Required?** Yes (File, Directory or Base64 must be present).
|
||||
|
||||
- **Base64**
|
||||
|
||||
Base64 encoded certificate(s).
|
||||
Where the certificate(s) can be encoded as:
|
||||
- single certificate
|
||||
- p7b
|
||||
- sst.
|
||||
|
||||
This allows the certificates to be included in the XML file without a file directory dependency.
|
||||
|
||||
> [!Note]
|
||||
> You can use **certutil -encode** to a .cer file into base64. You can then use Notepad to copy and paste the base64 encoded certificate into the pin rule.
|
||||
|
||||
**Required?** Yes (File, Directory or Base64 must be present).
|
||||
|
||||
- **EndDate**
|
||||
|
||||
Enables you to configure an expiration date for when the certificate is no longer valid in the pin rule.
|
||||
|
||||
If you are in the process of switching to a new root or CA, you can set the **EndDate** to allow matching of this element’s certificates.
|
||||
|
||||
If the current time is past the **EndDate**, then, when creating the certificate trust list (CTL), the parser outputs a warning message and exclude the certificate(s) from the Pin Rule in the generated CTL.
|
||||
|
||||
For help with formatting Pin Rules, see [Representing a Date in XML](#representing-a-date-in-xml).
|
||||
|
||||
**Required?** No.
|
||||
| Attribute | Description | Required |
|
||||
|-----------|-------------|----------|
|
||||
| **File** | Path to a file containing one or more certificates. Where the certificate(s) can be encoded as: <br>- single certificate <br>- p7b <br>- sst <br> These files can also be Base64 formatted. All **Site** elements included in the same **PinRule** element can match any of these certificates. | Yes (File, Directory or Base64 must be present). |
|
||||
| **Directory** | Path to a directory containing one or more of the above certificate files. Skips any files not containing any certificates. | Yes (File, Directory or Base64 must be present). |
|
||||
| **Base64** | Base64 encoded certificate(s). Where the certificate(s) can be encoded as: <br>- single certificate <br>- p7b <br> - sst <br> This allows the certificates to be included in the XML file without a file directory dependency. <br> Note: <br> You can use **certutil -encode** to convert a .cer file into base64. You can then use Notepad to copy and paste the base64 encoded certificate into the pin rule. | Yes (File, Directory or Base64 must be present). |
|
||||
| **EndDate** | Enables you to configure an expiration date for when the certificate is no longer valid in the pin rule. <br>If you are in the process of switching to a new root or CA, you can set the **EndDate** to allow matching of this element’s certificates.<br> If the current time is past the **EndDate**, then, when creating the certificate trust list (CTL), the parser outputs a warning message and exclude the certificate(s) from the Pin Rule in the generated CTL.<br> For help with formatting Pin Rules, see [Representing a Date in XML](#representing-a-date-in-xml).| No.|
|
||||
|
||||
#### Site element
|
||||
|
||||
The **Site** element can have the following attributes:
|
||||
The **Site** element can have the following attributes.
|
||||
|
||||
- **Domain**
|
||||
|
||||
Contains the DNS name to be matched for this pin rule.
|
||||
When creating the certificate trust list, the parser normalizes the input name string value as follows:
|
||||
- If the DNS name has a leading "*" it is removed.
|
||||
- Non-ASCII DNS name are converted to ASCII Puny Code.
|
||||
- Upper case ASCII characters are converted to lower case.
|
||||
|
||||
If the normalized name has a leading ".", then, wildcard left hand label matching is enabled.
|
||||
For example, ".xyz.com" would match "abc.xyz.com".
|
||||
|
||||
**Required?** Yes.
|
||||
|
||||
- **AllSubdomains**
|
||||
|
||||
By default, wildcard left hand label matching is restricted to a single left hand label.
|
||||
This attribute can be set to "true" to enable wildcard matching of all of the left hand labels.
|
||||
|
||||
For example, setting this attribute would also match "123.abc.xyz.com" for the ".xyz.com" domain value.
|
||||
|
||||
**Required?** No.
|
||||
| Attribute | Description | Required |
|
||||
|-----------|-------------|----------|
|
||||
| **Domain** | Contains the DNS name to be matched for this pin rule. When creating the certificate trust list, the parser normalizes the input name string value as follows: <br>- If the DNS name has a leading "*" it is removed. <br>- Non-ASCII DNS name are converted to ASCII Puny Code. <br>- Upper case ASCII characters are converted to lower case. <br>If the normalized name has a leading ".", then, wildcard left hand label matching is enabled. For example, ".xyz.com" would match "abc.xyz.com". | Yes.|
|
||||
| **AllSubdomains** | By default, wildcard left hand label matching is restricted to a single left hand label. This attribute can be set to "true" to enable wildcard matching of all of the left-hand labels.<br>For example, setting this attribute would also match "123.abc.xyz.com" for the ".xyz.com" domain value.| No.|
|
||||
|
||||
### Create a Pin Rules Certificate Trust List
|
||||
|
||||
@ -302,10 +202,6 @@ Sign-in to the reference computer using domain administrator equivalent credenti
|
||||
|
||||
To assist in constructing certificate pinning rules, you can configure the **PinRulesLogDir** setting under the certificate chain configuration registry key to include a parent directory to log pin rules.
|
||||
|
||||
```code
|
||||
HKLM\SOFTWARE\Microsoft\Cryptography\OID\EncodingType0\CertDllCreateCertificateChainEngine\Config
|
||||
```
|
||||
|
||||
| Name | Value |
|
||||
|------|-------|
|
||||
| Key | HKLM\SOFTWARE\Microsoft\Cryptography\OID\EncodingType0\CertDllCreateCertificateChainEngine\Config |
|
||||
|
||||
@ -13,7 +13,13 @@ author: nickbrower
|
||||
|
||||
A configuration service provider (CSP) is an interface to read, set, modify, or delete configuration settings on the device. These settings map to registry keys or files. Some configuration service providers support the WAP format, some support SyncML, and some support both. SyncML is only used over–the–air for Open Mobile Alliance Device Management (OMA DM), whereas WAP can be used over–the–air for OMA Client Provisioning, or it can be included in the phone image as a .provxml file that is installed during boot.
|
||||
|
||||
For information about the bridge WMI provider classes that map to these CSPs, see [MDM Bridge WMI Provider](https://msdn.microsoft.com/library/windows/hardware/dn905224). See the [list of CSPs supported in Windows Holographic](#hololens) and the [list of CSPs supported in Microsoft Surface Hub ](#surfacehubcspsupport) for additional information.
|
||||
For information about the bridge WMI provider classes that map to these CSPs, see [MDM Bridge WMI Provider](https://msdn.microsoft.com/library/windows/hardware/dn905224).
|
||||
|
||||
Additional lists:
|
||||
- [List of CSPs supported in Windows Holographic](#hololens)
|
||||
- [List of CSPs supported in Microsoft Surface Hub ](#surfacehubcspsupport)
|
||||
- [List of CSPs supported in Windows 10 IoT Core](#iotcoresupport)
|
||||
- [List of CSPs supported in Windows 10 S](#windows10s)
|
||||
|
||||
The following tables show the configuration service providers support in Windows 10.
|
||||
|
||||
@ -2426,4 +2432,55 @@ Footnotes:
|
||||
- [RootCATrustedCertificates CSP](rootcacertificates-csp.md)
|
||||
- [Update CSP](update-csp.md)
|
||||
- [VPNv2 CSP](vpnv2-csp.md)
|
||||
- [WiFi CSP](wifi-csp.md)
|
||||
- [WiFi CSP](wifi-csp.md)
|
||||
|
||||
## <a href="" id="windows10s"></a>CSPs supported in Windows 10 S
|
||||
|
||||
The CSPs supported in Windows 10 S is the same as in Windows 10 Pro except that Office CSP and EnterpriseDesktop CSP are not available in Windows 10 S. Here is the list:
|
||||
|
||||
- [ActiveSync CSP](activesync-csp.md)
|
||||
- [APPLICATION CSP](application-csp.md)
|
||||
- [AppLocker CSP](applocker-csp.md)
|
||||
- [BOOTSTRAP CSP](bootstrap-csp.md)
|
||||
- [CellularSettings CSP](cellularsettings-csp.md)
|
||||
- [CertificateStore CSP](certificatestore-csp.md)
|
||||
- [ClientCertificateInstall CSP](clientcertificateinstall-csp.md)
|
||||
- [CM_CellularEntries CSP](cm-cellularentries-csp.md)
|
||||
- [Defender CSP](defender-csp.md)
|
||||
- [DevDetail CSP](devdetail-csp.md)
|
||||
- [DeviceManageability CSP](devicemanageability-csp.md)
|
||||
- [DeviceStatus CSP](devicestatus-csp.md)
|
||||
- [DevInfo CSP](devinfo-csp.md)
|
||||
- [DiagnosticLog CSP](diagnosticlog-csp.md)
|
||||
- [DMAcc CSP](dmacc-csp.md)
|
||||
- [DMClient CSP](dmclient-csp.md)
|
||||
- [EMAIL2 CSP](email2-csp.md)
|
||||
- [EnterpriseAPN CSP](enterpriseapn-csp.md)
|
||||
- [EnterpriseDataProtection CSP](enterprisedataprotection-csp.md)
|
||||
- [EnterpriseModernAppManagement CSP](enterprisemodernappmanagement-csp.md)
|
||||
- [HealthAttestation CSP](healthattestation-csp.md)
|
||||
- [NAP CSP](nap-csp.md)
|
||||
- [NAPDEF CSP](napdef-csp.md)
|
||||
- [NetworkProxy CSP](networkproxy-csp.md)
|
||||
- [NodeCache CSP](nodecache-csp.md)
|
||||
- [PassportForWork CSP](passportforwork-csp.md)
|
||||
- [Policy CSP](policy-configuration-service-provider.md)
|
||||
- [Provisioning CSP](provisioning-csp.md)
|
||||
- [PROXY CSP](proxy-csp.md)
|
||||
- [PXLOGICAL CSP](pxlogical-csp.md)
|
||||
- [Reboot CSP](reboot-csp.md)
|
||||
- [RemoteFind CSP](remotefind-csp.md)
|
||||
- [RemoteWipe CSP](remotewipe-csp.md)
|
||||
- [Reporting CSP](reporting-csp.md)
|
||||
- [RootCATrustedCertificates CSP](rootcacertificates-csp.md)
|
||||
- [SecureAssessment CSP](secureassessment-csp.md)
|
||||
- [SecurityPolicy CSP](securitypolicy-csp.md)
|
||||
- [SharedPC CSP](sharedpc-csp.md)
|
||||
- [Storage CSP](storage-csp.md)
|
||||
- [SUPL CSP](supl-csp.md)
|
||||
- [Update CSP](update-csp.md)
|
||||
- [VPNv2 CSP](vpnv2-csp.md)
|
||||
- [WiFi CSP](wifi-csp.md)
|
||||
- [Win32AppInventory CSP](win32appinventory-csp.md)
|
||||
- [WindowsAdvancedThreatProtection CSP](windowsadvancedthreatprotection-csp.md)
|
||||
- [WindowsLicensing CSP](windowslicensing-csp.md)
|
||||
|
||||
@ -880,6 +880,14 @@ For details about Microsoft mobile device management protocols for Windows 10 s
|
||||
<li>Ownership</li>
|
||||
</ul>
|
||||
</td></tr>
|
||||
<tr class="odd">
|
||||
<td style="vertical-align:top">MDM support for Windows 10 S</td>
|
||||
<td style="vertical-align:top"><p>Updated the following topics to indicate MDM support in Windows 10 S.</p>
|
||||
<ul>
|
||||
<li>[Configuration service provider reference](configuration-service-provider-reference.md)</li>
|
||||
<li>[Policy CSP](policy-configuration-service-provider.md)</li>
|
||||
</ul>
|
||||
</td></tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
@ -1224,6 +1232,14 @@ The DM agent for [push-button reset](https://msdn.microsoft.com/windows/hardware
|
||||
<td style="vertical-align:top">[Firewall CSP](firewall-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added new CSP in the next major update to Windows 10.</p>
|
||||
</td></tr>
|
||||
<tr class="odd">
|
||||
<td style="vertical-align:top">MDM support for Windows 10 S</td>
|
||||
<td style="vertical-align:top"><p>Updated the following topics to indicate MDM support in Windows 10 S.</p>
|
||||
<ul>
|
||||
<li>[Configuration service provider reference](configuration-service-provider-reference.md)</li>
|
||||
<li>[Policy CSP](policy-configuration-service-provider.md)</li>
|
||||
</ul>
|
||||
</td></tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -64,7 +64,7 @@ There are three categories of apps that might be pinned to a taskbar:
|
||||
* Apps pinned by the enterprise, such as in an unattended Windows setup
|
||||
|
||||
>[!NOTE]
|
||||
>The earlier method of using [TaskbarLinks](https://go.microsoft.com/fwlink/p/?LinkId=761230) in an unattended Windows setup file is deprecated in Windows 10, version 1607.
|
||||
>We recommend using [the layoutmodification.xml method](configure-windows-10-taskbar.md) to configure taskbar options, rather than the earlier method of using [TaskbarLinks](https://go.microsoft.com/fwlink/p/?LinkId=761230) in an unattended Windows setup file.
|
||||
|
||||
The following example shows how apps will be pinned - Windows default apps to the left (blue circle), apps pinned by the user in the center (orange triangle), and apps that you pin using XML to the right (green square).
|
||||
|
||||
|
||||
@ -73,16 +73,23 @@ MBR2GPT: Validation completed successfully
|
||||
|
||||
In the following example:
|
||||
|
||||
1. The current disk partition layout is displayed prior to conversion - three partitions are present on the MBR disk (disk 0): a system reserved partition, a Windows partition, and a recovery partition. A DVD-ROM is also present as volume 0.
|
||||
1. Using DiskPart, the current disk partition layout is displayed prior to conversion - three partitions are present on the MBR disk (disk 0): a system reserved partition, a Windows partition, and a recovery partition. A DVD-ROM is also present as volume 0.
|
||||
2. The OS volume is selected, partitions are listed, and partition details are displayed for the OS partition. The [MBR partition type](https://msdn.microsoft.com/library/windows/desktop/aa363990.aspx) is **07** corresponding to the installable file system (IFS) type.
|
||||
2. The MBR2GPT tool is used to convert disk 0.
|
||||
3. The DISKPART tool displays that disk 0 is now using the GPT format.
|
||||
3. The DiskPart tool displays that disk 0 is now using the GPT format.
|
||||
4. The new disk layout is displayed - four partitions are present on the GPT disk: three are identical to the previous partitions and one is the new EFI system partition (volume 3).
|
||||
5. The OS volume is selected again, and detail displays that it has been converted to the [GPT partition type](https://msdn.microsoft.com/library/windows/desktop/aa365449.aspx) of **ebd0a0a2-b9e5-4433-87c0-68b6b72699c7** corresponding to the **PARTITION_BASIC_DATA_GUID** type.
|
||||
|
||||
>As noted in the output from the MBR2GPT tool, you must make changes to the computer firmware so that the new EFI system partition will boot properly.
|
||||
|
||||
```
|
||||
X:\>DiskPart
|
||||
|
||||
Microsoft DiskPart version 10.0.15048.0
|
||||
|
||||
Copyright (C) Microsoft Corporation.
|
||||
On computer: MININT-K71F13N
|
||||
|
||||
DISKPART> list volume
|
||||
|
||||
Volume ### Ltr Label Fs Type Size Status Info
|
||||
@ -140,7 +147,7 @@ MBR2GPT: Fixing drive letter mapping
|
||||
MBR2GPT: Conversion completed successfully
|
||||
MBR2GPT: Before the new system can boot properly you need to switch the firmware to boot to UEFI mode!
|
||||
|
||||
X:\>diskpart
|
||||
X:\>DiskPart
|
||||
|
||||
Microsoft DiskPart version 10.0.15048.0
|
||||
|
||||
@ -364,9 +371,16 @@ You can also view the partition type of a disk by opening the Disk Management to
|
||||
|
||||
|
||||
|
||||
If Windows PowerShell and Disk Management are not available, such as when you are using Windows PE, you can determine the partition type at a command prompt with the diskpart tool. To determine the partition style, type **diskpart** and then type **list disk**. See the following example:
|
||||
If Windows PowerShell and Disk Management are not available, such as when you are using Windows PE, you can determine the partition type at a command prompt with the DiskPart tool. To determine the partition style from a command line, type **diskpart** and then type **list disk**. See the following example:
|
||||
|
||||
```
|
||||
X:\>DiskPart
|
||||
|
||||
Microsoft DiskPart version 10.0.15048.0
|
||||
|
||||
Copyright (C) Microsoft Corporation.
|
||||
On computer: MININT-K71F13N
|
||||
|
||||
DISKPART> list disk
|
||||
|
||||
Disk ### Status Size Free Dyn Gpt
|
||||
|
||||
@ -44,7 +44,7 @@ With Windows Update for Business, you can set a device to be on either the Curre
|
||||
| GPO for version 1607 and above: </br>Computer Configuration > Administrative Templates > Windows Components > Windows Update > Defer Windows Updates > **Select when Feature Updates are received** | \Policies\Microsoft\Windows\WindowsUpdate\BranchReadinessLevel |
|
||||
| GPO for version 1511: </br>Computer Configuration > Administrative Templates > Windows Components > Windows Update > **Defer Upgrades and Updates** | \Policies\Microsoft\Windows\WindowsUpdate\DeferUpgrade |
|
||||
| MDM for version 1607 and above: </br>../Vendor/MSFT/Policy/Config/Update/</br>**BranchReadinessLevel** | \Microsoft\PolicyManager\default\Update\BranchReadinessLevel |
|
||||
| MDM for version 1511: </br>../Vendor/MSFT/Policy/Config/Update/</br>**RequireDeferredUpgrade** | \Microsoft\PolicyManager\default\Update\RequireDeferUpgrade |
|
||||
| MDM for version 1511: </br>../Vendor/MSFT/Policy/Config/Update/</br>**RequireDeferUpgrade** | \Microsoft\PolicyManager\default\Update\RequireDeferUpgrade |
|
||||
|
||||
Starting with version 1703, users are able to configure their device's branch readiness level, by going to **Settings > Update & security > Windows Update > Advanced options**.
|
||||
|
||||
|
||||
@ -60,7 +60,7 @@ Current Branch is the default servicing branch for all Windows 10 devices except
|
||||
|
||||
- In Windows 10, version 1511:
|
||||
|
||||
../Vendor/MSFT/Policy/Config/Update/**RequireDeferredUpgrade**
|
||||
../Vendor/MSFT/Policy/Config/Update/**RequireDeferUpgrade**
|
||||
|
||||
- In Windows 10, version 1607:
|
||||
|
||||
@ -70,7 +70,7 @@ Current Branch is the default servicing branch for all Windows 10 devices except
|
||||
|
||||
- In Windows 10 Mobile Enterprise, version 1511:
|
||||
|
||||
../Vendor/MSFT/Policy/Config/Update/RequireDeferredUpgrade
|
||||
../Vendor/MSFT/Policy/Config/Update/RequireDeferUpgrade
|
||||
|
||||
- In Windows 10 Mobile Enterprise, version 1607:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user