[comp.os.vms] Moving users to a new Vax

SYSMAN@NMSUVM1.BITNET (06/10/88)

Date: 10 June 88, 09:04:03 GMT
From: Mark Nichols              (505) 646-4183       SYSMAN   at NMSUVM1
To:   INFO-VAX at KL.SRI.COM

We are in the process of upgrading our 780 to a 8530. This is a complete
upgrade meaning that nothing from the old system is being kept for the
new one.

Not wanting to reinvent the wheel, I figure somebody else has done something
like this at least once. So I have a few requests for those that have done
it:

    1. Can you explain how you went about moving all the user accounts
       over to the new machine. It appears that you can use a copy of
       the old one and use the Authorize command Modify/device=NEW$DISK
       to reassign the default directory of all the users to the new
       disk.

    2. How about diskquota.dat. Do you have any com files that take a
       diskquota listing from the old machine and use it to create a
       new diskquota.dat file on the new one.

Thanks

                  Mark Nichols
                  Systems Programmer
                  New Mexico State University
                  SYSMAN@NMSUVM1.BITNET
                  mnichols@nmsu.edu

MCGUIRE@GRIN1.BITNET ("The Sysco Kid ", McGuire,Ed) (06/17/88)

Mark,

Moving SYSUAF.DAT seems reasonable to me.  Don't simply MODIFY/DEVICE on all
accounts, though, or you'll change accounts you shouldn't, such as SYSTEM,
FIELD and SYSTEST.  I'd print a list first and go back and fix the ones that
shouldn't change:

   LIST/BRIEF [*,*]
   MODIFY/DEVICE=newdisk *
   MODIFY/DEVICE=SYS$SYSROOT SYSTEM
    etc. . . .

Ed

reden@sys1.TANDY.COM (06/25/88)

you can always change devices in various groups...

AUTHORIZE> mod/device=newdisk [44,*]

of coarse, a little note to all new system managers... if you use logical
names for devices, you wouldn't have this problem!!

Robert