Exchange Connector - Add a mailbox to ManagementScope

Hi,
I have installed SCSM 2012 RTM, also configured Exchange Connector 3.0 in my Test Environment. Also implemented Impersonate ([email protected]), everything is working fine. In prod we use [email protected] for generating ticket, I am trying to
add another Exchange Connector in Test lab with [email protected] to duplicate prod tickets in test lab. Is Multiple Exchange connectors possible in SCSM.
Thanks and Regards,
Pradeep Kumar
Pradeep Kuimar

Andreas,
Thank you for your reply. Presently we are using another ticketing system in Prod, i have been in-charge of testing SCSM product and replacing it with present Ticketing system. Prod and test has different email mailbox configured. In prod we use [email protected]
and in Test lab we are using [email protected]
when user sends email to [email protected], regular ticket will be generated in Prod and need duplicate ticket to be created in test lab.
[email protected] has impersonation rights. I am trying to add [email protected] also to impersonation group.
New-ManagementScope
-Name: 'Exchange Impersonation Incident'
-RecipientRestrictionFilter
'Name -eq "helpdesk"'
Its giving me below error :
+ CategoryInfo : NotSpecified: (0:Int32) [New-ManagementScope], ADObjectAlreadyExistsException
+ FullyQualifiedErrorId : 96079C5B,Microsoft.Exchange.Management.Tasks.NewManagementScope
Please help....
Pradeep Kuimar

Similar Messages

Exchange Connector adds Workflow user as related Item to Review Activity

We use Servcie Manager 2012 R2 with Exchange Connector 2.0
For some reason, the Exchange Connector adds the workflow user to the review activity as a related config item. The sender of the email would make sence, but the workflow user does not.
Does the Exchange Connector 3.0 Rerelease also add the workflow user?
Is there a possibility to avoid this behavior?
tia
Patrick Wahlmüller

Hi Patrik !
Never saw that before, what i can say is that the upgrade/change to Exchange COnnector 3.0 is easy low-risk and you add MS-Support possibilities for it.
Go for 3.0 !
R.

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

Exchange Connector 3.0 (Hotfix Release) Error - Error Message=The key value of an object cannot be changed.

Hello,
I am running Service Manager 2012 with the Exchange Connector 3.0 RTM (Re-release Version). The issue I have is that when an e-mail is processed that is trying to update the status or event log of an incident, the Exchange Connector encounters an error
and will not update the object. The Operations Manager log denotes:
Exchange Connector: Unable to process mail item. Subject="Close Ticket: [IRXXXXX]", Error Message=The key value of an object cannot be changed.
This will happen on a seemingly random selection of Incident work items. I cannot correlate them with a specific template, exchange connector, or incident tier queue that could be causing the issue. I can recreate the way a specific ticket
was created and update it through e-mail without issue, and the next ticket can cause the error to trigger.
I have already opened a Microsoft Support Case using our Software Assurance agreement. After a few months of troubleshooting the issue and trying different fixes, Microsoft support said they were unable to fix the problem and that we would need to
purchase Premier support to go further. At this point I thought I would reach out to the community for ideas.
The setup I have for the Exchange connectors is as follows.
I have three separate Exchange connectors set up to three different mailboxes. One Exchange connector processes external support tickets and applies a specific template. Another processes client support tickets and applies a different template.
And the last Exchange connector processes internal tickets and also processes the updates of tickets created by the other two exchange connectors.
Here are the fixes I've attempted so far:
1. Changed the templates that each Exchange connector applies.
2. Changed the management pack that each template is stored in.
3. Checked my management pack(s) for extended classes by searching for Extension="true" (This was also checked by Microsoft support)
4. Deleted each Exchange connector and recreated each connector
5. Deleted each Exchange connector, deleted the management pack, and reinstalled the management pack and connectors
6. Repeated Step 5, deleted Microsoft.SystemCenter.ExchangeConnector.dll and Microsoft.SystemCenter.ExchangeConnector.resources.dll and then installed the Exchange connector Re-release version 3.0 Published 10/7/2013 (which is supposed to address this
issue)
7. Deleted the HealthServiceState folder and restarted the Management Service
I'm not really sure what to do at this point. I've put many hours into customizing my installation to get it working for my organization so reformatting and starting from scratch would be a nightmare scenario. This environment is in production.
I do have a band-aid in place using Orchestrator. Basically I have a monitor task searching for the error message and when it finds one it searches the mailbox for the offending e-mail and applies either the Resolve or Close status change that is requested
from the user. However, I do not have it working to update the ticket if a comment is applied to the incident. If anyone is in this position and needs to know how to apply this Orchestrator task I am willing to provide my workflow.
I am new to the community and am already impressed with the amount of help and effort there is in this forum. I appreciate in advance any help that is provided and am open to any ideas at this point. I can post more information as needed.
Thank you,
John

Yes that is the whole template. However, I did confirm that this is only happening to incidents where either of two situations triggers a runbook to fire and modify the incident. When I remove the activity from the incident it does clear the
issue. For some background the first Runbook Activity set's the first response date when an incident is resolved if the first response value is null. The second assigns the incident to a user upon creation if the title contains assignto:username;
1.)
<ObjectTemplate ID="Template.d33b5bbcaf3c49b18d8b72bc1e5e1ee4" TypeID="IncidentManagement!System.WorkItem.Incident.ProjectionType">
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Incident_Library!System.WorkItem.Incident']/Escalated$">False</Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Incident_Library!System.WorkItem.Incident']/NeedsKnowledgeArticle$">False</Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Incident_Library!System.WorkItem.Incident']/HasCreatedKnowledgeArticle$">False</Property>
<Object Path="$Context/Path[Relationship='CustomSystem_WorkItem_Activity_Library!System.WorkItemContainsActivity' TypeConstraint='CustomMicrosoft_SystemCenter_Orchestrator!Microsoft.SystemCenter.Orchestrator.RunbookAutomationActivity']$">
<Property Path="$Context/Property[Type='CustomMicrosoft_SystemCenter_Orchestrator!Microsoft.SystemCenter.Orchestrator.RunbookAutomationActivity.Base']/RunbookId$">4085f0da-ab83-48e5-bbe3-1f3b5fa2dc4a</Property>
<Property Path="$Context/Property[Type='CustomMicrosoft_SystemCenter_Orchestrator!Microsoft.SystemCenter.Orchestrator.RunbookAutomationActivity.Base']/TemplateId$">Template.d33b5bbcaf3c49b18d8b72bc1e5e1ee4</Property>
<Property Path="$Context/Property[Type='CustomMicrosoft_SystemCenter_Orchestrator!Microsoft.SystemCenter.Orchestrator.RunbookAutomationActivity.Base']/IsReadyForAutomation$">True</Property>
<Property Path="$Context/Property[Type='CustomMicrosoft_SystemCenter_Orchestrator!Microsoft.SystemCenter.Orchestrator.RunbookAutomationActivity.Base']/PropertyMapping$"><?xml version="1.0" encoding="utf-16"?>
<ParameterMapping xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<ParameterList>
<RunbookParameterItem>
<Name>Get RA Guid</Name>
<Id>344b15effc1a44528e517c5b4227179c</Id>
<Type>String</Type>
<Value>Generic::Id</Value>
<Direction>In</Direction>
<ContextInfo />
</RunbookParameterItem>
</ParameterList>
<RunbookId>4085f0da-ab83-48e5-bbe3-1f3b5fa2dc4a</RunbookId>
</ParameterMapping></Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Activity_Library!System.WorkItem.Activity']/ChildId$">1906</Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Activity_Library!System.WorkItem.Activity']/Status$">$MPElement[Name='CustomSystem_WorkItem_Activity_Library!ActivityStatusEnum.Active']$</Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Activity_Library!System.WorkItem.Activity']/Skip$">False</Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Library!System.WorkItem']/Title$">Set First Response on Resolve</Property>
</Object>
</ObjectTemplate>
2.)
<ObjectTemplate ID="Template.b311e1f9126e4e19bbbbeb65ddb220ba" TypeID="IncidentManagement!System.WorkItem.Incident.ProjectionType">
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Incident_Library!System.WorkItem.Incident']/Escalated$">False</Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Incident_Library!System.WorkItem.Incident']/Status$">$MPElement[Name='CustomSystem_WorkItem_Incident_Library!IncidentStatusEnum.Active']$</Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Incident_Library!System.WorkItem.Incident']/NeedsKnowledgeArticle$">False</Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Incident_Library!System.WorkItem.Incident']/HasCreatedKnowledgeArticle$">False</Property>
<Object Path="$Context/Path[Relationship='CustomSystem_WorkItem_Activity_Library!System.WorkItemContainsActivity' TypeConstraint='CustomMicrosoft_SystemCenter_Orchestrator!Microsoft.SystemCenter.Orchestrator.RunbookAutomationActivity']$">
<Property Path="$Context/Property[Type='CustomMicrosoft_SystemCenter_Orchestrator!Microsoft.SystemCenter.Orchestrator.RunbookAutomationActivity.Base']/RunbookId$">ca88b13b-861a-4d39-a3cb-fd912d951e35</Property>
<Property Path="$Context/Property[Type='CustomMicrosoft_SystemCenter_Orchestrator!Microsoft.SystemCenter.Orchestrator.RunbookAutomationActivity.Base']/TemplateId$">Template.b311e1f9126e4e19bbbbeb65ddb220ba</Property>
<Property Path="$Context/Property[Type='CustomMicrosoft_SystemCenter_Orchestrator!Microsoft.SystemCenter.Orchestrator.RunbookAutomationActivity.Base']/IsReadyForAutomation$">True</Property>
<Property Path="$Context/Property[Type='CustomMicrosoft_SystemCenter_Orchestrator!Microsoft.SystemCenter.Orchestrator.RunbookAutomationActivity.Base']/PropertyMapping$"><?xml version="1.0" encoding="utf-16"?>
<ParameterMapping xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<ParameterList>
<RunbookParameterItem>
<Name>RA Activity GUID</Name>
<Id>5677d117a0294a2c898a695032f26c72</Id>
<Type>String</Type>
<Value>Generic::Id</Value>
<Direction>In</Direction>
<ContextInfo />
</RunbookParameterItem>
</ParameterList>
<RunbookId>ca88b13b-861a-4d39-a3cb-fd912d951e35</RunbookId>
</ParameterMapping></Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Activity_Library!System.WorkItem.Activity']/ChildId$">1120</Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Activity_Library!System.WorkItem.Activity']/Status$">$MPElement[Name='CustomSystem_WorkItem_Activity_Library!ActivityStatusEnum.Active']$</Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Activity_Library!System.WorkItem.Activity']/Skip$">False</Property>
<Property Path="$Context/Property[Type='WorkItem!System.WorkItem']/Title$">Execute Orchestrator IR - Autoassign</Property>
</Object>
</ObjectTemplate>

Custom Script Execution with 11.1.1.5.0 Exchange Connector

Folks ,
We would be cloning the 11.1.1.5.0 Exchange connector to support 2 different kind of mailboxes in Exchange server 2010 SP2.
The 2 kinds of mailboxes are Personal mailbox and a reference mailbox (similar like a personal mailbox , the only difference is that Auto-reply will be set on this mailbox).
OOTB Exchange connector will be used to create both of these mailboxes . However we want to set auto-reply only on reference mailbox using a powershell cmdlet
http://technet.microsoft.com/en-us/library/dd638217.aspx
So i would like to understand , does the connector provide such a capability to execute a cmdlet from a provisioning process via a process task or some other mechanism .
Thanks
Sid

Thanks Rahul , I have gone through the documentation .
But i dont understand , when doc mentiona you can execute a script before/after a user is created , so is this based on the event on the target after/before a mailbox is created or its triggerd from the create user task in OIM .
As i have 2 clones of exchange connector and both create mailboxes, i want invoke the script in 1 scenario and dont want to execute the script in other scenario .
thanks
Sid

Exchange Connector Setup: Could not establish trust relationship for the SSL/TLS secure channel

This may be more of a cert issue than an issue with SCSM, but here goes.
I am running into something new when creating an Exchange Connector (I swear its always something with this thing. Check the screen shot:
I can get to the service in IE, however there is a cert issue. Again, see the screen shot:
So it appears that the management server does not trust my Exchange cert, nor does it trust my root cert. I added the root CA cert to the management server snapin but still nothing.
If the root cert is under Trusted Root Certification Authorities, shouldn't it trust it? I'm not sure where to go from here?
- Get on the floor, do that dinosaur

Looking at that certificate path tab, it looks like this certificate is a self-signed certificate issued by the exchange server to the exchange server. is it safe to assume this is a lab environment? it's kinda rare for that to be left as-is in a production
exchange architecture.
If it is a self signed certificate (the Issuer and subject fields on the first page will be the same), then the only wat to trust it is to add that certificate to the trusted root certificate authorities under the system certificate store.
Here is an excellent tutorial on how to add certificates to the local machine trusted root store.
If this is a production environment, get with your exchange administrator, because you might be hitting the wrong CAS server, and getting the wrong certificate as a result.m

Exchange Connector 3.0 RTM - Wrong action log type (user comments are sometimes analyst comments)

Hi,
We started using Service Manager a few days ago and I'm noticing some strange behavior from the Exchange connector. Sometimes when a user replies to an e-mail, it get's added as an "Analyst comment", also the private checkbox has a dot in it (not
blank or checked, but a dot..)
In this screenshot user "Marwan" is a regular user, replying to us via email...
Any ideas?

Today there already is intelligence that checks if the recipient == affected user. I am merely suggesting to rewise and/or extend this logic
As I wrote, I see two possible ways here. The easy and the hard (optimal) way. The easy way would be to turn it around, meaning all comments = End-User comments unless it's coming from the Assigned User. So the check would be on the Assigned User instead
of the Affected User as it is today. I understand that some people might complain about this, and might have adapted to the current solution, so it should be optional. In my experience I just see this as more suitable for the customers needs. Well if the source
code could be released it would make it easier to make custom adjustments, e.g. change the Private boolean value to false etc. ;)
The hard optimal way would be to add more options for deciding when it's an Analyst and when it's an End-User. Of course the Exchange connector can't figure that out, but if it did comparison to preselected groups or perhaps User Roles (e.g. if recipient
is Incident Resolver and not affected user => analyst comment).
In any case it's an interesting discussion with many aspects, but one thing is for certain: the exchange connector is unfinished. Not broken, just lacking options. Today people are making alot of custom workflows and even their own connectors to accommodate
for these issues.

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?

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

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:

Microsoft Exchange Connector Reconciliation Problem

Hi,
i am trying to run the Exchange Target Resource User Reconciliation and Exchange User Distribution Group Lookup Reconciliation scheduled tasks but i am getting below mentioned error.
ConnectorServer.exe Error: 0 : Org.IdentityConnectors.Framework.Common.Exceptions.ConnectorException: Problem while PowerShell execution System.Management.Automation.ParameterBindingException: A parameter cannot be found that matches parameter name 'IgnoreDefaultScope'.
at System.Management.Automation.CmdletParameterBinderController.VerifyArgumentsProcessed()
at System.Management.Automation.CmdletParameterBinderController.BindCommandLineParametersNoValidation(Collection`1 arguments)
at System.Management.Automation.CmdletParameterBinderController.BindCommandLineParameters(Collection`1 arguments)
at System.Management.Automation.CommandProcessor.BindCommandLineParameters(CommandParameterInternal[] parameters)
at System.Management.Automation.CommandProcessor.Prepare(CommandParameterInternal[] parameters)
at System.Management.Automation.CommandProcessorBase.DoPrepare(CommandParameterInternal[] parameters)
at System.Management.Automation.Internal.PipelineProcessor.Start(Boolean incomingStream)
at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
at Org.IdentityConnectors.Exchange.Service.Impl.PowerShellExchangeServiceImpl.InvokePipeline(Command cmd) in c:\ADE\aime_oimcp\idc\bundles\dotnet\Exchange\ExchangeConnector\PowerShellExchangeConnectorServiceImpl.cs:line 635
at Org.IdentityConnectors.Exchange.Service.Impl.PowerShellExchangeServiceImpl.SearchDistributionGroups(ObjectClass oclass, String query, ResultsHandler handler, OperationOptions options, ObjectClassInfo ocInfo) in c:\ADE\aime_oimcp\idc\bundles\dotnet\Exchange\ExchangeConnector\PowerShellExchangeConnectorServiceImpl.cs:line 293
at Org.IdentityConnectors.Exchange.Service.Impl.PowerShellExchangeServiceImpl.ExecuteQuery(ObjectClass oclass, String query, ResultsHandler handler, OperationOptions options) in c:\ADE\aime_oimcp\idc\bundles\dotnet\Exchange\ExchangeConnector\PowerShellExchangeConnectorServiceImpl.cs:line 252
at Org.IdentityConnectors.Exchange.ExchangeConnector.ExecuteQuery(ObjectClass oclass, String query, ResultsHandler handler, OperationOptions options) in c:\ADE\aime_oimcp\idc\bundles\dotnet\Exchange\ExchangeConnector\ExchangeConnector.cs:line 228
at Org.IdentityConnectors.Framework.Impl.Api.Local.Operations.RawSearcherImpl`1.RawSearch(SearchOp`1 search, ObjectClass oclass, Filter filter, ResultsHandler handler, OperationOptions options) in c:\ADE\aime_icf\icf\framework\dotnet\FrameworkInternal\ApiLocalOperations.cs:line 1223
at Org.IdentityConnectors.Framework.Impl.Api.Local.Operations.RawSearcherImpl`1.RawSearch(Object search, ObjectClass oclass, Filter filter, ResultsHandler handler, OperationOptions options) in c:\ADE\aime_icf\icf\framework\dotnet\FrameworkInternal\ApiLocalOperations.cs:line 1194
at Org.IdentityConnectors.Framework.Impl.Api.Local.Operations.SearchImpl.Search(ObjectClass oclass, Filter originalFilter, ResultsHandler handler, OperationOptions options) in c:\ADE\aime_icf\icf\framework\dotnet\FrameworkInternal\ApiLocalOperations.cs:line 1156
at Org.IdentityConnectors.Framework.Impl.Api.Local.Operations.ConnectorAPIOperationRunnerProxy.Invoke(Object proxy, MethodInfo method, Object[] args) in c:\ADE\aime_icf\icf\framework\dotnet\FrameworkInternal\ApiLocalOperations.cs:line 244
at ___proxy1.Search(ObjectClass , Filter , ResultsHandler , OperationOptions )
at Org.IdentityConnectors.Framework.Impl.Server.ConnectionProcessor.ProcessOperationRequest(OperationRequest request) in c:\ADE\aime_icf\icf\framework\dotnet\FrameworkInternal\Server.cs:line 609
Please any one suggest to me on this error.
Thanks,
venu

Yes we finally solved it.
The Exchange connector creates mailboxes in the Exchange Server using the CreateMailboxExchange2007.vbs script. This script invokes another program called PowerShell.exe. We found out there were 2 different versions of Powershell.exe in our system. One of them was obsolete and it was the one being called. We solved the problem specifying the complete path of the good Powershell.exe version in the CreateMailboxExchange2007.vbs script ($PowerShell_PATH$/Powershell.exe...).
Regards

Exchange connector to hosted Exchange Server gives Connection errors in log.

I have setup the exchange connector within SCCM 2012 R2 CU3. Everything seems to work. I get the EAS connected devices discovered in the SCCM console.
The Hosted Exchange server I used is https://ps.outlook.com/PowerShell-Live-ID
Although everything seems to work i frequently get the following errors in the EASdisc.log:
ERROR: [MANAGED] Failed to open Runspace. Exception: System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server failed with the following error message : The SSL connection cannot be established. Verify that the service
on the remote host is properly configured to listen for HTTPS requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command
on the destination to analyze and configure the WinRM service: "winrm quickconfig -transport:https". For more information, see the about_Remote_Troubleshooting Help topic.~~   at System.Management.Automation.Runspaces.AsyncResult.EndInvoke()~~
  at System.Management.Automation.Runspaces.Internal.RunspacePoolInternal.EndOpen(IAsyncResult asyncResult)~~   at System.Management.Automation.Runspaces.RunspacePool.Open()~~   at System.Management.Automation.RemoteRunspace.Open()~~
  at Microsoft.ConfigurationManager.ExchangeConnector.ExchangeRunspace.InitRunspace()
ERROR: Failed to call Initialize of managed COM. error = Unknown error 0x80131501
ERROR: Failed to initialize managed com instance. Error = Unknown error 0x80131501, -2146233087
There is no fixed interval in which these errors are reported.
Can i neglect these errors, or am I missing something?
I found the following thread without a solution:
http://community.office365.com/en-us/f/156/t/265109.aspx

Try to use FQDN of Cas server in URL and Add CASADMIN into all the three Exchage Roles: Recipient Management; View Only Organization Management; and Server
Management. Enabled the Windows Authentication on Exchange CAS Server for /powershell in IIS.
Also You can check below link
https://social.technet.microsoft.com/Forums/en-US/e7ca3f0c-a793-4437-8050-2de4c9d9253c/exchange-connector?forum=configmanagergeneral
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"Mai Ali | My blog:
Technical | Twitter:
Mai Ali

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:

Exchange Connector 3.0 status Never Run

Hi,
I've setup lab enviroment of SCSM 2012 SP1 following the instructions:
http://technet.microsoft.com/en-us/library/hh914226.aspx
Everything works fine with an exception of Exchange Connector. It is stuck in status: Never Run
I was able to configure the connector with out error. I checked the event logs and it showed success
of all the config items and even showed it connected to an email that I sent to the workflow mailbox:
Logs:
Log Name: Operations Manager
Source: Exchange Connector
Date: 7/28/2014 11:52:00 AM
Event ID: 0
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: GENINGSCSMT01.CORP.IGES.SI
Description:
Exchange Connector: Attempting to connect to Exchange with the settings: login email address="contoso@CORP", impersonation email address="none", server URL="https://geningcas.corp.iges.si/EWS/Exchange.asmx"
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Exchange Connector" />
<EventID Qualifiers="0">0</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-07-28T09:52:00.000000000Z" />
<EventRecordID>152481</EventRecordID>
<Channel>Operations Manager</Channel>
<Computer>CONTOSO.COM</Computer>
<Security />
</System>
<EventData>
<Data>Exchange Connector: Attempting to connect to Exchange with the settings: login email address="testscsm@CORP", impersonation email address="none", server URL="...................................................................."
</Data>
</EventData>
</Event>
- Exchange Connector: Exchange web service tracing enabled.
- Exchange Connector: Using Exchange Web Service URL:.....................
EwsRequestHttpHeaders: <Trace Tag="EwsRequestHttpHeaders" Tid="1" Time="2014-07-28 09:52:00Z">
POST /EWS/Exchange.asmx HTTP/1.1
Content-Type: text/xml; charset=utf-8
Accept: text/xml
User-Agent: ExchangeServicesClient/14.03.0032.000
Accept-Encoding: gzip,deflate
</Trace>
EwsRequest: <Trace Tag="EwsRequest" Tid="1" Time="2014-07-28 09:52:00Z" Version="14.03.0032.000">
<?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="Central 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>
EwsResponseHttpHeaders: <Trace Tag="EwsResponseHttpHeaders" Tid="1" Time="2014-07-28 09:52:00Z">
200 OK
Transfer-Encoding: chunked
Content-Encoding: gzip
Vary: Accept-Encoding
Persistent-Auth: true
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Date: Mon, 28 Jul 2014 09:52:00 GMT
Server: Microsoft-IIS/7.5
X-AspNet-Version: 2.0.50727
X-Powered-By: ASP.NET
</Trace>
EwsResponse: <Trace Tag="EwsResponse" Tid="1" Time="2014-07-28 09:52:00Z" Version="14.03.0032.000">
<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Header>
<h:ServerVersionInfo MajorVersion="14" MinorVersion="2" MajorBuildNumber="347" MinorBuildNumber="0" 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="2" IncludesLastItemInRange="false">
<t:Items>
<t:Message>
<t:ItemId Id="AAMkAGY0NWM1MDJlLWNlYzctNDUwMy04NjUyLWZmNmJhODZmZWFjNwBGAAAAAABEWg/FMFIlQ6snViUYxTCgBwCX9G6oX6gvSK4RK8YlCtwaAAAApoPnAACX9G6oX6gvSK4RK8YlCtwaAAAApqtHAAA=" ChangeKey="CQAAABYAAACX9G6oX6gvSK4RK8YlCtwaAAAApwJt"
/>
<t:ParentFolderId Id="AAMkAGY0NWM1MDJlLWNlYzctNDUwMy04NjUyLWZmNmJhODZmZWFjNwAuAAAAAABEWg/FMFIlQ6snViUYxTCgAQCX9G6oX6gvSK4RK8YlCtwaAAAApoPnAAA=" ChangeKey="AQAAAA==" />
<t:ItemClass>IPM.Note</t:ItemClass>
<t:Subject>FW:
Test 2</t:Subject>
<t:Sensitivity>Normal</t:Sensitivity>
<t:DateTimeReceived>2014-06-13T05:41:55Z</t:DateTimeReceived>
<t:Size>9889</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-06-13T05:41:53Z</t:DateTimeSent>
<t:DateTimeCreated>2014-06-13T05:41:55Z</t:DateTimeCreated>
<t:ReminderIsSet>false</t:ReminderIsSet>
<t:ReminderMinutesBeforeStart>0</t:ReminderMinutesBeforeStart>
<t:DisplayCc />
<t:DisplayTo>Test Scsm</t:DisplayTo>
<t:HasAttachments>false</t:HasAttachments>
<t:Culture>en-US</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>Gorazd Lenko</t:LastModifiedName>
<t:LastModifiedTime>2014-06-13T05:41:55Z</t:LastModifiedTime>
<t:Sender>
<t:Mailbox>
<t:Name>Gorazd Lenko</t:Name>
</t:Mailbox>
</t:Sender>
<t:IsReadReceiptRequested>false</t:IsReadReceiptRequested>
<t:IsDeliveryReceiptRequested>false</t:IsDeliveryReceiptRequested>
<t:ConversationIndex>Ac+Gyiy/zkDKDTIqSzSWEj8rvPTxVQ==</t:ConversationIndex>
<t:ConversationTopic>test2</t:ConversationTopic>
<t:From>
<t:Mailbox>
<t:Name>Gorazd Lenko</t:Name>
</t:Mailbox>
</t:From>
<t:InternetMessageId><CC14C50767AF3448BEC68A24DC76AC439F00CDE0@></t:InternetMessageId>
<t:IsRead>false</t:IsRead>
<t:IsResponseRequested>false</t:IsResponseRequested>
<t:ReceivedBy>
<t:Mailbox>
<t:Name>Test Scsm</t:Name>
</t:Mailbox>
</t:ReceivedBy>
<t:ReceivedRepresenting>
<t:Mailbox>
<t:Name>Test Scsm</t:Name>
</t:Mailbox>
</t:ReceivedRepresenting>
</t:Message>
</t:Items>
</m:RootFolder>
</m:FindItemResponseMessage>
</m:ResponseMessages>
</m:FindItemResponse>
</s:Body>
</s:Envelope>
</Trace>
As you can see from the last event (bold letters) the Workflow account manages to get to the Exchange account, reads the inbox, but it isn't able to poll the message to SM.
Any ideas guys?

Hi,
It was set to Default Incident Template. I have created a new Incident template and recreated Exchange Connector, but the issue is still present. Workflow account is a member of SCSM Admin role, Workflow role and a local admin on the server. It is also Sysadmin
on the database.
On the Exchange server I have also ran Get_MailboxStatistics command and the output:
[PS] C:\Windows\system32>Get-MailboxStatistics | select lastlog* | fl
cmdlet Get-MailboxStatistics at command pipeline position 1
Supply values for the following parameters:
Identity: testscsm
LastLoggedOnUserAccount : CORP\testscsm
LastLogoffTime : 31.7.2014 7:45:14
LastLogonTime : 31.7.2014 7:39:58
So that means that the a
ccount logs in to mailbox but is unable to process emails.
Also I have found the difference in the EWSLogEntry on the test and production server:
The production log says:
<m:IndexedPageItemView MaxEntriesReturned="2147483647" Offset="0" BasePoint="Beginning" />
and the test log:
<m:IndexedPageItemView MaxEntriesReturned="1"
Offset="0" BasePoint="Beginning" />
Is there any way I can edit those settings?

Exchange Connector - Add a mailbox to ManagementScope

Similar Messages

Maybe you are looking for