SCCM Failure to Image

[Gongalong]

Hi folks,

 

I've got around 300 PCs that I'm looking to reimage over the hols. Last year we used SCCM in anger, reimaging the same number of PCs from Win 7 to 10. The actual imaging ran fine, and I was able to deploy to the CM client rather than PXE booting.

 

Ironically this time around it's not working as well. For example I have tried to reimage a classroom of 28 PCs, and only a handful imaged. The rest seemingly did nothing, but I see these errors in the SMSTS.log:

 

Volume '\\?\Volume{1fc8bd7a-f18d-4abf-b5f5-09e7e0538aa7}\' not found TSManager 06/08/2018 12:35:25 17460 (0x4434)

BackupEfiBoot: Z:\, C:\_SMSTaskSequence\backup-EFI TSManager 06/08/2018 12:35:25 17460 (0x4434)

Failed to copy Z:\EFI\Microsoft\Boot\BCD to C:\_SMSTaskSequence\backup-EFI\EFI\Microsoft\Boot\BCD. 0x80070020 TSManager 06/08/2018 12:35:26 17460 (0x4434)

Failed to copy Z:\EFI\Microsoft\Boot\BCD.LOG to C:\_SMSTaskSequence\backup-EFI\EFI\Microsoft\Boot\BCD.LOG. 0x80070020 TSManager 06/08/2018 12:35:26 17460 (0x4434)

BcdBackup: C:\_SMSTaskSequence\BCD-EFI\bcd TSManager 06/08/2018 12:35:26 17460 (0x4434)

Executing command line: "bcdedit.exe" /export C:\_SMSTaskSequence\BCD-EFI\bcd TSManager 06/08/2018 12:35:26 17460 (0x4434)

Process completed with exit code 0 TSManager 06/08/2018 12:35:26 17460 (0x4434)

TSUEFIDrive: TSManager 06/08/2018 12:35:26 17460 (0x4434)

Staging boot image S0100005 TSManager 06/08/2018 12:35:26 17460 (0x4434)

Volume '\\?\Volume{1fc8bd7a-f18d-4abf-b5f5-09e7e0538aa7}\' not found TSManager 06/08/2018 12:35:26 17460 (0x4434)

Boot Image not found in local data cache at 'C:\_SMSTaskSequence\WinPE\sources\boot.wim'. Staging is required TSManager 06/08/2018 12:35:26 17460 (0x4434)

 

And later...

 

Failed to install boot image.

Unspecified error (Error: 80004005; Source: Windows) TSManager 06/08/2018 12:35:32 17460 (0x4434)

Failed to install boot image S0100005.

Unspecified error (Error: 80004005; Source: Windows) TSManager 06/08/2018 12:35:32 17460 (0x4434)

Failed to reboot the system. Error 0x80004005) TSManager 06/08/2018 12:35:32 17460 (0x4434)

Failed to initialize a system reboot.

Unspecified error (Error: 80004005; Source: Windows) TSManager 06/08/2018 12:35:32 17460 (0x4434)

Fatal error is returned in check for reboot request of the action (Restart in Windows PE).

Unspecified error (Error: 80004005; Source: Windows) TSManager 06/08/2018 12:35:32 17460 (0x4434)

An error (0x80004005) is encountered in execution of the task sequence TSManager 06/08/2018 12:35:32 17460 (0x4434)

Set authenticator in transport TSManager 06/08/2018 12:35:32 17460 (0x4434)

Task Sequence Engine failed! Code: 80004005 TSManager 06/08/2018 12:35:32 17460 (0x4434)

**************************************************************************** TSManager 06/08/2018 12:35:32 17460 (0x4434)

Task sequence execution failed with error code 80004005 TSManager 06/08/2018 12:35:32 17460 (0x4434)

 

 

Any ideas what's wrong? Am I better just to PXE boot these machines instead?

 

Thanks

[kevin_lane]

Hi folks,

 

I've got around 300 PCs that I'm looking to reimage over the hols. Last year we used SCCM in anger, reimaging the same number of PCs from Win 7 to 10. The actual imaging ran fine, and I was able to deploy to the CM client rather than PXE booting.

 

Ironically this time around it's not working as well. For example I have tried to reimage a classroom of 28 PCs, and only a handful imaged. The rest seemingly did nothing, but I see these errors in the SMSTS.log:

 

Volume '\\?\Volume{1fc8bd7a-f18d-4abf-b5f5-09e7e0538aa7}\' not foundTSManager06/08/2018 12:35:2517460 (0x4434)

BackupEfiBoot: Z:\, C:\_SMSTaskSequence\backup-EFITSManager06/08/2018 12:35:2517460 (0x4434)

Failed to copy Z:\EFI\Microsoft\Boot\BCD to C:\_SMSTaskSequence\backup-EFI\EFI\Microsoft\Boot\BCD. 0x80070020TSManager06/08/2018 12:35:2617460 (0x4434)

Failed to copy Z:\EFI\Microsoft\Boot\BCD.LOG to C:\_SMSTaskSequence\backup-EFI\EFI\Microsoft\Boot\BCD.LOG. 0x80070020TSManager06/08/2018 12:35:2617460 (0x4434)

BcdBackup: C:\_SMSTaskSequence\BCD-EFI\bcdTSManager06/08/2018 12:35:2617460 (0x4434)

Executing command line: "bcdedit.exe" /export C:\_SMSTaskSequence\BCD-EFI\bcdTSManager06/08/2018 12:35:2617460 (0x4434)

Process completed with exit code 0TSManager06/08/2018 12:35:2617460 (0x4434)

TSUEFIDrive: TSManager06/08/2018 12:35:2617460 (0x4434)

Staging boot image S0100005TSManager06/08/2018 12:35:2617460 (0x4434)

Volume '\\?\Volume{1fc8bd7a-f18d-4abf-b5f5-09e7e0538aa7}\' not foundTSManager06/08/2018 12:35:2617460 (0x4434)

Boot Image not found in local data cache at 'C:\_SMSTaskSequence\WinPE\sources\boot.wim'. Staging is requiredTSManager06/08/2018 12:35:2617460 (0x4434)

 

And later...

 

Failed to install boot image.

Unspecified error (Error: 80004005; Source: Windows)TSManager06/08/2018 12:35:3217460 (0x4434)

Failed to install boot image S0100005.

Unspecified error (Error: 80004005; Source: Windows)TSManager06/08/2018 12:35:3217460 (0x4434)

Failed to reboot the system. Error 0x80004005)TSManager06/08/2018 12:35:3217460 (0x4434)

Failed to initialize a system reboot.

Unspecified error (Error: 80004005; Source: Windows)TSManager06/08/2018 12:35:3217460 (0x4434)

Fatal error is returned in check for reboot request of the action (Restart in Windows PE).

Unspecified error (Error: 80004005; Source: Windows)TSManager06/08/2018 12:35:3217460 (0x4434)

An error (0x80004005) is encountered in execution of the task sequenceTSManager06/08/2018 12:35:3217460 (0x4434)

Set authenticator in transportTSManager06/08/2018 12:35:3217460 (0x4434)

Task Sequence Engine failed! Code: 80004005TSManager06/08/2018 12:35:3217460 (0x4434)

****************************************************************************TSManager06/08/2018 12:35:3217460 (0x4434)

Task sequence execution failed with error code 80004005TSManager06/08/2018 12:35:3217460 (0x4434)

 

 

Any ideas what's wrong? Am I better just to PXE boot these machines instead?

 

Thanks

Did you manage to sort this ?

[Gongalong]

Nope. I ended up PXE booting the lot. I raised the same query on Technet, and someone from Microsoft said it was unable to access a partition. There is no encryption on the drives though, so not sure why.

[kevin_lane]

Encryption well unless you have the encryption turned on which I presume you don't I don't understand why bit locker is being mentioned - you don't have different partitions setup on your task schedule do ? And you don't pre stage your boot Images ?

[Gongalong]

No, definitely no encryption. As mentioned in the OP, the irony is these were Win 7 machines, and when I imaged using the CM client (rather than PXE/media) to Win 10 it went fine. Now that I've come to reimage with Win 10 again, it hasn't worked.

 

The Task Sequence is set to reboot in PE, then partition the disk either as BIOS or UEFI, then it applies the new OS. The only changes I've made to PE are to add in some network drivers.

 

I had to press ahead and get them imaged so used PXE. We'll see next Summer whether I have the same problem...

[Steve21]

80004005 is a failed to access file/file in use normally (not access denied), so could be something stupid like AV on-access scanning/firewall rules etc too.

 

Might be worth disabling the AV and trying a rebuild too if get a minute.

 

Steve

[markwilfan]

Make sure all packages are distributed and available

[free780]

Also make sure cache size is big enough.

[markwilfan]

Also make sure cache size is big enough.

Good point especially if you are downloading the packages before deploying instead of streaming them

[mrbios]

If you're deploying zero touch to PCs that are already on and running then you need to deploy the task sequence to "Configuration Manager clients, media, and PXE" rather than just "media and PXE" as that now fails. It used to work, but microsoft changed something.

 

Could that be where you got stuck?

[Gongalong]

Make sure all packages are distributed and available

Should be, as it's working fine via PXE.

If you're deploying zero touch to PCs that are already on and running then you need to deploy the task sequence to "Configuration Manager clients, media, and PXE" rather than just "media and PXE" as that now fails. It used to work, but microsoft changed something.

 

Could that be where you got stuck?

I pick the option "Only Configuration Manager Clients". It does work for some PCs, but others have something along the lines of the log in the OP. It's moot for the moment because I've imaged the lot via PXE, but might be useful to have a fix for next year.

[pauljebastin]

Hi Gongalong, Did you managed to fix this please? we have the same issue when deploying through clients

[Gongalong]

I haven't tried again, I just use PXE.

[pauljebastin]

Thank you, Gongalong