FAQShop.com : Updating existing resources with new GUIDs

Updating existing resources with new GUIDs

Occasionally our workstation techs re-image production workstations to solve various problems. Unfortunately, when this happens the SMS client installs with a new GUID.

Although there is a resource record in the database for that particular workstation, it is associated with the old GUID. We are not able to distribute software to that resource until the database is updated with the new GUID.

From the way I understand it...when the DDM processes DDR records that have a GUID that does not already exist in the database, the DDM builds a list of resources. It does this by looking at certain key attributes, and then uses the list to try to find an exact match for the DDR.

Does anyone know how long the process takes to update the database with the new GUID, or if there is a way to speed it up?

Contributed By: Wally Mead [MS]
There is a resource kit utility called newuid.exe that will create a new GUID on an existing system. This is useful when the client has received a cloned image of the SMS client from another system.

Contributed By: Cliff Hobbs [MVP SMS]
If your techs are going to be doing this the other approach is to get them to call you before they re-image the machine so that you can delete it from the SMS database. Once SMS rediscovers the machine it will drop in and receive any Adverts targetted to the original machine (assuming they're still valid).