On Mon, Mar 9, 2009 at 4:09 PM, Greg Farber <[email protected]> wrote: > Question: I thought it was bad to "recycle" the same computer name to a > different computer when joining a domain, but that seems to be what this > situation requires.
By itself, it's neither good nor bad, but you should understand what it does. When you join a new computer[1] to a domain but reuse an existing name, the old computer's machine trust account is discarded. So the old computer won't be recognized on the domain anymore. The new computer will have the same name, which will work for anything that only cares about the name. However, the new computer will have a different NT SID and a different GUID in AD, so for things like AD group membership, WSUS, etc., it won't be seen as the same thing. Obviously, you can't have two computers with the same name on the same domain running at the same time. In your situation, can we assume the hardware which was formerly known as AAA is never coming back? If so, it's probably fine to reuse the name AAA on the new hardware. Presumably, the vendor's software doesn't also care about GUID or SID. (If it did, they're kinda screwed, so they wouldn't have sent you new hardware.) [1] To be exact, a different installed instance of Windows. Could be same hardware after a disk wipe, for example. Or even two instances of Windows on the same disk (parallel install). -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
