How MSBATCH.INF Automated Windows 95 Setup

During the enterprise rollout of Windows 95, manually configuring every workstation was a time-consuming and error-prone process. The MSBATCH.INF file was Microsoft's solution for unattended mass deployments, acting as a script-driven answer file that supplied predefined configuration settings to the installation program. By bypassing interactive setup screens, it allowed system administrators to establish standardized, automated operating system installations across local machines and corporate networks.

The Purpose of MSBATCH.INF

The standard Windows 95 installation required extensive manual interaction, prompting technicians to enter product keys, select installation directories, configure network adapters, specify workgroups, and select optional components. MSBATCH.INF eliminated these manual prompts. When passed as a parameter to the setup program (such as running SETUP.EXE MSBATCH.INF), the installer read the file's contents, automatically populated the configuration fields, and suppressed the graphical user interface wizard where instructed.

Structure and Configuration Options

Structured similarly to a standard Windows INI file, MSBATCH.INF was organized into bracketed sections containing key-value pairs. Key sections included:

  • [Setup]: Managed core installation behavior, such as target directories (InstallDir), clean installs versus upgrades, Express or Custom installation types, and whether to prompt the user to reboot.
  • [System]: Defined hardware configurations, display resolutions, color depths, and international settings like time zones and keyboard layouts.
  • [Network]: Configured network clients, protocols (such as NetBEUI, IPX/SPX, or TCP/IP), computer names, workgroup or domain membership, and file and printer sharing permissions.
  • [OptionalComponents]: Allowed administrators to specify exactly which accessory programs, games, accessibility tools, and communication utilities to install or omit.

Creation and Deployment Methods

Administrators typically generated the file using Microsoft Batch 95 (BATCH.EXE), a graphical deployment utility included in the Windows 95 CD-ROM's administrative tools directory (\ADMIN\NETTOOLS\NETSETUP). This utility provided a user-friendly interface to configure parameters and output a valid .INF file. Alternatively, experienced administrators edited the file directly using any standard text editor.

Deployment was executed in several ways:

  1. Network Share Installs: Placing the setup files alongside MSBATCH.INF on a shared network drive (often via NetWare or Windows NT Server), allowing target client machines to boot via DOS network boot floppies and run setup unattended.
  2. Floppy-Based Overrides: Placing MSBATCH.INF in the root directory of a boot disk to automatically trigger a scripted local or network install.
  3. Server-Based Push Scripts: Incorporating the setup command line into logon scripts or batch routines.

Historical Impact

MSBATCH.INF marked a significant milestone in modern Windows systems administration. It introduced the baseline architecture for unattended operating system deployments that evolved into UNATTEND.TXT in Windows NT/2000/XP and ultimately modern unattend.xml answer files used in contemporary Windows imaging today.