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 you

Can anyone give me an idea here :\

Similar Messages

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.

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,
Abhilash

Cannot 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

Exchange Connector for 365 cloud email

We are hoping to use the Exchange Connector 3.0 for SCSM (Service Manager). Do we have to install the API on the Exchange server in the cloud to accomplish this? Also does the Exchange Connector 3.0 work with Exchange 2007?

Using Office 365 there should be nothing you need to install in the cloud. You will need to install the Exchange Web Services Managed API client dll on your SCSM management server.
In the documentation for the Exchange Connector, it states it was tested on Exchange 2010 and Office 365. I'm not sure if it will work or not because Exchange 2007 doesn't have the same remote PowerShell abilities as 2010. I know this is why the Orchestrator
IP for Exchange will not work on 2007.
Matthew Dowst |
Blog | Twitter

Exchange connector to Office 365

Dears,
I am beginner to SCSM, so please forgive my non professional questions.....
I am trying to connect my Service Manager to Office 365, and I have below questions
In general settings > Enter one or more active directory: I added my local domain (John.Lab)
Is this correct?
In server settings > Use Auto discovery: I did not check it Is this correct?
In server settings > Exchange Server URL, I added: "https://pod51036.outlook.com/EWS/Exchange.asmx" is this correct or do I have to add:
https://pod51036.outlook.com/owa?
In server settings > User impersonation can I use this settings to link it with my IR since I am using office 365? "actually this is the main reason for my exchange connector?
In server settings > Run as account:
can I use a domain user account which does not have Mailbox and
mail address?
Thank you

Hi,
1. This is correct
2. This is correct
3. This looks good. Otherwise, try
https://outlook.office365.com/EWS/Exchange.asmx
4. No. You must not check this option.
5. You have to create a separate Run As account. The username would be [Office 365 Domain]\[Office 365 User Name], and the Password. SCSM will not be able to validate the credentials, however you can still accept it.
HTH,
Dieter

Scsm 2012 r2 (ur 3) with exchange connector 3 - state never run but reveices mail in opm log?!

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 Thomas

i 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 Exchange Connector - Close an Incident in SCSM?

Hi All
We have e-mails going from SCSM to 3rd party Ticketing tool called Footprints. We send New and Close e-mails to Footprints from SCSM. However I am exploring having Footprints to send its own Close emails to the Exchange Connector monitored
mailbox (so SCSM\SCOM will close Incidents\Alerts when they have been closed in Footprints). Is this possible? can the tool correlate an E-mail in the Monitored mailbox to an Incident in SCSM that should be closed? If so does the E-mail need to
be Formatted in a particular way? e.g. SCSM ID in E-mail Title? etc
Any thoughts much appreciated!
Kind Regards
Andrew

No need to modify the keyword cause incident ID must to be in the square brackets. Please refer to the connector's guide for a detailed explanation. Just place ID in [] and the keyword in the message's body.
Cheers,
Marat
Site: www.scutils.com Twitter:
LinkedIn:
Graveyard:

ADFS, Office 365 + Exchange 2012

Need information on How to configure the ADFS, Office 365 + Exchange 2012 on IOS device.

Hi,
Based on my research, we can join iOS devices to a workplace with
Windows Server 2012 R2:
Overview: Join to Workplace from Any Device for SSO and Seamless Second Factor Authentication Across Company Applications
http://technet.microsoft.com/en-us/library/dn280945.aspx
Walkthrough Guide: Workplace Join with an iOS Device
http://technet.microsoft.com/en-us/library/dn280933.aspx
Best Regards,
Amy

Exchange Connector 3.0 not processing Office 365 mailbox

Hi,
I have Service Manager 2012 SP1 configured with Exchange Connector 3.0. The mailbox to be monitored is in Office 365. everything was running fine last week until I removed the federation trust and connectors from our On-premise Exchange servers as part of
the On-premise Exchange server decommissioning process to remove the Exchange Hybrid configuration.
Now the Exchange Connector does not monitor the mailbox of the configured user in the "run as account", no new incidents are displayed when users sent an email to the run as account. No errors are logged in the Event Viewer for the Exchange Connector.
Any suggestions?

Hi,
Set up the detailed logging and then see in the Operations Manager's log what happens when the Exchange Connector is running.
Cheers,
Marat
Site: www.scutils.com Twitter:
LinkedIn:
Graveyard:

Exchange Connector / Office 365 Not matching affected user to AD user

We use Office 365 to host our email services. AD is not synchronized to office 365. We're bringing Exchange on premises soon so there isn't a lot we want to invest in that existing infrastructure. I'm using Service Manager 2012 R2.
I have the ADConnector configured, bringing in Active Directory users/groups/computers.
I've gotten the Exchange Connector running in order to retrieve emails from an "IT Services" Office 365 mailbox and automatically create tickets. Notifications back to the users are working fine.
The problem I'm having is the affected user is not being set properly when a user emails the mailbox and an incident is created. It is setting the Affected User to that user's name, but when I double click the Affected user, it brings up the "User
- <UserName>" screen. All of the information that would be coming in from AD is blank. So that association between my office 365 email address and the AD user account is not being made. Even though it says my name with
correct (username) on the incident as the affected user. And even though my email address is stored inside of AD in the e-mail field.
What am I missing in this process?
Thank you,
Mark

I ended up messing around and added a UPN to AD Domains and Trusts matching the domain of our email accounts through Office 365. I found this because similar preparation is required for AD sync to Office 365, so a proper match can be made.
So for example, if our internal domain is Contoso.Local, and our email addresses are [email protected]
I added a UPN for contosolimited.com in Active Directory Domains & Trusts. Then I changed my UPN in Active Directory Users and Computers (Account tab), to @contosolimited.com.
Now when the AD Connector ran, it set my user CI UPN (in the Extensions tab) to [email protected] I then sent an email to [email protected] and it matched my email correctly to my user CI created by the AD Connector.
Now I just have to run a script against AD to update all user UPNs to @contosolimited.com from @Contoso.local.

How to create a Service request using Exchange connector in SCSM 2012

HI ,
I am able to create Incident request using exchange connector.Could you please let me know that how can i create Service request using Exchange connector 3.0.
Thanks in advance.

Hi,
Select a service request's template for new work items on the last wizard's page.
Cheers,
Marat
Site: www.scutils.com Twitter:
LinkedIn:
Graveyard:

Scsm 2012 - exchange connector 3

Hi,
I have been asked to check that we are on exchange connector 3, am i correct in saying that the bit I have highlighted below shows we are on exchange connector 3 already?
Plus i noticed the version number of 7.5.8501.0 is old and this maybe why we have no option to select/or unselect 'log items for user from CMDB only' when we set up an exchange connector. Does
anyone know how I can update this?
<ManagementPack ContentReadable="true" SchemaVersion="2.0" OriginalSchemaVersion="1.1" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<Manifest>
    <Identity>
      <ID>Microsoft.SystemCenter.ExchangeConnector</ID>
      <Version>3.0.0.0</Version>
    </Identity>
    <Name>Microsoft.SystemCenter.ExchangeConnector</Name>
    <References>
      <Reference Alias="ServiceManager.LinkingFramework.Library">
        <ID>ServiceManager.LinkingFramework.Library</ID>
        <Version>7.5.3079.0</Version>
        <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
      </Reference>
      <Reference Alias="Console">
        <ID>Microsoft.EnterpriseManagement.ServiceManager.UI.Console</ID>
        <Version>7.5.3079.61</Version>
        <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
      </Reference>
      <Reference Alias="Windows">
        <ID>Microsoft.Windows.Library</ID>
        <Version>7.5.8501.0</Version>

oh, you did start another thread....
ok, you might want to make sure you are using
the RTM version, rather then the RC version which was also called 3.0.
the version number you reference is the expected minimum version of the Microsoft.Windows.Library (which explains why it has the somewhat odd version number). it's ok if it's below the current version, since this is just the minimum accepted version
for that Reference Alias.

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?
Thanks

Hi,
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:

Connector help ( Coexistence Exchange 2003 and Exchange 2010)

Dear all,
we are in a Coexistence state where all the mailboxes are not yet migrated to Exchange Sever 2010.
On Exchange server 2003 we have two connectors 1) Internal 3) External
1) Internal connector is used to have mail flow between postfix mail and Exchange server.
2) External Connector is used for sending/receiving emails from External domains (like gmail,yahoo etc...)
3) when we added first Exchange 2010 that time it created one RGC used for sending/receving emails between Legacy and new server.
What I want to achieve is created new two more connectors on Exchange server which will act as Internal & External connector.
if these works then delete connectors on legacy server and go ahead with for rest migration
is it possible if not then how do it ?
TheAtulA

Hi AtulA,
Thank you for your question.
Internal:
To support coexistence between these two routing topologies, all Exchange 2010 servers are automatically added to a single routing group when Exchange 2010 is installed. The Exchange 2010 routing group is recognized in Exchange System Manager in Exchange
2003 as Exchange Routing Group within Exchange Administrative Group.
During the installation of the first Exchange 2010 Hub Transport server in an existing Exchange organization, we must specify an Exchange 2003 bridgehead server to which to establish the first routing group connector. We recommend that you select a bridgehead
server located in a hub routing group or in a routing group that has many mailboxes. The routing group connector links the routing group where the Exchange 2003 server resides and the Exchange 2010 routing group. The Exchange 2010 routing group includes all
Exchange 2010 servers, regardless of the Active Directory site in which they reside.
Notice: Don't move Exchange 2010 servers out of Exchange Routing Group (DWBGZMFD01QNBJR), and don't rename Exchange Routing Group (DWBGZMFD01QNBJR) by using a low-level directory editor. Neither action is supported. Exchange 2010 must use
this routing group for communication with Exchange 2003.
External:
We could create send connector and receive connector to send/receive email from Internet, we should modify the firewall setting to point to Exchange 2010.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

Exchange connector stops working after patching?

our service manager exchange connector stopped working after patching that we performed on wed.
When starting or stopping the exchange connector we get this info in the Operations manager log file.
Error importing solutions. Error message:Management Pack [Microsoft.EnterpriseManagement.ServiceManager.Connector.AD,d43c3091-62c2-6404-607d-4376e592a89b] already imported.
Management Pack [Microsoft.EnterpriseManagement.ServiceManager.Connector.Sms,f772aa89-b934-2fac-4f37-5e0165d390ec] already imported.
Management Pack [Microsoft.SystemCenter.ConfigurationManager.Connector.PowerManagement,a070249c-6b56-37b8-d52c-a2906a63f9fc] already imported.
Management Pack [Microsoft.EnterpriseManagement.ServiceManager.Connector.Sms2011,fbea6f5a-838d-25a2-20af-fc21eb0b6706] already imported.
Management Pack [Microsoft.SystemCenter.ConfigurationManager2011.Connector.PowerManagement,bc23ed54-a33a-f608-05a9-c1f292140d2e] already imported.
Has anybody else seen this? Any suggestions?
Thanks Lance

Hi,
Did you try to restart SCSM's services?
If this doesn't help, I would try to delete and recreate the connectors.
More info:
System Center Service Manager Connector 3.0 for Exchange
http://www.microsoft.com/en-us/download/details.aspx?id=38791
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

SCSM Exchange Connector Help, NO ADFS Exchange 365

Similar Messages

Maybe you are looking for