Votos - 0, Puntuación media: 0 ( )

Fabricar: HP Tamaño del archivo: 361.97 kb Nombre del archivo: Idioma del manual:

3 - Disk 2 prepares the source file copy and launches the unattended installation
When the server is ready, a more complete boot disk is required to check the location of the OS
nb: the boot disk can
source files and configuration files (CD ROM or Network).
also be a .dsk
image file that can
The second boot disk is more difficult to create because we have to start the Netserver, access the
be downloaded by
CD ROM or a mapped network drive, copy all the files and then launch the installation.
a TT_RCC.
This disk will be an MS DOS boot disk, with CD ROM drivers (in case of unattended installation by
CD) or TCP/IP stack (in case of unattended installation from a shared distant directory).
Creation of the base boot disk:
nb: a Win9x-based
Use HPFORMAT.EXE on the HP Navigator CD, located in the directory \System and all the files such
system must
as msdos.sys, io.sys, etc. in the sub-directory \Dosstub\Language.
be used because
Usage:
this software does
hpformat -b bootSec [-i ioSys -m msdossys] [-l language] [-v label] drive
not work on an
where
NT system.
- b bootSec: boot sector for the formatted drive
- i ioSys: io.sys for the formatted drive, optional
- m msdossys: msdos.sys for the formatted drive, optional
- v label: disk label, optional
- l language: us, fr, ge, it, or sp
We can also copy XCOPY.EXE to the disk.
Creation of the network boot disk
Use “Network Client Administrator” on a Windows NT4 Server, choose “Make Network Installation
Disk”, Select the correct path for the Client files (the directory \Clients included on the Windows NT4
Server CD ROM), and then choose “Network Client MS DOS...”, a driver for the NIC integrated into
the Netserver or any that can easily be identified in the configuration files. When this has been
done, we can add some other useful information, such as the distant server name, etc., because all
this information will be required later. All the files necessary for the TCP/IP stack will be copied to
the disk and AUTOEXEC.BAT and CONFIG.SYS database files will also be added.
It is necessary for the disk to be able to boot so that we can run the above files.
Now refer to the specific configuration documentation to change PROTOCOL.INI and SYSTEM.INI
files located into \Net subdirectory.
Certain files must be modified to be appropriate for the automatic installation, in particular
SYSTEM.INI in the \Net directory in which it is necessary to remove the computer name, the
username, etc. and insert the correct “.DOS” driver files (see variables put in memory in the list
below).
It is necessary to format the partition of 2Go and to start a copy of all necessary files, i.e. \i386 for
OS and possibly other directories for additional applications such as pcAnywhere(r).
The following operation consists of loading in memory all the useful variables to parse to various
nb: all resource names
possible scripts. This stage is not mandatory but can prove useful when several different systems have
are arbitrary and
to be installed.
will depend
on the actual
ECHO SET TEMPLATE=%TEMPLATE%> A:\VARS.BAT
implementation.
ECHO SET COMPUTERNAME=%COMPUTERNAME%>> A:\VARS.BAT
ECHO SET LOGIN=Administrator>> A:\VARS.BAT
ECHO SET WORKGROUP=HP-LABS>> A:\VARS.BAT
ECHO SET DOMAIN=HP>> A:\VARS.BAT
ECHO SET NETDRIVE=i:>> A:\VARS.BAT
ECHO SET NETSERVER=E800-TTDM>> A:\VARS.BAT
ECHO SET NETSHARE=W2KSRV>> A:\VARS.BAT
ECHO SET SRVTYPE=%SRVTYPE%>> A:\VARS.BAT
5

Descargar ahora

Introduzca dos números de la imagen: