How to Manage Conflicting Records for Configuration Manager Clients: The easiest way would be a merge, which combines the old & new records to one while preserving all information of the older record. If the site is not configured to handle conflicting records (Site Properties/ Advanced), both records are shown under the conflicting records node in the ConfigMgr console and the Administrator has to manually choose the method for managing these records. In that case the old record is marked as obsolete and deleted according to the Delete obsolete Client Discovery Data Maintenance Task (Default= 7 days). SCCM 2007 can manage these Records automatically. A second record is created in the DB, a so called conflicting Record. The Client is issued a new SCCM GUID, but the Hardware ID stays the same. In both cases ConfigMgr reacts in the following way: ![]() The second scenario that leads to duplicate entries is the reinstallation of the operating system on existing hardware. In these cases the new HardwareID implies creation of a new SMS GUID what is why we get multiple entries in the ConfigMgr DB for just one machine. For Notebooks 2 of 7 criteria have to change. There‘s 10 criteria monitored for Desktops, if 3 of them change, the ID also changes. some aspects accountable for the Hardware ID have changed. While in native mode, clients authenticate via certificates and thus when reinstalling a native mode client it gets a new certificate which contains the same subject (normally the Netbios computername).Ĭircumstances that trigger generation of a new Hardware ID:ġ. Conflicting records in ConfigMgr mean multiple DB records for one machine.Ĭonflicting records are created only in sites that run in ConfigMgr mixed mode. In these cases a new SMS GUID is generated by the client and Conflicting Records are created. ![]() Reinstallation of the operating system or changes to the Hardware components. ![]() There are several scenarios that may lead to problems with records in the ConfigMgr database. This ID, also known as SMS GUID is generated during ConfigMgr Client installation.Īn Algorithm, which combines the Timestamp (Time of ConfigMgr Client Installation) and the Universally Unique Identifier (UUID) is used to generate a unique Identifier.Ī Client generates a new SMS GUID if the following things change ConfigMgr uses an ID that is generated on the Client to identify a machine inside the ConfigMgr hirarchy.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |