In the Server-Based Setup dialog box, the Set Server Install Path box shows the mapped drive or the UNC path for the selected server.
For example, if the server where you want to install the files is named NWSVR1 and the share is WIN95SRC, type:
Notice that you can specify a UNC path for a NetWare server if you are already attached to that server.
If you specify a subdirectory on the server and that directory does not already exist, Server-based Setup asks if you want to create the directory, and then completes this action if you confirm the message.
If you have insufficient privileges for connecting to or creating a directory on the specified server, a message warns you. You can specify another server, or quit Server-based Setup and log on using an account that has sufficient privileges on the specified server.
When Server-based Setup is set to a new path, it looks for the Registry file (NETSETUP.POL) that it uses to track which computers have been set up. Each time you use Server-based Setup to create a machine directory, an entry is added to this file. No entry is added when a user runs Windows 95 Setup from that shared directory.
Note NETSETUP.POL is read only by Server-based Setup to create MSBATCH.INF. You cannot run System Policy Editor to read or modify NETSETUP.POL. Also, you cannot edit MSBATCH.INF using Server-based Setup; you must edit setup scripts using a text editor.