Hmm...forgive me if I stumble here, its been a while since I messed with NT4 SID:s...
The machine gets a unique SID when installed. Subsequently, all clones have the same Machine SID.
When you make machine A member of a domain, I think the machine gets another (or modified) SID.
Machine B has never been connected, and therefore the domain does not recognize it.
In order to save yourself some trouble, always make sure that the master for the clones is NOT a domain member. Take the trouble to manually add (or use GhostWalker for auto-adding) the clones to the domain, this will save you lots of hours troubleshooting the strangest SID-related problems.
BTW, why on earth would you want to substitute comp_A with comp_B ?
For FAQ:s , see the really good www.ntfaq.com
Hope this helps. And you tech guys/MCSE:s et al, please dont flame/spam/kill me for getting some detail wrong here.... as I said, its been a while.
>Excuse the dumb cloning question but,
>Our IT department produces standard "user" pcs comp_A & comp_B using a
>Comp_A is connected to network and added to domain. We can see a new account
>for comp_A$ in a sam dump. If we swap comp_B for comp_A, comp_B is
>recognised as not part of domain. Er why ?
>If there's a faq for this do let on.