Sunday, 28 April 2013

ConfigMgr 2012 / SCCM 2012 SP1 Step by Step Guide Part 13c: Create MDT Boot Image

Back to main menu

There are two ways to create an MDT Boot Image

 1. Using the Create MDT Boot Image wizard (standalone)
2. As part of the Create MDT Task Sequence Wizard

 Part 13c of my Config Mgr 2012 SP1 Step by Step Guide describes #1 - using the Create MDT Boot Image wizard

 Navigate to Software Library > Operating Systems > Boot Images.


Right click and see the additional option added by the MDT/Config Mgr Integration. Choose "Create Boot Image using MDT"


 Specify a folder that will contain the boot image. Note that the folder must exist.



Enter a suitable name.





Enable command line support


Click Next to create the image




Verify progress


Boot image has been created



See new boot image


Folder has been populated with new boot image.
Posted by at
Labels: , ,

11 comments:

  1. Naveen23 May 2014 at 13:40

    Hi Gerry,

    I am getting following error while creating MDT

    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)

    ReplyDelete
    Replies
    1. Basti Scapa27 June 2014 at 08:59

      Hi Naveen,
      Temp disable your antivirus software and temp give everyone full control on SMS_P01 and REMINST shares. Then your newly created MDT Boot Image .wim file can be imported into SCCM.

      Delete
  2. Unknown2 June 2014 at 20:08

    Hi Gerry,

    I can not get this to work. I get the following:

    Copying WIM to the package source directory.
    Creating boot image package.
    Error while importing Microsoft Deployment Toolkit Task Sequence.

    Failed to verify that the WIM file has a valid compression type.

    Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The SMS 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)
    at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put()


    Any advice?

    Thanks

    Chris

    ReplyDelete
    Replies
    1. Gerry Hampson3 June 2014 at 12:29

      I do recall seeing this error before. Have you carried out some kind of upgrade or migration in this environment?

      Delete
  3. Unknown18 September 2014 at 03:14

    Hey Gerry. Great blog, it has helped out a lot with our setup of SCCM.

    I created the MDT Boot image using this guide and no errors came up. I distributed the content and that had no errors. What i can't get working is when you PXE boot for the option of SCCM Boot image x64 and MDT Boot image x64 to show up. It just automatically chooses the SCCM Boot image x64.

    Our old setup used to be WDS / MDT and it gave you the option to pick whichever boot image you wanted to go into. SCCM doesn't seem to do the same even though its based off WDS.

    I have tried ticking the "Deploy this boot image from the PXE-Enabled distribution point" under Data source on the MDT image.

    Our current server setup is
    Windows Server 2012 R2 with all current windows updates
    MDT 2013 + ADK 8.1
    SCCM 2012 R2 with the CU1

    Any suggestions on how we can get this working?
    Thank you

    ReplyDelete
    Replies
    1. Anonymous18 November 2014 at 18:23

      James, if you cancel out of the task sequence if your mdt boot files have been "deployed" it will kick in the mdt task sequence

      Delete
  4. Unknown7 May 2015 at 19:42

    Can this be done via scripting? (Powershell/wmi?)

    ReplyDelete
    Replies
    1. Gerry Hampson8 May 2015 at 10:25

      You can do most things through PoSH Matt. I've not tried this but have a look

      http://www.alexcomputerbubble.com/creating-a-winpe-5-x-boot-image-with-powershell/

      Delete
  5. Anonymous1 January 2016 at 23:48

    Hi Gerry, when trying to build the MDT x86 boot image I am getting an error.
    "Failed to read image property from the source WIM file due to error 80070002. My account has full local admin rights and is part of the local admin group on the SCCM 2012 server. Sounds like a permissions issue to me. Any help would be appreciated. Raji...

    ReplyDelete
    Replies
    1. Gerry Hampson11 January 2016 at 11:30

      Have you disabled your AV when carrying out this process?

      Delete
    2. Anonymous23 January 2016 at 01:49

      Yes, I did look under dcomcnfg and all the permissions are set correctly as well. I'm trying to perform this on a Windows 7 machine, since I'm running the SCCM console remotely.

      Delete

Subscribe to: Post Comments (Atom)