|
|
IMPORTANT: ITCS LAN/NOS would like to encourage
everyone to install NetWare 5.1 or
NetWare 6 for any
new servers in the Michigan Tree or servers being upgraded from NetWare
4.xx. If you are supporting Macintosh clients, you may need to install
NetWare 4.2. But no new servers should be installed as NetWare 5.0 or
4.11. These versions are due to reach their end of life in the near
future. See Novell's end of life product cycle web page for more details here.
Hardware requirements
- Pentium
- Mouse and VGA video
- 64 MB RAM (128 MB recommended)
- 50 MB DOS partition with DOS 3.3 or greater, NOT the version of DOS that ships with Windows
95. Windows 98 or Windows NT
Disk space needed for SYS: add 100 MB for System Operation
-NetWare 5 operating system (350 MB)
-NetWare 5 with default products (450 MB)
-NetWare 5 with all products (550 MB)
-NetWare 5 with all products and documentation (700 MB)
Drivers
Hardware must be compatible with HAM/CDM drivers. Verify that your hardware has
been tested with NetWare 5. To help with hardware compatibility, see the check
out TID 2942610, http://developer.novell.com/netware5/hardware.htm, and
http://developer.novell.com/infosys/bulletn.htm Be particularly careful with
servers hosting backup devices. To date, even backup software packages claiming
to run on NetWare 5 have had spotty performance and reliability records.
File Systems
The traditional file system continues to be available in NetWare 5. The SYS
volume must reside on a traditional volume. As in previous versions of NetWare,
there may be only one NetWare partition on a disk or a disk system (RAID) and
there may be only 8 segments per disk or disk system. NSS (Novell Storage System)
is the new file system with NetWare 5. NSS enhances the management of large
files, large volumes, name spaces, and storage devices. NSS allows you to create
files and volumes up to 8 TB (terabytes), depending on the amount of
unpartitioned free space on your hard disk. The time required to mount large
volumes is significantly reduced with NSS. NSS volumes are created from free
space outside of a NetWare partition. In the initial release of NetWare 5, NSS
volumes do not support disk space quotas, data migration, disk duplexing, disk
mirroring, disk striping, file compression, TTS, File Transfer Protocol (FTP),
VREPAIR, Network File System (NFS), or file and record locks.
Macintosh Support
The released version of NetWare 5 does not include Macintosh support. Novell has
outsourced development of the Macintosh components of NetWare to Prosoft
Engineering. Prosoft is has released its new NetWare client. NLM support for
NetWare 5 will follow (first for current Mac NLMs like AFP and ATPS). Currently,
the Mac name space is supported on all volumes (traditional and NSS), so
technically, using the Novell/Prosoft Mac client, Macs can access files on
NetWare 5 volumes. MACFILE.NLM does not ship with NetWare 5, but the version that
ships with NetWare 4.11 appears to work with NetWare 5. However, support for AFP
and ATPS is not currently available and the NetWare 4.11 NLMs do NOT work with
NetWare 5.
Existing Software Considerations
Do not use INSTALL.NLM if 4.11 server loaded the following services. Before
upgrading the server, unload the software and then reinstall the appropriate
version after the upgrade.
-DHCP (new NDS-based DHCP support)
-NetWare/IP (not supported in NetWare 5)
-AppleTalk File and Print Services (not available in NetWare 5)
-ManageWise (install MW 2.6 after upgrading to NetWare 5)
Novell Web Server
-Border Manager (must install BM 3.0)
Clients
NetWare 5 ships with a new set of clients. These clients enable access of NetWare 5 servers over IP
and/or IPX. These clients also work with NetWare 4.11 (over IPX only). Additionally, the older clients will
allow you to attach to NetWare 5 servers (over IPX only).
Security
Do not install security options yet. Stay tuned for campus deployment.
Pure IP
Initial deployment of NetWare 5 in the Michigan tree will be with IPX only or IPX/IP (dual stacks). This
deployment will allow for migration to NetWare 5 as a separate event from migrating to Pure IP. This is
important as the network infrastructure is not yet in place for implementing Pure IP. To avoid negatively
impacting Michigan tree stability, do NOT install NetWare 5 except in dual stack mode. This means: do NOT
install a server with IP only; do NOT run SCMD.NLM; do NOT run the migration agent on your server. We
are working with network providers on campus to plan the migration to Pure IP. We will let you know when
we have more information.
DNS/DHCP
DNS/DHCP has been enabled for campus use. Several one-time-only objects required for DNS/DHCP
deployment in a NetWare tree have been created in the Services container. You may implement DNS or DHCP
in your container for managing your subnet. Catalog Services (Contextless Login) We have provided a
tree-wide catalog for contextless login. That catalog is .UserCat.Services This catalog is updated once a
day at 5:00 am. Therefore,changes you make to users will not be reflected in the catalog until the next day.
You may also deploy your own catalog if you want to use one local to your branch of the tree. MCIT is
currently testing a local MED catalog for use by the Medical Campus. For information on configuring
contextless login on your clients, see TID 2940793. Steps 10-15 deal with client configuration.
LDAP
LDAP NDS support will be deployed for LDAP lookups of the Michigan tree. Password Administrator and
Changes to Rights Inheritance With DS 6.00 (and of course, NetWare 5), comes the flexibility to give help
desk staff the ability to reset passwords without having rights to the entire user object. This is
accomplished via a new property called "Password Management" and a new NDS Object and Property right
called ŒInheritable'. The Inheritable right applies only to containers and it provides the ability to make
individual properties inherited within the container. This change adds another level of complexity to rights
administration. By default the Inheritable right is always granted for Object and All Properties rights. This
results inthe same effect as in native NetWare 4.11. If the Inheritable right is not granted, the rights will
be effective on that object only, even for Object and All Properties rights. In addition, individual property
rights can now be inherited, unlike in NetWare 4.11. For more explanation of inheritable rights in NetWare
5, see TID 2942077. For instructions on setting up password administrators see TID 2942076. Note that to
use the Inheritable right feature, all servers in the replica ring of the partition containing the accounts to be
managed must run NetWare 5.
Licensing
On campus we have a Master License Agreement (MLA). As with previous versions of NetWare, the license
we are provided with on campus allows us to install the same license multiple times within the Michigan
Tree.
The MLA license for NetWare 5 allows for unlimited servers and connections. The licensing model has
changed. Licenses now exist as objects in NDS. There are three types of objects associated with licensing, a
server base license object, a connection license object and an NLS licensing object. Each server has an
associated NLS licensing object, named NLS_LSP_servername. Servers may share MLA server base license
objects and connection license objects. MLA licenses are unlimited, Therefore it is not necessary to install
a license for each server. In fact, licenses are limited to one per container. Only the first NetWare 5 server
in container a will create server and connection license objects. License objects will be created in the
UMich container. Servers installed into the tree can use these license objects. However, to speed
authentication, Novell recommends that a license be installed into the root of each partition in the tree.
Therefore, you will probably want to install license objects with the first NetWare 5 server you bring into
the tree (or upgrade in the tree).
-To use existing license objects, install (or upgrade) the server without
licenses (our 9-digit license will not install during an upgrade).
Only the NLS licensing object will be created.
-Make sure that the NLS licensing object is configured to "Search to the root of the tree" if you want it to
use a license located above its container (e.g. in UMich). This is the default setting. In addition to installing
the license in this manner, if you intend to use SSL and related security features, you must copy the NICI
Foundation Keys to your server. Do that by copying the file XXXXXXXX.NFK in the
NetWare:License.5\License folder to SYS:SYSTEM and renaming it to NICIFK. See the document "Installing
MLA License Certificates and Cryptographic Foundation Key" for the documentation that is distributed with
the NetWare 5 MLA license.
A few tips on licensing in the Michigan tree:
Licenses with 9-digit serial numbers (e.g. ours) will not install during an upgrade to NetWare5. Instead,
install your server without a license, then after the server is up, install licenses through NWCONFIG.NLM on
the server or NWAdmin or NLSManager from a client workstation. Copy the contents of the License.5
directory on the NetWare volume to a floppy diskette. Licensing over the network is not reliable. For more
help with licensing, see , TIDs 2943750 and 2944797.
To offer constructive criticism, or provide other feedback
about our site, click here.
Information Technology Central Services at the University of Michigan
|
|
|
