Anyone aware of one?

In microsoft.public.win2000.registry -|Tree=Bonz|- <nospam@hotmail.com> wrote:
> Anyone aware of one?

Please post your question in the body of the message. Many of us can't
see enough of it to be able to tell what you're asking.

--
Gary L. Smith
Columbus, Ohio

-|Tree=Bonz|- wrote:
> Anyone aware of one?

http://www.sysinternals.com/utilities/newsid.html

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

-|Tree=Bonz|- wrote:
> Anyone aware of one?


Help us help you:
http://dts-l.org/goodpost.htm
http://www.catb.org/~esr/faqs/smart-questions.html


--

Bruce Chambers

Help us help you:
http://dts-l.org/goodpost.htm
http://www.catb.org/~esr/faqs/smart-questions.html

You can have peace. Or you can have freedom. Don't ever count on having
both at once. - RAH

"Cloning or duplicating an installation without taking the recommended
steps can lead to duplicate SIDs. In the case of removable media, a duplicate
SID might give an account access to files even though NTFS permissions for
the account specifically deny access to those files. Because the SID identifies
both the computer or domain and the user, unique SIDs are essential to maintain
support for current and future programs."

Ref: http://support.microsoft.com/default.aspx?scid=kb;en-us;314828&Product=winxp

Computers that run the Windows XP operating system use a security ID (SID) as a unique identifier.
If you use disk-duplication software, you must ensure the uniqueness of these security IDs.

The Microsoft Policy Concerning Disk Duplication of Windows XP Installations
http://support.microsoft.com/default.aspx?scid=kb;en-us;314828&Product=winxp

When you clone a Windows NT/2000/XP installation to many computers,
the destination computers have the same SID and computer name as the source
Windows installation. Because Windows NT/2000/XP networks use each computer's
SID and computer name to uniquely identify the computer on the network, you must
change the SID and computer name on each destination (client) computer after cloning.

Visit:
http://service1.symantec.com/SUPPORT/ghost.nsf/docid/1999050308324125?Open&src=sg&docid=2000081610075225&nsf=ghost.nsf&view=docid/2000081610075225?open&src=sg&docid=1999070716282425&nsf=ghost.nsf&view=8f7dc138830563c888256c2200662ecd/92c05c601bf35fb2882567a70080df54?opendocument&prod=norton%20ghost&ver=2003%20for%20windows%202000/nt/me/98&dtype=&prod=norton%20ghost&ver=2003%20for%20windows%202000/nt/me/98&dtype=&prod=norton%20ghost&ver=2003%20for%20windows%202000/nt/me/98&osv=&osv_lvl

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User
Microsoft Newsgroups

-------------------------------------------------------------------------------------------

"-|Tree=Bonz|-" wrote:

| Anyone aware of one?

One of our techs didn't sysprep PCs he put out and it caused all sorts of
problems for us. People would log on to a PC and not be given to any network
resources. Printing was spotty - sometimes things would print, sometimes not.
Newly installed programs would work on one PC and not another. All kinds of
weird behavior that you couldn't explain.

It was a pain in the neck until we realized that this guy wasn't sysprepping
PCs. Many of the PCs had to be reimaged because they were so borked up that
there was no fixing them. Others simply needed to have Sysprep run on them
again to clear up the problems.

Trust me. Sysprep all the PCs you image.

"-|Tree=Bonz|-" wrote:
>
> Thing is, I want to see an article that explains exactly *what* happens when you don't change the SID
>
> Anyone aware of one?
>

> "Because Windows NT/2000/XP networks use each computer's
> SID and computer name to uniquely identify the computer
> on the network, "

That part should be changed as it isn't correct. A computer's local SID is not
used for identifying it on the network. The SID in the domain is a different SID
from the SID on the computer. The only place the local computer's SID is used is
on the machine itself and any media that you write NTFS ACLs too.

joe



--
Joe Richards Microsoft MVP Windows Server Directory Services
www.joeware.net


Carey Frisch [MVP] wrote:
> "Cloning or duplicating an installation without taking the recommended
> steps can lead to duplicate SIDs. In the case of removable media, a duplicate
> SID might give an account access to files even though NTFS permissions for
> the account specifically deny access to those files. Because the SID identifies
> both the computer or domain and the user, unique SIDs are essential to maintain
> support for current and future programs."
>
> Ref: http://support.microsoft.com/default.aspx?scid=kb;en-us;314828&Product=winxp
>
> Computers that run the Windows XP operating system use a security ID (SID) as a unique identifier.
> If you use disk-duplication software, you must ensure the uniqueness of these security IDs.
>
> The Microsoft Policy Concerning Disk Duplication of Windows XP Installations
> http://support.microsoft.com/default.aspx?scid=kb;en-us;314828&Product=winxp
>
> When you clone a Windows NT/2000/XP installation to many computers,
> the destination computers have the same SID and computer name as the source
> Windows installation. Because Windows NT/2000/XP networks use each computer's
> SID and computer name to uniquely identify the computer on the network, you must
> change the SID and computer name on each destination (client) computer after cloning.
>
> Visit:
> http://service1.symantec.com/SUPPORT/ghost.nsf/docid/1999050308324125?Open&src=sg&docid=2000081610075225&nsf=ghost.nsf&view=docid/2000081610075225?open&src=sg&docid=1999070716282425&nsf=ghost.nsf&view=8f7dc138830563c888256c2200662ecd/92c05c601bf35fb2882567a70080df54?opendocument&prod=norton%20ghost&ver=2003%20for%20windows%202000/nt/me/98&dtype=&prod=norton%20ghost&ver=2003%20for%20windows%202000/nt/me/98&dtype=&prod=norton%20ghost&ver=2003%20for%20windows%202000/nt/me/98&osv=&osv_lvl
>