| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5348.1 | see note #5318 | CPEEDY::COOK | Changes In Lattitudes... | Thu Nov 14 1996 05:35 | 1 |
| 5348.2 | ghost | NQOS01::pto1038_port9.pto.dec.com::Kuratana | NSIS - Pittsburgh | Mon Nov 18 1996 10:05 | 10 |
| 5348.3 | using Unix to clone NT? | BGSDEV::POEGEL | | Thu Feb 06 1997 08:37 | 27 |
|
One of the system managers I work with has been able to clone an NT disk
by either using a Unix system with the "DD" command or a VMS system
with "backup/image". This is making an exact copy of every bit of the
disk. After booting the system, we just need to go in and change the
system name and TCP/IP address and the system is running fine.
The goal of this is to be able to take a fully loaded system disk image
with the OS, DDK/SDK, compilers, and tools installed and deploy it the
same way for everyone. Building a fully loaded developers system takes
alot of time.
The only problem so far seems to be that the disk is specific to a type
of machine and Hal type. We'll need a disk for an avanti/mustang class,
an alcor/brett class, an XL3xx, etc. And then if the target system has
any different ethernet or graphics, that driver would have to be added
later. That all sounds ok.
It sounds like we could save ourselves alot of time doing it this way
but people keep talking about problems with SIDs. We did do a successful
test of 2 cloned machines on the network at the same time in the domain
and everything worked.
Are we missing something?
Garry
|
| 5348.4 | | BHAJEE::JAERVINEN | Ora, the Old Rural Amateur | Thu Feb 06 1997 10:56 | 11 |
| >Are we missing something?
Probably yes (maybe lack of security). I have never seen the SID
problems documented anywhere, even though everyone warns about it.
The documentation for Ghost says the SID is only assigned when you join
a domain. They tell you to install your master system, but make sure
it's not connected to the network when the final boot for the
installation is done. Then use this system as image for the clones,
which will eventually get different SID.
|
| 5348.5 | on VMS I assume you mean BACKUP/PHYSICAL | CSC32::BOWMAN | Mission Critical OpenVMS;Windows NT Support | Thu Feb 06 1997 11:27 | 5 |
| Since BACKUP/IMAGE attempts to read a ODS-2 file structure from the disk this
won't work with NT disks (which have FAT or NTFS). BACKUP/PHYSICAL on the other
hand does a disk block by disk block copy, and the input and output disks must
be the same, including the location of bad blocks...not a very trustworthy way
to duplicate disks in general.
|
| 5348.6 | Good to see you watching out for us Sean;-} | ALFSS2::CHURCHE_J | Nothing endures but change | Thu Feb 06 1997 12:07 | 2 |
| re .-1
|
| 5348.7 | do it all on NT ... SCOPY | CERN::HOBBS | Congrats to the Ignoble Peace Prize winner! (http://www.eecs.harvard.edu/ig_nobel) | Thu Feb 06 1997 23:42 | 33 |
| The SCOPY command in the resource kit will also work, with the advantages:
- use disk admin to format the new disk, so you don't have the
problem that every disk has the same signature (boy, did I wreck
havoc with that one once!)
- the new copy is defragmented *and* file-ordered (files and
meta-data are stored in file alphabetical sequence)
- much faster, since you don't have to copy pagefiles and unallocated
data
- input and output disks can be different disk types, can have
different partition layouts, and different compression attributes
- the cloned system can be added to an existing disk - even into
an existing partition without hurting existing files
- the source disk can be a library of systems
Q:\1381-sp2-no_network\winnt40...
Q:\1381-sp2-developer\winnt40...
- a script could easily create the system, then fix it up
copy_and_set_alcor.bat
copy_and_set_maverick_4DT.bat
copy_and_set_kauai_smp.bat
copy_and_set_kauai_uni.bat
This doesn't help with the SID issue, of course.
-cw
|