Error when deploying "some" machines in our network - 0x80004005

[stylaren]

Hello!

 

We recently updated our Configmgr environment to R2 SP1. After the upgrade we tried to OSD a laptop and one of our thinclient without any problems. A couple a days ago i was going to install a new workstation when i relized something isn't working as it should. The task sequence that we use is the same as the one we use on laptops.

 

For example, everything is wokring on our HP 820 G2 laptop while we cannot succeed on a HP Z230.

 

The error we got on the Z230 and other workstations is the following:

 

 

 

I have collected to logs after the restart and the can be found here (also attached):

 

https://www.dropbox.com/s/i3nrw6nyo3zawuj/SMSTSLog%20-%20After%20restart.zip?dl=0

 

This error shows after that the TS have installed the Driverpackade and just before SCCM client installation..

 

I have checked the Network access account and tried a driverpackade that only has the network drivers assigned.

 

Any help or tips is very appreciated!

 

Kind Regards,

Anthon

SMSTSLog - After restart.zip

[Adam Bise]

smsts.log

Microsoft Deployment Toolkit version: 6.2.5019.0 InstallSoftware 7/20/2015 2:37:28 PM 1420 (0x058C)
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. InstallSoftware 7/20/2015 2:37:28 PM 1420 (0x058C)
ZTI deployment failed, Return Code = -2147467259 0x80004005 InstallSoftware 7/20/2015 2:37:28 PM 1420 (0x058C)
Command line returned 2147500037 InstallSoftware 7/20/2015 2:37:28 PM 1420 (0x058C)
Process completed with exit code 2147500037 TSManager 7/20/2015 2:37:28 PM 1320 (0x0528)

dism.log

2015-07-20 14:37:21, Error CBS Failed to load offline store from boot directory: '\\?\D:\' and windows directory: '\\?\D:\Windows\' [hrESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2015-07-20 14:37:21, Error CBS Failed to initialize store parameters with boot drive: D:\ and windows directory: D:\Windows [hrESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2015-07-20 14:37:21, Error DISM DISM Package Manager: PID=1624 Failed initializing the session - CDISMPackageManager::RefreshInstanceAndLock(hr:0x80070002)
2015-07-20 14:37:21, Error DISM DISM Package Manager: PID=1624 Failed doing internal initialization - CDISMPackageManager::Initialize(hr:0x80070002)

2015-07-20 14:37:21, Error DISM DISM OS Provider: PID=1624 Failed to open the key Microsoft\Windows NT\CurrentVersion. - CDISMOSServiceManager::DetermineBootDrive(hr:0x80070002)
2015-07-20 14:37:21, Error DISM DISM Driver Manager: PID=1624 Failed to getting the boot drive from the os services provider. - CDriverManager::Initialize(hr:0x80070002)

2015-07-20 14:37:21, Error DISM DISM Unattend Manager: PID=1624 d:\win7sp1_gdr\base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:390 - CUnattendManager::Apply(hr:0x80004005)
2015-07-20 14:37:21, Error DISM DISM Unattend Manager: PID=1624 d:\win7sp1_gdr\base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:654 - CUnattendManager::InternalExecuteCmdLine(hr:0x80004005)
2015-07-20 14:37:21, Error DISM DISM Unattend Manager: PID=1624 d:\win7sp1_gdr\base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:603 - CUnattendManager::ExecuteCmdLine(hr:0x80004005)
2015-07-20 14:37:21, Error DISM DISM.EXE: DISM Unattend Manager processed the command line but failed. HRESULT=80004005

 

Only thing I can suggest is try this since your errors are similar to this guy Basically he recreated the image.

http://en.community.dell.com/techcenter/enterprise-client/f/4448/t/19544668

 

 

I had a similar issue that we have still not resolved.. On Dell OptiPlex 3020 machines the video driver could cause the system to hang during the unnattented portion of setup. IE Setup is installing drivers 50% and it would stay at 50% until the same error code you got. Are your machines doing this?

 

We would restart the TS on the machines that failed and about 10% of the time it would error again, so we would just restart the TS again until it worked.

 

I was going to remove the video driver from that package but we wound up not deploying anymore of that model.

 

Seems like a driver issue, but I think those would be in the unattended setup logs.

One thing I have done before and I could have sworn it was an error 0x4005 was simply delete the driver package and recreate it. Other times we had to omit some of the drivers because they caused issues.

[HappySCCM]

It's failing to inject all the Z230 drivers, you could try continue on error for the drivers step but that may not get you very far.

 

We recently had the issue with an Apple iMac, the driver pack had a Windows 8 WLAN driver in it that was causing issues when Applying to Windows 7 even though it shouldn't be compatible.

Removing that driver fixed it. Drivers are funny idiots.