mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 18:33:43 +00:00
Merge branch 'master' of https://github.com/MicrosoftDocs/windows-docs-pr into FromPrivateRepo
This commit is contained in:
huaping yu
@ -186,7 +186,7 @@ You can verify the Windows 10 Enterprise E3 or E5 subscription in **Settings &g
|
||||
|
||||
If there are any problems with the Windows 10 Enterprise E3 or E5 license or the activation of the license, the **Activation** panel will display the appropriate error message or status. You can use this information to help you diagnose the licensing and activation process.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>If you use slmgr /dli or /dlv commands to retrieve the activation information for the Windows 10 E3 or E5 license, the license information displayed will be the following:
|
||||
>Name: Windows(R), Professional edition
|
||||
>Description: Windows(R) Operating System, RETAIL channel
|
||||
|
||||
@ -95,7 +95,7 @@ After you create the task sequence, we recommend that you configure the task seq
|
||||
|
||||
* OSDPreserveDriveLetter: True
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>If you don't change this value, your Windows installation will end up in E:\\Windows.
|
||||
|
||||
3. In the **Post Install** group, select **Apply Network Settings**, and configure the Domain OU value to use the **Contoso / Workstations** OU (browse for values).
|
||||
@ -112,7 +112,7 @@ After you create the task sequence, we recommend that you configure the task seq
|
||||
|
||||
* Options: Task Sequence Variable: Model equals HP EliteBook 8560w
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>You also can add a Query WMI condition with the following query: SELECT \* FROM Win32\_ComputerSystem WHERE Model LIKE '%HP EliteBook 8560w%'
|
||||
|
||||
|
||||
@ -153,7 +153,7 @@ After you create the task sequence, we recommend that you configure the task seq
|
||||
|
||||
11. Click **OK**.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>The Request State Store and Release State Store actions need to be added for common computer replace scenarios.
|
||||
|
||||
|
||||
|
||||
@ -80,7 +80,7 @@ This section will show you how to populate the MDT deployment share with the Win
|
||||
|
||||
MDT supports adding both full source Windows 10 DVDs (ISOs) and custom images that you have created. In this case, you create a reference image, so you add the full source setup files from Microsoft.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>Due to the Windows limits on path length, we are purposely keeping the operating system destination directory short, using the folder name W10EX64RTM rather than a more descriptive name like Windows 10 Enterprise x64 RTM.
|
||||
|
||||
### Add Windows 10 Enterprise x64 (full source)
|
||||
@ -120,7 +120,7 @@ By storing configuration items as MDT applications, it is easy to move these obj
|
||||
|
||||
In these examples, we assume that you downloaded the software in this list to the E:\\Downloads folder. The first application is added using the UI, but because MDT supports Windows PowerShell, you add the other applications using Windows PowerShell.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>All the Microsoft Visual C++ downloads can be found on [The latest supported Visual C++ downloads](https://go.microsoft.com/fwlink/p/?LinkId=619523).
|
||||
|
||||
### Create the install: Microsoft Office Professional Plus 2013 x86
|
||||
@ -138,7 +138,7 @@ You also can customize the Office installation using a Config.xml file. But we r
|
||||
|
||||
Figure 5. The Install - Microsoft Office 2013 Pro Plus - x86 application properties.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>If you don't see the Office Products tab, verify that you are using a volume license version of Office. If you are deploying Office 365, you need to download the Admin folder from Microsoft.
|
||||
|
||||
3. In the Office Customization Tool dialog box, select the Create a new Setup customization file for the following product option, select the Microsoft Office Professional Plus 2013 (32-bit) product, and click OK.
|
||||
@ -160,7 +160,7 @@ You also can customize the Office installation using a Config.xml file. But we r
|
||||
- In the **Microsoft Office 2013** node, expand **Privacy**, select **Trust Center**, and enable the Disable Opt-in Wizard on first run setting.
|
||||
5. From the **File** menu, select **Save**, and save the configuration as 0\_Office2013ProPlusx86.msp in the **E:\\MDTBuildLab\\Applications\\Install - Microsoft Office 2013 Pro Plus - x86\\Updates** folder.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>The reason for naming the file with a 0 (zero) at the beginning is that the Updates folder also handles Microsoft Office updates, and they are installed in alphabetical order. The Office 2013 setup works best if the customization file is installed before any updates.
|
||||
|
||||
6. Close the Office Customization Tool, click Yes in the dialog box, and in the **Install - Microsoft Office 2013 Pro Plus - x86 Properties** window, click **OK**.
|
||||
@ -379,7 +379,7 @@ When using MDT, you don't need to edit the Unattend.xml file very often because
|
||||
>[!WARNING]
|
||||
>Do not use **SkipMachineOOBE** or **SkipUserOOBE** in your Unattend.xml file. These settings are deprecated and can have unintended effects if used.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>You also can use the Unattend.xml to enable components in Windows 10, like the Telnet Client or Hyper-V client. Normally we prefer to do this via the **Install Roles and Features** action, or using Deployment Image Servicing and Management (DISM) command-line tools, because then we can add that as an application, being dynamic, having conditions, and so forth. Also, if you are adding packages via Unattend.xml, it is version specific, so Unattend.xml must match the exact version of the operating system you are servicing.
|
||||
|
||||
Follow these steps to configure Internet Explorer settings in Unattend.xml for the Windows 10 Enterprise x64 RTM Default Image task sequence:
|
||||
@ -460,7 +460,7 @@ For that reason, add only a minimal set of rules to Bootstrap.ini, such as which
|
||||
|
||||
Figure 12. The boot image rules for the MDT Build Lab deployment share.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>For security reasons, you normally don't add the password to the Bootstrap.ini file; however, because this deployment share is for creating reference image builds only, and should not be published to the production network, it is acceptable to do so in this situation.
|
||||
|
||||
4. In the **Windows PE** tab, in the **Platform** drop-down list, select **x86**.
|
||||
@ -473,7 +473,7 @@ For that reason, add only a minimal set of rules to Bootstrap.ini, such as which
|
||||
2. ISO file name: MDT Build Lab x64.iso
|
||||
8. Click **OK**.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>In MDT, the x86 boot image can deploy both x86 and x64 operating systems (except on computers based on Unified Extensible Firmware Interface).
|
||||
|
||||
|
||||
@ -484,7 +484,7 @@ After the deployment share has been configured, it needs to be updated. This is
|
||||
1. Using the Deployment Workbench, right-click the **MDT Build Lab deployment share** and select **Update Deployment Share**.
|
||||
2. Use the default options for the Update Deployment Share Wizard.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>The update process will take 5 to 10 minutes.
|
||||
|
||||
### The rules explained
|
||||
@ -495,7 +495,7 @@ The Bootstrap.ini and CustomSettings.ini files work together. The Bootstrap.ini
|
||||
|
||||
The CustomSettings.ini file is normally stored on the server, in the Deployment share\\Control folder, but also can be stored on the media (when using offline media).
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>The settings, or properties, that are used in the rules (CustomSettings.ini and Bootstrap.ini) are listed in the MDT documentation, in the Microsoft Deployment Toolkit Reference / Properties / Property Definition section.
|
||||
|
||||
### The Bootstrap.ini file
|
||||
@ -518,12 +518,12 @@ So, what are these settings?
|
||||
- **DeployRoot.** This is the location of the deployment share. Normally, this value is set by MDT, but you need to update the DeployRoot value if you move to another server or other share. If you don't specify a value, the Windows Deployment Wizard prompts you for a location.
|
||||
- **UserDomain, UserID, and UserPassword.** These values are used for automatic log on to the deployment share. Again, if they are not specified, the wizard prompts you.
|
||||
|
||||
>[!WARNING]
|
||||
>[!WARNING]
|
||||
>Caution is advised. These values are stored in clear text on the boot image. Use them only for the MDT Build Lab deployment share and not for the MDT Production deployment share that you learn to create in the next topic.
|
||||
|
||||
- **SkipBDDWelcome.** Even if it is nice to be welcomed every time we start a deployment, we prefer to skip the initial welcome page of the Windows Deployment Wizard.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>All properties beginning with "Skip" control only whether to display that pane in the Windows Deployment Wizard. Most of the panes also require you to actually set one or more values.
|
||||
|
||||
### The CustomSettings.ini file
|
||||
|
||||
@ -95,7 +95,7 @@ In these steps, we assume that you have completed the steps in the [Create a Win
|
||||
6. On the **Destination** page, in the **Destination directory name** text box, type **W10EX64RTM**, click **Next** twice, and then click **Finish**.
|
||||
7. After adding the operating system, double-click the added operating system name in the **Operating Systems / Windows 10** node and change the name to match the following: **Windows 10 Enterprise x64 RTM Custom Image**.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>The reason for adding the setup files has changed since earlier versions of MDT. MDT 2010 used the setup files to install Windows. MDT uses DISM to apply the image; however, you still need the setup files because some components in roles and features are stored outside the main image.
|
||||
|
||||
|
||||
@ -290,7 +290,7 @@ This section will show you how to create the task sequence used to deploy your p
|
||||
1. Choose a selection profile: Nothing
|
||||
2. Install all drivers from the selection profile
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>The configuration above indicates that MDT should only use drivers from the folder specified by the DriverGroup001 property, which is defined by the "Choose a selection profile: Nothing" setting, and that MDT should not use plug and play to determine which drivers to copy, which is defined by the "Install all drivers from the selection profile" setting.
|
||||
|
||||
3. State Restore. Enable the **Windows Update (Pre-Application Installation)** action.
|
||||
|
||||
@ -46,7 +46,7 @@ For a computer refresh with MDT, you use the User State Migration Tool (USMT), w
|
||||
|
||||
During the computer refresh, USMT uses a feature called Hard-Link Migration Store. When you use this feature, the files are simply linked in the file system, which allows for fast migration, even when there is a lot of data.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>In addition to the USMT backup, you can enable an optional full Windows Imaging (WIM) backup of the machine by configuring the MDT rules. If you do this, a .wim file is created in addition to the USMT backup. The .wim file will contain the entire volume from the computer, and helpdesk personnel can extract content from it if needed. Please note that this is a data WIM backup only. Using this backup to restore the entire machine is not a supported scenario.
|
||||
|
||||
### Multi-user migration
|
||||
@ -56,7 +56,7 @@ by configuring command-line switches to ScanState (added as rules in MDT).
|
||||
|
||||
As an example, the following line configures USMT to migrate only domain user profiles and not profiles from the local SAM account database: ScanStateArgs=/ue:\*\\\* /ui:CONTOSO\\\*
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>You also can combine the preceding switches with the /uel switch, which excludes profiles that have not been accessed within a specific number of days. For example, adding /uel:60 will configure ScanState (or LoadState) not to include profiles that haven't been accessed for more than 60 days.
|
||||
|
||||
### Support for additional settings
|
||||
@ -91,7 +91,7 @@ In order to use the custom MigContosoData.xml USMT template, you need to copy it
|
||||
|
||||
After adding the additional USMT template and configuring the CustomSettings.ini file to use it, you are now ready to refresh a Windows 7 SP1 client to Windows 10. In these steps, we assume you have a Windows 7 SP1 client named PC0001 in your environment that is ready for a refresh to Windows 10.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>MDT also supports an offline computer refresh. For more info on that scenario, see the USMTOfflineMigration property in the [MDT resource page](https://go.microsoft.com/fwlink/p/?LinkId=618117).
|
||||
|
||||
### Upgrade (refresh) a Windows 7 SP1 client
|
||||
|
||||
@ -88,7 +88,7 @@ During a computer replace, these are the high-level steps that occur:
|
||||
* Specify where to save your data and settings: Specify a location
|
||||
* Location: \\\\MDT01\\MigData$\\PC0002
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>If you are replacing the computer at a remote site you should create the MigData folder on MDT02 and use that share instead.
|
||||
|
||||
2. Specify where to save a complete computer backup: Do not back up the existing computer
|
||||
|
||||
@ -49,7 +49,7 @@ This section will show you how to import some network and storage drivers for Wi
|
||||
|
||||
*Figure 21. Add drivers to Windows PE*
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>The Updating Boot Image part of the wizard will appear to hang when displaying Done. It will complete in a minute or two.
|
||||
|
||||
|
||||
@ -74,13 +74,13 @@ This section illustrates how to add drivers for Windows 10 through an example in
|
||||
|
||||
* Path: \\\\CM01\\Sources$\\OSD\\DriverPackages\\Windows 10 x64\\HP EliteBook 8560w
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>The package path does not yet exist, so you have to type it in. The wizard will create the new package in that folder.
|
||||
|
||||
|
||||
5. On the **Select drivers to include in the boot image** page, do not select anything, and click **Next** twice. After the package has been created, click **Close**.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>If you want to monitor the driver import process more closely, you can open the SMSProv.log file during driver import.
|
||||
|
||||
|
||||
|
||||
@ -29,7 +29,7 @@ Microsoft System Center 2012 R2 Configuration Manager supports deploying applica
|
||||
|
||||
For the purposes of this topic, we will use CM01, a machine running Windows Server 2012 R2 Standard that is a member of the domain contoso.com for the fictitious Contoso Corporation. 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).
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>Even though the new application model is fully supported to deploy via the task sequence, the most reliable way to deploy software via the task sequence is still the legacy packages, especially if you deploy many applications.
|
||||
|
||||
## Example: Create the Adobe Reader XI application
|
||||
|
||||
@ -96,7 +96,7 @@ This section will show you how to configure the rules (the Windows 10 x64 Settin
|
||||
|
||||
3. Update the distribution point for the **Windows 10 x64 Settings** package by right-clicking the **Windows 10 x64 Settings** package and selecting **Update Distribution Points**.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>Although you have not yet added a distribution point, you still need to select Update Distribution Points. That process also updates the Configuration Manager 2012 content library with changes.
|
||||
|
||||
|
||||
@ -160,7 +160,7 @@ This section provides steps to help you configure the All Unknown Computers coll
|
||||
|
||||
3. Click **OK**.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>Configuration Manager can prompt for information in many ways. Using a collection variable with an empty value is just one of them. Another option is the User-Driven Installation (UDI) wizard.
|
||||
|
||||
|
||||
|
||||
@ -130,7 +130,7 @@ In order for the Configuration Manager Join Domain Account (CM\_JD) to join mach
|
||||
|
||||
To support the packages you create in this section, the following folder structure should be created on the Configuration Manager primary site server (CM01):
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>In most production environments, the packages are stored on a Distributed File System (DFS) share or a "normal" server share, but in a lab environment you can store them on the site server.
|
||||
|
||||
- E:\\Sources
|
||||
|
||||
@ -70,7 +70,7 @@ In this topic, we assume that you have a Windows 7 SP1 client named PC0003 with
|
||||
|
||||
2. Review the Install Windows 10 Enterprise x64 collection. Do not continue until you see the PC0003 machine in the collection.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>It may take a short while for the collection to refresh; you can view progress via the Colleval.log file. If you want to speed up the process, you can manually update membership on the Install Windows 10 Enterprise x64 collection by right-clicking the collection and selecting Update Membership.
|
||||
|
||||
|
||||
@ -90,7 +90,7 @@ Using the Configuration Manager console, in the Software Library workspace, sele
|
||||
|
||||
- Make available to the following: Configuration Manager clients, media and PXE
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>It is not necessary to make the deployment available to media and Pre-Boot Execution Environment (PXE) for a computer refresh, but you will use the same deployment for bare-metal deployments later on and you will need it at that point.
|
||||
|
||||
|
||||
@ -118,7 +118,7 @@ Now you can start the computer refresh on PC0003.
|
||||
|
||||
1. Using the Configuration Manager console, in the Asset and Compliance workspace, in the Install Windows 10 Enterprise x64 collection, right-click **PC0003** and select **Client Notification / Download Computer Policy**. Click **OK**.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>The Client Notification feature is new in Configuration Manager.
|
||||
|
||||
2. On PC0003, using the Software Center (begin using the Start screen, or click the **New software is available** balloon in the system tray), select the **Windows 10 Enterprise x64 RTM** deployment and click **INSTALL**.
|
||||
|
||||
@ -168,7 +168,7 @@ This section assumes that you have a machine named PC0004 with the Configuration
|
||||
|
||||
2. In the **Actions** tab, select the **Machine Policy Retrieval & Evaluation Cycle**, select **Run Now**, and click **OK**.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>You also can use the Client Notification option in the Configuration Manager console, as shown in [Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager](refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md).
|
||||
|
||||
3. Using the Software Center, select the **Replace Task Sequence** deployment and click **INSTALL**.
|
||||
@ -181,7 +181,7 @@ This section assumes that you have a machine named PC0004 with the Configuration
|
||||
|
||||
7. Using the Configuration Manager console, in the Asset and Compliance workspace, select the **User State Migration** node, right-click the **PC0004/PC0006** association, and select **View Recovery Information**. Note that the object now also has a user state store location.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>It may take a few minutes for the user state store location to be populated.
|
||||
|
||||
|
||||
|
||||
@ -53,7 +53,7 @@ Completing these steps will give you a generic Windows To Go drive that can be d
|
||||
|
||||
In this step we are creating the operating system image that will be used on the Windows To Go drives. You can use the Windows To Go Creator Wizard or you can [do this manually](https://go.microsoft.com/fwlink/p/?LinkId=619174) using a combination of Windows PowerShell and command-line tools.
|
||||
|
||||
>[!WARNING]
|
||||
>[!WARNING]
|
||||
>The preferred method to create a single Windows To Go drive is to use the Windows To Go Creator Wizard included in Windows 10 Enterprise and Windows 10 Education.
|
||||
|
||||
#### To create a Windows To Go workspace with the Windows To Go Creator Wizard
|
||||
@ -64,7 +64,7 @@ In this step we are creating the operating system image that will be used on the
|
||||
|
||||
3. Verify that the .wim file location (which can be a network share, a DVD , or a USB drive) is accessible and that it contains a valid Windows 10 Enterprise or Windows 10 Education image that has been generalized using sysprep. Many environments can use the same image for both Windows To Go and desktop deployments.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>For more information about .wim files, see [Windows System Image Manager (Windows SIM) Technical Reference](https://go.microsoft.com/fwlink/p/?LinkId=619150). For more information about using sysprep, see [Sysprep Overview](https://go.microsoft.com/fwlink/p/?LinkId=619151).
|
||||
|
||||
4. Using Cortana, search for **Windows To Go** and then press **Enter**. If the **User Account Control** dialog box appears, confirm that the action it displays is what you want, and then click **Yes**. The **Windows To Go Creator Wizard** opens.
|
||||
@ -76,7 +76,7 @@ In this step we are creating the operating system image that will be used on the
|
||||
7. (Optional) On the **Set a BitLocker password (optional)** page, you can select **Use BitLocker with my Windows To Go Workspace** to encrypt your Windows To Go drive. If you do not wish to encrypt the drive at this time, click **Skip**. If you decide you want to add BitLocker protection later, see [Enable BitLocker protection for your Windows To Go drive](https://go.microsoft.com/fwlink/p/?LinkId=619152) for instructions.
|
||||
r
|
||||
|
||||
>[!WARNING]
|
||||
>[!WARNING]
|
||||
>If you plan to use a USB-Duplicator to create multiple Windows To Go drives, do not enable BitLocker. Drives protected with BitLocker should not be duplicated.
|
||||
|
||||
If you choose to encrypt the Windows To Go drive now:
|
||||
@ -85,13 +85,13 @@ r
|
||||
|
||||
|
||||
~~~
|
||||
>[!IMPORTANT]
|
||||
>[!IMPORTANT]
|
||||
>The BitLocker recovery password will be saved in the documents library of the computer used to create the workspace automatically. If your organization is using Active Directory Domain Services (AD DS) to store recovery passwords it will also be saved in AD DS under the computer account of the computer used to create the workspace. This password will be used only if you need to recover access to the drive because the BitLocker password specified in the previous step is not available, such as if a password is lost or forgotten. For more information about BitLocker and AD DS, see [Active Directory Domain Services considerations](https://go.microsoft.com/fwlink/p/?LinkId=619157).
|
||||
~~~
|
||||
|
||||
8. Verify that the USB drive inserted is the one you want to provision for Windows To Go and then click **Create** to start the Windows To Go workspace creation process.
|
||||
|
||||
>[!WARNING]
|
||||
>[!WARNING]
|
||||
>The USB drive identified will be reformatted as part of the Windows To Go provisioning process and any data on the drive will be erased.
|
||||
|
||||
9. Wait for the creation process to complete, which can take 20 to 30 minutes. A completion page will be displayed that tells you when your Windows To Go workspace is ready to use. From the completion page you can configure the Windows To Go startup options to configure the current computer as a Windows To Go host computer.
|
||||
@ -142,7 +142,7 @@ The following Windows PowerShell cmdlet or cmdlets perform the same function as
|
||||
|
||||
3. Next you need to apply the operating system image that you want to use with Windows To Go to the operating system partition you just created on the disk (this may take 30 minutes or longer, depending on the size of the image and the speed of your USB connection). The following command shows how this can be accomplished using the [Deployment Image Servicing and Management](https://go.microsoft.com/fwlink/p/?LinkId=619161) command-line tool (DISM):
|
||||
|
||||
>[!TIP]
|
||||
>[!TIP]
|
||||
>The index number must be set correctly to a valid Enterprise image in the .WIM file.
|
||||
|
||||
``` syntax
|
||||
@ -225,7 +225,7 @@ W:\Windows\System32\bcdboot W:\Windows /f ALL /s S:
|
||||
|
||||
After the answer file has been saved, copy unattend.xml into the sysprep folder on the Windows To Go drive (for example, W:\\Windows\\System32\\sysprep\)
|
||||
|
||||
>[!IMPORTANT]
|
||||
>[!IMPORTANT]
|
||||
>Setup unattend files are processed based on their location. Setup will place a temporary unattend file into the **%systemroot%\\panther** folder which is the first location that setup will check for installation information. You should make sure that folder does not contain a previous version of an unattend.xml file to ensure that the one you just created is used.
|
||||
|
||||
If you do not wish to boot your Windows To Go device on this computer and want to remove it to boot it on another PC, be sure to use the **Safely Remove Hardware and Eject Media** option to safely disconnect the drive before physically removing it from the PC.
|
||||
@ -238,7 +238,7 @@ Your Windows To Go workspace is now ready to be started. You can now [prepare a
|
||||
|
||||
Computers running Windows 8 and later can be configured as host computers that use Windows To Go automatically whenever a Windows To Go workspace is available at startup. When the Windows To Go startup options are enabled on a host computer, Windows will divert startup to the Windows To Go drive whenever it is attached to the computer. This makes it easy to switch from using the host computer to using the Windows To Go workspace.
|
||||
|
||||
>[!TIP]
|
||||
>[!TIP]
|
||||
>If you will be using a PC running Windows 7 as your host computer, see [Tips for configuring your BIOS settings to work with Windows To Go](https://go.microsoft.com/fwlink/p/?LinkId=618951) for information to help you prepare the host computer.
|
||||
|
||||
|
||||
@ -303,7 +303,7 @@ Making sure that Windows To Go workspaces are effective when used off premises i
|
||||
djoin /provision /domain <exampledomain.com> /machine <examplewindowstogo_workspace_name> /certtemplate <WorkstationAuthentication_template> /policynames <DirectAccess Client Policy: {GUID}> /savefile <C:\example\path\domainmetadatafile> /reuse
|
||||
```
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>The **/certtemplate** parameter supports the use of certificate templates for distributing certificates for DirectAccess, if your organization is not using certificate templates you can omit this parameter. Additionally, if are using djoin.exe with Windows Server 2008-based Domain Controllers, append the /downlevel switch during provisioning. For more information see the [Offline Domain Join Step-by-Step guide](https://go.microsoft.com/fwlink/p/?LinkId=619171).
|
||||
|
||||
2. Insert the Windows To Go drive.
|
||||
@ -350,7 +350,7 @@ Making sure that Windows To Go workspaces are effective when used off premises i
|
||||
|
||||
|
||||
~~~
|
||||
>[!TIP]
|
||||
>[!TIP]
|
||||
>The index number must be set correctly to a valid Enterprise image in the .WIM file.
|
||||
|
||||
``` syntax
|
||||
@ -409,7 +409,7 @@ dism /apply-image /imagefile:n:\imagefolder\deploymentimages\mywtgimage.wim /ind
|
||||
|
||||
* If off premises, join a wired or wireless network with internet access and then sign on again using your domain credentials.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>Depending on your DirectAccess configuration you might be asked to insert your smart card to log on to the domain.
|
||||
|
||||
You should now be able to access your organization’s network resources and work from your Windows To Go workspace as you would normally work from your standard desktop computer on premises.
|
||||
@ -457,7 +457,7 @@ BitLocker recovery keys are the keys that can be used to unlock a BitLocker prot
|
||||
|
||||
4. Provision the Windows To Go drive using the following cmdlets:
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>If you used the [manual method for creating a workspace](https://go.microsoft.com/fwlink/p/?LinkId=619174) you should have already provisioned the Windows To Go drive. If so, you can continue on to the next step.
|
||||
|
||||
``` syntax
|
||||
@ -496,7 +496,7 @@ BitLocker recovery keys are the keys that can be used to unlock a BitLocker prot
|
||||
|
||||
Next you need to apply the operating system image that you want to use with Windows To Go to the operating system partition you just created on the disk (this may take 30 minutes or longer, depending on the size of the image and the speed of your USB connection). The following command shows how this can be accomplished using the [Deployment Image Servicing and Management](https://go.microsoft.com/fwlink/p/?LinkId=619161) command-line tool (DISM):
|
||||
|
||||
>[!TIP]
|
||||
>[!TIP]
|
||||
>The index number must be set correctly to a valid Enterprise image in the .WIM file.
|
||||
|
||||
``` syntax
|
||||
@ -528,12 +528,12 @@ BitLocker recovery keys are the keys that can be used to unlock a BitLocker prot
|
||||
Enable-BitLocker W: -PasswordProtector $spwd
|
||||
```
|
||||
|
||||
>[!WARNING]
|
||||
>[!WARNING]
|
||||
>To have BitLocker only encrypt used space on the disk append the parameter `–UsedSpaceOnly` to the `Enable-BitLocker` cmdlet. As data is added to the drive BitLocker will encrypt additional space. Using this parameter will speed up the preparation process as a smaller percentage of the disk will require encryption. If you are in a time critical situation where you cannot wait for encryption to complete you can also safely remove the Windows To Go drive during the encryption process. The next time the drive is inserted in a computer it will request the BitLocker password. Once the password is supplied, the encryption process will continue. If you do this, make sure your users know that BitLocker encryption is still in process and that they will be able to use the workspace while the encryption completes in the background.
|
||||
|
||||
8. Copy the numerical recovery password and save it to a file in a safe location. The recovery password will be required if the password is lost or forgotten.
|
||||
|
||||
>[!WARNING]
|
||||
>[!WARNING]
|
||||
>If the **Choose how BitLocker-protected removable data drives can be recovered** Group Policy setting has been configured to back up recovery information to Active Directory Domain Services, the recovery information for the drive will be stored under the account of the host computer used to apply the recovery key.
|
||||
|
||||
If you want to have the recovery information stored under the account of the Windows To Go workspace you can turn BitLocker from within the Windows To Go workspace using the BitLocker Setup Wizard from the BitLocker Control Panel item as described in [To enable BitLocker after distribution](#enable-bitlocker).
|
||||
@ -561,7 +561,7 @@ The Windows To Go drives are now ready to be distributed to users and are protec
|
||||
|
||||
4. Complete the steps in the **BitLocker Setup Wizard** selecting the password protection option.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>If you have not configured the Group Policy setting **\\Windows Components\\BitLocker Drive Encryption\\Operating System Drives\\Require additional authentication at startup** to specify **Allow BitLocker without a compatible TPM** you will not be able to enable BitLocker from within the Windows To Go workspace.
|
||||
|
||||
### Advanced deployment sample script
|
||||
|
||||
@ -34,7 +34,7 @@ Device Health is offered as a *solution* which you link to a new or existing [Az
|
||||
|
||||
1. Sign in to the [Azure Portal](https://portal.azure.com) with your work or school account or a Microsoft account. If you don't already have an Azure subscription you can create one (including free trial options) through the portal.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
> Device Health is included at no additional cost with Windows 10 [education and enterprise licensing](https://docs.microsoft.com/windows/deployment/update/device-health-monitor#device-health-licensing). An Azure subscription is required for managing and using Device Health, but no Azure charges are expected to accrue to the subscription as a result of using Device Health.
|
||||
|
||||
2. In the Azure portal select **Create a resource**, search for "Device Health", and then select **Create** on the **Device Health** solution.
|
||||
|
||||
@ -102,7 +102,7 @@ loss of business information, or other pecuniary loss) arising out of the use of
|
||||
or documentation, even if Microsoft has been advised of the possibility of such damages.
|
||||
```
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>If you elect not to override the default setup priority, you will need to increase the [maximum run time](https://docs.microsoft.com/sccm/sum/get-started/manage-settings-for-software-updates#BKMK_SetMaxRunTime) value for Feature Update to Windows 10, version 1709 or higher from the default of 60 minutes. A value of 240 minutes may be required. Remember to ensure that your maintenance window duration is larger than your defined maximum run time value.
|
||||
|
||||
## Manually deploy feature updates
|
||||
@ -133,13 +133,13 @@ Before you deploy the feature updates, you can download the content as a separat
|
||||
- **Description**: Specifies the description of the deployment package. The package description provides information about the package contents and is limited to 127 characters.
|
||||
- **Package source**: Specifies the location of the feature update source files. Type a network path for the source location, for example, \\server\sharename\path, or click **Browse** to find the network location. You must create the shared folder for the deployment package source files before you proceed to the next page.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>The deployment package source location that you specify cannot be used by another software deployment package.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>[!IMPORTANT]
|
||||
>The SMS Provider computer account and the user that is running the wizard to download the feature updates must both have Write NTFS permissions on the download location. You should carefully restrict access to the download location to reduce the risk of attackers tampering with the feature update source files.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>[!IMPORTANT]
|
||||
>You can change the package source location in the deployment package properties after Configuration Manager creates the deployment package. But if you do so, you must first copy the content from the original package source to the new package source location.
|
||||
|
||||
Click **Next**.
|
||||
@ -163,7 +163,7 @@ Before you deploy the feature updates, you can download the content as a separat
|
||||
- **Download software updates from the Internet**: Select this setting to download the software updates from the location on the Internet. This is the default setting.
|
||||
- **Download software updates from a location on the local network**: Select this setting to download software updates from a local folder or shared network folder. Use this setting when the computer running the wizard does not have Internet access.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>When you use this setting, download the software updates from any computer with Internet access, and then copy the software updates to a location on the local network that is accessible from the computer running the wizard.
|
||||
|
||||
Click **Next**.
|
||||
@ -195,15 +195,15 @@ After you determine which feature updates you intend to deploy, you can manually
|
||||
|
||||
- **Type of deployment**: Specify the deployment type for the software update deployment. Select **Required** to create a mandatory software update deployment in which the feature updates are automatically installed on clients before a configured installation deadline.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>[!IMPORTANT]
|
||||
> After you create the software update deployment, you cannot later change the type of deployment.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>A software update group deployed as Required will be downloaded in background and honor BITS settings, if configured.
|
||||
|
||||
- **Use Wake-on-LAN to wake up clients for required deployments**: Specify whether to enable Wake On LAN at the deadline to send wake-up packets to computers that require one or more software updates in the deployment. Any computers that are in sleep mode at the installation deadline time will be awakened so the software update installation can initiate. Clients that are in sleep mode that do not require any software updates in the deployment are not started. By default, this setting is not enabled and is available only when Type of deployment is set to Required.
|
||||
|
||||
>[!WARNING]
|
||||
>[!WARNING]
|
||||
>Before you can use this option, computers and networks must be configured for Wake On LAN.
|
||||
|
||||
- **Detail level**: Specify the level of detail for the state messages that are reported by client computers.
|
||||
@ -211,19 +211,19 @@ After you determine which feature updates you intend to deploy, you can manually
|
||||
|
||||
- **Schedule evaluation**: Specify whether the available time and installation deadline times are evaluated according to UTC or the local time of the computer running the Configuration Manager console.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>When you select local time, and then select **As soon as possible** for the **Software available time** or **Installation deadline**, the current time on the computer running the Configuration Manager console is used to evaluate when updates are available or when they are installed on a client. If the client is in a different time zone, these actions will occur when the client's time reaches the evaluation time.
|
||||
|
||||
- **Software available time**: Select **As soon as possible** to specify when the software updates will be available to clients:
|
||||
- **As soon as possible**: Select this setting to make the software updates in the deployment available to clients as soon as possible. When the deployment is created, the client policy is updated, the clients are made aware of the deployment at their next client policy polling cycle, and then the software updates are available for installation.
|
||||
- **Installation deadline**: Select **Specific time** to specify the installation deadline for the software updates in the deployment.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>You can configure the installation deadline setting only when **Type of deployment** is set to **Required** on the Deployment Settings page.
|
||||
|
||||
- **Specific time**: Select this setting to automatically install the software updates in the deployment at a specific date and time. Set the date and time value to correspond with your defined maintenance window for the target collection. Allow sufficient time for clients to download the content in advance of the deadline. Adjust accordingly if clients in your environment will need additional download time. E.g., slow or unreliable network links.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>The actual installation deadline time is the specific time that you configure plus a random amount of time up to 2 hours. This reduces the potential impact of all client computers in the destination collection installing the software updates in the deployment at the same time. Configure the Computer Agent client setting, Disable deadline randomization to disable the installation randomization delay for the required software updates to allow a greater chance for the installation to start and complete within your defined maintenance window. For more information, see [Computer Agent](https://docs.microsoft.com/sccm/core/clients/deploy/about-client-settings#computer-agent).
|
||||
7. On the User Experience page, configure the following settings:
|
||||
- **User notifications**: Specify whether to display notification of the software updates in Software Center on the client computer at the configured **Software available time** and whether to display user notifications on the client computers. When **Type of deployment** is set to **Available** on the Deployment Settings page, you cannot select **Hide in Software Center and all notifications**.
|
||||
@ -234,7 +234,7 @@ After you determine which feature updates you intend to deploy, you can manually
|
||||
>Suppressing system restarts can be useful in server environments or for cases in which you do not want the computers that are installing the software updates to restart by default. However, doing so can leave computers in an insecure state, whereas allowing a forced restart helps to ensure immediate completion of the software update installation.
|
||||
- **Write filter handling for Windows Embedded devices**: When you deploy software updates to Windows Embedded devices that are write filter enabled, you can specify to install the software update on the temporary overlay and either commit changes later or commit the changes at the installation deadline or during a maintenance window. When you commit changes at the installation deadline or during a maintenance window, a restart is required and the changes persist on the device.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>When you deploy a software update to a Windows Embedded device, make sure that the device is a member of a collection that has a configured maintenance window.
|
||||
- **Software updates deployment re-evaluation behavior upon restart**: Starting in Configuration Manager version 1606, select this setting to configure software updates deployments to have clients run a software updates compliance scan immediately after a client installs software updates and restarts. This enables the client to check for additional software updates that become applicable after the client restarts, and to then install them (and become compliant) during the same maintenance window.
|
||||
8. On the Alerts page, configure how Configuration Manager and System Center Operations Manager will generate alerts for this deployment. You can configure alerts only when **Type of deployment** is set to **Required** on the Deployment Settings page.
|
||||
|
||||
@ -80,7 +80,7 @@ loss of business information, or other pecuniary loss) arising out of the use of
|
||||
or documentation, even if Microsoft has been advised of the possibility of such damages.
|
||||
```
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>If you elect not to override the default setup priority, you will need to increase the [maximum run time](https://docs.microsoft.com/sccm/sum/get-started/manage-settings-for-software-updates#BKMK_SetMaxRunTime) value for Feature Update to Windows 10, version 1709 or higher from the default of 60 minutes. A value of 240 minutes may be required. Remember to ensure that your maintenance window duration is larger than your defined maximum run time value.
|
||||
|
||||
## Manually deploy feature updates in a user-initiated installation
|
||||
@ -111,13 +111,13 @@ Before you deploy the feature updates, you can download the content as a separat
|
||||
- **Description**: Specifies the description of the deployment package. The package description provides information about the package contents and is limited to 127 characters.
|
||||
- **Package source**: Specifies the location of the feature update source files. Type a network path for the source location, for example, \\\server\sharename\path, or click **Browse** to find the network location. You must create the shared folder for the deployment package source files before you proceed to the next page.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>The deployment package source location that you specify cannot be used by another software deployment package.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>[!IMPORTANT]
|
||||
>The SMS Provider computer account and the user that is running the wizard to download the feature updates must both have Write NTFS permissions on the download location. You should carefully restrict access to the download location to reduce the risk of attackers tampering with the feature update source files.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>[!IMPORTANT]
|
||||
>You can change the package source location in the deployment package properties after Configuration Manager creates the deployment package. But if you do so, you must first copy the content from the original package source to the new package source location.
|
||||
|
||||
Click **Next**.
|
||||
@ -141,7 +141,7 @@ Before you deploy the feature updates, you can download the content as a separat
|
||||
- **Download software updates from the Internet**: Select this setting to download the software updates from the location on the Internet. This is the default setting.
|
||||
- **Download software updates from a location on the local network**: Select this setting to download software updates from a local folder or shared network folder. Use this setting when the computer running the wizard does not have Internet access.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>When you use this setting, download the software updates from any computer with Internet access, and then copy the software updates to a location on the local network that is accessible from the computer running the wizard.
|
||||
|
||||
Click **Next**.
|
||||
@ -173,15 +173,15 @@ After you determine which feature updates you intend to deploy, you can manually
|
||||
|
||||
- **Type of deployment**: Specify the deployment type for the software update deployment. Select **Required** to create a mandatory software update deployment in which the feature updates are automatically installed on clients before a configured installation deadline.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>[!IMPORTANT]
|
||||
> After you create the software update deployment, you cannot later change the type of deployment.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>A software update group deployed as **Required** will be downloaded in background and honor BITS settings, if configured.
|
||||
|
||||
- **Use Wake-on-LAN to wake up clients for required deployments**: Specify whether to enable Wake On LAN at the deadline to send wake-up packets to computers that require one or more software updates in the deployment. Any computers that are in sleep mode at the installation deadline time will be awakened so the software update installation can initiate. Clients that are in sleep mode that do not require any software updates in the deployment are not started. By default, this setting is not enabled and is available only when **Type of deployment** is set to **Required**.
|
||||
|
||||
>[!WARNING]
|
||||
>[!WARNING]
|
||||
>Before you can use this option, computers and networks must be configured for Wake On LAN.
|
||||
|
||||
- **Detail level**: Specify the level of detail for the state messages that are reported by client computers.
|
||||
@ -194,7 +194,7 @@ After you determine which feature updates you intend to deploy, you can manually
|
||||
|
||||
- **Installation deadline**: Select **Specific time** to specify the installation deadline for the software updates in the deployment.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>You can configure the installation deadline setting only when **Type of deployment** is set to **Required** on the Deployment Settings page.
|
||||
|
||||
- **Specific time**: Select this setting to automatically install the software updates in the deployment at a specific date and time. However, for the purposes of the fixed servicing window, set the installation deadline date and time to a future value, well beyond the fixed servicing window.
|
||||
@ -204,7 +204,7 @@ After you determine which feature updates you intend to deploy, you can manually
|
||||
7. On the User Experience page, configure the following settings:
|
||||
- **User notifications**: Specify **Display in Software Center and show all notifications**.
|
||||
- **Deadline behavior**: Available only when **Type of deployment** is set to **Required** on the Deployment Settings page. Specify the behavior that is to occur when the deadline is reached for the software update deployment. Specify whether to install the software updates in the deployment. Also specify whether to perform a system restart after software update installation regardless of a configured maintenance window.
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>Remember that the installation deadline date and time will be well into the future to allow plenty of time for the user-initiated install during a fixed servicing window.
|
||||
- **Device restart behavior**: Available only when **Type of deployment** is set to **Required** on the Deployment Settings page. Specify whether to suppress a system restart on servers and workstations after software updates are installed and a system restart is required to complete the installation.
|
||||
|
||||
@ -212,7 +212,7 @@ After you determine which feature updates you intend to deploy, you can manually
|
||||
>Suppressing system restarts can be useful in server environments or for cases in which you do not want the computers that are installing the software updates to restart by default. However, doing so can leave computers in an insecure state, whereas allowing a forced restart helps to ensure immediate completion of the software update installation.
|
||||
- **Write filter handling for Windows Embedded devices**: When you deploy software updates to Windows Embedded devices that are write filter enabled, you can specify to install the software update on the temporary overlay and either commit changes later or commit the changes at the installation deadline or during a maintenance window. When you commit changes at the installation deadline or during a maintenance window, a restart is required and the changes persist on the device.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>When you deploy a software update to a Windows Embedded device, make sure that the device is a member of a collection that has a configured maintenance window.
|
||||
- **Software updates deployment re-evaluation behavior upon restart**: Starting in Configuration Manager version 1606, select this setting to configure software updates deployments to have clients run a software updates compliance scan immediately after a client installs software updates and restarts. This enables the client to check for additional software updates that become applicable after the client restarts, and to then install them (and become compliant) during the same maintenance window.
|
||||
8. On the Alerts page, configure how Configuration Manager and System Center Operations Manager will generate alerts for this deployment. You can configure alerts only when **Type of deployment** is set to **Required** on the Deployment Settings page.
|
||||
|
||||
@ -73,7 +73,7 @@ To enable data sharing, configure your proxy server to whitelist the following e
|
||||
>[!NOTE]
|
||||
>Proxy authentication and SSL inspections are frequent challenges for enterprises. See the following sections for configuration options.
|
||||
|
||||
> [!Important]
|
||||
> [!IMPORTANT]
|
||||
> For privacy and data integrity, Windows checks for a Microsoft SSL certificate when communicating with the diagnostic data endpoints. SSL interception and inspection aren't possible. To use Desktop Analytics, exclude these endpoints from SSL inspection.<!-- BUG 4647542 -->
|
||||
|
||||
|
||||
|
||||
@ -63,7 +63,7 @@ The WU engine has different component names. The following are some of the most
|
||||
- DataStore - Caching update data locally
|
||||
- IdleTimer - Tracking active calls, stopping a service
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>Many component log messages are invaluable if you are looking for problems in that specific area. However, they can be useless if you don't filter to exclude irrelevant components so that you can focus on what’s important.
|
||||
|
||||
### Windows Update log structure
|
||||
|
||||
@ -29,7 +29,7 @@ This flow only enforces the deadline where the device will attempt to silently r
|
||||
|
||||
Once the device is in the pending restart state, it will attempt to restart the device during non-active hours. This is known as the auto-restart period, and by default it does not require user interaction to reboot the device.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>Deadlines are enforced from pending restart state (for example, when the device has completed the installation and download from Windows Update).
|
||||
|
||||
### Policy overview
|
||||
|
||||
@ -47,7 +47,7 @@ Upgrade Readiness is offered as a *solution* which you link to a new or existing
|
||||
|
||||
1. Sign in to the [Azure Portal](https://portal.azure.com) with your work or school account or a Microsoft account. If you don't already have an Azure subscription you can create one (including free trial options) through the portal.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
> Upgrade Readiness is included at no additional cost with Windows 10 Professional, Education, and Enterprise editions. An Azure subscription is required for managing and using Upgrade Readiness, but no Azure charges are expected to accrue to the subscription as a result of using Upgrade Readiness.
|
||||
|
||||
2. In the Azure portal select **Create a resource**, search for "Upgrade Readiness", and then select **Create** on the **Upgrade Readiness** solution.
|
||||
|
||||
@ -28,7 +28,7 @@ The compatibility update that sends diagnostic data from user computers to Micro
|
||||
|
||||
If you need to update user computers to Windows 7 SP1 or Windows 8.1, use Windows Update or download and deploy the applicable package from the Microsoft Download Center.
|
||||
|
||||
> [!NOTE]
|
||||
> [!NOTE]
|
||||
> Upgrade Readiness is designed to best support in-place upgrades. In-place upgrades do not support migrations from BIOS to UEFI or from 32-bit to 64-bit architecture. If you need to migrate computers in these scenarios, use the wipe-and-reload method. Upgrade Readiness insights are still valuable in this scenario, however, you can ignore in-place upgrade specific guidance.
|
||||
|
||||
See [Windows 10 Specifications](https://www.microsoft.com/en-US/windows/windows-10-specifications) for additional information about computer system requirements.
|
||||
|
||||
@ -23,10 +23,10 @@ This topic describes how to install the Volume Activation Management Tool (VAMT)
|
||||
|
||||
You install VAMT as part of the Windows Assessment and Deployment Kit (ADK) for Windows 10.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>[!IMPORTANT]
|
||||
>VAMT requires local administrator privileges on all managed computers in order to deposit confirmation IDs (CIDs), get the client products’ license status, and install product keys. If VAMT is being used to manage products and product keys on the local host computer and you do not have administrator privileges, start VAMT with elevated privileges. For Active Directory-Based Activation use, for best results we recommend running VAMT while logged on as a domain administrator.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>The VAMT Microsoft Management Console snap-in ships as an x86 package.
|
||||
|
||||
### Requirements
|
||||
|
||||
@ -35,7 +35,7 @@ ms.topic: article
|
||||
|
||||
During the activation process, information about the specific installation is examined. In the case of online activations, this information is sent to a server at Microsoft. This information may include the software version, the product key, the IP address of the computer, and information about the device. The activation methods that Microsoft uses are designed to help protect user privacy, and they cannot be used to track back to the computer or user. The gathered data confirms that the software is a legally licensed copy, and this data is used for statistical analysis. Microsoft does not use this information to identify or contact the user or the organization.
|
||||
|
||||
>[!NOTE]
|
||||
>[!NOTE]
|
||||
>The IP address is used only to verify the location of the request, because some editions of Windows (such as “Starter” editions) can only be activated within certain geographical target markets.
|
||||
|
||||
## Distribution channels and activation
|
||||
|
||||
@ -39,7 +39,7 @@ Windows 10, version 1709 is available starting on 10/17/2017 in all relevant dis
|
||||
|
||||
For ISOs that you download from the VLSC or Visual Studio Subscriptions, you can still search for the individual Windows editions. However, each of these editions (Windows 10 Pro, Windows 10 Enterprise, and Windows 10 Education) will point to the same ISO file, so you only need to download the ISO once. A single Windows image (WIM) file is included in the ISO that contains all the volume licensing images:
|
||||
|
||||
|
||||
|
||||
|
||||
When using the contents of these ISOs with tools such as the Microsoft Deployment Toolkit or System Center Configuration Manager, make sure you select the appropriate image index in any task sequences that you create or update.
|
||||
|
||||
@ -66,7 +66,7 @@ This Semi-Annual Channel release of Windows 10 continues the Windows as a servic
|
||||
|
||||
See the following example for Windows 10, version 1709:
|
||||
|
||||
|
||||
|
||||
|
||||
### Features on demand
|
||||
|
||||
|
||||
@ -32,7 +32,7 @@ The Windows Autopilot Reset process automatically retains information from the e
|
||||
|
||||
Windows Autopilot Reset will block the user from accessing the desktop until this information is restored, including re-applying any provisioning packages. For devices enrolled in an MDM service, Windows Autopilot Reset will also block until an MDM sync is completed.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>[!IMPORTANT]
|
||||
>To reestablish Wi-Fi connectivity after reset, make sure the **Connect automatically** box is checked for the device's wireless network connection.
|
||||
|
||||
>[!NOTE]
|
||||
|
||||
Reference in New Issue
Block a user