![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 37%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFV%3C/text%3E%3C/svg%3E)
Service Manager
A family of System Center products for managing incidents and problems.
241 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(131.20000000000002, 40%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
It seems like you are facing an issue with the Service Manager SCCM Connector not grooming old information properly, resulting in multiple entries for the same computer in the [ServiceManager].[LFXSTG].[CMv5_OPERATING_SYSTEM] table. These multiple entries have different values in the "Group key" field, and the obsolete records are not being removed.
- Check the configuration of your SCCM Connector in Service Manager to ensure that it is set up correctly. Verify that the grooming settings are configured appropriately to remove obsolete records.
- Review the data synchronization processes between SCCM and Service Manager. Ensure that the data is being synchronized correctly and that there are no issues with the synchronization process that could be causing duplicate entries.