Skip to content

Question about the build and capture Task Sequence

Featured Replies

and probably a dumb question, but Im confused what this process does. It seems to deploy a WIM from Installation source, then copy up that WIM and push a copy back to a share again, which you use within a task sequence. Why dont you just directly use the WIM from the installation source ?

the idea is that you use this process to make changes to the standard wim, by introducing updates for example or installing apps, so the end result (the captured wim) contains not only the original operating system, but all the latest windows updates and a few key applications like office 2013 or similar...

  • Author

ok thanks. So if I want to deploy the base vanilla OS source as is, then there is no requirement for the build and capture process.

  • Author

wouldnt you normally just do the updates/software etc during the task sequence ?? Otherwise id need to re-capure the image every time something changed. or am I misunderstanding.

you can deploy updates during the task sequence, however in the case of say Windows 7 which has hundreds of updates, your deploy task sequence would take forever, so not a nice way to deliver OSD, for that reason you'd want to capture a 'gold' image once every quarter or so with as many windows updates bundled into it

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.