SCSM - CI Connector
Dears,
I have a big doubt, and I do not know the answer.
Q 1: Why SCSM CI Connector to SCOM does not Synchronize all the MPs that are implemented on SCOM Server?
Examples:
CI Connector does not synchronize AD MP, VMM MP, SCCM MP.
Q 2: Why to only synchronize some MP such: Systemcenter.servicedesinger.library, Windows.Library, System.Library etc..?
Thanks in advance
Once you have the
base Ops Manager MPs imported into the database, then you will need to make sure the MPs that define the Configuration Items you want to copy are
enabled in the connector. the connector should keep those MPs synchronized between Service Manager and Ops Manager by coping the latest version from OM to SM.
Finally, you may want to
edit the allow list to control what types of CI classes are created in Service Manager.
Similar Messages
-
How to configure SCSM exchange connector when exchange server is in different domain.
We installed/configured SCSM in ABC domain and now need to use exchange connector for incident alert mail.
But exchange server is in different domain, say XYZ.
How do we configure?
Thanks,
AbhilashCannot configure trust at AD level. But in the config article, following points are given.. but not clear on first 2 steps. Also, we did not find option to "navigate to certificate template and right click certificate templates".
sorry, i dont have much exp with certificates. If steps are described little more clear, would be helpful.
a. If your Service Manager management server does not have a trusted relationship with the Exchange Server, open Certificate Services and create a duplicate copy of the Web Server Certificate Template. Ensure that Private Key Export and Publish
in AD are selected, and then add Read and Enroll permission to Authenticated Users.
b. In Certificate Services, navigate to Certificate Template and right-click Certificate Templates. Click New and then click Certificate Template to Issue. Select the template that you created in the previous step.
c. In Exchange Server, open the Microsoft Management Console and add the Certificates snap-in for the local computer. Right-click the Personal logical store, and then hover over All Tasks.
d. Select Request for New certificate and in the Certificate Enrollment wizard, select Active Directory Enrollment Policy and select the template that you created previously. When you select the certificate, you can click More Information to type
the Exchange Server’s FQDN name as the common name in the Subject tab. You can also type the FQDN name as the Friendly Name in the General tab.
Thanks,
Abhilash -
SCSM Exchange Connector Help, NO ADFS Exchange 365
Im struggling to find what Im doing wrong here, I have followed the connector docs for setting this up and have also read plenty of forums but still having no luck. The one thing Im having a difficult time understanding is the email impersonation setup.
Are there powershell commands I "have" to use to get this to work?
So here is what I have done so far
*created AD account with a .com account vs our .local domain account because we are not federated
*gave that account admin local and also console admin on SCSM server
* created reg entries as needed for 365
* created workflow account with .com account as well
*not sure if it was needed but created SMTP instance local as well.
Any help would be awesome... Thank youCan anyone give me an idea here :\
-
SCSM Exchange Connector not recognizing custom Service Request prefix
Hello,
We have an Orchestrator runbook that brings over "Projects" from our Financial system into Service Manager as Service Request. As a way to distinguish these as projects we changed the prefix from the default "SR" to "PT".
In all out testing everything worked fine until we installed the Exchange connector. It won't recognize any Service Request that starts with a different prefix than "SR" (defined in the system settings). Does anyone know of
a way to get the Exchange connector to recognize other prefixes?
ThanksHi,
The system uses the only prefix that defined in the settings. There's no way to add support for the second prefix in Microsoft Exchange Connector. But you can create your own custom connector with the required behavior.
Cheers,
Marat
Site: www.scutils.com Twitter:
LinkedIn:
Graveyard: -
SCSM 2012 Exchange connector 3.0 Status Never Run.
HI ,
SCSM exchange connector was Running for almost 8 months . all of sudden it stopped pulling email from Exchange Server.
I looked in to the issue and did not found any major error in the Event log “Operation Manager”
Only event were warning, “OpsMgr Config Service failed to send the dirty state notifications to the dirty OpsMgr Health Services. This may be happening because the Root OpsMgr Health Service is not running.” I did not installed SCOM at
all. This server is not connected to any SCOM server.
I have reinstalled the Exchange web Service API (copied file to SCSM folder)
I have reinstalled exchange connector 3.0 (copied files to SCSM folder and imported management packs)
Created new Exchange connector and all test passed.
But the connector status stays “Never Run”
In my regedit ,I also made the following changes
KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center Service Manager Exchange Connector
EnableEWSTracing = 7
LoggingLevel= 7
I have also looked and tried every option with “Run as Account” and also making admin Role.
I am not getting any error in the log apart from following warning .
I did not found any major error in the Event log “Operation Manager
Only event were warning, “OpsMgr Config Service failed to send the dirty state notifications to the dirty OpsMgr Health Services. This may be happening because the Root OpsMgr Health Service is not running.
Can someone help me , what should be the next step.the reason you are seeing operations manager errors is because Service manager uses the operations manager SDK to do all of it's work. the error that you are seeing "OpsMgr Config Service failed to send the dirty state notifications to the dirty OpsMgr
Health Services. This may be happening because the Root OpsMgr Health Service is not running." means that the service manager configuration service can't notify the data access service that there are changes to it's MP base, for whatever reason.
i would stop all the system center services on this server, go into the service manager folder, find the "Health state" and "Config State" folders, and move them somewhere else on the system, then restart both services. assuming your
system isn't otherwise damaged, this will force both the config and data access services to rebuild their cache from the database, and should unstick your workflows. -
SCSM to SCOM Alert Connector Error
Hello,
Long story short, the SCSM admin created an Alert Connector between SCSM and SCOM, then uninstalled SCSM and started over. That means I had an orphaned SCSM connector in SCOM.
In order to set up a new connection, I followed the instructions found in Kevin Holman's blog post:
http://blogs.technet.com/b/kevinholman/archive/2012/09/28/opsmgr-2012-how-to-delete-an-old-product-connector.aspx
Now, when I try to re-create a new Alert Connector, I get this error:
"Found at least one other alert connector in Operations Manager. Alerts may not be routed as expected if multiple connectors subscribe to the same alert."
I checked the SCOM server to make sure there were no orphaned connectors by running this SQL code against the OperationsManager database:
Aside from the copious number of SCVMM connectors, there were six connectors. Of those six, the previous SCSM connector is marked as "IsDeleted":
Next, I checked the "Microsoft.SystemCenter.Notifications.Internal" management pack to verify that there are no orphaned subscriptions. The ONLY alert referenced is for the "Advisor Data Connector".
At this point, my questions are as follows:
1) Will the System Center Advisor (now renamed Azure Operational Insights) connector cause the warning message I listed above when setting up an Alert Connector in SCSM?
2) Is there another orphaned entry in SCOM that I need to check for and remove before setting up the SCSM alert connector?Hi,
I would like to suggest you remove the subscription that was orphaned. When remove a connector we should remove the subscriptions first.
And here is a similar thread
SCSM 2012 Cannot create SCOM Alert Connector
https://social.technet.microsoft.com/Forums/en-US/a5d0b921-bb0a-43b8-99ca-8b0112ab3bf0/scsm-2012-cannot-create-scom-alert-connector?forum=connectors
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. -
Error adding a SCOM Alert Connector
I have a SCOM 2012 SP1 and SCSM 2012 SP1 environment in production. I have had a working CI connector for some time, but we decided to try to add an alert connector to the mix.
At the point where I provide credentials for SCOM I get the following warning
"Found at least one other alert connector in Operations Manager. Alerts may not be routed as expected if multiple connectors subscribe to the same alert."
Hmm. That's interesting because there are no other alert connectors.
I checked the SCOM side for any alert connectors and any configured subscriptions on the internal connectors and came up blank.
I then ran the following queries on the SCOM and SCSM databases:
select DisplayName,IsInitialized,ConnectorID from Connector,BaseManagedEntity
where Connector.BaseManagedEntityID=BaseManagedEntity.BaseManagedEntityID
Neither shows an alert connector in place.
I pressed on and created the connector. I then added my subscriptions to the SCOM side.
I can see my Connector run every 30 seconds, but it never retrieves any alerts.
The state never flips to initialized on the connector either.
I have removed and recreated the connector and always see the same error.
Aside from checking SCOM and the connector tables in the operational databases, where else can I look for this mysterious other alert connector?
Thanks,
JoeDear Joe,
hope these links will help you:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/3075bbb7-59db-4671-994d-7540871a2a23/scom-connector-to-multiple-service-manager-environments?forum=connectors
http://www.thecloudbuilderblog.com/blog/2012/6/2/scsm-2012-connector-bugndashincidents-generated-from-rule-ba.html
Regards
Jreij12 -
Hello Guys
I have installed
SCSM 2012 R2 and we are setting
support requests. Within configurations
want to see if you can relate to
requests for mail flow, for example if
a user requests an injunction to a mail
account and that the subject indicating Support Request - Notebook Failed,
it will automatically create a request
in SCSM.
Thanks for your help.
SebastianIf I get your requirement right the SCSM Exchange Connector should help:
System Center Service Manager Connector 3.1 for Exchange
Hope this helps.
Andreas Baumgarten | H&D International Group -
We have found a need for users in the company, whom for whatever reason, cannot access their domain email, and need to send a message to helpdesk. As is stands right now, the service manager will not take emails from outside the domain and create a ticket
for our helpdesk. Q: 1. is there a way to configure Service Manager to allow non-domain emails. 2. is this a setting within the Exchange server, or does this even exist?
Jerome ReafsHi,
The SCSM Exchange Connector has an option 'Only process emails from users in CMDB'. Uncheck it and EC will create a new user for every email sender not presented in the CMDB.
Cheers,
Marat
Site: www.scutils.com Twitter:
LinkedIn:
Graveyard: -
Is there a way of monitoring SCSM connector failures using SCOM
I have an environment comprising SCSM2012 SP1, SCOM2012 SP1 and SCCM2012SP1 with Orchestrator forwarding the CI data and alerts to a 3rd party CMDB/ServiceDesk system. We have SCSM connectors for AD, SCCM and SCOM CI. There was a recent issue with SCSM UR6
where the SCCM connector stopped working. I regressed the Microsoft.EnterpriseManagement.ServiceManager.Linking.Consumer.OperationalStore.dll back to the RTM release version and it all works again.
I want to know if there is a way of monitoring each of the connectors in SCOM to ensure I get alerted if the status of the 3 connectors is anything other than "Finished Success" - maybe only generating an alert if the status stays in a failed status
for more than 24 hours.
There appears to be very little documentation on how these connectors work or what errors they write into logs. Any tricks or tips would be appreciated.On you management server, if you open Event Viewer, the logs are keep under Application and Services Logs Operations Manager. (Yes, the Service Manager logs are keep in the Operations Manager logs folder) In this folder you should find the event logs for
your connectors. Just search for different sources to find the connector you want to monitor. Some of the sources include Exchange Connector, OpsMgr Connector, Data Connectors (AD connector), System Center Orchestrator, and Lfx Service (SCCM
Connector). You could easily setup SCOM or Orchestrator to monitor these logs.
Matthew Dowst |
Blog | Twitter -
Enabling SCOM Alert Connector in SCSM
Hi,
Had a query regarding the Alert Connector in SCOM that forwards alerts in SCOM to SCSM (Service Manager) to create incidents.
Currently, we had SCOM and SCSM at the same level i.e 2012 SP1. But, in future we might have to upgrade to R2 so is there any compatibility matrix for the SCOM and SCSM versions for the Alert Connector. Like if we had SCOM on Sp1 and SCSM on R2 would it
affect or the vice-a-versa.
Regards,
Daya RamHi,
System Center 2012 – Operations Manager is supported by Service Manager and Service Manager SP1 for connectors and agents. However, only corresponding System Center versions are supported when you register a data source in the Data Warehouse
workspace.
System Center 2012 – Operations Manager agents were not supported with System Center 2012 – Service Manager. However, the agent that is automatically installed by System Center 2012 – Service Manager
SP1 is compatible with System Center 2012 – Operations Manager and System Center 2012 – Operations Manager SP1.
More details:
Operations Manager Considerations in System Center 2012 - Service Manager
http://technet.microsoft.com/en-us/library/hh524312.aspx
Regards,
Yan Li
Regards, Yan Li -
SCSM's Allowed List for SCOM CI Connector not working as expected
Hi Everyone,
We're running into some unexpected behavior with the SCOM CI Connector, wondering if anyone can shed some light on it. Our requirement is to ensure Distributed Applications are not sync'd from SCOM to SCSM (hence, they don't show up in the "All
Business Services" view). We have only two MPs in SCOM/SCSM that sync Distributed Applications, both of which are for SharePoint monitoring.
We have the 2 SharePoint MP's in both SCSM and SCOM. We've configured the SCOM CI Connector to select the 2 SharePoint MP's for synchronization.
Now, we thought all we'd need to do to ensure the SharePoint Distributed Applications no longer sync from SCOM to SCSM is remove the "System.Service" class from the Allowed List of classes for SCOM CI -- which we did, however, they continue to
sync.
After a fair amount of back and forth trying to figure out how we need to configure the Allowed List of classes for the SCOM CI Connector to ensure the DA's aren't sync'd any more, we finally removed ALL classes from the Allowed List. Surely, this
will stop the sync we thought -- however, after having deleted the SharePoint Business Service CI's, removing ALL classes from the Allowed List, and then rerunning the SCOM CI Connector, the Distributed Applications associated with the SharePoint MP's STILL
come over.
Is there something I'm missing here?
Thanks!Hi -- can anyone provide any feedback for me on this one?
Thanks! -
Hello everybody,
we have installed scsm 2012 r2 (UR 3) with exchange connector 3. We have connected the connector by the workflow Account (domain user "servicedesk" is in local admin group of the sm server and in the sm Administrators group) and have access
to the mailbox on exchange (2010; autodiscovery is working correct). We receive all mails in the servicedesk mailbox on restarting the sm services and see the mails in the opm logs. But no incidents are created and the connector stays in "never
tun" state and does not receive mails any More after the first start. What do we have missed to check? Beste regards Thomasi have added the registry keys.
the last log says:
EwsResponse: <Trace Tag="EwsResponse" Tid="1" Time="2014-08-10 18:38:52Z" Version="14.03.0067.001">
<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Header>
<h:ServerVersionInfo MajorVersion="14" MinorVersion="3" MajorBuildNumber="174" MinorBuildNumber="1" Version="Exchange2010_SP2" xmlns:h="http://schemas.microsoft.com/exchange/services/2006/types"
xmlns="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" />
</s:Header>
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<m:FindItemResponse xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types">
<m:ResponseMessages>
<m:FindItemResponseMessage ResponseClass="Success">
<m:ResponseCode>NoError</m:ResponseCode>
<m:RootFolder IndexedPagingOffset="1" TotalItemsInView="1" IncludesLastItemInRange="true">
<t:Items>
<t:Message>
<t:ItemId Id="AAMkAGM0NzI4Nzc5LWM0NWMtNDBiZC1iMjIyLWU5YTZlNGM0YjVjZgBGAAAAAADPPKNYSCzLRLMWL/UoJg1CBwAVmecTYATlQovl76GEizxlAAAAoyGrAAAVmecTYATlQovl76GEizxlAAAAo0kZAAA="
ChangeKey="CQAAABYAAAAVmecTYATlQovl76GEizxlAAAAo4Fd" />
<t:ParentFolderId Id="AAMkAGM0NzI4Nzc5LWM0NWMtNDBiZC1iMjIyLWU5YTZlNGM0YjVjZgAuAAAAAADPPKNYSCzLRLMWL/UoJg1CAQAVmecTYATlQovl76GEizxlAAAAoyGrAAA="
ChangeKey="AQAAAA==" />
<t:ItemClass>IPM.Note</t:ItemClass>
<t:Subject>Test 1</t:Subject>
<t:Sensitivity>Normal</t:Sensitivity>
<t:DateTimeReceived>2014-08-10T18:35:12Z</t:DateTimeReceived>
<t:Size>2858</t:Size>
<t:Importance>Normal</t:Importance>
<t:IsSubmitted>false</t:IsSubmitted>
<t:IsDraft>false</t:IsDraft>
<t:IsFromMe>false</t:IsFromMe>
<t:IsResend>false</t:IsResend>
<t:IsUnmodified>true</t:IsUnmodified>
<t:DateTimeSent>2014-08-10T18:34:56Z</t:DateTimeSent>
<t:DateTimeCreated>2014-08-10T18:35:12Z</t:DateTimeCreated>
<t:DisplayCc />
<t:DisplayTo>Service Desk</t:DisplayTo>
<t:HasAttachments>false</t:HasAttachments>
<t:Culture>de</t:Culture>
<t:EffectiveRights>
<t:CreateAssociated>false</t:CreateAssociated>
<t:CreateContents>false</t:CreateContents>
<t:CreateHierarchy>false</t:CreateHierarchy>
<t:Delete>true</t:Delete>
<t:Modify>true</t:Modify>
<t:Read>true</t:Read>
</t:EffectiveRights>
<t:LastModifiedName>Thomas Göttl</t:LastModifiedName>
<t:LastModifiedTime>2014-08-10T18:35:12Z</t:LastModifiedTime>
<t:Sender>
<t:Mailbox>
<t:Name>Thomas Göttl</t:Name>
</t:Mailbox>
</t:Sender>
<t:IsReadReceiptRequested>false</t:IsReadReceiptRequested>
<t:ConversationIndex>Ac+0ycOTmfHK8XrvSM2ftu9rcjREeg==</t:ConversationIndex>
<t:ConversationTopic>Test 1</t:ConversationTopic>
<t:From>
<t:Mailbox>
<t:Name>Thomas Göttl</t:Name>
</t:Mailbox>
</t:From>
<t:InternetMessageId><[email protected]></t:InternetMessageId>
<t:IsRead>false</t:IsRead>
<t:ReceivedBy>
<t:Mailbox>
<t:Name>Service Desk</t:Name>
</t:Mailbox>
</t:ReceivedBy>
<t:ReceivedRepresenting>
<t:Mailbox>
<t:Name>Service Desk</t:Name>
</t:Mailbox>
</t:ReceivedRepresenting>
</t:Message>
</t:Items>
</m:RootFolder>
</m:FindItemResponseMessage>
</m:ResponseMessages>
</m:FindItemResponse>
</s:Body>
</s:Envelope>
</Trace>
and the one before:
EwsResponseHttpHeaders: <Trace Tag="EwsResponseHttpHeaders" Tid="1" Time="2014-08-10 18:38:52Z">
200 OK
Transfer-Encoding: chunked
Content-Encoding: gzip
Vary: Accept-Encoding
Persistent-Auth: false
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Date: Sun, 10 Aug 2014 18:38:51 GMT
Server: Microsoft-IIS/7.5
WWW-Authenticate: Negotiate oYGyMIGvoAMKAQChCwYJKoZIgvcSAQICooGaBIGXYIGUBgkqhkiG9xIBAgICAG+BhDCBgaADAgEFoQMCAQ+idTBzoAMCAReibARqZCLk7OlBLjMLGg8XtQO+mutKfYPyK2jeJ2B+wq9raDj1chIZkQT0/72YftQJfdtu1DwfzmlEz8kDSD7ElFT2nF/T5LMDIMT4EpLJALsGQPTec86ubSbl1dKsIZn09qdoGDg5tGxV0bwOSg==
X-AspNet-Version: 2.0.50727
X-Powered-By: ASP.NET
</Trace>
the one before:
EwsRequest: <Trace Tag="EwsRequest" Tid="1" Time="2014-08-10 18:38:51Z" Version="14.03.0067.001">
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<t:RequestServerVersion Version="Exchange2007_SP1" />
<t:TimeZoneContext>
<t:TimeZoneDefinition Id="W. Europe Standard Time" />
</t:TimeZoneContext>
</soap:Header>
<soap:Body>
<m:FindItem Traversal="Shallow">
<m:ItemShape>
<t:BaseShape>AllProperties</t:BaseShape>
</m:ItemShape>
<m:IndexedPageItemView MaxEntriesReturned="1" Offset="0" BasePoint="Beginning" />
<m:Restriction>
<t:And>
<t:IsEqualTo>
<t:FieldURI FieldURI="message:IsRead" />
<t:FieldURIOrConstant>
<t:Constant Value="false" />
</t:FieldURIOrConstant>
</t:IsEqualTo>
<t:IsEqualTo>
<t:FieldURI FieldURI="item:ItemClass" />
<t:FieldURIOrConstant>
<t:Constant Value="IPM.Note" />
</t:FieldURIOrConstant>
</t:IsEqualTo>
</t:And>
</m:Restriction>
<m:ParentFolderIds>
<t:DistinguishedFolderId Id="inbox" />
</m:ParentFolderIds>
</m:FindItem>
</soap:Body>
</soap:Envelope>
</Trace>
the one before:
EwsRequestHttpHeaders: <Trace Tag="EwsRequestHttpHeaders" Tid="1" Time="2014-08-10 18:38:51Z">
POST /EWS/Exchange.asmx HTTP/1.1
Content-Type: text/xml; charset=utf-8
Accept: text/xml
User-Agent: ExchangeServicesClient/14.03.0067.001
Accept-Encoding: gzip,deflate
</Trace>
the one before (xxx for our Domain):
Exchange Connector: Autodiscovered URL: https://sv-exchange01.xxx.intra/EWS/Exchange.asmx
Is there something we missed? -
SCSM 2012 R2 workflows and connectors are not triggered
Hi All,
Suddenly in my SCSM 2012 R2 Production environment , the connectors stopped synchronising at the schedule time and the Service request was in New state for very long time (stuck in New state).
When I started troubleshooting , I saw the workflow status in SCSM console , oops!! no entries
In operations manager event log , no logs generated regarding the connector issue or the SR workflow issue .
Then I tried starting the AD connector manually , two event logs (information-LFX service) generated
SyncBegin:Connector Id
SyncEnd:Connector Id
Then I stopped the services
Microsoft Monitoring Agent
System Center Data Access Service
System Center Management Configuration
deleted the health service state folder content and restarted the services
Then issue is solved , the connector started syncg and the service request state changed from New to In progress and all the workflows were triggered.
Since there is no events logged for this issue , this gonna make a huge impact in SCSM environment since workflows are the key feature in SCSM .
Is this a known issue in SCSM 2012 R2 and are there is any fix in the update rollups
Are there is any reason behind why we need to flush the SCSM health service state and how this affect the functioning of SCSM?
since we have the SCOM agent installed as part of SCSM installation and scom uses the same Health service state folder to monitor the SCSM server ??
sorry for too many questions , just to clarify my all doubts
Is there any permanent solution ?
Thanks,
KalaiHi,
This issue seems like a performance issue. It is recommended that you schedule the AD/SCCM connectors to run when console/system usage is low since it can have an impact on performance. You can use the following instructions to reschedule the AD connectors.
http://blog.scsmsolutions.com/2012/03/update-ad-and-sccm-connector-scheduler-with-powershell/
And here is a similar thread for you referenc, please go through it for more details:
Connectors are not Syncing in Service manager 2012 Sp1 RTM
https://social.technet.microsoft.com/Forums/systemcenter/en-US/2824c769-99ea-4ec6-ab7b-1007efdcb339/connectors-are-not-syncing-in-service-manager-2012-sp1-rtm?forum=connectors
Here is a link about Description of Update Rollup 2 for System Center 2012 R2 Service Manager:
https://support.microsoft.com/kb/2904710?wa=wsignin1.0
It seems that it does not have fix for this.
In addition, the newest one is Update Rollup 4 for System Center 2012 R2 Service Manager:
http://support.microsoft.com/kb/2989601
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. -
SCSM 2012 AD Connector Sync Failure
Good afternoon,
We had an AD connector which synced everything in AD in one big go, which was an initial deployment mistake. This Connector functioned fine, but brought in lots of "rubbish" which we didnt want in our SCSM deployment. Due to the nature of our OU structure
we decided to go down the route of creating multiple connectors for multiple OUs within AD (we cant change AD structure) By going down this route we could take our user count down from 20,000+ to around 6,000. Much cleaner and quicker.
We disabled the original connector, which went fine, created all the new connectors and all synced fine (and quickly) with the exception of one. Sods law the IT Admins OU! The connector sticks and throws an error at 92% every time. Tried disabling \ enabling,
Manual Sync, Bouncing Management Servers. Even deleting and recreating the connector but it always sticks at the same point.
I have gone through the OU with a fine toothcomb and cannot spot anything out the ordinary with any of the accounts. I have removed disbaled accounts, contacts, groups, test accounts etc... so it is now just pure live IT Admins. I picked up on the error
from the MOM eventlog which seemed to point me in the "Manager" AD Attribute direction. So I proceeded to remove all Manager and Subordinate information from all 70 accounts. Still no joy.
Below is my MOM Eventlog Error Message does anyone have any ideas on where else I should be looking?
Data synchronization failed by DefaultCache.MomStore.ADUsers_Manager.DefaultCache.ADConnector.5e0dd86d1c3a4b8eaf75951c55ed0877:Microsoft.EnterpriseManagement.ServiceManager.Connector.Sql.DataConnectorSql.
Exception type:NullReferenceException
Exception message:Object reference not set to an instance of an object..
StackTrace: at Microsoft.EnterpriseManagement.ServiceManager.Linking.Consumer.OperationalStore.DataSetTransformer.ComputeManagerDeletes(Dictionary`2 result, IList`1 existingManagers, Dictionary`2 userToNewManager)
at Microsoft.EnterpriseManagement.ServiceManager.Linking.Consumer.OperationalStore.DataSetTransformer.DeleteObsoleteManagerRelationships(ManagementPackRelationship relationshipType, Dictionary`2 result, EnterpriseManagementGroup managementGroup)
at Microsoft.EnterpriseManagement.ServiceManager.Linking.Consumer.OperationalStore.DataSetTransformer.TransformToEnterpriseManagementObjects(EnterpriseManagementGroup managementGroup, ManagementPackType storeType, SessionSettings sessionSettings,
Boolean useStagingSDK, Boolean isGRCSolution)
at Microsoft.EnterpriseManagement.ServiceManager.Linking.Consumer.OperationalStore.OperationalStoreConsumer.ConsumeData(DataSet data, SessionSettings sessionSettings)
at Microsoft.EnterpriseManagement.ServiceManager.Connector.Datacenter.SessionHost.DataSync()Thanks, Morten! Same issue here... and a little bit more challenging as we have 2 domains and a manager on one domain could have direct reports on another one :|
Maybe you are looking for
-
I want to use Time Machine to back up my mac. I have heard that it will wipe the HDD if its not formatted correctly. Disk utility says its Mac OS Extended (Journaled). Is this alright? or will it wipe it?
-
i synced my iphone to my computer home but i moved to korea and got a mac so how do i sync my phone to this computer because it says I'm already synced to my home computer?
-
Boot Problem with new SSD Drive on CQ60-409SA
I have just replaced my HDD with a new Sandisk 120GB Extreme 11 SSD. All went OK with no problems installing Win 7 Ultimate and much faster search time, etc.. The problem I have is that when I boot the laptop from cold, i.e switch it on for use, the
-
Invoice Verification causes error "Table T030 ECOA WRX entry is missing"
I have manage to find a solution to the error message above that appears during Invoice Verification process. However, the solution (using Tcode FBKP) seems to work only with new purchase order document created after the solution was applied. Existin
-
Hello, I'm stuck on this issue. I got this error on Front-end server. Can someone help me on this. TLS outgoing connection failures. Over the past 28 minutes, Lync Server has experienced TLS outgoing connection failures 15 time(s). The error code of