-------------------------------------------------------------------------
410-41x.UPG -- 19980310 -- Email thread on Upgrading NetWare 4.10 to 4.1x
-------------------------------------------------------------------------

	Feel free to add or edit this document and then email
	it back to faq@jelyon.com




Date: Tue, 10 Mar 1998 17:21:53 +0200
From: Mike Glassman - Admin <admin@IAA.GOV.IL>
Subject: Re: Upg: 4.1 -> 4.11

We'v done quite a few of these here over the last year...about 36 to be
exact and in all there have been no problems whatsoever so long as you
do make sure you have enough space on SYS and on your DOS partition.
This is really the most important factor as you don't want to end up
half way thru the install with the program telling you to restart due to
insufficiant space.

We always run the install batch from the CD on the server, but it's just
as possible to do it from a network install or a remote server. It works
as well. Choose the 3.X or 4.x upgrade option and off you go. Easy and
simple.

As far as printers go, they migrate perfectly. I'v not had one cause a
problems after an inplace upgrade.

There is absolutely no reason to remove partitions. All it will ask is
the admins password to install the new DS and that is all. As far as
afterwards, I allways manually install the newest Ds files after making
backups and then set dstarce=*. which closes and opens the DS into the
new version. Only after this do I take the server down and bring it back
up and only run dsrepair about half an hour to an hour after that, just
to be safe.

All patches of course are installed prior to the DS upgrade.

I am a firm believer in installing patches immediately after an in-place
upgrade before dowming the server and bringing it up just in case there
are problems. So far this has worked for me 99.9% of the times.

---------

Date: Wed, 11 Mar 1998 21:18:48 +0000
From: Vikki Taxdal <taxdal@CLARK.NET>
Subject: Re: Upg: 4.1 -> 4.11

We did this upgrade last summer on about 20 servers.  The most
important thing for us was to make sure the NDS was completely up to
date with all replica holding servers in good communication.  We also
rolled back some replicas so we did not have so many of them talking
during the upgrade.  I mean, we took some of the replicas off, and
then we put them back on again after the upgrade.  Make sure you
know how to use dsrepair and dstrace.

This checking the health of the NDS before doing anything major like
putting a new server in the tree, taking an old one out, upgrading a
GroupWise domain, anything like that, has proved to be very serious.
I have learned NEVER to do any major moving or upgrading without
cleaning up directory services first.

------------------------------