From: Alexander Gonta 
Subject: Re: Upgrade advice needed
Date: 1999/03/11
Message-ID: #1/1
Content-Transfer-Encoding: 7bit
References: 
Content-Type: text/plain; charset=us-ascii
Organization: Netcom
Mime-Version: 1.0
Reply-To: agonta@ix.netcom.com
Newsgroups: fido.novell

Hi Mark,

Two very good old utilites:

FRYE Utilities for Netware
BindView for Netware

Also, the migration wizard
under Win31 is pretty good,
however, it will help you
move the bindery over, not
do what you're trying to do,
which is recreate from scratch
by hand.

I suggest you use the Over the
wire migration utility and clean up
after it runs, which is pretty easy.

Here's the steps:

1) Create your NW 5.0 server (but
I recommend you start with 4.2, not 4.11,
and not 5.0, and transition to 5.0 later)

2) Use ArcServe 6.1 to backup
your NW 3.12 box and restore
data only , not trustee rights,
to your new box. Back up the
nw312/SYS:MAIL Directories also and
copy these to new box
nw50/SYS:MAIL

Do not copy the SYS:LOGIN or
SYS:SYSTEM or SYS:PUBLIC
from the Novell 3.12 server to the
new server.

Then, on your existing server,
run bindfix 3 times. The first
time is to clean up the bindery,
the other 2 copies are considered
clean. Take the  files that are now
with the *.old extension and
copy them to the SYS:SYSTEM
of your new server, but copy
them as *.sys, not *.OLD
In other words, NET$PROP.SYS
NET$VAL.SYS, and so forth.

Then, from the Install screen , type
Install Directory Services, and
upon doing so, one other screen
says, Import bindery info into
directory services. You now
have the old bindery imported,
and the data on the new box,
but yet, not the trustee rights to
that various data.

Now then, run the migrate utility
for dos and tell the utility the
source server and the target server.
The utility will now assign the
trustee rights for all the users
and groups to the data on the volume.
(do not attach to either server
in running the migrate utility)

You're not done yet.
Now you need to re-associate
any personal login scripts to the
user's respective SYS:MAIL\000111
numeric directories, where they are stored.
You also need to re-associate the user
accounts not only with their respective
home directories, but with the numeric
subdirectories below SYS:MAIL.
I will mail you a detailed procedure for this
step in another e-mail.

Now then, delete all printer objects and recreate
fresh and from scratch. Delete any duplicated
bindery objects and all other objects. ( you
can do this step on the day of the cut-over however,
not all at once).

Now, run incremantal copy jobs from your new
server to new server for 2 weeks while doing
application and login script testing. The new
server is not in production yet, but is
getting fresh data updates every day just
until the day of the cut-over.

You've done in one weekend what will take
you a long time to recreate by hand. Refamiliarize
yourself with Novell's over the wire migrate procedure
It is very useful and straightforward.

            I'll be glad to help with any more info you need.
I've done many, many 3.x to 4.x upgrades.

                        Sincerely,

                                Alex Gonta




Mark Callahan wrote:

> Hi Folks,
>
> I am going to be upgrading my NetWare 3.12 servers to 5.0 in the next
> couple months or so.  I would prefer to migrate over a clean bindery. I
> know that if I migrate now, I am going to have a ton of unknown bindery
> objects in my NDS tree and I want to minimize this as much as possible.
> Since I am only dealing with about 170 users my plan is to completely
> rebuild the 3.12 server on a new machine, rebuild the users, trustee
> assignments, and rewrite the login scripts. A healthy chunk of work to be
> sure but it needs to be done anyway. My main question here is; does anyone
> know of a good bindery auditing software on the market that will print out
> reports on the bindery? Specifically I need user trustee assignments,
> personal loging scripts etc., etc.. We have used Frye in the past and it
> worked great. But the newest version, made by Seagate I believe, does not
> have the reporting functions that we are looking for.
>
> Any thoughts on this would be greatly appreciated.
>
> Mark Callahan
> mcallahan@officespec.com