![\"\"](\"http:\/\/contoso.se\/blog\/wp-content\/uploads\/2011\/09\/20110918_SCSM_DiscoverySource_01.jpg\" "\\"20110918_SCSM_DiscoverySource_01\\"")
<\/a><\/p>\nIf I add another AD connector, that also synchronize this John Connor account, I can see in the database that the account now I have discovery sources<\/p>\n
If I now delete the first AD connector, field.local, and run the query again, we see that the John Connor accounts now have only one discovery source, the “Accounts OU” Active Directory connector.<\/p>\n If I now delete the second AD connector too, and run the SQL query, I see that the object now is deleted as there is no longer any discovery source. All incidents where John Connor was affected user now have a blank affected user field. If I create a new Active Directory connector, Account OU v2, I can see that the account is back in the CMDB and the new connector is discovery source. For the incident that John had before, the affected user field is still blank. Even if we synchronize the same account into the CMDB, it is not mapped together with the incident again<\/p>\n If I update the user object manually, for example adding the Office attribute, I can see an update in the database from the SDKDefaultConnector<\/p>\n If I now delete the Active Directory connector, the user object will not be deleted, as the manually modification of the object is a discovery source, and Service Manager will not delete an object with discovery sources.<\/p>\n If I modify a user in the Service Manager console, and then delete the modification again, for example let\u00e2\u20ac\u2122s say I add department, then I remove it again in the service manager console, the user will still have the This is the query I use to get discovery source of a object. Replace John Connor with any displayname<\/p>\n SELECT\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 DS.ConnectorId, BaseManagedEntity.DisplayName AS [Connector DisplayName], BaseManagedEntity_1.DisplayName AS [Object DisplayName] Each configuration\u00c2\u00a0object in the Service Manager CMDB has a discovery source, or multiple\u00c2\u00a0discovery sources. This list contains all connectors or sources that have updated the object during its lifecycle. For example if we synchronize an active directory user object to the CMDB the AD connector is the first discovery source. If we later update the … Continue reading <\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n
\nSDKDefaultConnector as discovery source. \u00c2\u00a0The result would be that even if I delete the Active Directory connector, the user will not be deleted as there is a discovery source left for the object. Therefor it could be a good idea to update the object in the data source, in this example in Active Directory.<\/p>\n
\nFROM\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 DiscoverySource AS DS INNER JOIN
\nDiscoverySourceToTypedManagedEntity AS DSME ON DSME.DiscoverySourceId = DS.DiscoverySourceId INNER JOIN
\nConnector ON DS.DiscoverySourceId = Connector.ConnectorId INNER JOIN
\nBaseManagedEntity ON Connector.BaseManagedEntityId = BaseManagedEntity.BaseManagedEntityId INNER JOIN
\nBaseManagedEntity AS BaseManagedEntity_1 ON DSME.TypedManagedEntityId = BaseManagedEntity_1.BaseManagedEntityId
\nWHERE\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 (BaseManagedEntity_1.DisplayName = N’John Connor’)<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"