Failed to Create MDT Boot Image in SCCM 2007

Hello Everyone,
I am trying to create MDT Integrated Boot Image in SCCM to Enable DART Integration on it. But when i try to Create Boot Image it Fails with below Error Message.
Started processing.
Creating boot image.
Copying WIM file.
Mounting WIM file.
WIM file mounted.
Setting Windows PE system root.
Set Windows PE system root.
Set Windows PE scratch space.
Adding standard components.
Adding extra content from: C:\Users\ADMINI~1\AppData\Local\Temp\1\i5wqsynb.efm
Unmounting WIM.
Copying WIM to the package source directory.
Creating boot image package.
Error while importing Microsoft Deployment Toolkit Task Sequence.
Failed to insert OSD binaries into the WIM file
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The ConfigMgr Provider reported an error.
---> System.Management.ManagementException: Generic failure
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.Put(PutOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
--- End of inner exception stack trace ---
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
I have searched over Internet for the same Error and I guess it was a Permission Issue. But my Environment is as below.
AD & SCCM Server on Same Machine
Folder have Full Permissions to SYSTEM, SCCMComputerAccount, DomainAdministrators, and Even I gave to Everyone Full
Control.
This is a LAB Environment with No Antivirus, No UAC
ANY HELP ON THIS Folks..... (:-()
Ram

Hi Ychinnari,
As your question is related to SCCM report. it is not supported here.
you could post it in SCCM forum for better supports, Thanks for your understanding.
SCCM forum link:
https://social.technet.microsoft.com/Forums/systemcenter/en-US/home?category=configurationmanager
Best regards,
Youjun Tang
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Similar Messages

Create MDT Boot Image Fails

I'm trying to create MDT boot images using MDT 2012 U1 on CM 2012 R2 but I keep getting this error message as desribed by this entry on
James Bannan's blog
The suggested fix/workaround is to launch the CM console as administrator. I've tried that with no success and wondered if anyone else has seen this and perhaps knows what the problem is? Any help would be appreciated. Merry Christmas!

Thanks, is 2013 required or recommended? The guys running the server re-installed WAIK and the process completed successfully.

Using MDT boot image in SCCM 2012

Hi,
I want to import MDT boot image in SCCM 2012. Please let me know if this is possible.
I have integrated all the driver in it and want to use from SCCM.
Any suggestion on this?
Regards, Shishir Kushawaha "If this thread answered your question, please click on "Mark as Answer"

These two blogs explain this process very very well.
http://myitforum.com/myitforumwp/2013/08/01/how-to-create-configmgr-2012-boot-images-from-scratch/
http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

MDT Boot Image Creation Error: The server did provide a meaningful reply

I'm creating an mdt boot image in SCCM 2012 SP1. When I first configured MDT integration everything worked fine (version 6.1.2373). Then after creating 2 boot images, I went to create a 3rd, that's when I started having problems. The wizard starts, copies
the wim file, adds the standard components, then goes to add the winpe-dismcmdlets. After a few minutes this error comes up.
However, I went to check the pemanager.log file in the appdata\local\microsoft\temp\1\pemanager.3392 folder and it was adding the .net 4 components (after the error had already come up). I also opened up the dism.log file. The .net install completed without
error and then the winpe-dismcmdlets install started and finished without error. All this was after the error occured, so the process kept running after the error. This continues to happen after a reboot of the site server.
Log from pemanager.log:
Deployment Image Servicing and Management tool
Version: 6.2.9200.16384
Image Version: 6.2.9200.16384
Processing 1 of 1 - Adding package WinPE-DismCmdlets-Package~31bf3856ad364e35~amd64~en-US~6.2.9200.16384
The operation completed successfully.
Exit code = 0
Log snippet from dism.log
2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 Enter DismInitializeInternal - DismInitializeInternal
2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 Initialized GlobalConfig - DismInitializeInternal
2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 Initialized SessionTable - DismInitializeInternal
2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 Waiting for m_pInternalThread to start - CCommandThread::Start
2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3288 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 m_pInternalThread started - CCommandThread::Start
2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 Created g_internalDismSession - DismInitializeInternal
2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 Leave DismInitializeInternal - DismInitializeInternal
2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3288 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2013-04-29 20:20:10, Info                  DISM   API: PID=1296 TID=5096 Enter DismShutdownInternal - DismShutdownInternal
2013-04-29 20:20:10, Info                  DISM   API: PID=1296 TID=5096 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2013-04-29 20:20:10, Info                  DISM   API: PID=1296 TID=5096 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
2013-04-29 20:20:10, Info                  DISM   API: PID=1296 TID=5096 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2013-04-29 20:20:10, Info                  DISM   API: PID=1296 TID=3288 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2013-04-29 20:20:10, Info                  DISM   API: PID=1296 TID=3288 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2013-04-29 20:20:10, Info                  DISM   API: PID=1296 TID=3288 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2013-04-29 20:20:10, Info                  DISM   API: PID=1296 TID=3288 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2013-04-29 20:20:10, Info                  DISM   PID=1296 TID=3288 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
2013-04-29 20:20:10, Info                  DISM   PID=1296 TID=3288 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
2013-04-29 20:20:10, Info                  DISM   PID=1296 TID=3288 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
2013-04-29 20:20:12, Info                  DISM   API: PID=1296 TID=3288 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-04-29 20:20:12, Info                  DISM   API: PID=1296 TID=5096 Deleted g_internalDismSession - DismShutdownInternal
2013-04-29 20:20:12, Info                  DISM   API: PID=1296 TID=5096 Shutdown SessionTable - DismShutdownInternal
2013-04-29 20:20:12, Info                  DISM   API: PID=1296 TID=5096 Leave DismShutdownInternal - DismShutdownInternal
2013-04-29 20:20:12, Info                  DISM   API: PID=1296 TID=5096 DismApi.dll:
- DismShutdownInternal
2013-04-29 20:20:12, Info                  DISM   API: PID=1296 TID=5096 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2013-04-29 20:20:12, Info                  DISM   API: PID=1296 TID=5096 DismApi.dll:
- DismShutdownInternal
I tried removing the mdt integration, uninstalling mdt, reboot, install mdt, configure mdt integration. Error occurs whenever an additional component tries to install .net4 or if it installs directly. This is on an almost brand new install
of the sccm site server on sever 2012. Any ideas?

For me disabling the anti virus software (TrendMicro OfficeScan) solved the problem.

MDT Boot Image Creation

I just upgraded my SCCM 2012 RTM to SP1 and then to R2
I uninstalled the WAIK and installed 8.1 ADK
MDT 2012 Update 1
Now I am trying to add new MDT Boot images and I get this error
Started processing.
Creating boot image.
Copying WIM file.
Error while importing Microsoft Deployment Toolkit Task Sequence.
System.Exception: Unhandled exception occurred:
System.IO.FileNotFoundException: Could not find file '\winpe.wim'.
File name: '\winpe.wim'
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileInfo.get_Length()
at Microsoft.BDD.Core.DEInfo..ctor(FileInfo theFile)
at Microsoft.BDD.Core.DirectoryUtility.BeginCopyFile(String theSourceFile, String theDestFile)
at Microsoft.BDD.ElevatedProxy.NewBootImage.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)
Jacob

You need to remove the old MDT integration components and then reintegrate MDT with the new R2 installation of Configuration Manager by running the Configure ConfigMgr Integration utility from the start menu (inside the Microsoft Deployment Toolkit folder)
, if your on Server 2012 make sure you run the utility as an administrator (elevated) otherwise it will fail.
If you haven't already done so you will also need to update MDT to 2013 as 2012 Update 1 isn't supported in R2.
Its also a good idea to create new MDT Integrated Task Sequences and copy over any custom actions from your old ones to the new ones.
Cheers
Damon

MDT boot image and when we try to PXE boot it won't get the IP Address.

We created a custom MDT boot image and when we try to PXE boot it won't get the IP Address.
I press F8 and type IPCONFIG we get Windows IP Configuration. We are using vmxnet3 network adapter.
I think I need to inject 32-bit vmxnet3 driver to the custom MDT boot image which is 32-bit.
We are using it to deploy Windows Server 2008 R2 with SP1 operating System.
Can I just use the 32-bit custom MDT boot image or do I need to use 64-bit Custom MDT Boot Image?
Also Is there a blog on how to inject vmxnet3 driver to boot image?

You can try this:
http://mwesterink.wordpress.com/2013/12/03/configmgr-2012-obtaining-vmxnet3-nic-drivers-for-vmware-virtual-machines/
Honestly, your best bet is to use a different adapter (E1000). I personally have had no luck getting the vmxnet3 driver to work properly in WinPE. It's either really, really slow or it simply doesn't load at all.

Mdt integration boot image and SCCM boot image

I created a MDT task sequence in SCCM and went through all the steps for setting up the toolkit and settings and boot image. After all that, I distributed everything to my DP. When i try to boot to pxe and run that new MDT task sequence it finds the pxe
server, but just sits at "Contacting server" for some time until it times out. If I select the SCCM boot image in the task sequence properties then it works. the one created when i create the task sequence doesn't.
Any Idea?

Sounds like you didn't enable the boot image for PXE. This is a checkbox at the bottom of the Data Source page in the properties of the boot image.
Have you reviewed smspxe.log?
Jason | http://blog.configmgrftw.com | @jasonsandys

Disk Utility fails to create encrypted disk image

When creating a disk image using 256 bit encryption and a purely numeric password longer than 13 characters the following message appears:
Unable to create "ABC.dmg." (error -60008)
the error happens upon typing the 14th consecutive number into the Password field. I have created images under the same conditions in the past, Not sure if this is caused by Lion.

Looks like one of the drives is bad.
While it passed being zeored with Disk Utility, it failed about 15 minutes into a 'Certify' using SoftRAID.
Now waiting on a replacement drive from Newegg.

Lenovo X1 Carbon PXe boot errors with SCCM 2007

I know there are many posts on this and I've gone through them all, but I am still having issues PXe booting a X1. I have a USB ethernet dongle (the new type with the rounded edge). the part number is 0b67708. It's branded Lenovo but when I pxe it recognises it as ASIX AX88772b. So far so good. It picks up an IP from DHCP ok, recognises the hardware as x64 and then tries to download the \smsboot\boot.sdi file from the SCCM 2007 server. It waits for 20 seconds then falls over with the following:
Status: 0xc0000001 - Info: The boot selection failed because a required device is inaccessible.
Now, I have the the following drivers in the boot.wim file:
x86 -
1. Lenovo USB2.0 Ethernet Adapter 5.12.7.0
2. PCI bus
3. Intel ICHR/DO/DH SATA AHCI Controller
4. Intel USB 3.0 Root Hub
5. Intel USB 3.0 eXtensible Host Controller
x64 -
1. Lenovo USB 2.0 Ethernet Adapter 5.14.4.0
2. PCI Bus
3. Intel ICHR/DO/DH SATA AHCI Controller - 2821
4. Intel USB 3.0 Root Hub
5. Intel USB 3.0 eXtensible Host Controller
I have tried using the ASIX drivers, all previous driver version, adding in the mass storage drivers, adding in the USB 3.0 drivers, praying to the PXe gods but nothing works.
All other hardware works fine. Any suggestions greatly welcomed.
Cheers - Mark.

Make a USB recovery drive before reinstalling.Thats the only option with a preload. With a retail serial number, you can download an iso with the upgrade assistant.
Also, how much ram do you have. If yopu have more than 4GB, you will need 64 bit XP, or the performance will take a hit. I tried XP on my W530, but I had to change several settings in the BIOS/UEFI.
W530(2436-CTO): i7-3720QM, nVidia Quadro K2000M,16GB RAM, 500 GB hard drive, 128GB mSATA SSD, Ubuntu 14.04 Gnome, Centrino Ultimate-N 6300.
Yoga 3 Pro: Intel Core-M 5Y70, Intel HD 5300, 8GB RAM, 128GB eMMC, Windows 8.1, Broadcom Wireless 802.11ac.

How to create a liveworkstation details in sccm 2007

HI how to create query to find the live work station details for last 30 days?

There are several example on my old blog site.
http://smsug.ca/search/SearchResults.aspx?q=30+days
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

How to create the asset report in sccm 2007?

hi can any one please give the query for asset report?

how about this ?http://eskonr.com/2011/12/sccmconfigmgr-report-for-computer-asset-information-serialnumber-manufacturermodelprocessorip-addresshardaware-scan/
you can customize the fields .
Eswar Koneti | Configmgr blog:
www.eskonr.com | Linkedin: Eswar Koneti
| Twitter: Eskonr

MDT 2012 Update 1 Boot Image Creation Fails in SP1

I have my site server (SCCM 2012 SP1) installed on Server 2012 with the Windows 8 ADK installed (I've also tried installing the Win7 WAIK with no change to the below problem). It is hosting the site server, FSP, AIS, and Endpoint protection roles. I
installed MDT 2012 Update 1 (build 6.1.2373.0) and installed ConfigMgr integration. I have a share
\\siteserver\bootimages that I'm creating the boot image to and the system account has full control on both the NTFS and Share permissions. When I create the boot image I get an error almost immediately and
a popup that the Microsoft.BDD.ElevatedProxy has stopped working. Details from the pop-up:
Description:
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: microsoft.bdd.elevatedproxy.exe
Problem Signature 02: 3.0.0.0
Problem Signature 03: 50400c36
Problem Signature 04: System.ServiceModel
Problem Signature 05: 3.0.0.0
Problem Signature 06: 4fee6b19
Problem Signature 07: fb9
Problem Signature 08: a7
Problem Signature 09: G3DT0URDW53KGT4VJDEEQCRAUIFCNTLL
OS Version: 6.2.9200.2.0.0.272.7
Locale ID: 1033
The error in the boot image creation wizard is:
Started processing.
Creating boot image.
Error while importing Microsoft Deployment Toolkit Task Sequence.
System.ServiceModel.FaultException: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug>
configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.
Server stack trace:
   at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
   at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at INewBootImage.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)
   at NewBootImageClient.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)
   at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)
I haven't found anything online on this particular error, I've seen all the ones about MDT 2012 and ConfigMgr 2012 CU 1. Any ideas? Any logs that may be revealing to the cause of this error? I've tried removing integration components, uninstalling MDT, reboot,
re-installing, etc, but same problem occurs each time.

I just tried to create a new boot image again, the DISM.log file does not show any evidence of the attempt to create the boot wim, in fact nothing since 0800 this morning. The most recent logs are as follows:
2013-03-03 20:22:59, Info                  DISM   PID=2252 TID=4312 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
2013-03-03 20:22:59, Info                  DISM   PID=2252 TID=4312 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=4312 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 Deleted g_internalDismSession - DismShutdownInternal
2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 Shutdown SessionTable - DismShutdownInternal
2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 Leave DismShutdownInternal - DismShutdownInternal
2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 DismApi.dll:
- DismShutdownInternal
2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 DismApi.dll:
- DismShutdownInternal
2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:
- DismInitializeInternal
2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:
- DismInitializeInternal
2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Enter DismInitializeInternal - DismInitializeInternal
2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Initialized GlobalConfig - DismInitializeInternal
2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Initialized SessionTable - DismInitializeInternal
2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
2013-03-03 22:02:51, Info                  DISM   API: PID=3544 TID=3672 Waiting for m_pInternalThread to start - CCommandThread::Start
2013-03-03 22:02:51, Info                  DISM   API: PID=3544 TID=4172 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=4172 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 m_pInternalThread started - CCommandThread::Start
2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 Created g_internalDismSession - DismInitializeInternal
2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 Leave DismInitializeInternal - DismInitializeInternal
2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 Enter DismShutdownInternal - DismShutdownInternal
2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=4172 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=4172 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2013-03-03 22:03:59, Info                  DISM   API: PID=3544 TID=4172 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2013-03-03 22:03:59, Info                  DISM   API: PID=3544 TID=4172 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2013-03-03 22:04:39, Info                  DISM   PID=3544 TID=4172 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
2013-03-03 22:04:39, Info                  DISM   PID=3544 TID=4172 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
2013-03-03 22:04:39, Info                  DISM   PID=3544 TID=4172 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=4172 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 Deleted g_internalDismSession - DismShutdownInternal
2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 Shutdown SessionTable - DismShutdownInternal
2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 Leave DismShutdownInternal - DismShutdownInternal
2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:
- DismShutdownInternal
2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:
- DismShutdownInternal
2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:
- DismInitializeInternal
2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:
- DismInitializeInternal
2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Enter DismInitializeInternal - DismInitializeInternal
2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Initialized GlobalConfig - DismInitializeInternal
2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Initialized SessionTable - DismInitializeInternal
2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
2013-03-04 08:41:08, Info                  DISM   API: PID=1016 TID=1620 Waiting for m_pInternalThread to start - CCommandThread::Start
2013-03-04 08:41:08, Info                  DISM   API: PID=1016 TID=4176 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=4176 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 m_pInternalThread started - CCommandThread::Start
2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 Created g_internalDismSession - DismInitializeInternal
2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 Leave DismInitializeInternal - DismInitializeInternal
2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 Enter DismShutdownInternal - DismShutdownInternal
2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2013-03-04 08:42:44, Info                  DISM   PID=1016 TID=4176 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
2013-03-04 08:42:44, Info                  DISM   PID=1016 TID=4176 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
2013-03-04 08:42:44, Info                  DISM   PID=1016 TID=4176 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=4176 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 Deleted g_internalDismSession - DismShutdownInternal
2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 Shutdown SessionTable - DismShutdownInternal
2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 Leave DismShutdownInternal - DismShutdownInternal
2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:
- DismShutdownInternal
2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:
- DismShutdownInternal
2013-03-05 08:44:10, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll:
- DismInitializeInternal
2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll:
- DismInitializeInternal
2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 Enter DismInitializeInternal - DismInitializeInternal
2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 Initialized GlobalConfig - DismInitializeInternal
2013-03-05 08:44:13, Info                  DISM   API: PID=4140 TID=3140 Initialized SessionTable - DismInitializeInternal
2013-03-05 08:44:13, Info                  DISM   API: PID=4140 TID=3140 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
2013-03-05 08:44:14, Info                  DISM   API: PID=4140 TID=3140 Waiting for m_pInternalThread to start - CCommandThread::Start
2013-03-05 08:44:14, Info                  DISM   API: PID=4140 TID=640 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 m_pInternalThread started - CCommandThread::Start
2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 Created g_internalDismSession - DismInitializeInternal
2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 Leave DismInitializeInternal - DismInitializeInternal
2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=640 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 Enter DismShutdownInternal - DismShutdownInternal
2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2013-03-05 08:46:18, Info                  DISM   PID=4140 TID=640 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
2013-03-05 08:46:18, Info                  DISM   PID=4140 TID=640 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
2013-03-05 08:46:18, Info                  DISM   PID=4140 TID=640 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=640 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 Deleted g_internalDismSession - DismShutdownInternal
2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 Shutdown SessionTable - DismShutdownInternal
2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 Leave DismShutdownInternal - DismShutdownInternal
2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 DismApi.dll:
- DismShutdownInternal
2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 DismApi.dll:

2 questions - missing boot image, create mdt task sequence button missing

I'm learning SCCM 2012. I am watching a training video and the instructor shows a "Create MDT Task Sequence" button at the top of his ribbon bar when going into Task Sequence. I do not have this button - where did it go? I am
using 2012 SP1.
All I see is "Create Task Sequence" and "Create Task Sequence Media" but not "Create MDT Task Sequence".
Also - I only have an x86 boot image, and no x64. How do I get this into my inventory?
Thank you
Nathan

"Create MDT Task Sequence" will be visible after you install MDT and integrate it to SCCM.
MDT is different product and not part of default SCCM installation.
You can integrate MDT to SCCM to create advanced Task Sequence if the default is not suitable for your needs.
Integrate MDT to SCCM.
MDT latest version is 2013:
http://www.microsoft.com/en-us/download/details.aspx?id=40796
For creating x64 boot image:
http://social.technet.microsoft.com/Forums/en-US/a3877a66-d35c-49ca-95c5-1c02d1611f2f/default-x64-boot-image-not-created-during-sccm-2012-setup
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

System Image Utility fails to create boot image

I am not able to successfully build a boot image with the System Image Utility. The build starts and runs for about 1 minute and then I get 100's of ditto messages saying "No space left on device". There's plenty of space left on the device. Eventually I get a GUI message stating the there was an error creating the image. The image is of course unusable. This only happens on a Boot image. I have no problem making an install image from the same source. Is it just me??
Xserve G5 Dual Mac OS X (10.4.5)

I had simililar problems with much headscratching as the result.
I found that whenever I tried to create a boot image with System Image Utility (SIU) using an image file of my existing system as the source SIU would fail with the annoying "No space left on device" message everytime. I did a little investigating and found that SIU always created a 400 MB disk image file to copy to. So the error message was correct as my source was way over 4 GB.
I checked the manual and found the embarrasingly simple solution. It's not mentioned directly, rather it is stated that when you want to create an boot image from an existing system you should boot the machine containing the desired system on disk from an alternate source and the run SIU on that machine. The "trick" is that you're running SIU with the existing system mounted as a disk.
So I went back to my Xserve, mounted the image so it appeared on the desktop. Ran SIU and chose the mounted volume as the source instead of the image file, and hey presto!
MacBook Pro, Xserve, eMac, iMac... any Mac I can get my hands on Mac OS X (10.4.6)

Build & Capture TS (MDT) - Capture fails at PrepareOS (sysprep) with "Boot Image package not found"

Hi all,
I'm searching for a while on this one now... I'm unable to perform a "ZeroTouch" Build & Capture of my reference machine to get a master image, with Capture Media it seems to be working, but this is a manual step...
While running a W7SP1 Build & Capture task sequence, the "Capture the reference machine" group fails at "PrepareOS". The step before "PrepareOS", "Prepare ConfigMgr Client" runs without any issues.
The only error I can find, shows up in the report "OSD - history of a TS":
... 0005 that is either already released or we have not connected to it.
BootImage::ResolveImageSource( pszPackageId, sImagePackageSourcePath, sImageSourcePath), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\bootimage.cpp,732)
TS::Boot::BootImage::StageBootImage(sPkgID), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\prepareos.cpp,917)
PreStageWINPE(m_bDebug), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\prepareos.cpp,1363)
pCmd->Sysprep(bActivate, bMsd), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\main.cpp,270)
De-Initialization successful
Exiting with error code 2
sending with winhttp failed; 80072ee2
SendResourceRequest() failed. 80072ee2
Download() failed. 80072ee2.
Boot Image package not found.
he system cannot find the file specified. (Error: 80070002; Source: Windows)
Failed to pre-stage WINPE image, hr=0x80070002
Unable to sysprep the machine, hr=80070002
Sysprep'ing the machine failed, hr=80070002
I've searched the smsts.log file hundreds of times for errors, nothing there...
Can anyone give me a clue or just something...? I really don't know what my next step, to make this work, could be...
Thanks!

The error Torsten pointed out gave me some clue... After much digging around on the web, I've stumbled upon this
article which led me into adding the following TS-variables:
SMSTSDownloadRetryCount: 5
SMSTSDownloadRetryDelay: 15
It seems to be working now on all types of hardware...
Case closed, thank you for the assistance!
Let's hope this article can save someone a couple of days... :)
Wesley

Failed to Create MDT Boot Image in SCCM 2007

Similar Messages

Maybe you are looking for