deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 21:37:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

fix bulleted lists; notes

Browse Source
This commit is contained in:
Jan Backstrom 2016-10-17 16:37:34 -07:00
parent 50da42cd6f
commit 9d4bdec3d2
2 changed files with 36 additions and 42 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
windows/deploy/create-a-custom-windows-pe-boot-image-with-configuration-manager.md
View File

@ -47,10 +47,8 @@ By using the MDT wizard to create the boot image in Configuration Manager, you g
2. On the **Package Source** page, in the **Package source folder to be created (UNC Path):** text box, type **\\\\CM01\\Sources$\\OSD\\Boot\\Zero Touch WinPE x64** and click **Next**. 2. On the **Package Source** page, in the **Package source folder to be created (UNC Path):** text box, type **\\\\CM01\\Sources$\\OSD\\Boot\\Zero Touch WinPE x64** and click **Next**.
**Note**   >[!NOTE]
The Zero Touch WinPE x64 folder does not yet exist. The folder will be created later by the wizard. >The Zero Touch WinPE x64 folder does not yet exist. The folder will be created later by the wizard.
 
3. On the **General Settings** page, assign the name **Zero Touch WinPE x64** and click **Next**. 3. On the **General Settings** page, assign the name **Zero Touch WinPE x64** and click **Next**.
@ -58,16 +56,14 @@ By using the MDT wizard to create the boot image in Configuration Manager, you g
5. On the **Components** page, in addition to the default selected **Microsoft Data Access Components (MDAC/ADO)** support, select the **Microsoft Diagnostics and Recovery Toolkit (DaRT)** check box. 5. On the **Components** page, in addition to the default selected **Microsoft Data Access Components (MDAC/ADO)** support, select the **Microsoft Diagnostics and Recovery Toolkit (DaRT)** check box.
![figure 15](images/mdt-06-fig16.png) ![Add the DaRT component to the Configuration Manager boot image](images/mdt-06-fig16.png "Add the DaRT component to the Configuration Manager boot image")
Figure 15. Add the DaRT component to the Configuration Manager boot image. Figure 15. Add the DaRT component to the Configuration Manager boot image.
6. On the **Customization** page, select the **Use a custom background bitmap file** check box, and in the **UNC path:** text box, browse to **\\\\CM01\\Sources$\\OSD\\Branding\\ ContosoBackground.bmp**. Then click **Next** twice. 6. On the **Customization** page, select the **Use a custom background bitmap file** check box, and in the **UNC path:** text box, browse to **\\\\CM01\\Sources$\\OSD\\Branding\\ ContosoBackground.bmp**. Then click **Next** twice.
**Note**   >[!NOTE]
It will take a few minutes to generate the boot image. >It will take a few minutes to generate the boot image.
 
7. Distribute the boot image to the CM01 distribution point by selecting the **Boot images** node, right-clicking the **Zero Touch WinPE x64** boot image, and selecting **Distribute Content**. 7. Distribute the boot image to the CM01 distribution point by selecting the **Boot images** node, right-clicking the **Zero Touch WinPE x64** boot image, and selecting **Distribute Content**.
@ -75,9 +71,9 @@ By using the MDT wizard to create the boot image in Configuration Manager, you g
9. Using Configuration Manager Trace, review the E:\\Program Files\\Microsoft Configuration Manager\\Logs\\distmgr.log file. Do not continue until you can see that the boot image is distributed. Look for the line that reads STATMSG: ID=2301. You also can view Content Status in the Configuration Manager Console by selecting **the Zero Touch WinPE x86** boot image. 9. Using Configuration Manager Trace, review the E:\\Program Files\\Microsoft Configuration Manager\\Logs\\distmgr.log file. Do not continue until you can see that the boot image is distributed. Look for the line that reads STATMSG: ID=2301. You also can view Content Status in the Configuration Manager Console by selecting **the Zero Touch WinPE x86** boot image.
![figure 16](images/fig16-contentstatus.png) ![Content status for the Zero Touch WinPE x64 boot image](images/fig16-contentstatus.png "Content status for the Zero Touch WinPE x64 boot image")
Figure 16. Content status for the Zero Touch WinPE x64 boot image. Figure 16. Content status for the Zero Touch WinPE x64 boot image
10. Using the Configuration Manager Console, right-click the **Zero Touch WinPE x64** boot image and select **Properties**. 10. Using the Configuration Manager Console, right-click the **Zero Touch WinPE x64** boot image and select **Properties**.

60
windows/deploy/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md
View File

@ -49,25 +49,25 @@ To configure permissions for the various service accounts needed for operating s
2. Select the Service Accounts OU and create the CM\_JD account using the following settings: 2. Select the Service Accounts OU and create the CM\_JD account using the following settings:
1. Name: CM\_JD * Name: CM\_JD
2. User logon name: CM\_JD * User logon name: CM\_JD
3. Password: P@ssw0rd * Password: P@ssw0rd
4. User must change password at next logon: Clear * User must change password at next logon: Clear
5. User cannot change password: Select * User cannot change password: Select
6. Password never expires: Select * Password never expires: Select
3. Repeat the step, but for the CM\_NAA account. 3. Repeat the step, but for the CM\_NAA account.
4. After creating the accounts, assign the following descriptions: 4. After creating the accounts, assign the following descriptions:
1. CM\_JD: Configuration Manager Join Domain Account * CM\_JD: Configuration Manager Join Domain Account
2. CM\_NAA: Configuration Manager Network Access Account * CM\_NAA: Configuration Manager Network Access Account
![figure 6](images/mdt-06-fig06.png) ![figure 6](images/mdt-06-fig06.png)
@ -93,39 +93,37 @@ In order for the Configuration Manager Join Domain Account (CM\_JD) to join mach
3. The Set-OUPermissions.ps1 script allows the CM\_JD user account permissions to manage computer accounts in the Contoso / Computers / Workstations OU. The following is a list of the permissions being granted: 3. The Set-OUPermissions.ps1 script allows the CM\_JD user account permissions to manage computer accounts in the Contoso / Computers / Workstations OU. The following is a list of the permissions being granted:
1. Scope: This object and all descendant objects * Scope: This object and all descendant objects
2. Create Computer objects * Create Computer objects
3. Delete Computer objects * Delete Computer objects
4. Scope: Descendant Computer objects * Scope: Descendant Computer objects
5. Read All Properties * Read All Properties
6. Write All Properties * Write All Properties
7. Read Permissions * Read Permissions
8. Modify Permissions * Modify Permissions
9. Change Password * Change Password
10. Reset Password * Reset Password
11. Validated write to DNS host name * Validated write to DNS host name
12. Validated write to service principal name * Validated write to service principal name
## <a href="" id="sec03"></a>Review the Sources folder structure ## <a href="" id="sec03"></a>Review the Sources folder structure
To support the packages you create in this section, the following folder structure should be created on the Configuration Manager primary site server (CM01): 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. >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 - E:\\Sources
@ -168,9 +166,9 @@ To extend the Configuration Manager console with MDT 2013 Update 2 wizards and t
5. From the Start screen, run Configure ConfigManager Integration with the following settings: 5. From the Start screen, run Configure ConfigManager Integration with the following settings:
1. Site Server Name: CM01.contoso.com * Site Server Name: CM01.contoso.com
2. Site code: PS1 * Site code: PS1
![figure 8](images/mdt-06-fig08.png) ![figure 8](images/mdt-06-fig08.png)
@ -221,15 +219,15 @@ Configuration Manager has many options for starting a deployment, but starting v
3. In the **PXE** tab, select the following settings: 3. In the **PXE** tab, select the following settings:
1. Enable PXE support for clients * Enable PXE support for clients
2. Allow this distribution point to respond to incoming PXE requests * Allow this distribution point to respond to incoming PXE requests
3. Enable unknown computer support * Enable unknown computer support
4. Require a password when computers use PXE * Require a password when computers use PXE
5. Password and Confirm password: Passw0rd! * Password and Confirm password: Passw0rd!
![figure 12](images/mdt-06-fig13.png) ![figure 12](images/mdt-06-fig13.png)