Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security & DevOps Insights

  • Home
  • About
  • Advertise With US
  • Contact
  • Reviews
  • Toggle search form
Home » Windows Server » Differences between Capture image, Discover image, Install and Boot images
  • image 38
    How to Fix “Unknown hard error” on Windows Server and Windows 10 Windows
  • Machine does not support XSAve
    How to disable side-channel mitigations on VMware Workstation Virtualization
  • FileNotFoundError Errno 2 No such file or directory
    Fix FileNotFoundError: [Errno 2] No such file or directory Scripts
  • sdfgh 1
    How to fix “Unable to Sign In: Domain Not Available” Windows Server
  • GNS 3
    Graphical Network Simulator: How to uninstall GNS3 in Windows Windows
  • dfghjk
    How to setup and arrange your external displays on your Mac Mac
  • CAL Removal
    How to Remove and Manage RDS Licenses Web Server
  • FIDO KEY FEATURE
    How to use a Fido Certified U2F Key for Authentication Password Manager

Differences between Capture image, Discover image, Install and Boot images

Posted on 24/05/202008/09/2024 Christian By Christian 2 Comments on Differences between Capture image, Discover image, Install and Boot images


In this article, we shall discuss the differences between Capture image, Discover image, Install and Boot images. Windows Deployment Services (WDS) role is to efficiently install Windows on multiple computers automatically. This involves installing Windows on a device called the reference computer. Then copying the contents of the hard disk drive of that Windows installation onto other computers. Please how to configure Windows Deployment Services on Windows Server. Also, see how to install Dynamic Host Configuration Protocol on Windows Server 2019.

Therefore, imaging is the process of taking a snapshot of an entire hard disk of a device or server and saving it to the file. Therefore a single image file will contain an entire operating system (OS) installation.

The idea here is to take a single image and then deploy it to multiple devices in an automated fashion. This will in turn save us time and effort. (We will only have to spend time configuring one device which we will use to deploy other systems.

You may want to see the following guides: How to add boot and install images to Windows Deployment Services and configure Multicast transmission via the GUI and WDSUTIL. Learn how to setup and install WDS.

Note: The image which we deploy to other machines is called the base image or source image.We can have several types of images on our WDS server. We can extract those images from our DVD media or from downloadable media.

Install.wim

An install image stores the operating system that will be installed on a client (remote) computer. This install image contains all the settings and applications that were installed and configured from a reference computer.

This install image is used to deploy Windows to the other computers in your enterprise environment. The file format of an install image is wim. Simply put, an install image is a wim file containing a Windows operating system.

Boot.wim

Boot images are the Windows Preinstallation Environment (Windows PE) images that are used to start the deployment. They can be started from a CD or DVD, an ISO file, a USB device, or over the network using a Pre-Boot Execution Environment (PXE) server. The boot images connect to the deployment share on the server and start the deployment.

Boot images are used to boot computers before the install image is loaded. It holds the minimal operating system (Windows PE) that is sent to the client when it first connects to the WDS server.

This image is a stripped-down OS that only includes the necessary drivers (tools) to install, deploy, and repair Windows. This image is necessary so that the Windows Installation media has something to boot up from. Simply put, boot images are used to boot computers before the install image is loaded and it is just a bootable copy of Win PE that is setup to automatically contact the WDS Server over the network when the computer boots up.

Simply put, a boot image is a Windows PE that is sent to the client when it first connects to the WDS.

Note: You can also have multiple boot images on our WDS server. In that case, clients will see a menu of boot images and be able to select the proper one.

Drivers from boot.wim are needed for booting the windows OS which is the first phase of windows installation, while install.wim is needed for the second phase of windows installation. WIM files can be manipulated using systems such as MDT or WDS, to add drivers or distribute them out to clients.

In the Windows Deployment Services world, below are some additional boot images

Capture Image

A capture Image is required for an environment where you are deploying a similar OS that contains the same basic applications. The image is used to create a captured image.

Simply put, it is a bootable copy of WinPE that allows you to copy the hard disk of the reference computer as a WIM file over the network to WDS. This WIM file is called the Install image.

The captured image is a specialized version of WinPE that works with PXE to boot the computer over the network using PXE. When Win PE boots, the captured image will find the WDS and create the install image to WDS.

Discover Image

A bootable copy of WinPE that allows you to copy the reference computer as a WIM file. Unlike a captured image, the Discover Image is booted via DVD or USB Key.

Simply put, a discover boot image is used when we don’t have PXE-enabled NIC. This image is then placed on removable media such as CD, DVD, or USB drive.

I hope you found this blog post on the Differences between Capture image, Discover image, Install and Boot images helpful. If you have any questions, please let me know in the comment session.

5/5 - (1 vote)

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Windows Server Tags:Boot Image, deployment, install.wim, troubleshooting, WDS, Windows 10, Windows Deployment Services, Windows Server 2016

Post navigation

Previous Post: Install Applications with Winget CLI on Windows
Next Post: The security database on the server does not have a computer account for this workstation trust relation [Part 1]

Related Posts

  • How to determine Active Directory Site Name
    How to determine Active Directory Site Name Network | Monitoring
  • Windows server 2025 set up
    Install Windows Server 2025 via iDRAC Virtual Media or PXE Windows Server
  • ansible business cards 1600x0 c default
    Kerberos error: Clock skew too great while getting initial credentials Windows Server
  • telnet
    Could not open a connection to the host, on the port, connect failed Windows Server
  • wingettool
    Install Applications with Winget CLI on Windows Windows Server
  • diag7
    How to run Windows Memory Diagnostics Tool on Windows Windows

More Related Articles

How to determine Active Directory Site Name How to determine Active Directory Site Name Network | Monitoring
Windows server 2025 set up Install Windows Server 2025 via iDRAC Virtual Media or PXE Windows Server
ansible business cards 1600x0 c default Kerberos error: Clock skew too great while getting initial credentials Windows Server
telnet Could not open a connection to the host, on the port, connect failed Windows Server
wingettool Install Applications with Winget CLI on Windows Windows Server
diag7 How to run Windows Memory Diagnostics Tool on Windows Windows

Comments (2) on “Differences between Capture image, Discover image, Install and Boot images”

  1. Avatar photo Tim says:
    08/04/2021 at 9:35 PM

    Very well written and easy to understand. Thank you!

    Log in to Reply
    1. chris Christian says:
      08/04/2021 at 9:37 PM

      You are welcome!

      Log in to Reply

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

sysadmin top30a

  • image 38
    How to Fix “Unknown hard error” on Windows Server and Windows 10 Windows
  • Machine does not support XSAve
    How to disable side-channel mitigations on VMware Workstation Virtualization
  • FileNotFoundError Errno 2 No such file or directory
    Fix FileNotFoundError: [Errno 2] No such file or directory Scripts
  • sdfgh 1
    How to fix “Unable to Sign In: Domain Not Available” Windows Server
  • GNS 3
    Graphical Network Simulator: How to uninstall GNS3 in Windows Windows
  • dfghjk
    How to setup and arrange your external displays on your Mac Mac
  • CAL Removal
    How to Remove and Manage RDS Licenses Web Server
  • FIDO KEY FEATURE
    How to use a Fido Certified U2F Key for Authentication Password Manager

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,825 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

AWS Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2025 TechDirectArchive

 

Loading Comments...
 

You must be logged in to post a comment.