Deployment Summary error from operating system

Asked By 0 points N/A Posted on -
qa-featured

Hello there,

After updating my Microsoft Deployment Toolkit to the 2013 version, I encountered these errors. I didn’t expect to have so many errors and also I don’t know how to solve them. Can an expert help me please to fix this one ?

Thanks !

Failure

Operating system deployment did not complete successfully.

Please review the log files to determine the cause of the problem

During the deployment process, 14 errors and 0 warnings were reported.

ZTI ERROR-Unhandled error returned by LTIApply: Not found (-2147217406 0x80041002)

Litetouch deployment failed Return Code=-2147467259 0x80004005

Failed to run the action: Apply Windows PE.

Not found (Error:80041002:Source:WMI)

The execution of the group(Capture Image) has failed and the execution has been aborted.An action failed.

Operation aborted (Error: 80004004; Source: Windows)

Failed to run the last action: Apply Windows PE. Execution of task sequence failed.

Not found (Error:80041002: Source: WMI)

Task Sequence Engine failed! Code: enExecutionFail

Task sequence execution failed with error code 80004005

Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

Failed to run the action: Apply Windows PE.

Not found (Error:80041002:Source:WMI)

The execution of the group(Capture Image) has failed and the execution has been aborted.An action failed.

Operation aborted (Error: 80004004; Source: Windows)

Failed to run the last action: Apply Windows PE. Execution of task sequence failed.

Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

  • Answer Accepted: No
  • Question Category:
SHARE
Answered By 0 points N/A #179101

Deployment Summary error from operating system

qa-featured

Hi Vince, whenever a set-up is running it really needs to be configured in such a way that the log-in files will not encounter any errors such as the one that you described. The next step is to locate a certain file named unattend.xml. Some of the errors are actually Windows Setup errors with exit code 31. These are caused by faulty drivers, an incorrect .xml file or often as in this case, a misplaced or wrong Windows entry key. Don’t inject any HyperDrivers since this may just worsen the situation and would cause a serious crash in your system. Try this one Vince, Click your Start menu then type msconfig.exe to start the System Configuration Utility. Now in the General tab, click Selective Start-Up, and then click Load Start-Up items. On the Services tab, just try to choose the Microsoft Service and click OK. Re-start now your computer. 

About ferdinand Magellan
Questions
0
Answers
102
Best Answers
10
  • Posted on -
  • Question Category:

Windows Server error launching VERITAS backup exec

Previous

Windows Features error with .NET Framework

Next

Related Questions