mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 18:33:43 +00:00
fixing more note/important/tip/warning space issues
This commit is contained in:
Liza Poggemeyer
@ -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,8 @@ 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 +161,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 +380,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 +461,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 +474,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 +485,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 +496,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
|
||||
@ -523,7 +524,7 @@ So, what are these settings?
|
||||
|
||||
- **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.
|
||||
|
||||
|
||||
|
||||
@ -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
|
||||
|
||||
Reference in New Issue
Block a user