SCCM Image Troubleshooting

1.    Purpose

The purpose of this document is to outline the troubleshooting steps taken to remedy some problems that might occur while re-imaging student and/or staff laptops or desktop computers.

2.    Assumptions

This document makes the following assumptions;

  • You have access to CMTrace.exe.
  • All hardware faults have been rectified.
  • The machine is running in UEFI with secure boot turned off.
  • You understand what PXE (Preboot Execution Environment) Booting is.
  • You understand what WinPE (Windows Reinstallation Environment) is.
  • You understand what OSD (Operating System Deployment) is.

3.    Common Issues

 

3.1  Can’t find log file paths during an image or after build is complete

The purpose of the SMSTS.log file is to record successful and failed events during a re-image. When you re-image the SMSTS.log log file will move around. This log file can be found in these locations when;

Phase Path
WinPE, before HDD format X:\Windows\temp\smstslog\smsts.log
 WinPE, after HDD format Copied to C:\_SMSTaskSequence\Logs\Smsts\smsts.log
Full version windows, before SCCM agent is installed C:\_SMSTaskSequence\Logs\Smstslog\smsts.log
Full OS, after SCCM agent is installed %windir%\system32\ccm\logs\Smstslog\smsts.log or %windir%\sysWOW64\ccm\logs\Smstslog\smsts.log (64-bit)
Full OS, build complete %windir%\system32\ccm\logs\smsts.log or %windir%\sysWOW64\ccm\logs\smsts.log (64-bit)

 

3.2  Can’t get into F8 command shell support while in OSD

All images during the WinPE stage of imaging has access to the command shell by pressing F8. Once the build begins and loads into OSD this menu is not accessible.

3.3 Failed to run task-sequence (0x80070032)

Cause

There is no valid file system either because the target is corrupt, encrypted or unformatted. The task requires SCCM to COPY the WinPE files to C: i.e. you must have an NTFS partition as a pre-requisite.

            Fix

To fix this issue perform the following steps in WinPE just after its booted from PXE;

  1. Press F8 to open command shell
  2. Type the following disk part commands

Diskpart

list disk

select disk 0

create part primary

format fs=ntfs quick

assign letter=c

active

exit

exit

  1. Reboot the computer and try imaging again.

3.3  The parameter is incorrect. Error 0×80070057

Cause

There are no writeable volumes. Potentially the local disk is unavailable, offline or faulty.

            Fix

Use disk part to see if there are any devices being detected while in WinPE. If this fails perform hard disk diagnostics and determine if the drive is functioning correctly.

3.4  The task-sequence has failed with Error: 0x80070070

Cause

The partition is too small for the build. On a new OEM machine the Task Sequence will default to install to the machine’s super secret OEM partition, which is 1GB at best, so the SOE will not fit on this partition. You may have the 100MB BitLocker partition present instead.

            Fix

The machine has not been formatted. Format the machine with Disk part and try again.

3.5  The directory is not empty. Error 0x80070091

Cause

Once I somehow managed to allow the Task Sequence to write a logfile to C: whilst trying to wipe it at the same time.

            Fix

My fix was simply to reboot, but as a general issue if SCCM cannot wipe the target disk because of corrupt files or illegal filenames, use “diskpart clean” and then re-run the deployment.

3.6  Element not found. Error 0x80070490

Cause

The C drive is not formatted (or is encrypted) so SCCM cannot create logs, the task sequence or stage WinPE.

Symptom 1: if you open shell and try changing drive to C: you get: “The volume does not contain a recognised file system..”

Symptom 2: Unable to find a volume that is suitable for staging the boot image. Element not found.

            Fix

  1. Open a shell (F8)
  2. Format c: /q

Don’t wipe the drive with “clean”! Format C will leave the other partitions (e.g. D: or whatever you have) intact.

Alternate CAUSE: The BIOS has set the HDD in RAID mode and the WinPE boot image has no suitable driver to even wipe the disk.

3.7  Image has failed with the Error: 0x800700A1

Cause

No C: partition exists OR the disk is RAW.

            Fix

Disk part has not run correctly. Perform the following steps;

  1. Press F8 to open command shell
  2. Type the following disk part commands

Diskpart

list disk

select disk 0

create part primary

format fs=ntfs quick

assign letter=c

active

exit

exit

  1. Reboot the computer and try imaging again.

3.8  Error: 0x80042413; source: unknown

Cause

Trying to format disk 0, partition 0, whilst using it at same time is generally not a good idea! Diskpart quits with error 2147755027

Fix

The disk will be corrupt now, so use diskpart clean. Format c: is not enough this time.

3.9  Failed to run Task Sequence (unknown host). Error: 0x80072EE7

Cause

The machine cannot talk to the SCCM server because of a network issue of some kind.

Fix

Plug in a different Ethernet cable and/ or USB ethernet adapter if no on board nic, check over network settings shown with IPCONFIG /all. Check to see if you can ping SPCM.

3.10 The system cannot find the file specified. Error: 0x80070002

Symptom:

Unknown host (gethostbyname failed) repeatedly appears in the log file.

Cause:

SCCM can’t find any source path to a file because there’s no network driver loaded/installed in the WinPE boot image.

Fix:

If “restart computer (reboot to WinPE)” hangs, it’s also because there’s no network driver. It’s waiting for WinPE to download but it can’t so just sits there.

3.11 The specified domain either does not exist or could not be contacted. Error: 0x8007054B

Cause:

Failed to join the domain

Fix:

Check the user account or the domain or that you installed network drivers *cough*.

3.12 Failed to run command line Error: 0x8007010B

Cause:

A file/dir is bad or missing. (The directory name is invalid.)

Fix:

Rebuild your build media as a write error or crash has resulted in not all packages being correct.

3.13 Error: 0x800700002

Cause:

SCCM can’t read the file in sms\data\policy.xml

Fix:

Rebuild the build media or copy policy.xml from known good media (USB/DVD) or set in tsbootstrap.ini’s mediatype=Bootmedia if you only want to boot and build from LAN.

3.14 WARNING – This Machine is not set to UEFI in the BIOS – The next step will shutdown this computer. Try again once this setting is set.

Cause

The machines BIOS is currently set in LEGACY BIOS setting.

Fix

Reboot the machine and go into the BIOS. Change legacy mode to UEFI mode. Ensure that Secure Boot is also turned off.

3.15 No task sequences are being displayed.

Cause

The machine either has an expired hostname, is doubled up in SCCM or is not part of a device collection with advertised task sequences.

Fix

Search for the hostname in SCCM and see if there is a double up. If there is a double up delete both. Try again and see if this resolves the issue. If this does not escalate to Systems Administrator.

3.16 Office 365 is not streaming or has come up with a connection error

Cause

The machine does not have unfiltered access to the internet. Potentially not connecting to the required Microsoft servers to download office files.

Fix

Verify the network connection. Use IPCONFIG to see if you are still connecting to the imaging vlan. You should have a host ip of 192.168.75.x .

See if you can ping Microsoft.com and get a response back.

Restart the image and try again.

3.17 Start menu is not working and/or upon logging in you have a black screen

Cause

The machine has not been imaged properly and has failed to write the start menu logic to display the layout of the start menu as customised by SPC.

The task sequence has failed to remove temporary files and folders and has failed part way through the image.

There is existing files still present even after a format of the machines drive.

Join the domain as failed and has prevented a successful build.

Fix

Retry the image again. Replace network cable and/ or if using a USB network adapter try another one.

Complete a format before the image starts. Restart the imaging process again.

If the above steps don’t work, remove from machine from Active Directory and retry the image again.

3.18 WiFi not connecting once logged into the student/ staff account

Cause

When logging into the machine, the device fails to connect to the “SPC” ssid.

Fix

There are no User or Device groups assign to the user account of the device itself. Check in Active Directory under Member of and verify that the right groups are added.

3.19 Software Center is not opening up after a re-image

            Cause

After logging into a user’s account Software Center is not able to open up and is presenting an error explaining there are no connection servers available.

Fix

Patience, after a re-image each device has to go through a Phone Home cycle for SCCM to collect device information, software information and user state. This can take anywhere from 5 minutes to 1 hour. Best fix for this scenario is to leave the machine for an hour or so and come back to it again later.

If you still find that Software Center perform a re-image. It is in this scenario that the image may have failed.

3.20 Software Center has installed the old Software Center

Cause

Upon opening up Software Center the older version of SC loads. It has also not found the PAT site code.

Fix

Again, patience. During the initialisation of the client, it still installed the older version as part of the SCCM Client install. Once it finalises this installation it then removes it and the new version slots into its place. The reason why you might see this are in scenarios where you have click on SC to soon, or you are working on an older machine with slow performance. Example: slow mechanical hard drive or slow processor.