mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-17 19:33:37 +00:00
Merge branch 'master' of https://github.com/microsoftdocs/windows-itpro-docs
This commit is contained in:
Liza Poggemeyer
@ -27,7 +27,7 @@ When you run the Microsoft Surface Dock Updater installer you will be prompted t
|
||||
>Updating Surface Dock firmware requires connectivity to the Surface Dock via the Surface Connect™ port. Installation of the Microsoft Surface Dock Updater is only supported on devices that feature the Surface Connect™ port.
|
||||
|
||||
>[!NOTE]
|
||||
>The Surface Dock Updater tool is unable to run on Windows 10 S. Surface Dock devices used with Surface Laptop with Windows 10 S will receive updates natively through Windows Update. To manually update a Surface Dock for use with Surface Laptop and Windows 10 S, connect the Surface Dock to another Surface device with a Windows 10 Pro or Windows 10 Enterprise environment.
|
||||
>The Surface Dock Updater tool is unable to run on Windows 10 S. To manually update a Surface Dock for use with Surface Laptop and Windows 10 S, connect the Surface Dock to another Surface device with a Windows 10 Pro or Windows 10 Enterprise environment.
|
||||
|
||||
## Update a Surface Dock with Microsoft Surface Dock Updater
|
||||
|
||||
|
||||
@ -53,5 +53,5 @@ Enrolling Surface devices in Windows Autopilot at the time of purchase is a capa
|
||||
When you purchase Surface devices from a Surface partner enabled for Windows Autopilot, your new devices can be enrolled in your Windows Autopilot deployment for you by the partner. Surface partners enabled for Windows Autopilot include:
|
||||
|
||||
- [SHI](https://www.shi.com/?reseller=shi)
|
||||
- [Insight](https://www.insight.com/en_US/buy/partner/microsoft/surface.html)
|
||||
- [Atea](https://www.atea.com/)
|
||||
- [Insight](https://www.insight.com/en_US/buy/partner/microsoft/surface/windows-autopilot.html)
|
||||
- [Atea](https://www.atea.com/)
|
||||
|
||||
@ -63,10 +63,6 @@ Starting with Windows 10, version 1703, users can configure the branch readiness
|
||||
|
||||
After you configure the servicing branch (Windows Insider Preview or Semi-Annual Channel), you can then define if, and for how long, you would like to defer receiving Feature Updates following their availability from Microsoft on Windows Update. You can defer receiving these Feature Updates for a period of up to 365 days from their release by setting the `DeferFeatureUpdatesPeriodinDays` value.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>
|
||||
>You can only defer up to 180 days on devices running Windows 10, version 1703.
|
||||
|
||||
For example, a device on the Semi-Annual Channel with `DeferFeatureUpdatesPeriodinDays=30` will not install a feature update that is first publicly available on Windows Update in September until 30 days later, in October.
|
||||
|
||||
|
||||
@ -274,4 +270,4 @@ When a device running a newer version sees an update available on Windows Update
|
||||
- [Walkthrough: use Intune to configure Windows Update for Business](waas-wufb-intune.md)
|
||||
- [Deploy Windows 10 updates using Windows Server Update Services](waas-manage-updates-wsus.md)
|
||||
- [Deploy Windows 10 updates using System Center Configuration Manager](waas-manage-updates-configuration-manager.md)
|
||||
- [Manage device restarts after updates](waas-restart.md)
|
||||
- [Manage device restarts after updates](waas-restart.md)
|
||||
|
||||
@ -22,7 +22,7 @@ The simplest path to upgrade PCs currently running Windows 7, Windows 8, or Wi
|
||||
## Proof-of-concept environment
|
||||
|
||||
|
||||
For the purposes of this topic, we will use three machines: DC01, CM01, and PC0003. DC01 is a domain controller and CM01 is a Windows Server 2012 R2 standard machine, fully patched with the latest security updates, and configured as a member server in the fictional contoso.com domain. PC0003 is a machine with Windows 7 SP1, targeted for the Windows 10 upgrade. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](../deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit.md).
|
||||
For the purposes of this topic, we will use three machines: DC01, CM01, and PC0001. DC01 is a domain controller and CM01 is a Windows Server 2012 R2 standard machine, fully patched with the latest security updates, and configured as a member server in the fictional contoso.com domain. PC0001 is a machine with Windows 7 SP1, targeted for the Windows 10 upgrade. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](../deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit.md).
|
||||
|
||||
|
||||
|
||||
@ -48,7 +48,7 @@ For full details and an explanation of the task sequence steps, review the full
|
||||
## Create a device collection
|
||||
|
||||
|
||||
After you create the upgrade task sequence, you can create a collection to test a deployment. In this section, we assume you have the PC0003 machine running Windows 7 SP1, with the Configuration Manager client installed.
|
||||
After you create the upgrade task sequence, you can create a collection to test a deployment. In this section, we assume you have the PC0001 machine running Windows 7 SP1, with the Configuration Manager client installed.
|
||||
|
||||
1. On CM01, using the Configuration Manager console, in the Asset and Compliance workspace, right-click **Device Collections**, and then select **Create Device Collection**. Use the following settings:
|
||||
- General
|
||||
@ -65,13 +65,13 @@ After you create the upgrade task sequence, you can create a collection to test
|
||||
|
||||
- Attribute Name: Name
|
||||
|
||||
- Value: PC0003
|
||||
- Value: PC0001
|
||||
|
||||
- Select Resources
|
||||
|
||||
- Select PC0003
|
||||
- Select PC0001
|
||||
|
||||
2. Review the Windows 10 Enterprise x64 Upgrade collection. Do not continue until you see the PC0003 machine in the collection.
|
||||
2. Review the Windows 10 Enterprise x64 Upgrade collection. Do not continue until you see the PC0001 machine in the collection.
|
||||
|
||||
## Deploy the Windows 10 upgrade
|
||||
|
||||
@ -94,9 +94,9 @@ In this section, you create a deployment for the Windows 10 Enterprise x64 Upda
|
||||
## Start the Windows 10 upgrade
|
||||
|
||||
|
||||
In this section, you start the Windows 10 Upgrade task sequence on PC0003 (currently running Windows 7 SP1).
|
||||
In this section, you start the Windows 10 Upgrade task sequence on PC0001 (currently running Windows 7 SP1).
|
||||
|
||||
1. On PC0003, start the **Software Center**.
|
||||
1. On PC0001, start the **Software Center**.
|
||||
2. Select the **Windows vNext Upgrade** task sequence, and then click **Install**.
|
||||
|
||||
When the task sequence begins, it will automatically initiate the in-place upgrade process by invoking the Windows setup program (Setup.exe) with the necessary command-line parameters to perform an automated upgrade, which preserves all data, settings, apps, and drivers.
|
||||
@ -143,7 +143,7 @@ Figure 3. The Configuration Manager upgrade task sequence.
|
||||
|
||||
### Create a device collection
|
||||
|
||||
After you create the upgrade task sequence, you can create a collection to test a deployment. In this section, we assume you have the PC0003 machine running Windows 7 SP1, with the next version of System Center Configuration Manager client installed.
|
||||
After you create the upgrade task sequence, you can create a collection to test a deployment. In this section, we assume you have the PC0001 machine running Windows 7 SP1, with the next version of System Center Configuration Manager client installed.
|
||||
|
||||
1. On CM01, using the Configuration Manager console, in the Asset and Compliance workspace, right-click **Device Collections**, and then select **Create Device Collection**. Use the following settings:
|
||||
- General
|
||||
@ -160,13 +160,13 @@ After you create the upgrade task sequence, you can create a collection to test
|
||||
|
||||
- Attribute Name: Name
|
||||
|
||||
- Value: PC0003
|
||||
- Value: PC0001
|
||||
|
||||
- Select Resources
|
||||
|
||||
- Select PC0003
|
||||
- Select PC0001
|
||||
|
||||
2. Review the Windows 10 Enterprise x64 Upgrade collection. Do not continue until you see the PC0003 machine in the collection.
|
||||
2. Review the Windows 10 Enterprise x64 Upgrade collection. Do not continue until you see the PC0001 machine in the collection.
|
||||
|
||||
### Deploy the Windows 10 upgrade
|
||||
|
||||
@ -187,9 +187,9 @@ In this section, you create a deployment for the Windows 10 Enterprise x64 Upda
|
||||
|
||||
### Start the Windows 10 upgrade
|
||||
|
||||
In this section, you start the Windows 10 Upgrade task sequence on PC0003 (currently running Windows 7 SP1).
|
||||
In this section, you start the Windows 10 Upgrade task sequence on PC0001 (currently running Windows 7 SP1).
|
||||
|
||||
1. On PC0003, start the **Software Center**.
|
||||
1. On PC0001, start the **Software Center**.
|
||||
2. Select the **Windows 10 Enterprise x64 Upgrade** task sequence, and then click **Install.**
|
||||
|
||||
When the task sequence begins, it automatically initiates the in-place upgrade process by invoking the Windows setup program (Setup.exe) with the necessary command-line parameters to perform an automated upgrade, which preserves all data, settings, apps, and drivers.
|
||||
|
||||
@ -46,7 +46,7 @@ Sign-in a certificate authority or management workstations with _Domain Admin_ e
|
||||
4. On the **Compatibility** tab, clear the **Show resulting changes** check box. Select **Windows Server 2008 R2** from the **Certification Authority** list. Select **Windows 7.Server 2008 R2** from the **Certification Recipient** list.
|
||||
5. On the **General** tab, type **Domain Controller Authentication (Kerberos)** in Template display name. Adjust the validity and renewal period to meet your enterprise's needs.
|
||||
**Note**If you use different template names, you'll need to remember and substitute these names in different portions of the lab.
|
||||
6. On the **Subject** tab, select the **Build from this Active Directory information** button if it is not already selected. Select **None** from the **Subject name format** list. Select **DNS name** from the **Include this information in alternate subject** list. Clear all other items.
|
||||
6. On the **Subject Name** tab, select the **Build from this Active Directory information** button if it is not already selected. Select **None** from the **Subject name format** list. Select **DNS name** from the **Include this information in alternate subject** list. Clear all other items.
|
||||
7. On the **Cryptography** tab, select **Key Storage Provider** from the **Provider Category** list. Select **RSA** from the **Algorithm name** list. Type **2048** in the **Minimum key size** text box. Select **SHA256** from the **Request hash** list. Click **OK**.
|
||||
8. Close the console.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user