OSD TS Fails with 0x80004005 on osdwinsettings.exe
I am trying to image a machine using our standard 64-bit OSD TS, which has not changed recently. The machine consistently fails on what appears to be the applying image step. The excerpt from the smsts.log is below. I know the 4005 error is pretty generic, but I don't see anything else in the logs that seems to help. The interesting part is that it's only failing on this machine. I can run the same TS on another machine, and it runs without issue. Any ideas? <![LOG[Set command line: osdwinsettings.exe /config]LOG]!><time="16:40:27.617+300" date="09-24-2012" component="TSManager" context="" type="0" thread="1136" file="commandline.cpp:707"> <![LOG[Start executing the command line: osdwinsettings.exe /config]LOG]!><time="16:40:27.617+300" date="09-24-2012" component="TSManager" context="" type="1" thread="1136" file="instruction.cxx:2928"> <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="16:40:27.617+300" date="09-24-2012" component="TSManager" context="" type="1" thread="1136" file="instruction.cxx:2957"> <![LOG[Expand a string: WinPE]LOG]!><time="16:40:27.617+300" date="09-24-2012" component="TSManager" context="" type="0" thread="1136" file="executionenv.cxx:782"> <![LOG[Executing command line: osdwinsettings.exe /config]LOG]!><time="16:40:27.617+300" date="09-24-2012" component="TSManager" context="" type="1" thread="1136" file="commandline.cpp:805"> <![LOG[============================[ OSDWinSettings.exe ]============================]LOG]!><time="16:40:27.632+300" date="09-24-2012" component="OSDWinSettings" context="" type="1" thread="1552" file="osdwinsettings.cpp:579"> <![LOG[Command line: "osdwinsettings.exe" /config]LOG]!><time="16:40:27.632+300" date="09-24-2012" component="OSDWinSettings" context="" type="0" thread="1552" file="osdwinsettings.cpp:580"> <![LOG[!sInstallType.empty(), HRESULT=80004005 (c:\nts_sms_fre\sms\framework\osdcore\infanswerfile.cpp,325)]LOG]!><time="16:40:27.632+300" date="09-24-2012" component="OSDWinSettings" context="" type="0" thread="1552" file="infanswerfile.cpp:325"> <![LOG[Failed to read installation type from environment.. Please ensure you are running this executable inside a properly configured OS Deployment task sequence. Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="16:40:27.632+300" date="09-24-2012" component="OSDWinSettings" context="" type="3" thread="1552" file="infanswerfile.cpp:325"> <![LOG[OSD::Utility::BaseAnswerFile::CreateAnswerFile( pAnswerFile ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdwinsettings\osdwinsettings.cpp,364)]LOG]!><time="16:40:27.632+300" date="09-24-2012" component="OSDWinSettings" context="" type="0" thread="1552" file="osdwinsettings.cpp:364"> <![LOG[Failed to initialize answer file.]LOG]!><time="16:40:27.632+300" date="09-24-2012" component="OSDWinSettings" context="" type="3" thread="1552" file="osdwinsettings.cpp:364"> <![LOG[ConfigureWinSettings(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdwinsettings\osdwinsettings.cpp,637)]LOG]!><time="16:40:27.632+300" date="09-24-2012" component="OSDWinSettings" context="" type="0" thread="1552" file="osdwinsettings.cpp:637"> <![LOG[Failed to open the Task Sequencing Environment. Code 0x80004005. Please ensure you are running this executable inside a properly configured OS Deployment task sequence. Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="16:40:27.632+300" date="09-24-2012" component="OSDWinSettings" context="" type="3" thread="1552" file="osdwinsettings.cpp:637"> <![LOG[Exiting with return code 0x80004005]LOG]!><time="16:40:27.632+300" date="09-24-2012" component="OSDWinSettings" context="" type="1" thread="1552" file="osdwinsettings.cpp:647"> <![LOG[Process completed with exit code 2147500037]LOG]!><time="16:40:27.632+300" date="09-24-2012" component="TSManager" context="" type="1" thread="1136" file="commandline.cpp:1102"> <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="16:40:27.632+300" date="09-24-2012" component="TSManager" context="" type="1" thread="1136" file="instruction.cxx:3010"> <![LOG[Failed to run the action: Personalize Windows. Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="16:40:27.632+300" date="09-24-2012" component="TSManager" context="" type="3" thread="1136" file="instruction.cxx:3101">
September 30th, 2012 11:47am

I manually cleaned the disk with diskpart and created a single partition to fill the whole drive, but that didn't make any difference. Plus, our TS is applying an image, not an OS installation.
Free Windows Admin Tool Kit Click here and download it now
September 30th, 2012 2:07pm

Is it possible that ConfigMgr wants to install the OS on the 100Mb Bitlocker partition created by Windows 7 install? Just clean the disk with diskpart then before OSD, or change the Task Sequence settings to the next available partition.My blogs: Henk's blog and Virtuall | Follow Me on: Twitter | View My Profile on: LinkedIn
September 30th, 2012 2:20pm

From the error it looks like it may be the apply OS image action that has an issue, or is perhaps somehow being bypassed in the task sequence. Can you just check further up the smsts.log and make sure the OS image is being applied? Mark.
Free Windows Admin Tool Kit Click here and download it now
September 30th, 2012 3:55pm

Does the other machine(s) are the same vendor/model/type and contains the same hardware? Is it possible that your NIC or SATA drive isn't recognized? Just press F8 during deployment (which must be enabled in your boot image) and try to ping the ConfigMgr server and to access your local drive for installation. That way you're sure about that parts.My blogs: Henk's blog and Virtuall | Follow Me on: Twitter | View My Profile on: LinkedIn
September 30th, 2012 4:27pm

Yes, I imaged an identical machine minutes after I created this thread.
Free Windows Admin Tool Kit Click here and download it now
September 30th, 2012 4:29pm

The image is now running successfully. Two things happened - 1) Removed the RAM that was installed prior to running the previous image attempts and 2) ran DBAN on the hard drive. I would say it's much more likely that the RAM caused the issue than something that was getting past formatting and partitioning the hard drive, but can't say for sure. Either way, this issue is resolved with an unfortunate lack of conclusive information.
September 30th, 2012 5:08pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics