Unable to Migrate UM from Exchange 2007 to Exchange 2010

[Bengal Tiger]

Sponsored Links

well I am looking to use Exchange 2010 from Exchange 2007. Recently completed with the migration from OSC to Lync. Right now I am wondering that I should go for partial migration, I mean I don’t wanted to move all the mailboxes at a time. Hence I have setup new Dial Plan. I have assigned a temp access number so that it can be tested. I have also configured a user with Exchange 2010 Exchange 2010 mailbox. That user is also enabled for UM as per new 2010 Dial Plan. I am able to contac him as well as drop voicemail messages. all the messages are getting delivered to his mailbox only. He will be able to listen voice mail by simply dialing number. I got below mentioned error message.

Log Name: Application
Source: MSExchange Unified Messaging
Date: 11/04/2012 9:40:38 p.m.
Event ID: 1400
Task Category: UMCore
Level: Warning
Keywords: Classic
User: N/A
Computer: ExchangeServer.domain
Description:
The following UM IP gateways did not respond as expected to a SIP OPTIONS request.
Transport = TLS, Address = LyncServer.domain, Port = 5067, Response Code = 0, Message = This operation has timed out.
Event Xml:
< Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchange Unified Messaging" />
<EventID Qualifiers="32772">1400</EventID>
<Level>3</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-04-11T09:40:38.000000000Z" />
<EventRecordID>7562</EventRecordID>
<Channel>Application</Channel>
<Computer>ExchangeServer.domain</Computer>
<Security />
</System>
<EventData>
<Data>Transport = TLS, Address = LyncServer.domain, Port = 5067, Response Code = 0, Message = This operation has timed out.
< /Data>
</EventData>
< /Event>
And this error on the Lync server.
Log Name: Lync Server
Source: LS Mediation Server
Date: 11/04/2012 7:38:19 p.m.
Event ID: 25087
Task Category: (1030)
Level: Error
Keywords: Classic
User: N/A
Computer: LyncServer.domain
Description:
There were one hundred TLS negotiations failures with incoming connections with the following remote peer on the Mediation Server Gateway side TLS endpoint.
Remote Endpoint: 192.168.x.xxx
Cause: A gateway may not be configured correctly, for example the Gateway peer may not be configured to send connections to the port Mediation Server is listening to. If this event fires multiple times in a short period for the same remote peer, the connections from this peer can be malicious connection attempts.
Resolution:
Check the Mediation Server and the Gateway server's certificates are configured correctly. Check if the MEDIATIONSERVER_MAJOR_CONFIGURATION_ALARM (Event ID: 25057) has been fired. Check whether the remote endpoint a known peer.
Event Xml:
< Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="LS Mediation Server" />
<EventID Qualifiers="50182">25087</EventID>
<Level>2</Level>
<Task>1030</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-04-11T07:38:19.000000000Z" />
<EventRecordID>7205</EventRecordID>
<Channel>Lync Server</Channel>
<Computer>LyncServer.domain</Computer>
<Security />
</System>
<EventData>
<Data>192.168.x.xxx</Data>
</EventData>
< /Event>

For your information I am having internal Cert installed on Exchange sever and it is associated with UM. This particular Cert cannot be used for multiple purpose. Let me know if you can help me out to resolve my issue. thanks a lot in advance.

[sameer22]

Looking at the situation I am suspecting that 2010 UM dial plan has been associated with Lync. If it is Lync then see that whether it is using same kind of internal CA for internal certificates. You have to go through Lync to Exchange 2010 UM in certificates or setup on Exchange 2010 UM is not correct. Do you have restarted UM service once you have set to SIP secured? For a sake of try I am suggesting that you should set new UM IP gateway and it should pointing towards new Lync Server 2010. So try it and let me know whether it is making any difference in the situation.

[Aaryan2011]

Communications Server 2007 is not able to detect version of mailbox for the users who are enabled for UM. Hence whenever you are supposed to received any call from Communications Server 2007 then it has been redirected to another UM server which is having same type of dial plan. So there are chances that Exchange 2007 UM server or Exchange 2010 UM server can take call. So that particular thing might cause an issue when you are supposed to partial upgrade. why because incoming call would failed if it has been received by Exchange 2007 UM server as well as UM-enabled user's mailbox which is on Exchange 2010 Mailbox server. this particular call would failed as Exchange 2007 UM servers si not having capability to process calls for the users who have enabled UM on Exchange 2010 mailboxes. Communications Server 2007 is not able to get whether that call made by users is redirected to Exchange 2007 UM server or Exchange 2010 UM server..
In case Communications Server 2007 is making use of IP gateway then there is need of new SIP URI dial plan will for Exchange 2007 mailboxes which are enabled for UM. new SIP URI dial plan should have Exchange 2010 UM servers only. It will be help to check whether incoming calls are redirected to Exchange 2010 UM servers only.

[Badrinath]

In this particular situation I recommend that you should not change presnet servers configuration and after that simply build new email system for exchange 2010 with coexistence of Exchange 2007. TWO server box are supposed to configured with CCR hence you will not be able to change one server. if you are havin virtul server then you should configured the same as LB. if you wanted to change then it would elongate migtration procedure. You have to configure couple of mailboxes as dag. two hub/cas/um servers should work as arrary. You should also have two edge servers which you can use the same as for array of edge HA. From ADUC you have to go for Problematic user properties and you have to reset settings which is available under Securty and after doing that you should try to move mailbox.