Windows 95 Network Deployment Script: MSBATCH.INF

During the mass enterprise adoption of Windows 95, system administrators relied on an automated configuration file named MSBATCH.INF to deploy the operating system across corporate networks. This article explains the role of MSBATCH.INF, how it facilitated silent and hands-free installations over local area networks (LANs), and the administrative tools Microsoft provided to manage automated rollouts without visiting every individual desktop.

The Role of MSBATCH.INF

MSBATCH.INF served as the primary answer file for unattended Windows 95 installations. In a corporate environment, manually inserting installation media and answering interactive setup prompts—such as entering product keys, specifying machine names, and choosing networking protocols—was inefficient.

By passing the MSBATCH.INF file to the Windows 95 setup program, administrators could predefine all hardware, network, and user settings, enabling fully automated, non-interactive installations across hundreds of workstations.

Deploying Over the Network

To deploy Windows 95 across a local network, administrators used a centralized shared directory on a server (often hosted on Windows NT Server or Novell NetWare). The deployment workflow operated as follows:

  1. Server Setup: The installation source files were copied to a shared network drive using the Server-Based Setup tool (NETSETUP.EXE).
  2. Workstation Boot: The client machine was booted into MS-DOS with basic network interface card (NIC) drivers and network client software (such as the Microsoft Client for MS-DOS).
  3. Execution: The client mapped a network drive to the server's shared installation folder and executed the setup program with the script attached: 
    SETUP.EXE Z:\WIN95\MSBATCH.INF

If the script was renamed to MSBATCH.INF and placed in the same directory as SETUP.EXE, the installer automatically detected it without requiring explicit command-line flags.

Configuration via the Batch95 Tool

While MSBATCH.INF was a plain text file structured with standard INI/INF syntax that could be modified in a text editor, Microsoft provided a dedicated graphical utility called Batch Setup (BATCH.EXE), included in the Windows 95 Resource Kit.

The Batch Setup utility allowed administrators to define critical enterprise settings, including:

  • Network adapter drivers and configurations
  • Protocols (NetBEUI, IPX/SPX, TCP/IP) and IP addressing schemes
  • Domain or Workgroup membership
  • Client for Microsoft Networks or NetWare client integration
  • Automated acceptance of the End-User License Agreement (EULA)
  • Default software components and peripheral installations

Historical Impact

The introduction of MSBATCH.INF represented Microsoft's first major standard for mass client-OS scripting over PC networks. It eliminated manual intervention during desktop upgrades and paved the way for subsequent automated deployment standards, such as UNATTEND.TXT in Windows NT 4.0 and Windows 2000, and later XML-based deployment systems in modern Windows environments.