Error 0x80070490 during PXE Boot

In this post, I will talk about repairing the 0x80070490 error you received when your PXE booting a system to re-image.

The cause of this error is your hard drive is not partition correctly or there is not any available space on the hard drive.  I have notice this error when making my Build & Capture image using a virtual system.

This fix is also good to repair error 0x80070002 and 0x80070570.  Your PXE boot will fail immediately and you will see error 0x80070002 or 0x80070570 in the SMSTS.logs.

Download and view SMSTS.log on a Virtual Machine

This post is about how to download and view the SMSTS.log file when imaging a Virtual Machine.  Viewing the SMST.log file helps you troubleshoot Operating System Deployment (OSD) steps when you run into issues.

Saving the SMSTS.log file on a physical machine is not that difficult because you can just attach a USB jump drive to the physical system and copy the log.  On a virtual machine you don't have this option because its virtual.

The first thing you need to do is "enable command support" on your PXE boot image ( You need to do this for both physical or virtual machines ).

In the SCCM 2012 console open "Software Library / Operating System / Boot Images".  Right click on your PXE boot image and open the "Customization" tab.  Check the "Enable Command Support" check box and click on the "Ok" button to save the change.

Software Updates not Installing during Task Sequence

I am having a problem where software update were not getting installed during the "Install Updates" step in the task sequence.  All the roles on my SCCM 2012 Server are configured correctly for software updates.  Updates are deployed correctly to the correct collection.  I know this because once the system completes imaging the updates that were not installed in the task sequence start downloading and installing automatically.

I was trying to build my gold image by using the default Build & Capture task sequence.  When the task sequence would come to the "Install Updates" step it would stop for about 3-5 minutes but never say downloading or installing updates.  After the 3-5 minutes, it would just go to the next step.  I also checked "Continue on Error" on the "Install Updates" step or the whole task sequence would error out.

This fix will work with any task sequence you create not just Build & Capture.

Create the additions steps like the task sequence pictured below.

By adding multiple "Install Updates" steps in the task sequence all your updates will get installed.  Certain updates depend on other updates before they can get installed.  Also the great amount of updates release will cause the "Install Updates" step to time out.

Importing Device Driver into SCCM 2012

This post will walk you through importing device driver into SCCM 2012 and adding these new drivers into your task sequence for use in operating system deployment

Create a folder named "Drivers" on a network shared to store all device driver in.  You can design your folder tree by device manufacture or by model depending on your needs.  An example is below.

Your going to have to go to the manufactures website and download all the drive that are needed for the model of system your imaging.  You have two options when determining which driver are needed. 

You can first image the device with no drivers and see which one are not included in your version of Windows and download the needed ones. 

Or you can download everything on the website that has driver in the title.

Once everything is downloaded you may have a folder tree as see below.

IMPORTANT NOTE:  Most manufacture usually have the driver packaged in a EXE or installer program.  You need to unzip the files from the packaged EXE file before the can be imported into SCCM 2012