Has anyone added a custom wizard pane in MDT 2013? RRS feed

  • Question

  • I'm trying to add a couple of panes I created for 2012 and they don't seem to be showing up.  At first I tried using the MDT Wizard Editor, but it apparently doesn't support 2013 yet.  I also tried to hand edit the whole thing and that doesn't seem to be working either.

    Has anyone done this successfully?  If so, could you provide some hints or walkthroughs on what might have changed in MDT 2013?

    Tuesday, February 4, 2014 8:33 PM

All replies

  • Have you defined your pane in 


    Example: I've the files


    in the scripts folder.

    and in DeployWiz_Definition.xml I've added

    <Pane id="AVEVA-Asset" reference="DeployWiz_AVEVA-Asset.xml">

    I tried to open DeployWiz_AVEVA-Asset.xml with Wizard Editor and it works fine.

    Have you tried the guide here:

    Wednesday, February 5, 2014 8:24 AM
  • Yes, I *think* I've done all of that.  I'm really just exporting work that I did to my MDT 2012 environment.  It just never sees or displays my added XML files.  If everything is the same between 2012 and 2013, then I'll go back to tearing my hair out.  I was hoping there was something different.  Here's an example of what I have:


    <Pane id="Partition_Size" reference="DeployWiz_Partition_Size.xml">
    <Condition><![CDATA[UCASE(Property("SkipTaskSequence"))<>"YES" ]]></Condition>


      <Pane id="Partition_Size" title="Partition Size">

       <Condition><![CDATA[UCASE(Property("SkipTaskSequence"))<>"YES" ]]></Condition>
        <Body><![CDATA[<H1>Custom Options</H1>
    <p>Choose partition size for the OS disk:</p>
    <tr valign=top>
    <td width=100>
    <img src="DeployWiz_PS.png">
    <td width="100%">
    <p><span class="Larger">Partition size (in GB)</span>
    <input type=text id=OSDPARTITIONS0SIZE name=OSDPARTITIONS0SIZE size=2 ></p>
    <p>*Note: To use 100% of the drive, choose a size larger than the disk (ie, 999GB)</p>

    Wednesday, February 5, 2014 1:22 PM
  • Turns out that I'm just a moron.  I was using the wrong boot media and therefore going to the wrong share.
    Thursday, February 6, 2014 12:38 PM