If you use a cloned image of a machine that's in a workgroup, do you
still need to manually change the sid with the newsid utility before
joining it to the domain?

I thought the act of joining a machine to an active directory domain
would create a new sid for that machine anyway.

The Microsoft policy concerning disk duplication of Windows XP installations
http://support.microsoft.com/kb/314828/en-us

--
Carey Frisch
Microsoft MVP
Windows Desktop Experience -
Windows System & Performance

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

If you use a cloned image of a machine that's in a workgroup, do you
still need to manually change the sid with the newsid utility before
joining it to the domain?

I thought the act of joining a machine to an active directory domain
would create a new sid for that machine anyway.

You should still run sysprep before you capture your image. There are
security issues with removable media and some other problems that can occur
because the PCs will have the same local SID even though they will have a
unique SID in re to Active Directory.
--
There seems to be a pattern to this random series of events.


"windowsname@gmail.com" wrote:

Bottom line is, this will only matter if users are sharing folders from their
own computers, which on a server-based LAN is a practice to discourage
anyway.

The important point is that the account SIDs on the server(s) should differ
from those on the clients. Since the server will not be part of the rollout
this is pretty-much guaranteed to be the case anyway.

"windowsname@gmail.com" wrote:

Ty G. wrote:


Wouldn't waste time or heartache with sysprep unless you're making
hardware independant images (and if you're doing that sysprep is the
perfect tool), for dedicated images for the same hardware newsid is more
than adequate. Why use a chainsaw to cut paper?