Jump to content


  • 0
blind3d

SCCM error 80004005 - no BiOS issue - driving me crazy!

Question

Hey guys,

 

I hope that you can help me out. Here is my situation:

 

-Using SCCM 2012 R1

-Usually deploying Windows 7 to Lenovo and Acer PCs - works perfect

-Got new industrial PCs by MSI now (Windbox II) - that had no UUID which I fixed with AMIDMI.exe /u etc.

-Task sequence starts like this:

 

2015_11_06_08_06_54_m_Remote_Witte_xml.p

 

-Step 2&3 check wether it's UEFI or not and partitions the disk

-Step 4 executes a script to allow me to give the machine a hostname

-This task sequence is used (in modified versions) for different PCs with different images and works for all of them

 

The issue:

 

As soon as I start the TS for the Windboxes, step 3 is chosen and completed succesfully (BIOS) but step 4 is ignored with the following error as logged in SMSTS.log:

 

2015_11_06_08_24_43_Configuration_Manage

 

What makes me wonder is the following message and I don't know if it is normal (CRL=false):

 

 

 

During Step3

 

2015_11_06_08_26_52_Configuration_Manage

 

Step 4

 

2015_11_06_08_25_46_Configuration_Manage

 

The most confusing thing about all that errors is, that 1 out of 15 attempts suddenly works and if you reboot the deployment fails again :-/ it doesn't even matter if I chose IDE or SATA in BiOS :(

I also tried a different HDD that works in our Lenovo devices btw. Log is attached as well (replaced the real name with fictional ;) ).

So when the TS starts to apply the OS it fails with 80004005 error.

 

Thanks in advance.

 

PS: Please move my post to this subforum: Configuration Manager 2012

 

Thnks.

 

Problem solved:

 

Hi again,

 

I think the issue is solved, but it doesn't really make sense to me, cuz it is incredibly stupid.. I tested the "workaround" 5 times now..

As we all know you're prompted to strike F12 for SCCM PE boot.

To avoid missing this step I hit F12 repeatedly which caused the TS to fail!!

If I only strike F12 when prompted the TS works properly..

If there is anyone out there who is able to explain this, just lemme know..

Maybe a secret AMI Bios command like in this case?

 

http://www.windows-noob.com/forums/topic/6240-toolkit-error-during-beginning-of-osd-ts/

smstsv2.log

Share this post


Link to post
Share on other sites

0 answers to this question

Recommended Posts

There have been no answers to this question yet

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.