Excahnge 2010 to 2013 Migration - multiple mailboxes

Hello,
We are trying estimate the time it will take to migrate our users from Exchange 2010 to 2013.
I understand we can migrate them in multiple batches but how many are actually moving at one time?
So if i batch migrate 20 mailboxes, are all 20 moving consecutively, or are 5 moving and 15 queued?
Hope you can understand what I'm asking.
Thanks
Lee

Hi,
There is a limit when you move mailboxex from Exchange 2010 to Exchange 2013. You can find the limit through the following path.
In Exchange 2010 (CAS):
<Exchange Installation Path>\Program Files\Microsoft\Exchange Server\V14\Bin\MSExchangeMailboxReplication.exe.config file.
In Exchange 2013 (MBX):
<Exchange Installation Path>\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeMailboxReplication.exe.config file.
You can reset the related keys based on your requirements.
Here is a similar thread for your reference.
https://social.technet.microsoft.com/Forums/exchange/en-US/876f7ee7-d4ae-4b81-bfba-7408d76aa139/increase-simultaneous-moverequests-from-exchange-2010-to-exchange-2013?forum=exchangesvrgeneral
Hope this is helpful to you.
Best regards,
Belinda Ma
TechNet Community Support

Similar Messages

Exchange 2010 to 2013 Migration: Authentication/Proxy Settings Issue

I'm in the final stages of preparing for our Exchange 2010 to 2013 migration. I'm noticing minor authentication issues on mobile devices (android & ios) and proxy setting issues with Outlook that require user intervention. In an effort to make the migration
as smooth as possible for our internal users, I'd like to get these settings ironed out before starting the migration.
Symptoms:
Outlook - I'm aware that internal Outlook usage has changed its connection protocol from RCP/TCP to RCP/HTTP, but it appears that Outlook isn't updating its settings in the "Microsoft Exchange Proxy Settings" after a users mailbox has been migrated
from 2010 to 2013. Currently, 2010 users with Outlook 2013 have the following settings configured in Outlook's Exchange Proxy Settings:
URL to connect to my proxy server for Exchange: webmail.domain.com
Connect using SSL only: Checked
Only connect to proxy servers that have this principal name in their certificates: Unchecked
On fast networks, connect using HTTP first, then connect using TCP/IP: Unchecked
On slow networks, connect using HTTP first, then connect using TCP/IP: Checked
After migrating a user's mailbox from 2010 to 2013, the above settings remain the same in Outlook and their client disconnects from Exchange and isn't able to reconnect. After manually enabling the checkbox for "On fast networks, connect using HTTP
first, then connect using TCP/IP", Outlook clients are able to connect to Exchange via their newly migrated mailbox.
Is there a way to automatically updating these 2 proxy settings in Outlook during the migration instead of having to manually change each user's configuration in Outlook?
Android & iOS - Currently, users on Android & iOS with Exchange 2010 mailboxes have the following configuration:
domain: blank
username: their AD username
server: webmail.domain.com
After migrating a mobile users mailbox from 2010 to 2013, neither OS (Android or iOS) is able to connect due to an authentication failure. On iOS, if I manually change the domain from blank to my company's domain, authentication succeeds and their 2013 mailbox
begins to update. On Android, the option to change the domain name from null is grayed out, requiring the user to delete the Exchange profile and re-add it with the domain name intact. Is there a way to configure Exchange 2013 to not require the domain name
for mobile users in the same way that it's been working for us with Exchange 2010?
Please let me know if you require cmdlet print outs of my virtual directories to help troubleshoot the issue.

Hi,
Generally, when the user mailbox is moved from Exchange 2010 to Exchange 2013, the Autodiscover service would detect the changes and update the new configuration automatically.
Please make sure the autodiscover service in your new Exchange 2013 is configured correctly. We can create a new mailbox in Exchange 2013 and check whether the new Exchange 2013 user can setup account successfully in Outlook or not. If the new user works
fine, it indicates the autodiscover service in Exchange 2013 should be proper for internal user.
Please restart the following Exchange service to have a try:
Microsoft Exchange RPC Client Access
Microsoft Exchange Mailbox Replication
Restart IIS service by running IISReset in a Command Prompt window.
Then check whether the Outlook client can connect to Exchange 2013 or not.
As for Android & iOS issue, I suggest we can ask a question in ActiveSync forum for more suggestion:
https://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrmobility
Regards,
Winnie Liang
TechNet Community Support

Lync 2010 to 2013 Migration DB issue, central management database.

Hello ,
During Lync 2010 to 2013 migration , on my back end database for Lync 2013 I previously created there data base instances on my lync 2013 BE , (RTC,MON, ARC) THERE DIFFERENT ISTNACE using sql server enterprise 2012 .
Now I want to finish the migration by moving the central management server to the lync server 2013.
my question now I tried to create a new DB instance and I face some issue related the space on the server .
can I use any of the existing isnatce which I created before for the (RTC,MON, ARC) or can I sue the default instance which is created by default with sql 2012 server installation .to install the central management database.
do I need a spate instance ? for the new central management store on my lync server 2013
Thanks
MK

Hello
After I run the command
Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn hq-lync2013-be.MYDOMAIN -SqlInstanceName RTC.
-Then
Enable-CsTopology
-Then
Move-CsManagementServer .
And now after the move when I check the logs :
WARNING: The move completed successfully but the following additional steps are required:
Run local setup on the following computers to remove Central Management services that are no longer defined in the topology:
    - HQ-LYNC-FE-01.MYDOMAIN
WARNING: "Move-CsManagementServer" processing has completed with warnings. "2" warnings were recorded during this run.
WARNING: Detailed results can be found at
"C:\Users\MYUSER\AppData\Local\Temp\2\Move-CsManagementServer-0d4806f4-554d-497d-a0dc-0fc98a6e076d.html".
THESE AR ETEH TWO WARININGS :
Warning: Failed to cleanup file store for the new Central Management Server. Error The directory is not empty.
Warning: The move completed successfully but the following additional steps are required:
Run local setup on the following computers to remove Central Management services that are no longer defined in the topology:
- HQ-LYNC-FE-01.MYDOMAIN.
I Run the local setup on both the FE2013 AND FE2010.
now when I run the command :
Get-CsManagementStoreReplicationStatus
UpToDate           : False    (I shutdown this server )
ReplicaFqdn        : HQ-EDGE01.mydomain
LastStatusReport   :
LastUpdateCreation : 3/16/2015 1:52:45 PM
ProductVersion     :
UpToDate           : False
ReplicaFqdn        : HQ-LYNC2013-FE.mydomain
LastStatusReport   :
LastUpdateCreation : 3/16/2015 1:52:45 PM
ProductVersion     :
UpToDate           : False
ReplicaFqdn        : HQ-LYNC-FE-01.mydomain
LastStatusReport   :
LastUpdateCreation : 3/16/2015 1:52:45 PM
ProductVersion     :
UpToDate           : False
ReplicaFqdn        : HQ-LYNC-MA-01.mydomain
LastStatusReport   :
LastUpdateCreation : 3/16/2015 1:52:45 PM
ProductVersion     :
NOW THEER IS REPLICATION ISSUE ?
I notice that service on my lync 2010 SOME OF THEM ARE STOPPED :
FILE TRANSFER AGENT , MASTER REPLICATORE AGENT , CALL PARK SERVICE (ALL ON LYNC 2010)
ALL SERVICE ON 2013 FE IS OK AND RUNNING..
I notice this error in my lync server 2013 vents .
I host the shared file on my lync server 2010 mediation server
Microsoft Lync Server 2013, Master Replicator Agent service encountered an error while accessing a file share and will continuously attempt to access this file share until this issue is resolved. While this condition persists, replication to replica machines
might not occur.
IO failure occurred for Path=\\HQ-LYNC-MA-01.mydomain\LYNCSHARE\1-CentralMgmt-1\CMSFileStore\xds-master\working\replication\tmp. Exception=Access to the path '\\HQ-LYNC-MA-01.mydomain\LYNCSHARE\1-CentralMgmt-1' is denied..
Cause: Possible issues with file share permissions. This can occur if the computer hosting the file share has outdated cached credentials for the computer that is trying to access the file share.
Resolution:
For details about how to resolve file share permission issues, see the product documentation.
SO ANY ADVICE ?
Regards
MK

Exchange 2010 to 2013 migration: Mailbox move requests are journaled.

Hello,
I've installed Exchange 2013 into Exchange 2010 infrastructure
[ single Exchange 2010 server; single AD site; AD = 2003 ],
Exchange 2010 has 2 databases:
1. Database with users mailboxes;    Journaling YES: Journal account.
2. Database with 1 mailbox for Journal user mentioned above:     Journaling NO.
Exchange 2013 has 1 database:
1. Database with moved users mailboxes;    Journaling YES: Journal account.
I saw that when I move mailbox from 2010 to 2013 then Journal Database INCREASES about size of MOVED MAILBOX !
I logged into Journal mailbox by OWA and didn't see any duplicate messages concerned with this mailbox user...
I'd like:
* to understand technically what happened,
* to avoid unnecessary growth of Journal Database.
I'd like not to switch off journaling for all users during mailbox move.
best regards Janusz Such

Hello Winnie,
your understanding is not correct:
I move mailboxes from first DATABASE which is journaled;
second database is dedicated solely for Journal user's mailbox and is not touched now.
Thank you for PS commands; I'll use them...
best regards Janusz Such
Hi Janusz,
Sorry for my delay. In your original posting, "I saw that when I move mailbox from 2010 to 2013 then Journal Database INCREASES about size of MOVED MAILBOX !"
My understanding is that when you move mailbox from Exchange 2010 Database 1 to Exchange 2013 database, the journal mailbox in Exchange 2010 Database 2 is incleased. Is it right?
Generally, the mailbox move would not be journaled unless there is any new email bening sent to the mailbox during the migration. Please run the commands in my original posting to check the statistics about it, and refer to Ed Crowdly's suggestion to use
Journal rule instead of database journal as a workaround.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2010 to 2013 Migration Question

Hi Folks,
This is where I'm at: We have 2 Exchange 2010 servers (both multi role) and I was given 4 VM's for exchange 2013. I just completed installing Exchange on the four 2013 VM's (2 dedicated CAS and 2 dedicated MBX) and applied SP1. I documented all
of the 2010 server config info (i.e. all the URL's for the namespaces, etc). We have a hardware NLB and a MacAfee host in the DMZ where all inbound/outbound email routes to check for AV/Spam. My question is, what are my next steps that
take place so that I'm truly in co-existence mode? I'm assuming I want to make the 2013 servers primary now so that all mail routes to/from them and all client connections are made to them? Could someone point me in the right direction maybe
to an article on what my next steps are? I want to get everything cut over while in co-existence so that I can start moving mailboxes. Thanks a lot !

Exchange Server Deployment Assistant is good starting point:
http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2284-W-AAAAAAAAQAAAAAEAAAAAAA%7e%7e
Upgrade from Exchange 2010 to Exchange 2013:
http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
http://msexchangeguru.com/2013/05/10/exchange2013-migration/
http://www.petenetlive.com/KB/Article/0000788.htm
Below is high level migration plan:
1. Update active directory schema for exchange 2010 sp3.
2. Install Exchange 2010 SP3 and rollup updates on existing servers.
3. Update active directory schema for exchange 2013 CU3.
4. Install and configure new Exchange 2013 CU3 servers.
5. Install public SSL Certificate.
6. Configure Web URL's for Exchange 2013 servers.
7. Configuration Hardware Load Balancer for:
a) High availability of Client Access roles.
b) Reverse Proxy for outlook web app.
8. Create mailbox databases and configure database copies for the corresponding DAG.
9. Test High Availability environment.
10. Test mail flow to & from internet/internally for all locations.
11. Test BlackBerry device connectivity with Exchange 2013 environment (if nay)
12. Test migrate mailbox from Exchange 2010 to Exchange 2013.
13. Test Outlook & OWA connectivity for migrated test mailbox.
14. Validate new Exchange 2013 environment.
15. Pilot mailboxes migration from Exchange 2010 to Exchange 2013.
16. Migrate mailboxes from Exchange 2010 to Exchange 2013.
17. Migrate Public Folders from Exchange 2010 to Exchange 2013
18. Dismount & stop Exchange 2010 services on all servers for few days before decommissioning of Exchange 2010 servers.
19. Decommission Exchange 2010 servers gracefully.
If this will help then please mark it as answer...thanks
Best of luck!
Liaqat

Issue sending bulk email after Exchange 2010 to 2013 migration

Hi!
I have an issue with some reporting software sending bulk emails after our Exchange 2013 migration.
I can see the connections in the firewall and I can see the first connections under the protocol logs in the Exchange servers. What happens is that after ~10 emails, within the same amount of seconds from what I can tell, the mail flow just stops to the
Exchange server. I cant seem to find an error message anywhere within the Exchange logs and I've tried updating the receive connector with higher timeouts / Connection limits but the users still cant send all the invoices etc right away.
We have multiple applications / receive connectors with this issue and the users did not report any issues with Exchange 2010 so I am assuming that this issue did not exist there.
We're running two multi-role (CAS/MB) Exchange 2013 servers in a DAG. Exchange 2010 is not fully decommissioned yet but all links and users are moved to 2013.
Any help is much appreciated!

Hi ,
To avoid the issues when relaying the emails from application server through exchange then we need concentrate on the below mentioned parameters on the receive connectors in exchange 2013 cas servers and also we need to set the parameter value as per your
environment requirement.
Please check the below mentioned values on the dedicated receive connectors in exchange 2013 cas server to relay emails from the application server
Parameters :
ConnectionInactivityTimeout
ConnectionTimeout
MaxInboundConnection
MaxInboundConnectionPercentagePerSource
MaxInboundConnectionPerSource
MaxRecipientsPerMessage
MessageRateLimit
Note : In case if none of the above changes help you then the final option would be to enable the protocol logging on the receive connector utilized by the application server to relay emails via exchange server and with the help of the logs we can can came
to know that why the connections from the application server to exchange server is disconnecting after some emails has send.
Thanks & Regards S.Nithyanandham
Here are the relevant values for the receive connector, doublechecked and it's the same on both DAG members;
ConnectionTimeout : 00:20:00
ConnectionInactivityTimeout : 00:05:00
MaxInboundConnection : 5000
MaxInboundConnectionPerSource : Unlimited
MaxInboundConnectionPercentagePerSource : 100
MaxRecipientsPerMessage : 200
MessageRateLimit
: Unlimited
Adding logs for one big connection spike from the customer. About 50 inbound connections to the Exchange servers .
SMTP Receive;
2015-01-26T18:02:46.991Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,0,DAG member 01:587,Customer IP:60262,+,,
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,1,DAG member 01:587,Customer IP:60262,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,2,DAG member 01:587,Customer IP:60262,>,"220 DAG member 01 Microsoft ESMTP MAIL Service ready at Mon, 26 Jan 2015 19:02:46 +0100",
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,3,DAG member 01:587,Customer IP:60262,<,EHLO customerdomain.com,
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,4,DAG member 01:587,Customer IP:60262,>,250-DAG member 01 Hello [Customer IP],
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,5,DAG member 01:587,Customer IP:60262,>,250-SIZE 36700160,
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,6,DAG member 01:587,Customer IP:60262,>,250-PIPELINING,
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,7,DAG member 01:587,Customer IP:60262,>,250-DSN,
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,8,DAG member 01:587,Customer IP:60262,>,250-ENHANCEDSTATUSCODES,
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,9,DAG member 01:587,Customer IP:60262,>,250-STARTTLS,
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,10,DAG member 01:587,Customer IP:60262,>,250-AUTH LOGIN,
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,11,DAG member 01:587,Customer IP:60262,>,250-8BITMIME,
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,12,DAG member 01:587,Customer IP:60262,>,250-BINARYMIME,
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,13,DAG member 01:587,Customer IP:60262,>,250 CHUNKING,
2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,14,DAG member 01:587,Customer IP:60262,<,STARTTLS,
2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,15,DAG member 01:587,Customer IP:60262,>,220 2.0.0 SMTP server ready,
2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,16,DAG member 01:587,Customer IP:60262,*,,Sending certificate
2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,17,DAG member 01:587,Customer IP:60262,*,CN=server,Certificate subject
2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,18,DAG member 01:587,Customer IP:60262,*,CN=server,Certificate issuer name
2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,21,DAG member 01:587,Customer IP:60262,*,server;DAG member 01,Certificate alternate names
2015-01-26T18:02:47.053Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,22,DAG member 01:587,Customer IP:60262,*,,TLS negotiation succeeded
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,23,DAG member 01:587,Customer IP:60262,<,EHLO customerdomain.com,
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,24,DAG member 01:587,Customer IP:60262,*,,Client certificate chain validation status: 'EmptyCertificate'
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,25,DAG member 01:587,Customer IP:60262,*,,TlsDomainCapabilities='None'; Status='NoRemoteCertificate'
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,26,DAG member 01:587,Customer IP:60262,>,250-DAG member 01 Hello [Customer IP],
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,27,DAG member 01:587,Customer IP:60262,>,250-SIZE 36700160,
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,28,DAG member 01:587,Customer IP:60262,>,250-PIPELINING,
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,29,DAG member 01:587,Customer IP:60262,>,250-DSN,
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,30,DAG member 01:587,Customer IP:60262,>,250-ENHANCEDSTATUSCODES,
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,31,DAG member 01:587,Customer IP:60262,>,250-AUTH LOGIN,
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,32,DAG member 01:587,Customer IP:60262,>,250-8BITMIME,
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,33,DAG member 01:587,Customer IP:60262,>,250-BINARYMIME,
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,34,DAG member 01:587,Customer IP:60262,>,250 CHUNKING,
2015-01-26T18:02:47.085Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,35,DAG member 01:587,Customer IP:60262,<,AUTH LOGIN,
2015-01-26T18:02:47.085Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,36,DAG member 01:587,Customer IP:60262,>,334 <authentication response>,
2015-01-26T18:02:47.100Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,37,DAG member 01:587,Customer IP:60262,>,334 <authentication response>,
2015-01-26T18:02:47.131Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,38,DAG member 01:587,Customer IP:60262,*,SMTPSubmit SMTPAcceptAnyRecCustomer IPient BypassAntiSpam AcceptRoutingHeaders,Set Session Permissions
2015-01-26T18:02:47.147Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,39,DAG member 01:587,Customer IP:60262,*,[email protected],authenticated
2015-01-26T18:02:47.272Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,40,DAG member 01:587,Customer IP:60262,*,,Proxy session was successfully set up. Session [email protected] will now be proxied
2015-01-26T18:02:47.272Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,41,DAG member 01:587,Customer IP:60262,>,235 2.7.0 Authentication successful,
2015-01-26T18:02:47.819Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,42,DAG member 01:587,Customer IP:60262,-,,Local
SMTP Send
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,0,,DAG member 02:465,*,,attempting to connect. Client proxy session for [email protected]
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,1,DAG member 01:57446,DAG member 02:465,+,,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,2,DAG member 01:57446,DAG member 02:465,<,"220 DAG member 02 Microsoft ESMTP MAIL Service ready at Mon, 26 Jan 2015 19:02:46 +0100",
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,3,DAG member 01:57446,DAG member 02:465,>,EHLO DAG member 01,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,4,DAG member 01:57446,DAG member 02:465,<,250-DAG member 02 Hello [DAG member 01],
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,5,DAG member 01:57446,DAG member 02:465,<,250-SIZE 36700160,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,6,DAG member 01:57446,DAG member 02:465,<,250-PIPELINING,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,7,DAG member 01:57446,DAG member 02:465,<,250-DSN,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,8,DAG member 01:57446,DAG member 02:465,<,250-ENHANCEDSTATUSCODES,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,9,DAG member 01:57446,DAG member 02:465,<,250-STARTTLS,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,10,DAG member 01:57446,DAG member 02:465,<,250-X-ANONYMOUSTLS,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,11,DAG member 01:57446,DAG member 02:465,<,250-AUTH GSSAPI NTLM,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,12,DAG member 01:57446,DAG member 02:465,<,250-X-EXPS GSSAPI NTLM,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,13,DAG member 01:57446,DAG member 02:465,<,250-8BITMIME,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,14,DAG member 01:57446,DAG member 02:465,<,250-BINARYMIME,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,15,DAG member 01:57446,DAG member 02:465,<,250-CHUNKING,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,16,DAG member 01:57446,DAG member 02:465,<,250-XEXCH50,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,17,DAG member 01:57446,DAG member 02:465,<,250-XRDST,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,18,DAG member 01:57446,DAG member 02:465,<,250 XSHADOWREQUEST,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,19,DAG member 01:57446,DAG member 02:465,>,X-ANONYMOUSTLS,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,20,DAG member 01:57446,DAG member 02:465,<,220 2.0.0 SMTP server ready,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,21,DAG member 01:57446,DAG member 02:465,*,,Received certificate
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,23,DAG member 01:57446,DAG member 02:465,*,,Proxy target certificate
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,24,DAG member 01:57446,DAG member 02:465,*,"CN=*.email.com, OU=IT, O=X, L=X, S=X, C=SE",Certificate subject
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,25,DAG member 01:57446,DAG member 02:465,*,"CN=DigiCert High Assurance CA-3, OU=www.digicert.com, O=DigiCert Inc, C=US",Certificate issuer name
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,28,DAG member 01:57446,DAG member 02:465,*,*.email.com;email.com,Certificate alternate names
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,29,DAG member 01:57446,DAG member 02:465,>,EHLO DAG member 01,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,30,DAG member 01:57446,DAG member 02:465,<,250-DAG member 02 Hello [DAG member 01],
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,31,DAG member 01:57446,DAG member 02:465,<,250-SIZE 36700160,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,32,DAG member 01:57446,DAG member 02:465,<,250-PIPELINING,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,33,DAG member 01:57446,DAG member 02:465,<,250-DSN,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,34,DAG member 01:57446,DAG member 02:465,<,250-ENHANCEDSTATUSCODES,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,35,DAG member 01:57446,DAG member 02:465,<,250-AUTH GSSAPI NTLM LOGIN,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,36,DAG member 01:57446,DAG member 02:465,<,250-X-EXPS EXCHANGEAUTH GSSAPI NTLM,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,37,DAG member 01:57446,DAG member 02:465,<,250-X-EXCHANGEAUTH SHA256,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,38,DAG member 01:57446,DAG member 02:465,<,250-8BITMIME,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,39,DAG member 01:57446,DAG member 02:465,<,250-BINARYMIME,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,40,DAG member 01:57446,DAG member 02:465,<,250-CHUNKING,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,41,DAG member 01:57446,DAG member 02:465,<,250-XEXCH50,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,42,DAG member 01:57446,DAG member 02:465,<,250-XRDST,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,43,DAG member 01:57446,DAG member 02:465,<,250-XSHADOWREQUEST,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,44,DAG member 01:57446,DAG member 02:465,<,250-XPROXY,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,45,DAG member 01:57446,DAG member 02:465,<,250-XPROXYFROM,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,46,DAG member 01:57446,DAG member 02:465,<,250-X-MESSAGECONTEXT ADRC-2.1.0.0 EPROP-1.2.0.0,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,47,DAG member 01:57446,DAG member 02:465,<,250 XSYSPROBE,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,48,DAG member 01:57446,DAG member 02:465,>,X-EXPS EXCHANGEAUTH SHA256 ,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,49,DAG member 01:57446,DAG member 02:465,>,<Binary Data>,
2015-01-26T18:02:47.272Z,Client Proxy Send Connector,08D2051B7AE3DA8F,50,DAG member 01:57446,DAG member 02:465,<,235 <authentication information>,
2015-01-26T18:02:47.272Z,Client Proxy Send Connector,08D2051B7AE3DA8F,51,DAG member 01:57446,DAG member 02:465,>,XPROXY SID=08D2051B7AE3DA8E IP=Customer IP PORT=60262 DOMAIN=customerdomain.com CAPABILITIES=0
2015-01-26T18:02:47.272Z,Client Proxy Send Connector,08D2051B7AE3DA8F,52,DAG member 01:57446,DAG member 02:465,<,250 XProxy accepted and authenticated,
2015-01-26T18:02:47.272Z,Client Proxy Send Connector,08D2051B7AE3DA8F,53,DAG member 01:57446,DAG member 02:465,*,,Proxy session successfully set up for [email protected]. Inbound session will now be blindly proxied
2015-01-26T18:02:47.819Z,Client Proxy Send Connector,08D2051B7AE3DA8F,54,DAG member 01:57446,DAG member 02:465,-,,Remote
Nothing after these logs indicating any type of issue with the receive connector. Tried to make the logs as anonymous as possible. Hope they still make sense.
Note; Database was active on DAG member 02 but all incoming traffic on port 587 was directed to DAG member 01.

2010 to 2013 migration. Can't connect OWA to 2013 server unless 2010 server is on line

I am migrating an SBS 2011 Exchange server (2010) to Exchange 2013 on a W2012 Server (not a DC). I completed the install and moved one user's mailbox to the 2013 server. All users can process their email via OWA and Outlook. But, if the SBS 2011 server is
disconnected, the migrated user cannot log on via OWA and I can't log in to administrator ecp. They just time out. I know the mailbox is migrated because if I disconnect the 2013 server and OWA into the SBS 2011 server it gets an error saying the mailbox server
is unavailable. I must have missed a step in the migration. Can someone please point me at some documentation for completing the migration.
Thank,
Lou
Louyo

Hi,
Please have a look in the similar threads.
https://social.technet.microsoft.com/Forums/office/en-US/5990037a-8b3f-4abe-8589-22032171adc6/exchange-2013-2013-coexistence-owa-rendering-on-2010-cas-for-2013-mailbox?forum=exchangesvrclients
https://social.technet.microsoft.com/Forums/office/en-US/bc8628e6-a0c5-4fd8-95c1-36ee5a644847/owa-still-lands-at-exchange-2010-for-users-migrated-from-exchange-2010-to-2013?forum=exchangesvrclients
https://support2.microsoft.com/kb/2931385?wa=wsignin1.0
Note : Just ensure the active directory replication is working properly in your exchange environment .
Regards
S.Nithyanandham
Thanks & Regards S.Nithyanandham

Exchange 2010 to 2013 Migration- orphaned 2010 servers in Edge subscription

Migration of Exchange 2010 to 2013 was carried out. Steps to decommission the 2010 servers was done, including removing the Exchange software fro the servers. Looks like some pieces were missed though as the 2010 servers still appear in the smarthostdelivery
and shadow redundancy on the 2010 edge transport server.
How can these be removed?

Hi,
I recommend you can use the following script to cleanup the queue:
Cleanup Shadow Redundancy Queues
Performs a search per server per shadow redundancy queue. If shadow redundancy queues contain
at least 1 message the receive date is inspected. If it is more then 1 day ago it will cleanup
the message.
Normally you do not have to cleanup the shadow redundancy queues because messages will automatically
expire, how long this takes depends on your config but normally 2 days.
However in some scenarios it might be necessary to clean the queues.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Need clarification on DNS, Certificate and URL? during 2010 to 2013 migration

Hi Guys,
I am working on a migration project Lync server 2010 to 2013.
Lync 2010 Standard Edition and Edge
Lync 2013 Ent edition and Edge (Enterprise Voice "SIP Trunk")
I need few clarification on How to setup the DNS, Certificate and URL Pre and post migration?
Shall we use the Lync 2010 existing internal and external URLs to lync 2013 or do we need to setup a new URLs for lync 2013?
How about the DNS records and Certificates?
I have gone trough the below blogs but need clear understanding on this part..
http://lyncdude.com/2013/08/11/understanding-lync-dns-records-and-autoconfiguration/
https://technet.microsoft.com/en-us/library/hh690044.aspx
and few more....
Thanks,
Balakrishna G
Regards, Balgates

Hi,
Agree with Thamara.Wijesinghe.
You need to different Web service URL for Lync Server 2010 and Lync Server 2013. If you only have Web service URL for Lync Server 2010, then Lync 2013 mobile will fail to connect to FE Server. If you point Web service URL point to Lync Server 2013 Pool,
then both Lync 2010 and 2013 mobile clients will connect to FE Server successfully.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Infopath forms 2010 to 2013 migration issue

I need to migrate InfoPath forms 2010 to SP 2013. Now in 2010 InfoPath forms are connected to data connection library & having classic authentication. Since SP 2013 doesn't support classic authentication what are the issues should come to handle? What
should be correct strategy & steps for this migration?

Hi Sunil
Sharepoint 2013 will support the Classic mode authintication but while creating any new webapplication using sharepoint central administration you can only used claim based authintication
Check the below link for step by step approcah about infopath
http://technet.microsoft.com/en-in/library/cc262263(v=office.14).aspx
You can alos check this link
Claims-based authentication is an essential component to enable the advanced functionality of SharePoint 2013. To move classic-mode web applications from SharePoint 2010 Products to SharePoint 2013, you can convert them to claims-based web applications within
SharePoint 2010 Products, and then migrate them to SharePoint 2013. The procedures in this article illustrate various supported scenarios.
The Windows PowerShell Convert-SPWebApplication cmdlet in SharePoint 2013 converts classic-mode web applications to claims-based web applications.
http://technet.microsoft.com/en-us/library/gg251985(v=office.15).aspx
http://blogs.technet.com/b/rajbugga/archive/2013/08/07/infopath-over-claims-authentication-sharepoint-2010-amp-2013.aspx
Please mark the Answer and Vote me if you think that it will you to resolved your issue
did you missed to give any link here:
"You can alos check this link" ?
Also, Can you plz tell how to manage data connections in case of infopath migration?
Your answer is overall good.

Lync 2010 to 2013 migration - Moving the conferencing directory ?

I am in the process of finishing our migration from Lync 2010 to 2013.
Reading the technet page, I don't see any mention to migrate the Lync 2010 Conferencing Directory to 2013.
http://technet.microsoft.com/en-us/library/jj204998.aspx
But doing some quick research, I see that some blog are suggesting of doing it:
http://www.oiboran.com/?p=1219
All my users have already been migrate to the Lync 2013 Pool. No problem so far.
But I am still wondering if the Lync 2010 conferencing should be move or not?
thanks
John

In step 7,
http://technet.microsoft.com/en-us/library/jj688011.aspx
The following user account information does not move to the new server.
Meeting content. In order to move the content shared during a meeting, for example PowerPoint, Whiteboard, attachments or poll data, use the
-MoveConferenceData parameter as part of the Move-CsUser cmdlet.
====
Did you move users with the GUI or with move-csuser -MoveConferenceData?
If you moved with the GUI, the conference data noted above isn't moved. If you think your users would care about this, you could move the directory to 2013 and forget about it. Otherwise, you could just remove it as you decommission the 2010
pool. It's rare that people would care about this data.
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".
SWC Unified Communications

2010 to 2013 migration problem with service application

With a 3rd party migrator we are able to migrate a simple 2010 site to 2013. By simple UI level approach sites are migrated easily. But we have a large project where we have good amount of work done on various service applications.
We are facing problem to migrate entire 2nd SP2010 application with service applications. Do any one has idea of smooth migration of large service applications to 2013 with avepoint or quest tools?
If faced same problem then share steps.

The Microsoft guidance for upgrading a SP2010 farm to SP2013 is in the link below. Most of your existing SharePoint out of the box service applications can be upgraded also. This includes User Profile Service Application and the Search Service Application.
Custom service applications most likely not upgradeable. Hopefully the guidance was followed so there should be no problems.
http://technet.microsoft.com/en-us/library/cc262483(v=office.15).aspx
Blog | SharePoint Field Notes Dev Tools |
SPFastDeploy | SPRemoteAPIExplorer

2010 to 2013 Migration causes extra h1 tag in Web Parts

I have completed an upgrade from SharePoint 2010 to SharePoint 2013 and noticed my Web Parts have an extra large font, using the F12 Key I noticed an extra <h1> tag surrounding the entire web part. If I go to add a new web part the <h1> tag does
not show, only on the migrated web parts, I have also added the site to compatibility mode since we are using IE11. Can anyone assist?

HI,As I assume the issue is with IE11 only,IE11 is having some compatible issues with the sharepoint.Please check with the other IE versions and firefox,chrome aswell to confirm the issue is not with the IE.please check the link below that explains the know
issues with the IE11.
http://expertsharepoint.blogspot.de/2014/08/issues-with-sharepoint-2013-and.html
Anil Avula[Partner,MCP,MCSE,MCSA,MCTS,MCITP,MCSM] See Me At: http://expertsharepoint.blogspot.de/

Lync 2010 to 2013 Migration (Standard) - Can't Move CMS

New virtual machine has Lync 2013 Standard installed. I've selected "Prepare first Standard Edition server" and launched the Lync Powershell, entered enable-cstopology, then move-csmanagementserver. It fails with the error "The New CMS located
at X.domain.com\rtc" is not accessible. -FullyQualifiedErrorId: Move not supported.,Microsoft.Rtc.Management.Deployment.MoveCms.Movecmscmdlet".
I've seen several commands to try while Googling, but unsure of which one to try:
Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn t-sql03.wesselius.local –SqlInstance –clean
Install-CsDatabase -CentralManagementDatabase -sqlserverfqdn server.fqdn.local -sqlinstancename rtc -clean
Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn sql.domain.local -SqlInstanceName INSTANCE -clean
If I download my current topology, expand Shared Components and then SQL Server Stores I see:
-servername.domain.com\rtc (lync 2010 FE server)
-servername2013.domain.com\rtc (lync 2013 FE server)

On the Lync 2013 vm I've been through all of the "prepare ad" steps, all of the "install or update lync server system" steps, "prepare first SE server", etc. So if I download my current topology, you can see my 2013 lync server
if you expand down to Lync server - OrgName - Lync Server 2013 - Standard Edition FE Servers.
All services are started.
I cannot move users to the pool due to what I have mentioned above. My CMS is still 2010/located on my 2010 server which is coexisting until the migration is complete. You cannot migrate a user to the 2013 pool from the 2010 CMS console.
I am running the command on the 2013 server.
Edit: I guess this link would show about where I am: http://technet.microsoft.com/en-us/library/jj205420.aspx
The difference is my 2013 CMS link doesn't work, I just get a "403 - Forbidden. Access is denied" error. If I launch my 2010 CMS link and go to the topology tab, I can see my 2013 lync server and the replication status is good.

Namespace for Exchange 2003 == 2010 == 2013 Migration

Hi
Hope someone can help. I am working on an Exchange 2003 to 2010 migration, which will then quickly move onto a 2010 to 2013 migration and need some clarification on the namespaces to use. I am aware that if I do not do this right at the 2003
to 2010 migration, this will cause a headache at the 2010 to 2013 migration.
Some background:
2003 Functional Level Domain - 2 x 2008 DC's
Currently users are on a 2003 exchange cluster with a mix of RPC (internal users) and RPC over HTTP connections (roaming users)
We will be installing Exchange 2010 on a single server, with CAS, HUB and Mailbox roles and no load balancer, as we will be moving quickly to 2013.
We have two Kemp load balancers ready for Exchange 2013.
Exchange 2010 is installed on a single server (exh2010.domain.local) and configured with an CAS array name (exh-cas.domain.local) which is resolvable internally only.
Currently we have multiple smtp namespaces e.g. @company.com, @company2.com.
Our main website etc is www.company.com
Our public facing services are at https://service.mycompany.com
Our 2003 RPC address is https://webmail.mycompany.com
I understand that the 2010 RPC CAS array name should be separated from the Outlook Anywhere (RPC over HTTPS) address so that when 2013 takes over the HTTPS address, the RPC connections are not broken.
Two Questions:
Do we have to use the HTTPS same namespace for 2013 as we do in 2010? Its just I would want to test the Kemp load balancers before making them live (slow careful transition), and giving them a different namespace, e.g.
https://mail.mycompany.com would allow a migration, rather then a cutover.
Can we use the *.mycompany.com address rather then the company.com address, even though we have no SMTP addresses at mycompany.com? Can autodiscover still work?
Thanks in advance for any guidance
Cheers
Steve

1. No, but you can. Exchange 2013 will proxy all services for Exchange 2010, so if you set up everything right, you should be able to simply swing the name from Exchange 2010 to 2013.
2. Your web services can be published with any domain as long as the hostname is in the certificate. Only Autodiscover needs to match the e-mail domain(s). So in your example, you could publish OWA, ECP, ActiveSync, Web Services and OAB
at owa.mycompany.com. You would need autodiscover.company.com, autodiscover.company2.com, etc., but if you don't have e-mail addresses with mycompany.com, you don't need autodiscover.mycompany.com. If all users have a company.com e-mail address,
the you only need autodiscover.company.com as long as users know to enter that e-mail address when configuring profiles on PCs or devices. If you're going to have to have Autodiscover for multiple domains, then you might consider using an SRV record
instead because it can greatly simplify your certificate requirements.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Excahnge 2010 to 2013 Migration - multiple mailboxes

Similar Messages

Maybe you are looking for