TIP: Click on subject to list as thread! ANSI
echo: novell
to: ALL
from: `alan` @ameritech.net
date: 1998-08-24 00:00:00
subject: Re: Help with Migrate

From: "alan" @ameritech.net>
Subject: Re: Help with Migrate
Date: 1998/08/24
Message-ID: #1/1
References: 
Organization: Ameritech.Net www.ameritech.net  Complaints: abuse@ameritech.net
NNTP-Posting-Date: Sun, 23 Aug 1998 20:16:58 CDT
Newsgroups: fido.novell

I am not sure but I don't believe that the migrate utility will overwrite
newer NLM's
AGAIN I am not sure so I would check with Novell.

As far as the password problem thought I am sure about this one.
run bindfix on the old server and then do the migrate.  I would use the no
password option.  What happens then is the next time a user logs on after
the migrate it asks for a password then ask the user to verify the password
and they are up and running with a new password.  (much easier than finding
the password file and handing out everyone's new password which is randomly
assigned)


TR  wrote in article
...
> I am about to migrate from a 25 user 3.12 server to a new 100 user 3.12
> machine.  I plan to use the Migrate utility in an accross the wire
upgrade,
> and have a few questions:
> 
> 1 - are there any issues in performing the upgrade?  The 100 user is a
> later patch rev, and I worry about overwriting newer files in System and
> Public with the older files from the source server.
> 
> 2 - When performing the migration, I have a choice to set passwords to
> blanks or random passwords, but I wondered if I did a bindfix on the old
> server, performed the migrate, then did a bindrest on the new server (
with
> the .old files from the 25 user server ), would that restore the
passwords,
> or just screw things up?
> 
> Thanks
> 

SOURCE: echoes via archive.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.