Notwithstanding the inevitable calls for using MDT to create your core image 
that are sure to come, in ConfigMgr 2012 you will want to import the 
Source\Install.wim as an Operating System Image and use that for your Task 
Sequence :)

If the Task Sequence is installing it to D: you will likely need to set the 
OSDPreserveDriveLetter task sequence variable to False.  Keep in mind though 
that just because it shows it installing to D: in the WinPE phase doesn't mean 
it will actually show as D: once the installed OS boots.

-Phil
_________________________________________________________________
Phil Schwan | Technical Architect, Enterprise Windows Services
Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI 
48075
Lync: 312.756.1626  Mobile: 419.262.5133
www.projectleadership.net<http://www.projectleadership.net/>
[Description: Description: Description: Arrow email]Lead with Strategy. 
Leverage Technology. Deliver Results.
[linkedin_logo-19x20]<http://www.linkedin.com/in/philschwan>[Twitter-Logo1-20x20]<https://twitter.com/philschwan>
 [wordpress-logo3] <http://myitforum.com/myitforumwp/author/philschwan>




From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Manfred Glaser
Sent: Wednesday, March 19, 2014 1:24 PM
To: mssms@lists.myitforum.com
Subject: [mssms] Tasksequence - Error Windows 7 - Deployment from Installation 
Source HRESULT=80004005 - Windows setup failed, code 31

Hello,

We currently rely on the ConfigMgr 2012 R2. We want Windows 7 - install using 
the task sequence Capture - so that we can create an image . Unfortunately, the 
task sequence step crashes on Windows 7 - Install and Configure from . On the 
hard drive of the client folder (Windows , programs, and programs ( x86) 
deleted. It looks , which is carried out a rollback of the installation here .

Strange this behavior is that if we embed the install.wim directly in ConfigMgr 
as an image , the same task sequence runs smoothly by . The only change which I 
had performed , is the change from the source media - from Installation Source 
Image. Unfortunately we can not use because Windows 7 here so with the drive 
letter D this: install - and I still have in mind , this is not recommended , 
this approach

Does anyone have a tip for me

Sorry for my english - is very bad - and the translator will help further ..

Greeting Manfred Glaser


Smsts.log

<![LOG[exitCode == 0, HRESULT=80004005 
(e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,440)]LOG]!><time="12:06:23.369-60"
 date="03-19-2014" component="OSDSetupWindows" context="" type="0" 
thread="1572" file="setupwindows.cpp:440">
<![LOG[Windows setup failed, code 31]LOG]!><time="12:06:23.369-60" 
date="03-19-2014" component="OSDSetupWindows" context="" type="3" thread="1572" 
file="setupwindows.cpp:440">
<![LOG[setup.run(), HRESULT=80004005 
(e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,1650)]LOG]!><time="12:06:23.369-60"
 date="03-19-2014" component="OSDSetupWindows" context="" type="0" 
thread="1572" file="setupwindows.cpp:1650">
<![LOG[Exiting with code 0x80004005]LOG]!><time="12:06:23.385-60" 
date="03-19-2014" component="OSDSetupWindows" context="" type="1" thread="1572" 
file="setupwindows.cpp:1696">
<![LOG[Process completed with exit code 
2147500037]LOG]!><time="12:06:23.385-60" date="03-19-2014" 
component="TSManager" context="" type="1" thread="1060" 
file="commandline.cpp:1123">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="12:06:23.389-60"
 date="03-19-2014" component="TSManager" context="" type="1" thread="1060" 
file="instruction.cxx:804">
<![LOG[Failed to run the action: Setup Windows and Configuration Manager.
Unspecified error (Error: 80004005; Source: 
Windows)]LOG]!><time="12:06:23.389-60" date="03-19-2014" component="TSManager" 
context="" type="3" thread="1060" file="instruction.cxx:895">

________________________________

PRIVILEGED AND CONFIDENTIAL. This email and any files transmitted with it are 
privileged and confidential and intended solely for the use of the individual 
or entity to whom they are addressed. If you have received this email in error 
please notify the sender. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail or any of its attachments.




<<inline: image001.jpg>>

<<inline: image002.jpg>>

<<inline: image003.jpg>>

<<inline: image004.jpg>>

Reply via email to