Forum Discussion
arifsohail92
Jan 09, 2019Copper Contributor
Exchange 2010 SP3 RU 17 to Exchange 2016 Enterprise CU11 Migration
Hello Good People, I am migrating from Exchange 2010 SP3 RU17 to Exchange 2016 CU 11. My setup is two Exchange 2010(MBX,HT,CA roles ) with DAG setup. I have completed all the prerequisites and ins...
arifsohail92
Jan 22, 2019Copper Contributor
Hi Asif,
Please follow this link for migration
https://practical365.com/exchange-server/migrating-exchange-server-2016/
Please follow this link for troubleshooting the issue
In my case solution is forcing outlook anywhere for outlook clients.
By default with Outlook Anywhere enabled in the environment your clients prefer RPC/TCP connections when on Fast Networks as seen below.<o:p></o:p>
The trick we use to force Outlook Anywhere to also be used internally is via Autodiscover. Using Autodiscover we can make Windows Outlook clients prefer RPC/HTTPS on both Fast and Slow networks as seen here.<o:p></o:p>
The method used to make clients always prefer HTTPS is configuring the OutlookProviderFlags option via the Set-OutlookProvider cmdlet. The following commands are executed from the Exchange 2010 Management Shell.<o:p></o:p>
Set-OutlookProvider EXPR -OutlookProviderFlags:ServerExclusiveConnect<o:p></o:p>
Set-OutlookProvider EXCH -OutlookProviderFlags:ServerExclusiveConnect<o:p></o:p>
If for any reason you need to put the configuration back to its default settings, issue the following commands and clients will no longer prefer HTTP on Fast Networks.<o:p></o:p>
Set-OutlookProvider EXPR -OutlookProviderFlags:None<o:p></o:p>
Set-OutlookProvider EXCH -OutlookProviderFlags:None
Hope it helps to others who are doing migrations.
asifjanjua88
Jan 23, 2019Copper Contributor
Hi arifsohail92 ,
Thank you so much for providing me such a valuable information. Right now only BASIC authentication is enabled of IIS Authentication Method on Exchange 2010 CAS servers. However, I am able to connect now with Exchange 2010 mailboxes after pointing the name space to Exchange 2016.
I am able to connect to Exchange 2010 mailboxes through outlook even on Local LAN after enabling the checking the option provided by you ( on fast networks, connect using http first).
However, in RPCHTTP logs I am getting following error that server is not available. I am confused now that if error is coming in logs then how outlook is connecting fine.
Question: Can I ignore the logs if outlook is connecting fine for Exchange 2010 mailboxes after pointing the name space to Exchange 2016? If not then i am not sure how outlook is connecting successfully?
Note: For security reason, I have replaced the domain name with mydomain.
"2019-01-22T07:26:07.281Z,da5e7680-86ec-4c54-9f23-3d818d1c7e8b,15,1,1591,10,,RpcHttp,webmail.mydomain.com,/rpc/rpcproxy.dll,,Basic,true,mydomain
\test.migration4,,Url~https://servervpexhc1.mydomain.local/rpc/rpcproxy.dll?
"webmail.mydomain.com:6002,MSRPC,10.80.90.11,PVEXMB01,200,,,RPC_IN_DATA,Proxy,servervpexhc1.mydomain.local,15.00.0000.000,IntraForest,RpcHttpProxyRules,,,,1073741824,,,,0,457,,0,,0,,0,0,,0,3376,0,2831,6,0,,,,,0,1,3376,0,,539,,545,3376,,?
webmail.mydomain.com:6002,,BeginRequest=2019-01-22T07:26:03.904Z;CorrelationID=<empty>;ProxyState-Run=None;FEAuth=BEVersion-
1941962752;NewConnection=10.0.0.115&0;H-BeginGetResponse=2019-01-22T07:26:04.362Z;H-OnResponseReady=2019-01-22T07:26:04.373Z;H-
EndGetResponse=2019-01-22T07:26:04.373Z;NewConnection=10.0.0.115&0;BeginGetRequestStream=2019-01-
22T07:26:04.374Z;OnRequestStreamReady=2019-01-22T07:26:04.380Z;ProxyState-Complete=ProxyRequestData;SharedCacheGuard=0;EndRequest=2019-
01-22T07:26:07.281Z;,WebExceptionStatus=ProtocolError;ResponseStatusCode=503;WebException=System.Net.WebException: The remote server
returned an error: (503) Server Unavailable. at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at
Microsoft.Exchange.HttpProxy.RpcHttpProxyRequestHandler.<>c__DisplayClass29_0.<OnValidateBackendServerCacheCompleted>b__0
();SharedCache=AMCacheRemovalFailure;StreamProxy=StreamProxy-Request-ExpectReadCallback;,,,,,CafeV1"
- arifsohail92Jan 26, 2019Copper Contributor
Hello Asif,
In my case i have ignored that error and started my migration and all users were connecting to 2016 mailbox databases.
However if you want to check the root cause of the issue, check with microsoft.
Thanks,
Arif