So lets say you’ve accidentally delete one or both Boot images from OSD in Configuration manager console and want to add them back.
When you delete the image in the console the default image file is still located on the SCCM server.
So here are the steps to add Boot image back:
1. Open Configuration manager console. Navigate to Site Database>Computer Management>Operating System Deployment>Boot images. Click on Add Boot Image
Add Boot Image Package Wizard will start
Continue reading ‘SCCM: Adding deleted Boot image’
Here are my finding why updates cannot be deployed to the clients.
As you probably know in order for SCCM to install updates it has to know what updates are already installed. ‘Software updates scan cycle’ action is responsible for scanning the machine and checking what updates installed and what are missing. If this action cannot be performed or fails it will display unknown deployment status in SCCM Software Updates. (see image image below)
Continue reading ‘SCCM: One of the reasons why clients report as unkown in Software updates’
Although I’ve seen this problem mentioned on many forums I’ve never got it myself. Here is a solution from SCCM support team for those who did. ConfigMgr 2007: Dell Latitude E6400 laptop hangs during Windows XP Mini-Setup
To troubleshoot SCCM OSD problems it is very handy to have Command console enabled. Basically what it does, it gives you a command prompt in WinPE. This allows you to do basic troubleshooting but the main thing for me is that it allows me to copy Task Sequence log file to USB drive, so I can check it for errors.
To enable this feature open Configuration Manager Console Continue reading ‘SCCM: How to enable Command console in WinPE’
When deploying image to the machine you receive the following error:
An error occurred while starting the task sequence (0×80070032).
The task sequence start running fine. It creates the partition, formats it and fails straight away when it starts applying the image.
Looking at the smsts.log file you can see the following: Continue reading ‘SCCM: An error occured while starting the task sequence (0×80070032)’
The new Dell E6400 gives some troubles while trying to OSD it. The drivers provided by Dell does not work. You can import XP drivers but not Vista. SCCM WinPE is based on Vista so you’ll need Vista drivers. without drivers the system will boot to WinPE but then it will restart.
The correct drivers can be found on Intel website.
Download both 32 and 64 bit drivers.
Once downloaded extract PRO1000 folder from both files. I used WinRar for that.
Place these to folder somewhere where your SCCM server could access them and import them to SCCM. Yuo can read on importing drivers here. You don’t have to create driver package. The only thing you need is to add the drivers to Boot images and update distribution points.
So you are trying to OSDnew machine using SCCM. The machine boots from PXE and starts loading WinPE. You see WinPE SCCM background image with a window ‘Windows is starting up‘ after that you briefly see message ‘Preparing network connection‘. The message disappears and you only see the background, and then system reboots.
In the task sequence log file smsts.log you find the error messages:
Failed to download pxe variable file. Code(0×00000001)
PxeGetPxeData failed with 0×80004005
This means that WinPE Boot image does not have required network card(NIC) driver in order to access SCCM servers.
To solve the problem, you have to download NIC drivers and add them to Boot image. I have created a separate post how to do that.
First do the following:
a. Download and extract the drivers to a network share
b. Create a network share that will be used for drivers storage.(I’ve created this on one of the SCCM servers)
Once you have the thing above you can Open Configuration Manager Console
1. Go to Computer Management>Operating Systems Deployment>Drivers
2. Now you can right click on Drivers and choose import but I would recommend first to create some kind of folder structure(like model\device) as this will make things easier in the future. Once you have folders created right click on it and select Import.
Continue reading ‘SCCM: How to Import Drivers, create driver packages and add them to WinPE boot images’
During image capture process you receive the following error:
Image Capture Wizard has failed with error code (0×80070020). For more information, please contact your system administrator or helpdesk operator.
This error might appear at any time during the image capture procedure.
In the smsts.log the following messaged error are logged:
Failed to run the action: Capture the Reference Machine.
The process cannot access the file because it is being used by another process. (Error: 80070020; Source: Windows)
The execution of the group (Capture the Reference Machine) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Capture the Reference Machine. Execution of task sequence failed.
The process cannot access the file because it is being used by another process. (Error: 80070020; Source: Windows)
As you can see from the error messages the problem is caused by inaccessible file. In my case capture wizard could not access the files located in HP restore partition. Because restore partinion was not needed l I’ve deleted it and image capture ran OK.
Continue reading ‘SCCM: Adding deleted Boot image’
