Windows 95 Automated Setup Script Tool

During the rollout of Windows 95 in enterprise environments, system administrators required an efficient method to deploy the operating system across multiple networked machines without manually completing the setup wizard on each computer. Microsoft solved this problem by providing BATCH.EXE (commonly referred to as Batch Setup or Microsoft Batch 95), a utility designed to generate unattended setup scripts. This article details what BATCH.EXE was, how it functioned, and how administrators used it to automate Windows 95 installations.

What Was BATCH.EXE?

Included within the Windows 95 Resource Kit and the CD-ROM's administration tools directory (\ADMIN\NETTOOLS\BIN), BATCH.EXE was a dedicated graphical tool developed by Microsoft. It eliminated the tedious process of manually writing configuration text files by providing a guided interface where administrators could define installation preferences in advance.

The Role of MSBATCH.INF

The primary function of BATCH.EXE was to generate an automated script file, typically named MSBATCH.INF. This file was a structured text-based setup script that contained predefined answers to every question the Windows 95 installation wizard would otherwise prompt the user to answer during setup.

Using BATCH.EXE, administrators could preconfigure:

  • User and System Information: Company name, computer name, workgroup, and domain membership.
  • Setup Options: Typical, Compact, Laptop, or Custom installation types.
  • Hardware and Peripherals: Network adapter configurations, printer setups, and display resolution settings.
  • Network Protocols: Client for Microsoft Networks, NetBEUI, IPX/SPX, or TCP/IP configuration details.
  • Automation Controls: Options to suppress user prompts, reboot automatically upon completion, and bypass license agreement acceptance screens.

How Administrators Executed Automated Deployments

Once the administrator generated the MSBATCH.INF file via BATCH.EXE, it was placed on a network distribution server alongside the Windows 95 installation source files, or written directly to a bootable floppy disk.

To run the unattended installation, the administrator or an automated batch script executed Setup from the MS-DOS command prompt using the script file as a parameter:

SETUP.EXE MSBATCH.INF

When called this way, the Windows 95 setup program read the configurations straight from the .INF file and deployed the operating system silently without requiring local user intervention.

BATCH.EXE established a precedent for Microsoft deployment tooling, serving as the direct precursor to the unattended deployment tools and answer files (UNATTEND.TXT and AUTUNATTEND.XML) used in modern versions of Windows.