The first step in preparing to use the Remoteboot service is to ensure that the server has enough disk space for the files needed by the remote clients. Use the values in the following table as a guideline.
Table 15.1 Disk Space Requirements
Component | Disk space required | |
Microsoft Network Client version 2.2 for MS-DOS | 5.1 MB | |
MS-DOS 3.30 | 0.7 MB | |
MS-DOS 4.01 | 1.5 MB | |
MS-DOS 5.00 | 2.8 MB | |
MS-DOS 6.x | 5.9 MB | |
Windows 3.1 | 12.4 MB | |
Windows 95 | 2.0 MB | |
Use this table to calculate the amount of disk space you need on the remoteboot server. For example, to install the Remoteboot service for a configuration of clients running MS-DOS 6.22, some with Windows 3.1, you need 23.4 MB of disk space, broken down as follows:
In addition, you need room for personal copies of remoteboot profiles (if needed) and for directories for each client, where people store their own data. The amount of space to allot per client is up to you. You can also define a separate server (or servers) to contain machine directories for Windows 95 clients, to distribute the load of storing client-specific data. Each Windows 95 client needs its own machine directory with a minimum of 8 MB of disk space; more if users install additional software.
Windows 95 remoteboot clients require 8 MB of RAM and must be 386-based or higher. The server you use as a Server-Based Setup server requires 90 MB of disk space to store Windows 95 files.