Windows Forum

Ask something
Discussion Locked

Creating new SID's on NT4.0 Clients

0 helpful
2 replies

by cmcclanahan

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Over the past few years, my company has been "cloning" our Windows NT Workstation 4.0 clients. Using a tool from Sysinternals, I discovered that we have many duplicate SIDs on our NT4.0 Domain. That hasn't been a problem with NT4; however, I understand it might be with an NT2000 Domain, which we will be moving to. Does anyone know if that is true?
Also, I have a tool that will allow me to change one workstation at a time, but does anyone know of a tool that will allow us to do multiple workstations at a time?

2 replies

by shmaltz

The SID problem is a problem that exists with NT 4.0 as well as NT2000.
To bypass the problem use sysprep.exe from microsoft when cloning.

by shanghai sam

I already know how to do it & I am aware of Sysprep.
I know that there is a security risk by using duplicate SIDs in an NT4.0 Network, but that workstations with duplicate SIDs can exist. I need to know whether the same thing holds true in an NT2000 Domain, or whether the duplicates will cause the workstations not to be seen or not to function properly on the network.

I also need to know of a utility that can be used across the network to change the SIDs on existing workstations that have duplicate SIDs.

This discussion is closed to new replies.