A few fixes to try here.

https://social.technet.microsoft.com/Forums/en-US/8e2f90c2-1ea8-4460-9ddf-f62624a7cd9b/mdt-2012-update-1-boot-image-creation-fails-in-sp1?forum=configmanagerosd

Daniel Ratliff

From: [email protected] [mailto:[email protected]] On 
Behalf Of Stephen Owen
Sent: Tuesday, October 04, 2016 9:37 PM
To: [email protected]
Subject: [MDT-OSD] [SCCM1602] Making a new boot image w/ MDT fails

Hi all,

  Running into an issue in which I'm unable to make a new boot image w/ MDT.  
We're using SCCM 1602, with MDT 2013 Update 2, and ADK 1607.  When we try to 
create a new boot image using the MDT wizard, it immediately fails with an 
error of:


  [Inline image 1]

 Here's the full stack trace:

  Description:
  Stopped working

Problem signature:
  Problem Event Name:     CLR20r3
  Problem Signature 01:   microsoft.bdd.elevatedproxy.exe
  Problem Signature 02:   6.3.8330.1000
  Problem Signature 03:   564adfe9
  Problem Signature 04:   System.ServiceModel
  Problem Signature 05:   3.0.0.0
  Problem Signature 06:   53a13bcb
  Problem Signature 07:   fb3
  Problem Signature 08:   a7
  Problem Signature 09:   G3DT0URDW53KGT4VJDEEQCRAUIFCNTLL
  OS Version:   6.1.7601.2.1.0.400.8
  Locale ID:    1033

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy 
statement offline:


   This should go down in records as the most helpful error message of all 
time, for sure.

   This ring any bells?

   We are going down this route because, when we're imaging, we're getting 
failures at 'ApplyWindowsImage', and it looks to be caused by incorrect 
settings coming back from Gather.

  Here's the precise failure we're experiencing.

 The task sequence execution engine failed executing the action (Apply Windows 
Settings) in the group (PostInstall) with the error code 2149711877
Action output: ... Name, pszPath, pszValue ), HRESULT=80220005 
(e:\nts_sccm_release\sms\framework\osdcore\xmlanswerfile.cpp,767)
this->SetValue( Specialize, XML::Shell::ComponentName, 
XML::Shell::ComputerName::Element, pszComputerName ), HRESULT=80220005 
(e:\nts_sccm_release\sms\framework\osdcore\xmlanswerfile.cpp,883)
m_pImpl->SetComputerNameW(pszComputerName), HRESULT=80220005 
(e:\nts_sccm_release\sms\framework\osdcore\xmlanswerfile.cpp,2183)
pAnswerFile->SetComputerNameW(sValue), HRESULT=80220005 
(e:\nts_sccm_release\sms\client\osdeployment\osdwinsettings\osdwinsettings.cpp,375)
ConfigureWinSettings(), HRESULT=80220005 
(e:\nts_sccm_release\sms\client\osdeployment\osdwinsettings\osdwinsettings.cpp,636)
Could not find CCM install folder. Don't use ccmerrors.dll
Exiting with return code 0x80220005
Failed to open the Task Sequencing Environment. Code 0x80220005. Please ensure 
you are running this executable inside a properly configured OS Deployment task 
sequence.
nknown error (Error: 80220005; Source: Unknown). The operating system reported 
error 50: The request is not supported.

The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material.  If you receive this 
material/information in error,
please contact the sender and delete or destroy the material/information.

Reply via email to