none
is it bad practice to capture an image that was deployed from mdt after adjustment? RRS feed

  • Question

  • is it bad practice to capture an image that was deployed from mdt after adjustment?

    or there is no any consequences?


    "When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

    Thursday, October 2, 2014 5:24 PM

Answers

  • Will it hurt anything?  Probably not. Is it bad to do?  Absolutely yes. Unless you're working with something that is impossible to silently install, you should perform tasks via script. This ensures that any adjustments you make are consistent every time you capture the image.
    • Marked as answer by pob579 Thursday, October 2, 2014 9:07 PM
    Thursday, October 2, 2014 6:15 PM
  • During the capture process, MDT will run a Sysprep to generalize the image. This is a standard procedure.

    You can run sysprep against an image that had been previously sysprep'ed.

    *HOWEVER* With Windows Vista and newer, you can only sysprep an image a maximum of 3 times before sysprep will start failing. http://technet.microsoft.com/en-us/library/cc766514(v=ws.10).aspx

    You can use the sysprep /generalize command to reset Windows Product Activation a maximum of three times

    In your scenario it's probably OK if the previous image was fairly new, and had only been syspreped once.

    This is one of the primary selling points of automated image build systems like MDT.
    Put your changes and know-how into MDT, and let MDT crank out a new build automatically.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Friday, October 3, 2014 5:24 PM
    Moderator

All replies

  • Will it hurt anything?  Probably not. Is it bad to do?  Absolutely yes. Unless you're working with something that is impossible to silently install, you should perform tasks via script. This ensures that any adjustments you make are consistent every time you capture the image.
    • Marked as answer by pob579 Thursday, October 2, 2014 9:07 PM
    Thursday, October 2, 2014 6:15 PM
  • During years I never captured the image deployed from mdt.

    Today was a rush.

    The request:

    to install time consuming configuration application into the image.

    I restored acronis image that used during couple of weeks for captures after small changes.

    And decided to capture it again before the installation of local progam and final capture.

    It failed after multiple trials. I posted the error yesterday here:

    http://social.technet.microsoft.com/Forums/windowsserver/en-US/a702bf17-8375-4bc7-b458-8ce4894f99e9/error-2147467259-during-capture?forum=mdt

    As a last tip before suggesting to deploy existing image and sysprep it 20 times I deployed the image from MDT applied just Windows KBs and captured again with MDT it worked without any prob.

    So against my usual habit I gave a deployd image for installing the tricky software and then will capture it for future deployment for 20 "special" computers. Feel not so good. But like you told:

    "Will it hurt anything?  Probably not"     I took a chance. In the image no AV, just small things like 7Z and Adobe.

    Encourage me for this case :)

    Thanks.


    "When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

    Thursday, October 2, 2014 9:07 PM
  • During the capture process, MDT will run a Sysprep to generalize the image. This is a standard procedure.

    You can run sysprep against an image that had been previously sysprep'ed.

    *HOWEVER* With Windows Vista and newer, you can only sysprep an image a maximum of 3 times before sysprep will start failing. http://technet.microsoft.com/en-us/library/cc766514(v=ws.10).aspx

    You can use the sysprep /generalize command to reset Windows Product Activation a maximum of three times

    In your scenario it's probably OK if the previous image was fairly new, and had only been syspreped once.

    This is one of the primary selling points of automated image build systems like MDT.
    Put your changes and know-how into MDT, and let MDT crank out a new build automatically.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Friday, October 3, 2014 5:24 PM
    Moderator
  • Good to know. Thanks!

    "When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

    Monday, October 6, 2014 3:54 PM