none
Update Deployment Share When Why and How

    Question

  • Good day.
    I am looking for some detailed information on the Update Deployment Share process.
    Not that mine is not working I am just trying to work out what is actually happening.
    Of course one has to do this before creating boot media - I fully understand that. but once boot media is created I notice that I can create new task sequences and modify others and the boot media will see them without having to use the Update Deployment share process. - I think I understand why/how that happens.
    One of the reasons that I ask this question is because in SMS and SCCM the update distribution point can be a little ambigious in the work that is actually done.
    So when is it "best practice" to update deployment share? (while developing one's Task sequences and overall MDT) when is it essential to update the deployment share to reflect changes made in the workbench.
    I have spent a while looking for the definative answer before posting the question and not found it yet. So if you know where it is written down please feel free to just link me the Doc or article cause it will be one that I have not read already and will proberbly include more under the covers ino.

    Saturday, February 27, 2010 1:32 PM

Answers

  • Generally, you need to update the deployment share any time you make changes that affect the boot image.  That would include:

    - New or modified mass storage and network drivers that need to be injected into the boot image.
    - Changes to the boot image settings (e.g. adding fonts, changing the RAMdisk size)
    - Changes to the bootstrap.ini file
    - Changes to any of the files in an "extra" folder

    The update process has been optimized to do as little as possible, so it knows what changes need to be made.  If there were no changes, it should finish very quickly.

    -Michael Niehaus
     Senior Software Development Engineer
     mniehaus@microsoft.com
    Saturday, February 27, 2010 7:13 PM

All replies

  • Generally, you need to update the deployment share any time you make changes that affect the boot image.  That would include:

    - New or modified mass storage and network drivers that need to be injected into the boot image.
    - Changes to the boot image settings (e.g. adding fonts, changing the RAMdisk size)
    - Changes to the bootstrap.ini file
    - Changes to any of the files in an "extra" folder

    The update process has been optimized to do as little as possible, so it knows what changes need to be made.  If there were no changes, it should finish very quickly.

    -Michael Niehaus
     Senior Software Development Engineer
     mniehaus@microsoft.com
    Saturday, February 27, 2010 7:13 PM
  • Thanks.
    Didnt expect to find any of the "bright sparks" here today. Its the weekend ! dont you guys have lives ;)
    Saturday, February 27, 2010 8:11 PM
  • So when do I have to "Completely regenerate the boot images" as opposed to optimizing the boot image update process?

    Gary Dunlop


    GD
    Monday, February 28, 2011 8:03 PM
  • Kris - No we don't :^)
    Gary - Generally an optimized update is good enough, however if things don't work, or you have the time, go ahead and rebuild from scratch.


    Keith Garner (KeithGa.com) - Deployment Consultant - http://deployment.XtremeConsulting.com
    Tuesday, March 1, 2011 6:46 AM
    Moderator
  • If i have a machine currently deploying, is it a bad idea to update the deployment share?  Will it cause any problems?
    Thursday, April 14, 2011 1:40 PM
  • During deployment if you update the deployment share - will deployment fail.

    It really depends at what stage of installation you are in. A lot of stuff gets copied to the local machine during different phases of installation.

    Eg: if you make changes to the boot.wim and currently the installation is post Windows Install and is installing updates, nothing will be affected

    regards,
    Vik

    Thursday, April 14, 2011 1:47 PM