Re:Changing hands shouldn't be a problem (Score 1)

This is only true if your database uses the computer name as primary key and doesn't allow for updating that field like any other field. Active Directory certainly supports this and the computer name is simply a variable that can be changed at any time. In all of the asset tracking software I've used the software has generated its own primary key to store information about the system and maintains history regarding audits and updates the name as it changes. The same goes for Active Directory. The machine has a SID (Security Identifier) tied to it and that information is ultimately uses. The machine name is simply updated when it is changed in a domain environment. Software tracking, hardware tracking, help desk history, etc, should all be able to be maintained in the event of a computer name change. No software developer should be so shortsighted as to assume that no one is going to use that handy Computer Name tab in Windows.