X-Routed-By: SMDF V1.1 Beta on bokonon.UUCP
Newsgroups: bit.listserv.novell
Date:         Thu, 7 Jan 1993 15:14:13 -0500
Reply-To:     stephen@bokonon.uucp
From:         stephen@BOKONON.UUCP
Subject: Re: NetWare v3.11 Server-to-Server Info Requested

$    Somewhere I remember hearing that it is possible, and preferable to
$install NetWare v3.11 from an existing server - if you are installing
$serveral systems.

   Yes indeed!  It's preferable for a number of reasons, including
a) speed - it's far faster for it to load the files over the LAN than
   from floppies
b) reduced need for supervision - once you've started it loading, you
   can go away and come back later.  No need to change floppies.
c) if you keep your installation directory up-to-date with the latest
   versions of various files from NetWire, any servers you install
   this way will automatically get the latest copy of all files.

   The first thing you need to do is to set up a directory on an existing
fileserver where you will load the NetWare diskettes.  For each diskette,
create a subdirectory with exactly the same name (e.g. SYSTEM-1) and
copy all of the files from that diskette into that directory.  There may
be a better way of doing this; it's been so long since we set ours up
that I really don't recall how it was done.

   Once this process is finished, you will end up with a directory
tree such as (assuming you use SYS:NETWARE):

SYS:+-PUBLIC
    |
    +-SYSTEM
    |
    +-NETWARE----+-SYSTEM-1
    |            |
    etc.         +-SYSTEM-2
                 |
                 +-SYSTEM-3
                 |
                 +-PUBLIC-1
                 |
                 etc.

   Here are the steps for installing a new server from this setup.

1.  Copy the new server's SYSTEM-1 diskette onto your installation
    tree.

2.  Set up your boot partition on the new server's hard drive.  Copy
    all of the usual stuff (all of SYSTEM-1, VREPAIR.NLM, whatever
    .DSK driver you require, etc.) onto it.  Also make a subdirectory
    into which you will install and configure software to make that
    machine work as a _workstation_ (e.g. LSL, NE2000, IPXODI, NETX,
    NET.CFG, etc.)

3.  Load your workstation software on the new server and log into your
    old server.  Map a drive (does not have to be MAP ROOT, though I
    like to do it that way) to SYS:NETWARE (or whatever).

4.  Run SERVER on your new server.  Do everything the same as usual up
    to, but not including, loading INSTALL (e.g. setting up and
    configuring your .DSK driver).

5.  Instead of saying "LOAD INSTALL", say "LOAD INSTALL /J".  Now
    go on as usual to create your NetWare partition, define your
    volume(s), etc.

6.  When you get to the step that asks you to insert the first diskette,
    you will see an additional option that lets you specify where the
    files are to be loaded from (I think it's F6 or F7).  Select this,
    and point it to the drive you mapped in step 3.  I think it then
    asks if the files are in subdirectories; they are.

   It will now go and merrily load all of the stuff from the network.
Once it's finished, DOWN your new server and EXIT to DOS.  Now reboot
it and go straight into SERVER rather than loading your workstation
drivers.  You're up and running.

   This method involves a front-end load of setting up the SYS:NETWARE
(or whatever) directory, once.  It also involves a little bit of
extra time to get your workstation software configured, though it has
the benefit of showing you that your NIC is functioning properly.
It saves a lot of time once it's all set up.  Our company is a Novell
Gold Authorized reseller and we do a fair number of 3.11 installs.
Knowing that this method works, we would never want to do it any other
way.

-Steve
--
stephen@bokonon.UUCP              ...!{xrtll,becker.gts.org}!bokonon!stephen
----------------------------------------------------------------------------
Stephen M. Dunn, CNE, ACE, Sr. Systems Analyst, United System Solutions Inc.
104 Carnforth Road, Toronto, ON, Canada M4A 2K7               (416) 750-7946
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU