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. 

Similar Messages

  • 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.

  • 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 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.

  • Image Capture Boot Image Fails with 0xc000000f

    I am trying to capture a Windows 8.1 Enterprise (with Update) x64 installation using WDS, but the Capture Image fails to load. I used the boot.wim from the Windows Server 2012 R2 (with Update) ISO to create a boot image in WDS and then a capture image from
    it. After I press F12 and the progress bar finishes the following message appears:
    This only happens when I boot the capture image - the original boot image that I imported in WDS boots normally. I also tried with the Windows 8.1 (with Update) boot.wim, but the issue reoccurs. This is a Hyper-V VM on Windows Server
    2012. Is this a problem with the recent update?

    Hi,
    We’re currently experiencing exactly the same issue. Also a fully-updated Server 2012R2 (with the recent KB2919355 update) machine.
    So far, I found two other posts with exactly the same issue:
    1) http://wp.secretnest.info/?p=1474
    2)
    http://community.spiceworks.com/topic/472581-wds-capture-image-winload-exe-corrupt-or-missing
    According to these posts it seems like the issue occurs after the first time a capture image based upon a Windows 8.1 or Server2012R2 boot.wim is created.
    What I’ve tried so far is removing the server role, deleting the WDS store, rebooting the server and start over with a Windows 7 boot.wim. The normal boot.wim starts ok, but the created capture image doesn’t.
    So the process of creating the capture boot image did ‘something’ in a way the new boot.wim differences from the old boot.wim. To find out what, I first mounted the new .wim file to see if winload.exe is actually there – it is both in
    system32 as well as systen32\boot. So my second guess was that the Windows Boot Manager cannot find the windows loader, because of an incorrect declaration of disks in the BCD store.
    I used BCDEDIT to show the differences between the working and non-working boot images:
    Windows Boot Loader
    identifier {1d214c07-6892-401c-a762-04647ad38560}
    device ramdisk=[boot]\Boot\x64\Images\boot.wim,{b321afc0-8a23-4
    961-85dd-a10f3c46473f}
    description Windows 7 Boot Image
    osdevice ramdisk=[boot]\Boot\x64\Images\boot.wim,{68d9e51c-a129-4
    ee1-9725-2ab00a957daf}
    systemroot \WINDOWS
    detecthal Yes
    winpe Yes
    Device options
    identifier {b321afc0-8a23-4961-85dd-a10f3c46473f}
    inherit {68d9e51c-a129-4ee1-9725-2ab00a957daf}
    ramdiskmcenabled No
    ramdiskmctftpfallback Yes
    -- Second - Non Working disk --
    Windows Boot Loader
    identifier {872352a0-0ad9-46f6-8612-1aed71ea8534}
    device ramdisk=[boot]\Boot\x64\Images\boot-win7-capture.wim,{7a
    b86a3a-3651-4f50-a748-34f3e784158c}
    description Windows 7 Capture
    osdevice ramdisk=[boot]\Boot\x64\Images\boot-win7-capture.wim,{68
    d9e51c-a129-4ee1-9725-2ab00a957daf}
    systemroot \WINDOWS
    detecthal Yes
    winpe Yes
    Device options
    identifier {7ab86a3a-3651-4f50-a748-34f3e784158c}
    inherit {68d9e51c-a129-4ee1-9725-2ab00a957daf}
    ramdiskmcenabled No
    ramdiskmctftpfallback Yes
    So the ID for the osdevice is the same, and only the device is different, but mentioned correctly under Device options (as far as my knowledge goes in this subject). I hope there will be a solution anytime soon.

  • 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 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 2012 - Image failing during system restore - C:\LTIBootstrap still there. Autologin not happening.

    Hello,
    I'm hoping someone can assist.  I have an image that was working but the builtin admin account was disabled.  I went into the image and enabled the account and set a password.  I ran sysprep and capture.  Now, when i try to deploy either
    image, it installs the OS, reboots and then sits at a login (does not go into the admin account to continue).  I login and i notice that LTIBootstrap.vbs is sitting on the root of c along with the Minint folder and other MDT folders.  I have MDT
    on 2 servers and they both do the same thing.  Unattend.xml in c:\minint has the correct local admin/password
    Customsettings.ini:
    [Settings]
    Priority=Default
    Properties=MyCustomProperties
    [Default]
    DeployRoot=\\ourserver\D$\DeploymentShare$
    ComputerBackupLocation=Network
    Home_Page=http://home
    OSInstall=Y
    SkipAdminPassword=YES
    SkipApplications=YES
    SkipAppsOnUpgrade=YES
    SkipBDDWelcome=YES
    SkipBitLocker=YES
    SkipComputerName=YES
    OSDComputerName=HDQ-%SerialNumber%
    SkipComputerBackup=YES
    SkipDeploymentType=YES
    SkipDomainMembership=YES
    JoinDomain=OurDomain
    DomainAdmin=xxxx(Account with Join domain rights)
    DomainAdminDomain= Our Domain
    DomainAdminPassword=Password for account
    SkipAdminAccounts=YES
    SkipFinalSummary=NO
    FinishAction=Reboot
    SkipLocaleSelection=YES
    KeyboardLocale=en-US
    UserLocale=en-US
    UILanguage=en-US
    SkipPackageDisplay=YES
    SkipProductKey=YES
    SkipSummary=No
    SkipTaskSequence=NO
    SkipTimeZone=YES
    TimeZoneName=Eastern Standard Time
    SkipUserData=YES
    EventService=http://OurServer:9800
    [Settings]
    Priority=Default
    [Default]
    DeployRoot=\\OurServer\D$\DeploymentShare$
    UserID=account to join to domain                                                                                                                  
    USerDomain=Our Domain
    UserPassword=Account password to join domain
    Any help would be greatly appreciated.
    Thanks
    Rick
    BDD.LOG
    <![LOG[ZTINextPhase COMPLETED.  Return Value = 0]LOG]!><time="14:10:58.000+000" date="01-13-2014" component="ZTINextPhase" context="" type="1" thread="" file="ZTINextPhase">
    <![LOG[ZTINextPhase processing completed successfully.]LOG]!><time="14:10:58.000+000" date="01-13-2014" component="ZTINextPhase" context="" type="1" thread="" file="ZTINextPhase">
    <![LOG[Event 41001 sent: ZTINextPhase processing completed successfully.]LOG]!><time="14:10:58.000+000" date="01-13-2014" component="ZTINextPhase" context="" type="1" thread="" file="ZTINextPhase">
    <![LOG[Command completed, return code = -2147021886]LOG]!><time="14:10:58.000+000" date="01-13-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property LTIDirty is now = FALSE]LOG]!><time="14:10:58.000+000" date="01-13-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[If there is a drive letter defined, make sure we clear it now so we can *force* recalcutation.]LOG]!><time="14:10:59.000+000" date="01-13-2014" component="LiteTouch" context="" type="1" thread=""
    file="LiteTouch">
    <![LOG[Property OSDTargetDriveCache is now = DIRTY]LOG]!><time="14:10:59.000+000" date="01-13-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[LTI initiating task sequence-requested reboot.]LOG]!><time="14:10:59.000+000" date="01-13-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Event 41017 sent: LTI initiating task sequence-requested reboot.]LOG]!><time="14:10:59.000+000" date="01-13-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

    Hi Rick,
    To my understanding, sysprep and to be more specific the "gerenalize" step will make sure all personalized information will be removed before entering the capture mode.
    I'm aware additional created account's will be preserved, but I can't tell you about the built-in administrator account.
    The first thing that comes to mind is that, your Build task sequence uses a Unattend.xml, just the same as your Deploy task sequence does this.
    Assuming that you don't do anything you haven't mentioned with the account in the task sequence, like renaming the admin account or setting a different password during the task sequence. Cross checking both your Unattended.xml would be a good place to start.
    Also, it is known, that Windows allows the machine to be auto logged on, a couple of times. So please check if this isn't also the case. See this link for more info: http://support.microsoft.com/kb/324737
    Lastly if all else fails, you can set the account enabled, and a password by commandline, but this should only be done as a temporarily work around. See these links for more information: http://support.microsoft.com/kb/251394 and http://social.technet.microsoft.com/wiki/contents/articles/3040.enable-disable-the-local-hidden-built-in-administrator-account-in-windows-7.aspx
    Good luck!
    If this post is helpful please click "Mark for answer", thanks! Kind regards

  • MDT 2012 Image Fail

    I have created a brand NEW deployment share and will be testing it as soon as the server reboots. I am hoping that this will resolve my issue but in the mean time I am looking to see if any one else has ran in to this issue before. Below are the error(s)
    I am getting.
    Thank you all in advance for the help!
    FAILURE 5627: 2: Run DISM.exe error!
    Litetouch deployment failed, Return Code = -2147457259 0×80004005
    Failed to run the action: Install Operating Ssytem.
    Unknown error (Error: 000015Fb; Source Unknown)
    The execution of the group (Install) has failed and the execution has been aborted. An action failed.
    Operation aborted( Error: 80004004; Source :Windows)
    Failed to run the last action: Install Operatin System. Execution of task sequence failed.
    Unknow error (Error: 000015fb; Source Unknown)
    Task Sequence Engine failed: enExecutionFail
    Task Sequence execution failed withj error code 80004005
    error Task Sequence Manger failed to execute task sequence. Code 0×80004005  

    Thank you for the information. I have reviewed the logs, but being new to such an indepth issue is new to me and I am working it as I can. Below is some of the information I found in the log files. My setup is MDT 2012, WDS, on a 2KR2 server.
    BDD.log
    FAILURE Run DISM.exe
    smsts.log
    The execution of the group (Install) has failed and the execution has been aborted. An action failed.
    Operation aborted( Error: 80004004; Source :Windows)
    Failed to run the last action: Install OperatinG System. Execution of task sequence failed.
    Unknow error (Error: 000015FB; Source Unknown)
    Task Sequence Engine failed: enExecutionFail
    Task Sequence execution failed with error code 80004005
    DISM.log
    Microsoft-Windows-ErrorReportingUI.Resources, Version 6.1.7600.16385.pA = PROCESSOR_ARCHITECTURE_AMD64 (9)
    Microsoft-Windows-ErrorReportingCore.Resources Version 6.1.7600.16385.pA = PROCESSOR_ARCHITECTURE_AMD64 (9)
    Microsoft-Windows-ErrorReportingFaul.Resources Version 6.1.7600.16385.pA = PROCESSOR_ARCHITECTURE_AMD64 (9)
    CBS Failed to find a matching version for servicing stack: C:\Users\........
    CBS Failed to find a servicing stack directory in online store, [HResult = 0x80070490 - Error_Not_Found
    Multiel CSI errors (Access Denied) for the registry
    CSI Processing Namespace
    I am hoping some of this helps, becasue the only option I have as of now is to redo the entire computer profile for sysprep and capture. Maybe I configured the default profile wrong or missed a permissions item, not sure, but all help is greatful.

  • Solaris boot images fail with bad magic number

    hi guys, have had Solaris on boxes for allmost 10 years. I have never installed sol10, and I have a problem
    1. I download the zip file, then use winrar to unzip them..
    2. burt the image with nero 7
    when my SunBlade 1000 comes up I do the Stop-A, and from the Ok promt
    I do boot cdrom
    this fails with "bad magic number" I have redown loaded it and reburnt it with nero reinstalled
    and also changed out the DVD on SunBlade
    3 I found a copy of Solaris 8 and the I got back a 'bitch' where is Solaris 9 so, most likely the drive is OK
    HELP
    Cris Harrison

    Hello Cris,
    unfortunately I don't understand your last sentence !
    I found a copy of Solaris 8 and the I got back a '*****' where is Solaris 9 so, most likely the drive is OK
    If this was a Solaris 8 (7/01 or later) DVD that did successfully boot, your DVD drive firmware (assuming that this is the Sun Toshiba SD-M1401) is up-to-date. If the DVD drive has firmware 1007, an update to 1009 is required to boot from DVD. otherwise you won't be able to boot from DVD (boot from CD works and a DVD can be automounted/mounted).
    Partial output of probe-scsi
    Before update:
    Unit 0 Removable Read Only device TOSHIBA DVD-ROM SD-M14011007
    After update:
    Unit 0 Removable Read Only device TOSHIBA DVD-ROM SD-M14011009
    [*Patch 111649-04 - Toshiba DVD 1401 firmware update*|http://sunsolve.sun.com/search/advsearch.do?collection=PATCH&type=collections&queryKey5=111649&toDocument=yes]
    when my SunBlade 1000 comes up I do the Stop-A, and from the Ok promt ...
    Instead of trying to directly boot, disable auto-boot and retry after a clean power-on.
    Break with Stop-A
    setenv auto-boot? false
    reset-all
    boot cdrom
    Michael

  • 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:                       

  • 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)  

  • 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.

  • Issues with Boot Images & PXE Booting Since SP1 Install

    Good Afternoon All - 
    I recently updated to SP1, had some issues, but they got resolved.  Now, though, I'm having an issue booting to PXE as well as updating any boot images created
    before SP1 was installed.  Booting to USB Bootable media using a newly created boot image seems to work fine. 
    Boot Images
    When I update my DPs for any of my boot images in SCCM, they fail and i get the below error:
      Error: The wizard detected the following problems when updating the boot image.
    • Failed to install required components into the boot image
    The SMS Provider reported an error.: ConfigMgr Error Object:
    instance of SMS_ExtendedStatus
    • Description = "Failed to insert OSD binaries into the WIM file";
    • ErrorCode = 2152205056;
    • File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
    • Line = 4566;
    • ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
    • Operation = "ExecMethod";
    • ParameterInfo = "SMS_BootImagePackage.PackageID=\"BBS0012F\"";
    • ProviderName = "WinMgmt";
    • StatusCode = 2147749889;
    I've even gone as far as removing all drivers from the boot image, but still get the same message.  I was able to create a couple of
    new MDT boot images which seem to work fine, though.  I am not sure which log file is for boot images, but nothing appeared in distmgr.log.
    PXE Booting Issue
    After trying many things, I removed PXE config from my site and uninstalled WDS then started all over again.  Here's what I did and my results.  Please tell me what I'm missing...
    After uninstall & server reboot, I enabled PXE + every option in DP tab in SCCM
    It automatically installed WDS (same server) and added the two boot images I had checked for PXE use.  one x64 and one x86.
    I checked my DHCP Scope whose values hadn't changed sine it worked (that I know of).  They are:
    Option #66: 192.168.20.37 (SCCM Server/DP/PXE) 
    Option #67 \boot\x86\wdsnbp.com.  I've tried \boot\x86\pxeboot.com as well as each of these with x64.
    When I PXE boot from a workstation, I receive an IP, a bit of info, then it goes to Contacting Server....  When trying one of the boot files above, I was prompted for F12, but receved a blue screen with error.  When trying all other boot files,
    they just hang at Contacting Server until they timeout.
    I looked at SMSPXE.log and found something interesting...
    The IDs for the two boot images I have assigned to PXE are ABC003B3 & ABC00B36.  In the smspxe.log, though, it keeps repeating "could not find boot image ABC0012F!  12F does exist and is a boot image,
    but not the one I want to use by any means and does not have PXE checked.
    I went ahead and checked 12F, updated DPs (which failed - see above); unchecked it; then updated the DPs again.  PXEBoot.log showed that it was trying to remove the 12F files from RemoteInstall which was a good sign.  I then restarted the WDS service
    and tried PXE booting again.  Yet again, it failed and was still looking for 12F.
    Any suggestions / Ideas???  Thanks!
    UPDATE 1
    I just changed option #67 to \smsboot\x86\pxeboot.com then restarted the WDS service.  I booted to PXE and this time was asked to hit F12.  I did so and it looked as if it would work.
    Instead, I got a blue screen with the following error:
    Recovery
    Your PC needs to be repaired
    The boot configuration disk contains errors or is missing 
    file: boot\BCD
    Error Code: 0x000000f
    I think that it's the same error as before, but is blue instead of black due to new Win8ADK perhaps.  Thanks
    Ben K.

    Update 4
    Sorry to make this the longest post ever :)
    I just read that others with this error checked DISM.log.  I did so when running a DP update for the boot image and got the below errors:
    2013-01-11 16:27:04, Info                  DISM   DISM Provider Store: PID=1636 TID=5104 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2013-01-11 16:27:07, Info                  CBS    Failed to find a matching version for servicing stack: C:\Windows\TEMP\BootImages\{DADCFE01-3557-4058-99CC-2A15EDF905AF}\mount\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810b\
    [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
    2013-01-11 16:27:07, Info                  CBS    Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
    2013-01-11 16:27:07, Warning               DISM   DISM Provider Store: PID=4104 Failed to Load the provider: C:\Windows\TEMP\0555ABC5-006D-4C3F-B79F-EA0E723FA971\MsiProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-01-11 16:27:07, Warning               DISM   DISM Provider Store: PID=4104 Failed to Load the provider: C:\Windows\TEMP\0555ABC5-006D-4C3F-B79F-EA0E723FA971\TransmogProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-01-11 16:27:07, Error                 DISM   DISM Package Manager: PID=4104 The package WinPE-Scripting-Package is not applicable to the image. - CPackageManagerCLIHandler::Private_ProcessPackageChange
    2013-01-11 16:27:08, Info                  DISM   DISM Package Manager: PID=4104  Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
    2013-01-11 16:27:08, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/TEMP/BootImages/{DADCFE01-3557-4058-99CC-2A15EDF905AF}/mount/Windows/System32/config/SOFTWARE,
    the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
    (The above one appears 8 times - almost in a row)
    2013-01-11 16:27:08, Error                 DISM   DISM Package Manager: PID=4104 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081e)
    Help!  Thanks :)
    Ben K.

  • Update Boot Image Issues

    Environment:  SCCM 2012 SP1 CU3
    Issue:  errors when trying to update distribution points (Driver Additions)
    Error Message:
      Error: Boot image to update:
    • Microsoft Windows PE (x64)
      Error: Actions to perform:
    • Add ConfigMgr binaries
    • Disable Windows PE command line support
    • Add drivers
      Error: Failed to import the following drivers:
    • Intel(R) Ethernet Connection I217-LM
    • Broadcom NetLink (TM) Gigabit Ethernet
    • 3Com Dual Port 1000-SX PCI-X Server NIC
    • Realtek PCI GBE Family Controller
    • LAN7500 USB 2.0 to Ethernet 10/100/1000 Adapter
    • Intel(R) 82579LM Gigabit Network Connection
    • Intel(R) 82575EB Gigabit Network Connection
    • Intel(R) 82580 Gigabit Network Connection
    • Intel(R) 82599 Multi-Function Network Device
    • DELL PERC RAID Virtual Device
    • PERC H310 for Dell Precision
    • LSI MegaRAID Virtual Device
    • Intel(R) C600 series chipset SATA AHCI Controller
    • Intel(R) C600/C220 series chipset SATA RAID Controller
    • Intel(R) C600 Series Chipset SAS RAID Controller
    • Intel(R) 5 Series 4 Port SATA AHCI Controller
    • Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller
    • System Management Device
    • System Management Device
    • LSI SAS x28 Expander
    • LSI Adapter, SAS2 2116 Meteor ROC(E)
    • Intel(R) ICH9M-E/M SATA AHCI Controller
    • Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller
     Optional components:
    • Scripting (WinPE-Scripting)
    • Startup (WinPE-SecureStartup)
    • Network (WinPE-WDS-Tools)
    • Scripting (WinPE-WMI)
      Error: The wizard detected the following problems when updating the boot image.
    • Failed to inject a ConfigMgr driver into the mounted WIM file
    The SMS Provider reported an error.: ConfigMgr Error Object:
    instance of SMS_ExtendedStatus
    • Description = "Failed to insert OSD binaries into the WIM file";
    • ErrorCode = 2152205056;
    • File = "e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
    • Line = 4630;
    • ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
    • Operation = "ExecMethod";
    • ParameterInfo = "SMS_BootImagePackage.PackageID=\"PS100081\"";
    • ProviderName = "WinMgmt";
    • StatusCode = 2147749889;
    Anyone have any idea's why the WIM file will not update?  I have been trying to get a Dell 7440 to boot properly so I can image it but the problem is:  PXE loads fine but when the system starts to load the SCCM deployment piece it just restarts. 
    I have not found any errors during this portion and did not see anything in the SCCM logs.  Assumed it had to do with the drivers but now I am unsure.
    Thanks,
    JAK
    EDIT:  on a side note, I have re-created the boot images and removed and re-added drivers still same issues.

    SMSPROV.log
    CExtUserContext::EnterThread : User=**** Sid=0x0105000000000005150000002EA925CE2D54C0A5946DF1F931320000 Caching IWbemContextPtr=00000000050CF1A0 in Process 0xe60 (3680) SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: SMSAppName=Configuration Manager Administrator console SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: MachineName=****.**** SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: UserName=**** SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: ObjectLockContext=501335b7-4817-4296-9032-30a05bb53be6 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: ApplicationName=Microsoft.ConfigurationManagement.exe SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: ApplicationVersion=5.0.7804.1400 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: LocaleID=MS\0x409 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: ReturnAll=1 (Bool) SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: FolderTypeName=SMS_BootImagePackage SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: QueryQualifiers=1 (Bool) SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: InstanceCount=1001 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: __ProviderArchitecture=32 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: __RequiredArchitecture=0 (Bool) SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: __ClientPreferredLanguages=en-US,en SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Context: __GroupOperationId=10280 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    CExtUserContext : Set ThreadLocaleID OK to: 1033 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    CSspClassManager::PreCallAction, dbname=CM_PS1 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    ExecQueryAsync: START SELECT * FROM SMS_BootImagePackage WHERE ActionInProgress!=3 ORDER BY Name SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Adding Handle 45277256 to async call map SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    CExtProviderClassObject::DoCreateInstanceEnumAsync (SMS_Query) SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    CSspQueryForObject :: Execute... SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Execute WQL  =SELECT * FROM SMS_BootImagePackage WHERE ActionInProgress!=3 ORDER BY Name SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Execute SQL =select  all SMS_BootImagePackage.PkgID,SMS_BootImagePackage.Action,SMS_BootImagePackage.Architecture,SMS_BootImagePackage.DefaultImage,SMS_BootImagePackage.Description,SMS_BootImagePackage.DisconnectDelay,SMS_BootImagePackage.UseForcedDisconnect,SMS_BootImagePackage.ForcedRetryDelay,SMS_BootImagePackage.Icon,SMS_BootImagePackage.IgnoreSchedule,SMS_BootImagePackage.ImagePath,SMS_BootImagePackage.IsVersionCompatible,SMS_BootImagePackage.Language,SMS_BootImagePackage.LastRefresh,SMS_BootImagePackage.Manufacturer,SMS_BootImagePackage.MIFFilename,SMS_BootImagePackage.MIFName,SMS_BootImagePackage.MIFPublisher,SMS_BootImagePackage.MIFVersion,SMS_BootImagePackage.Name,SMS_BootImagePackage.NumOfPrograms,SMS_BootImagePackage.PkgID,SMS_BootImagePackage.PackageType,SMS_BootImagePackage.PkgFlags,SMS_BootImagePackage.StorePkgFlag,SMS_BootImagePackage.Source,SMS_BootImagePackage.PreferredAddress,SMS_BootImagePackage.Priority,SMS_BootImagePackage.SedoObjectVersion,SMS_BootImagePackage.ShareName,SMS_BootImagePackage.ShareType,SMS_BootImagePackage.SourceDate,SMS_BootImagePackage.SourceSite,SMS_BootImagePackage.SourceVersion,SMS_BootImagePackage.StoredPkgPath,SMS_BootImagePackage.StoredPkgVersion,SMS_BootImagePackage.TransformAnalysisDate,SMS_BootImagePackage.TransformReadiness,SMS_BootImagePackage.Version
    from vSMS_BootImagePackage_List AS SMS_BootImagePackage  where (SMS_BootImagePackage.PkgID not  in (select  all Folder##Alias##810314.InstanceKey from vFolderMembers AS Folder##Alias##810314  where Folder##Alias##810314.ObjectTypeName =
    N'SMS_BootImagePackage') AND SMS_BootImagePackage.Action <> 3) order by SMS_BootImagePackage.Name SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Results returned : 0 of 0 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    Removing Handle 45277256 from async call map SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    ExecQueryAsync: COMPLETE SELECT * FROM SMS_BootImagePackage WHERE ActionInProgress!=3 ORDER BY Name SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    CExtUserContext::LeaveThread : Releasing IWbemContextPtr=84734368 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
    SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    CExtUserContext::EnterThread : User=**** Sid=0x0105000000000005150000002EA925CE2D54C0A5946DF1F931320000 Caching IWbemContextPtr=00000000050CF0C0 in Process 0xe60 (3680) SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: SMSAppName=Configuration Manager Administrator console SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: MachineName=****.**** SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: UserName=**** SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: ObjectLockContext=501335b7-4817-4296-9032-30a05bb53be6 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: ApplicationName=Microsoft.ConfigurationManagement.exe SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: ApplicationVersion=5.0.7804.1400 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: LocaleID=MS\0x409 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: __ProviderArchitecture=32 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: __RequiredArchitecture=0 (Bool) SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: __ClientPreferredLanguages=en-US,en SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: __GroupOperationId=10290 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: __WBEM_CLIENT_AUTHENTICATION_LEVEL=6 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    CExtUserContext : Set ThreadLocaleID OK to: 1033 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    CSspClassManager::PreCallAction, dbname=CM_PS1 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    ExecMethodAsync : SMS_BootImagePackage::GetImageProperties SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Requested class =SMS_BootImagePackage SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Requested num keys =0 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    CExtProviderClassObject::DoExecuteMethod GetImageProperties SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    *~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspimagepackage.cpp(586) : Failed to get the image property from the source WIM file due to error 80070002~*~* SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    *~*~Failed to get the image property from the source WIM file due to error 80070002 ~*~* SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    CExtUserContext::LeaveThread : Releasing IWbemContextPtr=84734144 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    CExtUserContext::EnterThread : User=**** Sid=0x0105000000000005150000002EA925CE2D54C0A5946DF1F931320000 Caching IWbemContextPtr=00000000050CF0C0 in Process 0xe60 (3680) SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: SMSAppName=Configuration Manager Administrator console SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: MachineName=****.**** SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: UserName=**** SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: ObjectLockContext=501335b7-4817-4296-9032-30a05bb53be6 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: ApplicationName=Microsoft.ConfigurationManagement.exe SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: ApplicationVersion=5.0.7804.1400 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: LocaleID=MS\0x409 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: __ProviderArchitecture=32 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: __RequiredArchitecture=0 (Bool) SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: __ClientPreferredLanguages=en-US,en SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: __GroupOperationId=10295 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Context: __WBEM_CLIENT_AUTHENTICATION_LEVEL=6 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    CExtUserContext : Set ThreadLocaleID OK to: 1033 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    CSspClassManager::PreCallAction, dbname=CM_PS1 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    ExecMethodAsync : SMS_BootImagePackage::GetImageProperties SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Requested class =SMS_BootImagePackage SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    Requested num keys =0 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    CExtProviderClassObject::DoExecuteMethod GetImageProperties SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    *~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspimagepackage.cpp(586) : Failed to get the image property from the source WIM file due to error 80070002~*~* SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    *~*~Failed to get the image property from the source WIM file due to error 80070002 ~*~* SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    CExtUserContext::LeaveThread : Releasing IWbemContextPtr=84734144 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
    JAK

Maybe you are looking for

  • Inbound delivery partner profile question

    Hello, Based on the help documentation, i have setup a distribution model between ECC and EWM system. After executing this transaction /n/SPE/OL19, my distribution model is properly generated and I am able to send Idoc from ECC system. However on on

  • Spec oversight? Using dynamic-attributes in XML tag files

    I have a couple of tagfiles that generate form elements with specific conventions for the 'name' and 'value' attribute. Basically, a data binding framework. Dynamic attributes are useful because you can delegate all the usual html attributes to the g

  • Problem in new update 10.3.1.156​5

    I am using software release 10.3.1.1565 on my Z 10 device. But it is not working fine. My device is slow and even touch is not that much good. Also increasing and decreasing media player volume some noise is coming. Any suggestions.

  • Callback for specific step group

    Hi, I have a sequence, Main sequence. In this sequence, there is Setup, Main and Cleanup step group. Setup is to initialise my devices, Main is to perform the tests on my UUTs, Cleanup is to stop and clear task for my devices. I would like to have a

  • Windows Server 2012 as NTP Server for Windows Server 2008R2 Domain Controller

    We have one domain with 3 Windows Server 2008R2 DC's. Our Edge router is configured to get the time from the internet, and was our timesource for the PDC emulator. But lately we have migrated our major routers to Cisco IOS15, and now the timeservice