none
Problem with migration meeting rooms from 2010 to 2013

    Question

  • We have Exchange 2013 in company A and Exchange 2010 + 2013 servers in company B. There is a two-way AD forest trust beetwen forests. We did GAL synchronization with Microsoft Forefront Identity Manager. There is organization sharing configured on both exchange organization in place. Everything worked as expected. Currently we are trying to migrate meeting rooms in company B from exchange 2010 to 2013 mailbox database. Move request was finished with success but some of meeting rooms (in company B) does not responds for meeting requests from users from federated company A. The same meeting rooms respond properly for meeting request from within the same forest (company B). Of course we did synchronization of GAL after move requests finished. Any idea how to troubleshoot it?
    Tuesday, October 13, 2015 7:00 AM

All replies

  • Hello,

    You can try comparing with their AD properties and see if there are any differences.

    Open Command Prompt, type the commands, compress and send the output files to me.

    ldifde -f c:\<Name of User>.txt -d "distinguishedName of User"

    Here is the detailed steps for getting the distinguishedName of a user:

    a. Run the Adsiedit.msc from a command prompt.
    b. Expand “Domain”->”DC=domainName,DC=com”->”CN=Users”
    c. Right click on ”CN=the problematic user name”, click “Properties”.
    d. Find the attribute “distinguishedName” attribute. Double click copy the value of it.

    Thanks,

    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 tnmff@microsoft.com


    Simon Wu
    TechNet Community Support



    Tuesday, October 13, 2015 3:13 PM
    Moderator
  • Below I paste output from ldifde for working\respongind meeting room (good) 

    dn:: Q049UmVzc3VyczogS1JLIOKAkyBEMjQgTcO4dGVyb20gU2FtaGFuZGxpbmcgMTIoa3JrczEyKSxPVT1Tb3Jjb0RvbWFpbkNvbnRhY3RzLERDPWFwcGx5cG9sYW5kLERDPWNvbQ==
    changetype: add
    objectClass: top
    objectClass: person
    objectClass: organizationalPerson
    objectClass: contact
    cn:: UmVzc3VyczogS1JLIOKAkyBEMjQgTcO4dGVyb20gU2FtaGFuZGxpbmcgMTIoa3JrczEyKQ==
    distinguishedName:: 
     Q049UmVzc3VyczogS1JLIOKAkyBEMjQgTcO4dGVyb20gU2FtaGFuZGxpbmcgMTIoa3JrczEyKSxPVT
     1Tb3Jjb0RvbWFpbkNvbnRhY3RzLERDPWFwcGx5cG9sYW5kLERDPWNvbQ==
    instanceType: 4
    whenCreated: 20151007075153.0Z
    whenChanged: 20151013063151.0Z
    displayName:: UmVzc3VyczogS1JLIOKAkyBEMjQgTcO4dGVyb20gU2FtaGFuZGxpbmcgMTI=
    uSNCreated: 20412492
    uSNChanged: 20939957
    proxyAddresses: 
     X500:/o=companyA/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Rec
     ipients/cn=contactae1f4b50
    proxyAddresses: smtp:krks12@companyB.com
    proxyAddresses: smtp:krks12@companyB.com
    proxyAddresses: 
     X500:/o=companyB/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Rec
     ipients/cn=KRK - DXX Moterom Samhendlig 12b47
    proxyAddresses: X400:C=US;A= ;P=companyB;O=Exchange;S=krks12;
    proxyAddresses: SMTP:krks12@companyB.com
    name:: 
     UmVzc3VyczogS1JLIOKAkyBEMjQgTcO4dGVyb20gU2FtaGFuZGxpbmcgMTIoa3JrczEyKQ==
    objectGUID:: WnBaTyX7y0WDqNN4fYNRrw==
    showInAddressBook: 
     CN=All Contacts(VLV),CN=All System Address Lists,CN=Address Lists Container,CN
     =companyA,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=applypolan
     d,DC=com
    showInAddressBook: 
     CN=All Recipients(VLV),CN=All System Address Lists,CN=Address Lists Container,
     CN=companyA,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=applypol
     and,DC=com
    showInAddressBook: 
     CN=Default Global Address List,CN=All Global Address Lists,CN=Address Lists Co
     ntainer,CN=companyA,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=
     companyA,DC=com
    showInAddressBook: 
     CN=All Rooms,CN=All Address Lists,CN=Address Lists Container,CN=companyA,C
     N=Microsoft Exchange,CN=Services,CN=Configuration,DC=companyA,DC=com
    showInAddressBook: 
     CN=All Contacts,CN=All Address Lists,CN=Address Lists Container,CN=APPLY Polan
     d,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=companyA,DC=com
    legacyExchangeDN: 
     /o=companyA/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipien
     ts/cn=contactae1f4b50
    objectCategory: CN=Person,CN=Schema,CN=Configuration,DC=companyA,DC=com
    dSCorePropagationData: 16010101000000.0Z
    textEncodedORAddress: X400:C=US;A= ;P=companyB;O=Exchange;S=krks12;
    mail: krks12@companyB.com
    msExchRecipientTypeDetails: 32768
    msExchUMDtmfMap: emailAddress:575712
    msExchUMDtmfMap: lastNameFirstName:737787757532466837667264263546412
    msExchUMDtmfMap: firstNameLastName:737787757532466837667264263546412
    msExchResourceSearchProperties: Room
    msExchResourceMetaData: ResourceType:Room
    mailNickname: krks12
    msExchPoliciesExcluded: {26491CFC-9E50-4857-861B-0CB8DF22B5D7}
    msExchOriginatingForest: companyB.com
    mAPIRecipient: TRUE
    targetAddress: SMTP:krks12@companyB.com
    msExchVersion: 88218628259840
    msExchRecipientDisplayType: -2147481850
    publicDelegates: 
     CN=xxx\, xxx,OU=companyBDomainContacts,DC=companyA,DC=com
    msExchResourceDisplay: Room
    

    and the second one which is not working as expected (wrong)

    dn:: Q049UmVzc3VyczogS1JLIOKAkyBEMjQgTcO4dHIgVGVzdEJhcnQoZDI0dGVzdEJhcnQpLE9VPVNvcmNvRG9tYWluQ29udGFjdHMsREM9YXBwbHlwb2xhbmQsREM9Y29t
    changetype: add
    objectClass: top
    objectClass: person
    objectClass: organizationalPerson
    objectClass: contact
    cn:: UmVzc3VyczogS1JLIOKAkyBEMjQgTcO4dHIgVGVzdEJhcnQoZDI0dGVzdEJhcnQp
    distinguishedName:: 
     Q049UmVzc3VyczogS1JLIOKAkyBEMjQgTcO4dHIgVGVzdEJhcnQoZDI0dGVzdEJhcnQpLE9VPVNvcm
     NvRG9tYWluQ29udGFjdHMsREM9YXBwbHlwb2xhbmQsREM9Y29t
    instanceType: 4
    whenCreated: 20151013063144.0Z
    whenChanged: 20151013180236.0Z
    displayName:: UmVzc3VyczogS1JLIOKAkyBEMjQgTcO4dHIgVGVzdEJhcnQ=
    uSNCreated: 20939948
    uSNChanged: 20992249
    proxyAddresses: smtp:d24testBart@companyB.com
    proxyAddresses: smtp:d24testBart@companyB.com
    proxyAddresses: 
     X500:/o=companyB/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Rec
     ipients/cn=user5f01ca0a
    proxyAddresses: X400:C=US;A= ;P=companyB;O=Exchange;S=d24testBart;
    proxyAddresses: SMTP:d24testBart@companyB.com
    name:: UmVzc3VyczogS1JLIOKAkyBEMjQgTcO4dHIgVGVzdEJhcnQoZDI0dGVzdEJhcnQp
    objectGUID:: juHQwczsA0GEUsEIDKQ9lQ==
    showInAddressBook: 
     CN=All Contacts(VLV),CN=All System Address Lists,CN=Address Lists Container,CN
     =companyA,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=applypolan
     d,DC=com
    showInAddressBook: 
     CN=All Recipients(VLV),CN=All System Address Lists,CN=Address Lists Container,
     CN=companyA,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=applypol
     and,DC=com
    showInAddressBook: 
     CN=Default Global Address List,CN=All Global Address Lists,CN=Address Lists Co
     ntainer,CN=companyA,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=
     companyA,DC=com
    showInAddressBook: 
     CN=All Rooms,CN=All Address Lists,CN=Address Lists Container,CN=companyA,C
     N=Microsoft Exchange,CN=Services,CN=Configuration,DC=companyA,DC=com
    showInAddressBook: 
     CN=All Contacts,CN=All Address Lists,CN=Address Lists Container,CN=APPLY Polan
     d,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=companyA,DC=com
    legacyExchangeDN: 
     /o=companyA/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipien
     ts/cn=contactdf6adeb5
    objectCategory: CN=Person,CN=Schema,CN=Configuration,DC=companyA,DC=com
    dSCorePropagationData: 16010101000000.0Z
    textEncodedORAddress: X400:C=US;A= ;P=companyB;O=Exchange;S=d24testBart;
    mail: d24testBart@companyB.com
    msExchRecipientTypeDetails: 32768
    msExchUMDtmfMap: emailAddress:32483782278
    msExchUMDtmfMap: lastNameFirstName:7377877575324668783782278
    msExchUMDtmfMap: firstNameLastName:7377877575324668783782278
    msExchResourceSearchProperties: Room
    msExchResourceMetaData: ResourceType:Room
    mailNickname: d24testBart
    msExchPoliciesExcluded: {26491CFC-9E50-4857-861B-0CB8DF22B5D7}
    msExchOriginatingForest: companyB.com
    mAPIRecipient: TRUE
    targetAddress: SMTP:d24testBart@companyB.com
    msExchVersion: 88218628259840
    msExchRecipientDisplayType: -2147481850
    publicDelegates: CN=user1\, test,OU=companyBDomainContacts,DC=companyA,DC=com
    msExchResourceDisplay: Room
    

    Wednesday, October 14, 2015 6:02 AM
  • Hello bbelko,

    From the log you provided, it seems there is no problematic attributes on the room mailboxes. Please try move the problematic room mailbox to another Exchange 2013 database and see if it works.

    By the way, when the room does not response, can you log in the problematic room mailbox and let us know if the room mailbox receives the meeting request from the users in company A?


    Thanks,

    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 tnmff@microsoft.com


    Simon Wu
    TechNet Community Support

    Sunday, October 18, 2015 2:29 PM
    Moderator
  • I tried to move problematic mailbox to another db - no success, the same situation. I logged on to this room mailbox and I can see invitations in inboox that comes from users from company A. But there is still no auto response from room mailbox. When I clicked accept and send response (in room mailbox opened in outlook) then user from company A get meeting confirmation. Any idea?
    Monday, October 19, 2015 6:25 AM
  • I changed default log level from lowest to high for the below items on exchange server

    MSExchangeMailboxAssistants\Resource Booking Attendant
    MSExchangeMailboxAssistants\Approval Assistant

    Then I looked at the application log on exchange server and I can find only logs for meeting request processing for users from domain B (local domain) - no logs for meeting requests processing for users from domain A

    Monday, October 19, 2015 7:49 AM
  • Hello,

    Since there is no sufficient information from the logs, in my opinion, the next step is to trace the problematic resource mailbox. As the extra.exe tool is not built-in Exchange 2013, we have to call Microsoft Support and they will help on this.

    Another workaround is to create a new Exchange 2013 resource mailbox and export the data from the problematic one to the new one.

    Thanks,

    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 tnmff@microsoft.com


    Simon Wu
    TechNet Community Support

    Tuesday, November 3, 2015 9:09 AM
    Moderator