PCBUILD Archives

Personal Computer Hardware discussion List

PCBUILD@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Content-Transfer-Encoding:
8bit
Sender:
PCBUILD - PC Hardware discussion List <[log in to unmask]>
Subject:
From:
Jeffrey Delzer <[log in to unmask]>
Date:
Tue, 7 Apr 1998 18:23:47 -0500
Content-Type:
text/plain; charset=iso-8859-1
MIME-Version:
1.0
Reply-To:
PCBUILD - PC Hardware discussion List <[log in to unmask]>
Parts/Attachments:
text/plain (40 lines)
Robert Orin Charles Kilroy wrote:
>
> Earl Douglass wrote:
> >
> > Is there a just as good way to copy to a new drive in Win NT 4?
>
> The problem you are going to run into is that each machine had a unique
> SID number.  I know that Mastering Computers had something about using
> Ghost to make copies of NT systems, but I don't recall the exact steps
> required.  The URL for Mastering Computer is:
>
> http://www.masteringcomputers.com/
>
> They specialize in undocumented features.  Not what you were looking
> for, but a place to start.

This is documented very well in the Ghost manual. I'll quote a bit:

Avoiding problems with the SID (Security Identifier)

Cloning WinNT is similar to cloning Window’s 95 but there is a problem
with the WinNT network Security Identifier or SID. Cloning a WinNT
workstation disk can produce another workstation with a duplicate SID -
something the NT Server will object to. Happily there is a way to get
around this problem.
The solution relies on the way the WinNT workstation and the WinNT
server assign the workstation a SID. It is not until the workstation
first connects to the NT Server that the SID is assigned. Up to that
point it is in a "waiting to be assigned" state. Therefore, the source
NT workstation must be cloned (copied to a disk image file or to a
destination disk) before the NT workstation makes its first official NT
connection to the NT Server.

The sequence of actions is:

(..actual steps deleted for brevity, but available on page 38 of the
manual)

Jeff Delzer

ATOM RSS1 RSS2