Step by Step configuring and troubleshooting SCCM · PDF file3/14/2016 Step by Step...

3/14/2016 Step by Step configuring and troubleshooting SCCM 2012 R2 OSD deployment

http://www.rickygao.com/stepbystepconfiguringandtroubleshootingsccm2012r2osddeployment/ 1/31

Step by Step configuring and troubleshooting SCCM2012 R2 OSD deployment

The "Step by Step" guides on my blog are getting more and more searched and hit now, whichinspired me to helping more people.configured the software update for automatically deploy the security patch

So guess what’s next?Today I’d like to talk about the OSD deployment in SCCM 2012 R2Let’s getstarted1. DHCPPXE boot require the network adapter to get a local IP address from the DHCPserver, so a working DHCP environment is requiredIn addition, if your DHCP server and WDS serverare the same server, there’s some extra steps you need to enable DHCP option 60If you need PXEbroadcast to a different VLAN, you will need to allow the IP Helpers traffic on the routerYou can find more details for the above two scenarios here

2. Create PXE boundariesSCCM Console>Administration>Overview>Hierarchy Configuration>BoundariesSCCM Console>Administration>Overview>Hierarchy Configuration>BoundaryGroupsSince my lab default boundary is the Active Directory site, which means all of the computer inlocal domain is included. However, a new bare metal machine needed to be deployed is not adomain joint machine, so we have to manually create a boundary based on PXE boot IP addressrange from my DHCP server.If you already have a IP address boundary included the PXE bootdevice, you can ignore this step

http://www.rickygao.com/use-sccm-2012-to-automatically-deploy-the-security-patch/

http://blogs.technet.com/b/system_center_configuration_manager_operating_system_deployment_support_blog/archive/2011/10/14/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx



As you can see from above, I’ve created a new IP address range boundary (based on my DHCP IPaddress range) for my PXE boot computers, and add it into my boundary groups as well3. EnablePXE supportSCCM console>Administration>Distribution Points



Enable PXE support for clientsAllow this distribution point to respond to incoming PXErequestsEnable unknown computer support (optional)If you selected Enable unknown computersupport, any unknown computer, like a new bare metal computer, can PXE boot and deploy the OSDimage, which may has potential security rickIf you disable this option, you can using “ImportComputer Information” to prestage your computer for the OSD deployment.SCCM console>Assetsand Compliance>Devices>Import Computer Information



4. WDS (Windows Deployment Service)WDS server role is required for OSD, unlike SCCM 2007,start from SCCM 2012, Microsoft add the ability to install WDS server role for the Distribution Pointserver automatically, It is always recommended to let SCCM to install the WDS for you since I sawsome people has problem when they manually installed the WDS role.Once it’s installed, let’s checkthe option in WDS

Make sure “Respond to all client computers (known and unknown)” is selected. I had this issue whenI enable the PXE boot, SCCM installed the WDS but leave here to “Do not respond to any clientcomputer”



That’s all we need to do with WDS, and we can just let SCCM to handle it from now on.5. NetworkAccess AccountSCCM Console>Administration>Site Configuration>Site>Your Site>Configure SiteComponents>Software DistributionThe Network Access Account is the account used to access yourshared folders and files on DP server which is a domain joint server, so we have to create adedicated domain account with read privilege to access those shared folder



6. Add Drivers (optional)SCCM Console>Software Library>Operating Systems>DriversYou canimport drivers which can be injected into your boot image or system image later7. Add DriverPackage (optional)A driver package is where all of the drivers files located8. Add Operating SystemImagesThis is the place where you can add the Operating System Image files (.wim) need to bedeployedExtract your Windows installation .iso file and located the install.wim (undersources\install.wim)



Distribute the OS image



9. Add Operating System InstallersThis is the place where all of your OS files you extract to

Distribute the OS installer



10. Boot ImagesThe default boot images came from SCCM can work well, but we still need to enablethe command support for troubleshooting purpose, which means we can hit F8 key to call up thecommand line and using CMtrace.exe (Trace32.exe in SCCM2007) to read the logs during thedeployment.

Enable “Deploy this boot image from the PXEenabled distribution point” as well



Don’t forget to distribute the boot images out

11. Configuration Manager client upgrade packageThe default Configuration Manager clientpackage is fine for a lab environment, but it’s not that flexible for hierarchy environment.



As you can see above, most of the settings are greyed out, which means you cannot "Copy thecontent in this package to a package share on distribution points"So we have to create a configurableclient package:SCCM console>Software Library>Application Management>Packages>Create fromDefinition



Select "Configuration Manager Client Upgrade" and then choose "Always obtain source files from asource folder", locate the SCCM client folder





12. Create Task SequencesSo up until this point, everything is ready to create our first tasksequence.Some people always confused about why we have to create a “Build and Capture” task sequencefirst, and then build create the real OS deployment task sequence

This is because the “Build and Capture” will build a bare metal machine as a golden computer, youcan make any changes you want on this OS and recapture it to your SOE image, then update theOS deployment task sequence, deploy it out.Build and Capture (optional)SCCM Console>SoftwareLibrary>Operating Systems>Task Sequences>Create Task Sequence

Name it and select a boot image



I’m going to build and capture a Windows 8.1 reference computer



Do not join your reference computer to the domain since it’s your SOE



Install the SCCM client package we created earlier:Microsoft Configuration Manager Client Upgrade6.0 ALLConfigure the MP (Management Point) server FQDN: SMSMP=SCCM.lab.RickyGao.com



Include Updates:Do not install any software updates since we can inject the patches later in tasksequenceInstall Application:Do not install any software updates since we can inject the applicationlater in task sequenceCapture Image:Specify the image path for your capture image



Distribute the task sequence outDeploy the task sequence to a specific computer collectionSince Idon’t have a computer account prestage in SCCM as I mentioned before, my bare metal computerwill be in “All Unknown Computers” collection





Available and RequiredAvailable means user either need to press F12 button during boot or run thetask sequence from the software centerRequired means when the computer boot up from the PXE, itstart running the task sequence straight away.Make available to the followingOnly ConfigurationManger Client: only available in software centerConfiguration Manger clients, media and PXE:available in software center, boot media or PXE bootOnly media and PXE: available in boot media and PXE boot

Only media and PXE (hidden): available in boot media and PXE boot but hidden13. PXE boot VM inHyperVOnly “Legacy Network Adapter” is supported in generation 1 VM



As you can see above, I got 2 NIC but only Legacy NIC is available for bootIf you have WindowsServer 2012 R2 Hyperv, you can use generation 2 VM which support PXE boot from the new NICadapter with the support gigabyte NIC



Boot your computerHit F12





It’s loading my Boot image (x64) now

You can protect access the task sequence by password, just go back to step 2, PXE setting, and setthe password there



Select the task sequence you want to deploy



Once it’s finished, you will see your captured image in your specified locationImport the capturedimage and distribute it out

14. Deploy your operating system imagesFinally it’s time we can deploy the OS images.The reasonwhy I mentioned the “Build and Capture” process above is optional is that if we don’t want customizethe operating system in that reference machine, just want to deploy a new OS via PXE like we installOS using the installation disc, we can just skip the “Build and Capture” stage, deploy the originalWindows image straight awayCreate a new task sequence>Install and existing image package



Here we can select either use the image we just captured, or just select the image from the originalinstallation disk.If you selected the image we just captured, then we will deploy our target machinebased on our reference computerIf you selected the original install.wim from the installation disc, wewill just deploy the target machine like factory defaultI’m going to deploy an original image from theinstallation disc this time



15. TroubleshootingWhen we are doing the troubleshooting in OSD, the most useful tool we areusing is to use CMTrace.exe (Trace32.exe) to check the log file smsts.log in differentlocationsWindowsPE, before HDD format: x:\windows\temp\smstslog\smsts.logWindowsPE, after HDD format: x:\smstslog\smsts.logWindows, SCCM agent not installed: c:\_SMSTaskSequence\Logs\Smstslog\smsts.logWindows, SCCM agent installed: c:\windows\system32\ccm\logs\Smstslog\smsts.logWindows x64, SCCM agent installed: c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.logTask Sequence completed: c:\windows\system32\ccm\logs\smsts.logTask Sequence completed x64: c:\windows\sysWOW64\ccm\logs\smsts.logUnfortunately, we have to memorize all of the locations ifyou want to boost your efficiency1). distmgr.logRecords details about package creation, compression,delta replication, and information updates.When you distribute content, this log is really useful2).SMSPXE.logRecords details about the responses to PXE boot clients and details about expansion ofboot images and boot files3). The specified UNC path does not contain a valid WIM file or you do nothave permission to access it. Specify a valid pathThis is because SCCM doesn’t accept administrative share when you importing the OS image

http://www.rickygao.com/sccm-import-os-image-error-with-administrative-share/



4). WINPE load failed and keep rebooting after it loaded up This is probably because of low memoryhas been allocated if you are using VM, 512MB may cause this issue, usually at least 1GB, better2GB for a VM When you are using the dynamic memory, low startup memory may trigger this issueas well.5). 0x800705AF error during the first time PXE bootFailed to create sharedenvironment)Failed to create the Shared Environment object. Code(0x800705AF)

This is still because insufficient memory16. Advanced MDT boot image (optional)17. Advanced MDTtask sequence (optional)I will have a separate post regarding to 16 and 17Author: rickygao on March 13, 2014



Category: SCCM, Tech

http://www.rickygao.com/category/sccm/

http://www.rickygao.com/category/tech/

Date post:	06-Mar-2018
Category:	Documents
Upload:	dangkiet
View:	272 times
Download:	10 times

Step by Step configuring and troubleshooting SCCM · PDF file3/14/2016 Step by Step...

Documents