mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 10:53:43 +00:00
fixing more note/important/tip/warning space issues
This commit is contained in:
Liza Poggemeyer
@ -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
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user