RW> *** Quoting Frank Ramsey to Tom Ruddy dated 12-24-96 ***
 RW> > 1) If you perform an inplace upgrade from 3.12 to 4.1, it's handled.  
 RW> > Everything is updated.  Folks continue to use their old passwords.
 RW> > 
 RW> > 2) the migrate utility can move most of the information.  It cannot 
 RW> > handle passwords however.  Everyone will get a new password, unless 
u
 RW> Frank,
 RW> Ya lost me a bit..  I didnt think a 3.x to 4.x upgrade was 
 RW> able to copy the passwords in any manner..
The docs clearly tell you if you perform a update-in-place, passwords are 
preserved.  If you perform a server migration, the docs say you can either 
have passwords randomly assigned or set everyone to no password.
 RW> *** Quoting Frank Ramsey to Tom Ruddy dated 12-24-96 ***
 RW> > If not, the trick is to do a BINDFIX on the 3.12 server, copy over the 
 RW> > .OLD files to the 4.1 server, run BINDREST and do the install.  4.1 
 RW> > will find the "bindery" and perform the upgrade.
 RW> Once the passwords are restore'd this way, can you get rid 
 RW> of the bindery in 4.x??  I havent done much with 4.1 
 RW> outside of a few short live'd tries..
You don't really havea bindery with this trick.  This comes from Novell's 
consulting services.  All that's required is to have the three NET$ files in 
SYS:SYSTEM during the install and the install procedure will pull the 
passwords into NDS.
framsey@goodyear.com; CIS 71631,1032 - CNE, CNA-4, PE
--- EZPoint V2.2
---------------