none
Sysprep fails on Windows 2008 R2 after installing Windows Management Framework 5.0... RRS feed

  • Question

  • Hey guys,

    We decided to make the recently released Windows Management Framework 5.0 a standard component in al our image builds. I was able to get it installed and use MDT to successfully capture new reference images on Windows 7 and Windows 2012 R2, but for some reason when MDT attempts to run sysprep right before capture on Windows 2008 R2 it fails. When I run the same task sequence and omit the Windows Management Framework 5.0 sysprep and capture succeeds.

    Anyone know of a fix for this?

    Wednesday, January 6, 2016 7:30 PM

Answers

  • You could look at the sysprep logs and check if the failure is there. https://technet.microsoft.com/en-us/library/hh825084.aspx.    Your BDD.log might also be interesting.


    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Long story short, I was hoping for a "quick fix" on this. I posted the question thinking maybe I'd get lucky and someone else would know right off how to resolve this. I did examine the logs, but there was so much going on there, it became clear that troubleshooting this was going to be time consuming. Right now I’m in the midst of a series of deadline scenarios that make that something I can’t get into right now. As a workaround I just took the install script I wrote for Windows Management Framework 5.0 and just added it as a mandatory application install as part of our standard server deployment (i.e. It’s not integrated into our reference image but installs after the fact via task sequence). Not as clean as I’d lie but it gets the job done. I’ll probably revisit this when time allows.

    Thanks anyway guys!


    • Marked as answer by ZeusABJ Wednesday, January 13, 2016 11:01 PM
    Wednesday, January 13, 2016 11:01 PM

All replies

  • You could look at the sysprep logs and check if the failure is there. https://technet.microsoft.com/en-us/library/hh825084.aspx.    Your BDD.log might also be interesting.


    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Wednesday, January 6, 2016 8:23 PM
    Moderator
  • You could look at the sysprep logs and check if the failure is there. https://technet.microsoft.com/en-us/library/hh825084.aspx.    Your BDD.log might also be interesting.


    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Long story short, I was hoping for a "quick fix" on this. I posted the question thinking maybe I'd get lucky and someone else would know right off how to resolve this. I did examine the logs, but there was so much going on there, it became clear that troubleshooting this was going to be time consuming. Right now I’m in the midst of a series of deadline scenarios that make that something I can’t get into right now. As a workaround I just took the install script I wrote for Windows Management Framework 5.0 and just added it as a mandatory application install as part of our standard server deployment (i.e. It’s not integrated into our reference image but installs after the fact via task sequence). Not as clean as I’d lie but it gets the job done. I’ll probably revisit this when time allows.

    Thanks anyway guys!


    • Marked as answer by ZeusABJ Wednesday, January 13, 2016 11:01 PM
    Wednesday, January 13, 2016 11:01 PM