Duplicate GUIDs are a real pain to deal with. Not everyone in our environment is a CM admin or has access to delete objects from the CM db so we need a way (and i'll suggest multiple) to force a client to regenerate a GUID that doesn't require coordination of activities on the endpoint and in the CM DB to make it happen.

1 - Allow a registry value to be set that blocks the retrieval of the GUID from CM when missing from the client
2 - Add a parameter to the RepairClient() WMI Method ... RepairClient can take an optional parameter, defaulted to false, to ForceNewGUID ... during the client repair. e.g. RepairClient(), RepairClient(False), RepairClient(True)
3 - Add client notification to Generate New GUID from the console
4 - Allow blacklisting of ClientGUIDs that force regeneration
5 - Add Site Maintenance item to find dup GUIDs and auto generate new GUIDs for those clients