ℹī¸ Application Information

Technical details about how BitOSDT works

📘 What is BitOSDT?

BitOSDT (Bit Operating System Deployment Tool) is a PowerShell-based automation tool designed to streamline Windows deployment, configuration, and customization. It helps IT professionals and power users deploy clean Windows installations with pre-configured settings, software, and drivers.

1. PowerShell Modules Used

BitOSDT leverages several PowerShell modules and cmdlets depending on the tasks and options selected:

1.1 Core PowerShell Modules

Module Purpose Source
BitOSDT Enhanced module for imaging and deployment - interacts with OSDCloud and uses some of their functions Custom (BitOSDT)
OSD Operating System Deployment - Core module for Windows imaging and deployment PowerShell Gallery (Microsoft)
OSDSUS Software Update Services - Manages Windows Updates during deployment PowerShell Gallery (David Segura)
PSWindowsUpdate Windows Update automation and management PowerShell Gallery (Michal Gajda)
MDT Provides cmdlets for managing Microsoft Deployment Toolkit (MDT) deployment shares, task sequences, and operating system images Microsoft Deployment Toolkit
LiteTouch Exposes MDT LiteTouch scripts and functions for automating task sequences and deployment actions Microsoft Deployment Toolkit
DISM Deployment Image Servicing and Management for mounting, editing, and applying WIMs and ISOs Built-in (Microsoft)
ImageTools Community module to automate WIM capture, apply, and export operations PowerShell Gallery
WIMManager Simplifies image mounting, driver injection, and cleanup tasks PowerShell Gallery
Storage Disk, partition, and volume management Built-in (Microsoft)
NetAdapter Network adapter configuration and driver management Built-in (Microsoft)
PnPDevice / PnpUtil Manages device drivers, enumerates hardware, and handles driver installation Built-in (Microsoft)
ComputerManagementDsc Desired State Configuration (DSC) resources for machine setup (rename, join domain, local users) PowerShell Gallery (Microsoft)
NetworkingDsc DSC resources for network configuration (adapters, IPs, DNS, routes) PowerShell Gallery (Microsoft)
xActiveDirectory / ADDSDeployment Automates AD join or domain controller promotion during deployment PowerShell Gallery
NetTCPIP / NetSecurity Manages network settings, firewall, and routing configuration Built-in (Microsoft)
Appx / PackageManagement Manages AppX packages and installs software from repositories Built-in (Microsoft)
Defender / DefenderPerformance Enables configuration of Windows Defender settings pre- or post-deployment Built-in (Microsoft)
WindowsAutopilotIntune Manages Autopilot device registration and profiles PowerShell Gallery (Microsoft)
CMDeploymentTools Community module for scripting ConfigMgr deployments and content distribution PowerShell Gallery
WMI / CIMCmdlets Provides WMI access for SCCM site server automation (querying SMS_ classes) Built-in (Microsoft)

⚙ī¸ Note on Module Usage

These modules are used dynamically based on your selected tasks and options. Not all modules are loaded simultaneously - BitOSDT intelligently loads only the modules required for your specific deployment scenario.

1.2 WinPE Optional Components

1.3 External Tools & Utilities

2. Download Sources

BitOSDT fetches Windows images, drivers, and updates from the following sources:

2.1 Windows Installation Media

🌐 Official Microsoft Sources

  • Microsoft Update Catalog: https://www.catalog.update.microsoft.com
  • Windows Media Creation Tool: https://www.microsoft.com/software-download
  • UUP Dump (Unified Update Platform): https://uupdump.net - Community-maintained tool that downloads directly from Microsoft servers
  • Volume Licensing Service Center (VLSC): For enterprise customers with licensing agreements

2.2 Drivers & Updates

2.3 Software Packages (Optional)

3. Elevation & Permissions

⚠ī¸ Administrator Privileges Required

BitOSDT MUST run with elevated administrator privileges. The tool performs system-level operations that require full administrative access.

3.1 Why Administrator Rights Are Required

3.2 UAC (User Account Control) Prompts

BitOSDT will trigger Windows UAC prompts when launched. You must click "Yes" to allow the application to make system changes.

# BitOSDT automatically checks for elevation if (-not ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)) { Write-Error "BitOSDT requires Administrator privileges. Please run as Administrator." Exit 1 }

4. File System Operations

4.1 Read Operations

BitOSDT reads from the following locations:

4.2 Write Operations

BitOSDT writes to the following locations:

4.3 Delete Operations

BitOSDT may delete:

⚠ī¸ Data Loss Warning

BitOSDT can PERMANENTLY DELETE all data on the target drive. Always ensure you have backups before proceeding with deployment operations.

5. Data Storage on Final OS

5.1 What Data Is Stored?

After deployment, BitOSDT leaves the following on the installed system:

Location Data Stored Purpose
C:\BitOSDT Deployment logs, driver cache, configuration files Troubleshooting and audit trail
%TEMP%\BitOSDT Temporary working files (cleaned after completion) Installation staging and processing
%LOCALAPPDATA%\BitOSDT User-specific configuration and cache User preferences and local settings
HKEY_USERS\Software\BitOSDT Deployment timestamp, BitOSDT version, configuration settings System identification and audit
C:\WIN_Mount Temporary mount point for WIM images (deleted after use) Used to add WinPE features - removed after image creation
C:\OSDCloud OSDCloud deployment files (if using OSDCloud features) OSDCloud-specific deployment data (occasional)
C:\ProgramData\OSDCloud OSDCloud shared data (if using OSDCloud features) OSDCloud system-wide settings (occasional)
%APPDATA%\OSDCloud OSDCloud user data (if using OSDCloud features) OSDCloud user preferences (occasional)

ℹī¸ About OSDCloud Folders

OSDCloud folders only appear if you're using OSDCloud integration features. If you're using BitOSDT standalone without OSDCloud, these directories will not be created.

5.2 NO Personal Data Stored

✅ Privacy Assurance

BitOSDT does NOT store any personal information on the deployed OS:

  • ❌ No license keys embedded in the OS
  • ❌ No user account information
  • ❌ No MAC addresses or hardware IDs
  • ❌ No telemetry or tracking beyond standard Windows telemetry
  • ❌ No "phone home" functionality

5.3 Logs & Audit Trail

Deployment logs are stored for troubleshooting:

These logs contain: Timestamps, operations performed, success/failure status, and error messages. They do NOT contain personal information or license data.

6. Network Activity

6.1 Outbound Connections

BitOSDT makes network connections to:

6.2 Firewall & Proxy Support

BitOSDT respects system proxy settings and can work behind corporate firewalls. Ensure the following domains are whitelisted:

7. Security Considerations

⚠ī¸ Important Security Notes

  • Third-Party Dependencies: BitOSDT uses PowerShell modules from third parties. We cannot control vulnerabilities in these dependencies.
  • Antivirus Detection: Some antivirus software may flag BitOSDT as suspicious due to its system-level operations. This is a false positive.
  • Secure Boot: BitOSDT supports Secure Boot-enabled systems. Drivers must be signed by Microsoft.
  • Code Signing: BitOSDT executables are digitally signed. Verify the signature before running.

7.1 Best Practices

8. System Requirements

8.1 Host System (Running BitOSDT)

8.2 Target System (Deployment Destination)

9. Support & Troubleshooting

If you encounter issues with BitOSDT:

📧 Get Help

9.1 Common Issues

10. Open Source Components

BitOSDT uses the following open-source components:

We extend our gratitude to the open-source community and all contributors to these projects.