MDT 2012 Update 1 - Error 500 = Variable is undefined RRS feed

  • Question

  • Hi All,

    I am getting an error I have not seen before with MDT 2012.
    Error 500 = Variable is undefined

    This happens when I try to Capture an image of this reference computer. Below is the information in the Deployment Wizard and as soon as I click next I get the error above.

    File Name:

    Please help this is a time crunch.


    Tuesday, September 10, 2013 8:11 PM

All replies

  • If you're running the Capture only task sequence, please don't... It's not very reliable...

    Use the standard client task sequence, and add the suspend action if you need to modify the refimage before sysprep and capture.

    / Johan

    Regards / Johan Arwidmark Twitter: @jarwidmark Blog: FB:

    Tuesday, September 10, 2013 9:42 PM
  • Thanks for the reply but I am not 100% what you mean. Are you saying use the standard client TS and add the syprep and capture TS steps to it? If so can you email me an example or provide screenshot?


    Wednesday, September 11, 2013 4:17 AM
  • Nope, I 'm saying the standard client task sequence already have those steps. It's made for both normal deployments, as well as build and capture. You change the behavior via rules (CustomSettings.ini) or the wizard.

    Check this video from TechEd, the steps are valid for Windows 7 as well.

    Building the Perfect Windows 8 Image

    / Johan

    Regards / Johan Arwidmark Twitter: @jarwidmark Blog: FB:

    Wednesday, September 11, 2013 5:46 AM
  • This still didn't work. I had to place a call to Microsoft. I will give resolution later. Thanks all. 
    Wednesday, September 11, 2013 6:22 PM
  • Additionally, if you are getting this error it means that there is a script error somewhere, and you will need to do some debugging here.

    1. Check the bdd.log file. Specifically, which component did you receive the "variable is undefined" error message.

    2. If you don't see any errors in the bdd.log file, you may need to check the smsts.log file on the client machine, to see which script was executing when the error happened.

    3. Finally, if you are still having trouble, it may require some debugging. I wrote this tool a while back to help in debugging pesky scripts:


    Keith Garner -

    Tuesday, September 24, 2013 1:03 AM