Home
OS Deployment
BigFix OS Deployment, which is part of the BigFix Lifecycle Management suite, provides a consolidated, comprehensive solution to quickly deploy new workstations and servers throughout a network from a single, centralized location. This solution saves time and money, enforces a standardized and approved image, and reduces risks associated with non-compliant or insecure configurations.
Maintenance and troubleshooting
You can monitor deployment activities, correct exceptions and adjust configuration settings specific to your environment through dashboards and tasks available for these purposes.
Problems and limitations
You can troubleshoot and gather information about known problems and limitations. A solution or workaround is provided if available.
Creation of OS resource fails

OS Deployment
BigFix OS Deployment, which is part of the BigFix Lifecycle Management suite, provides a consolidated, comprehensive solution to quickly deploy new workstations and servers throughout a network from a single, centralized location. This solution saves time and money, enforces a standardized and approved image, and reduces risks associated with non-compliant or insecure configurations.
- Product overview
- Configuring the OS Deployment Environment
  To start working with OS Deployment, run the configuration Fixlets and tasks listed in the Setup Node.
- Managing MDT Bundles and Deployment Media for Windows targets
  To perform OS Deployment of Windows operating systems, you prepare your deployment environment and resources using the Bundle and Media Manager Dashboard.
- Managing Drivers for Windows Deployments
  The Manage Images and Drivers node includes tasks to prepare and import drivers for deployment to Windows targets.
- Managing Linux OS Resources and Deployment Media
  You can import Linux OS Resources needed to create network boot media and to capture and deploy Linux images
- Managing Images
  The Manage Images and Drivers node includes tasks to capture, import and manage images for deployment to targets.
- Upload Mode
  By default, the OS images are permanently stored in the BigFix root server.
- Reimaging
  Reimaging is the process of saving the user state on a computer, installing a new image on it, and then restoring the user state.
- Installing Windows 10 or Windows 11 using in-place upgrade
  To upgrade your existing Windows systems to Windows 10 or Windows 11 you can use the in-place upgrade fixlets.
- Bare Metal deployments
  You can install and manage BigFix for OS Deployment servers and create profiles for bare metal deployments.
- Monitoring Deployment Activities
  You can track and monitor all deployment activities in your Endpoint Management network.
- Maintenance and troubleshooting
  You can monitor deployment activities, correct exceptions and adjust configuration settings specific to your environment through dashboards and tasks available for these purposes.
  - Maintenance and Configuration tasks and Fixlets
  - Log and trace files
    When problems occur, you can determine what went wrong by viewing messages in the appropriate log files which provide information about how to correct errors.
  - Troubleshooting MDT Bundle process errors
    This topic describes how to troubleshoot errors in the different steps of the MDT Bundle creation process, describing a solution or workaround, if available.
  - Problems and limitations
    You can troubleshoot and gather information about known problems and limitations. A solution or workaround is provided if available.
- Setting up OS Deployment in an air-gapped network
  You can choose to configure your OS Deployment and Bare Metal Imaging site in an air-gapped network.
- Deprecated and Superseded functionalities
  This topic lists the functionalities that are still present in OSD, but are deprecated.
- Create Ubuntu OS Resources manually

Creation of OS resource fails

Problem description

When creating an MDT Bundle with a parameters.ini file pointing to an .iso containing install.esd or to a folder containing an install.esd image, and not install.wim, the creation of the bundle fails because the creation binary searches for install.wim.

Solution/workaround

The code was changed to manage that if install.wim is not found, install.esd is searched. But this works only with WADK 10 Version 1607.

To avoid this problem, use WADK 10 Version 1607.

Note: It might occur that the install.wim file is in fact an ESD file and it is handled as such.

Note: ESD images with more than one architecture are not supported, independently from the WADK level used.