|
The Michigan Tree has been upgraded successfully to NetWare 6. Departments
throughout campus and MCIT are free to upgrade their servers to NetWare 6 (or
install new NetWare 6 servers.) Here is a document that we wrote to help you
through the upgrade process.
There are factors to consider before installing or upgrading to NetWare 6.
NetWare 6 has many differences from previous versions of NetWare. You should be
familiar with them before diving in. Here is a short and no where near
exhaustive list of some major differences:
SYS volume is NSS
eDirectory 8.6.x
iPrint/NDPS
iManage/Role Based Services
iMonitor
SLP v2
If you encounter others that you think should be on this list, please let us
know.
You may also want to take a look at the product web page:
http://www.novell.com/products/netware/
-Verify that all JetDirect Cards are up to the latest firmware to prevent print
queue corruption. See TID 10016807.
-Perform Routine Maintenance the servers
holding a replica of the partition the server is being installed into.
-Also make sure that time is synchronized by typing time at the console prompt.
IMPORTANT! You must Meet
System and Software Requirements, please review them as they are steeper
than in the past and your server will be difficult to recover from an install
that fails partly through the upgrade because you ran out of disk space.
-During the install you will be prompted for the servers host and domain names.
Make sure you have one registered in DNS. (the server will perform an nslookup
to verify its own name.) Some services on NetWare 6 require that the
Server name and DNS host name are the same. Changing a NetWare 6 servers
DNS information after an install is difficult. Please make sure you have
one that you will be using for a while.
-Have the NW6 license available on diskette.
-The user ID you use to install the server will need supervisor rights to the container the server resides in,
and will need to be a member of the .NetWare Administrators.NetWare_Admins.UMich
group. If you
do not have sufficient rights, please contact Netware Support.
The following does not cover every screen and prompt that will be presented to
you during the install, it covers the screens and prompts that ask for settings
that we consider important, or were determined to be confusing spots that we
felt needed clarification.
-Access the source files for NetWare 6 either from CD (either booting to it, or
accessing it using DOS cdrom drivers) or from the NetWare volume on ITD-NW1
using the DOS VLM client. We highly recommend you install NetWare 6 and Service
Pack 1 simultaneously, using the source files on ITD-NW1 in
NETWARE:\NETWARE.6\NW6SP1ES.
NOTE: If you are having problems communicating with ITD-NW1 please read
Problems
with Duplex Settings.
-Launch install.bat (if not booting from the CD)
-Select Custom and New Server at the Welcome to the NetWare server installation
screen after the license agreements screen.
-Enter ServerID
-Select YES at Load server at reboot prompt
-Continue with install
-Respond to disk and lan device configuration screens.
-Configure SYS volume (you should make it at least 4GB)
Note: If you used the VLM drivers to connect to ITD-NW1 for the source files,
you will be prompted to re-login to ITD-NW1 at this time.
-Enter Server Name
-Encryption Screen - provide the NICI Foundation Key (.nfk) file on the License
diskette.
-Configure the file system
-Configure LAN protocol information
---click Advanced | SLP tab | enter the addresses for the DAs (141.211.93.246
and 141.211.3.46)
-Configure Domain Name Service information
-Authenticate into the Michigan Tree with your container admin ID
-Choose time zone, click Advanced | check "use timesync configured sources" and
fill in sources from this
TIMESYNC.CFG.
-Provide correct NDS tree name and correct Server context
-Authenticate to the tree
Verify the License is correct and click next.
At the "select the NDS Context" dialog box select the container that the server
resides in.
-Select the appropriate options and click the Next button. We suggest choosing as
few of these options as possible during the upgrade. Instead, go back and add
them on after the upgrade has completed.
-Do not choose DNS/DHCP. This product will install regardless of your
selection here. This selection is actually for extending the schema for
DNS/DHCP.
-Export the trusted root certificate
-Click the Next button
-Be sure the Allow Clear Text Passwords box is unchecked and click next.
Based on which components you chose to install, you may be prompted for further
information pertaining to those products at this point.
ERROR!
At this point you will see an error message stating "eMFrame failed to get the
RBS context during registerSettingsPanel." Press OK.
Click the Finish button. Or choose customize if you would like to change some of
the default settings, such as port numbers used by some of the web services.
-If you provided the latest drivers for your NIC and/or disk
controller, several File Date Conflict windows may pop up for those files.
You will want to select Do Not Overwrite Newer File and click the OK button for
them.
ERROR!
When this copy portion reaches one hundred percent, the install will start
performing some configuration items. During this processing you will see
an error message stating "eMFrame failed to create the RBS container null.null."
Press OK.
-Reboot server as instructed
1. Perform a Schema check as follows:
SET DSTRACE=NODEBUG
SET DSTRACE=+SCHEMA
SET DSTRACE=*SS
Switch to the Directory Services screen. Pause for a moment while this processes. When you see “All processed = YES” you may proceed.
2. Browse your containers with ConsoleOne or NWAdmin32. Any unknown objects? Missing objects? Do things look generally normal?
3. Run DSREPAIR, using the Advanced options menu | Repair local DS database,
setting all options to “Yes” except for "Rebuild Operational Schema" and "Exit
automatically upon completion”. Upon completion, note the number of errors.
Continue to run DSREPAIR to zero errors or stasis, as during routine
maintenance.
-Install latest service pack.
Note: If a choice is present to update schema, be sure
not to choose it.
-From NWCONFIG, apply edir862 SP3a located at itd-nw1/netware:\eDir\8.6_2\patches\862sp3a\NW\.
RESET SERVER.
-Configure LAN Static Default Routing in Inetcfg/Protocols/TCP-IP
as described in the memo sent out about the June 6th announcement from UMNet
Admins.
-Configure SLP as described in this SLP Configuration Document.
-Configure Timesync as described in Michigan Tree Time
Synchronization.
-Edit AUTOEXEC.NCF, modify the Time Set statements at the top of the file so
that the "SET Time Zone = ??" line appears AFTER all of the Daylight Savings
Time set statements, if it doesn't already.
-Fix iManager and RBS after a departmental administrator installation of NetWare
6. Click here for the procedure.
Regardless of the options you chose to install, Novell's Remote Manager
(NRM) is
installed during the upgrade and is loaded upon reboot through the autoexec.ncf.
This is a great tool, but you may want to consider changing the TCP/IP port
numbers that NRM uses, for increased security.
To offer constructive criticism, or provide other feedback
about our site, click here.
Information Technology Central Services at the University of Michigan
|
|
|
