Welcome
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.
Update Driver Manifests on Bare Metal Servers action repeatedly fails

BigFix Documentation Homepage
BigFix 11 Lifecycle Documentation
Welcome to the BigFix Lifecycle documentation, where you can find information about how to install, maintain, and use BigFix Lifecycle.
BigFix Platform
BigFix Query
Lifecycle overview
BigFix Lifecycle is single-agent, single-console technology that provides near real-time visibility into the state of endpoints.
Lifecycle guides in PDF format
Following is a list of links to the BigFix Lifecycle guides in PDF format:
Software Distribution
Use the BigFix Software Distribution applications to deploy software to endpoints across your network from a single location. Maintain control and visibility into software delivery and installation. Device owners can use the Self Service Application to manage software and other BigFix actions that are deployed to them as offers.
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/11 or Windows Server using in-place upgrade
  To upgrade your existing Windows systems to Windows 10/11 or Windows Server 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
Remote Control
BigFix Remote Control application helps to communicate between different components, clients, and endpoints within BigFix environment.
Power Management
Use Power Management to control, monitor, and manage conservation policies in your deployment.
Server Automation
Server Automation provides powerful automation. You can use it to sequence automation actions in steps across multiple endpoints.
Profile Management
Profile Management is a WebUI-based feature of BigFix Lifecycle. It provides Security Administrators the capability to define and deploy security policies to Windows 10 and macOS devices.
BigFix Remediate
BigFix MCM

Update Driver Manifests on Bare Metal Servers action repeatedly fails

Problem description: Update Driver Manifests on Bare Metal Servers action repeatedly fails

Solution/workaround

In a network where the download from the BigFix Root Server to the Bare Metal Server computer takes time (for example, long download chain for long relays hierarchy), the Update Driver Manifests on Bare Metal Servers action could repeatedly fail, during the Bare Metal Server installation or for a Sync Driver action.

This happens because there's a timeout for the Bare Metal Server to download the driver packages to import. If this time is not enough, the action will fail.

To solve this issue, you can add this system variable TEM_RELAY_DOWNLOADER_TIMEOUT and set its value in minutes, to give more time to the Bare Metal Server to download the driver packages.

For example, to give 90 minutes, you set the value of this system variable to 90. The Bare Metal Service must be restarted after adding or modifying this variable value.