Outlook clients cannot connect Exchange 2013 cutover from 2010

Hello,
My company has been running an Exchange 2013/2010 coexistence. Currently, Exch 2013 (2mbx and 1 CAS) utilizes "mail2.domain.com" for the name space. Exch 2010 (1MBX 1 CAS) uses "mail.domain.com"
We recently attempted to cutover external and internal DNS to point "mail.domain.com" and "autodiscover.domain.com" to the Exch 2013 server.
We changed all virtual directories on 2013 to use "https://mail.domain.com/owa" (ECP, EWS, etc. were changed too) for the internal and external URL. The Exch 2010 virtual directories internal URL are set to "https://internalFQDN.domain.com/owa"
the external URLs are $null
Both CAS servers were setup to use Outlook Anywhere since this is how 2013 proxies to 2010. The internal URLs for both were set to "mail.domain.com" IIS authentication Methods (Basic, NTLM). ClientAuthenicsationMethod: NTLM.
For both servers the autodiscoverserviceinternaluri was set to: https://autodiscover.domain.com/autodiscover/autodiscover.xml
The 2013 server has two SSL certificates installed. One is a wildcard cert for "*.domain.com" and the other includes our SANs (mail.domain.com, mail2.domain.com, webmail.domain.com, autodiscover.domain.com) it also includes the FQDN for the 2010
and 2013 CAS servers.
I'm speaking in the past tense because we had to roll back. The problem was no Outlook user could connect. This goes for mailboxes hosted on the Exchange 2013 and 2010 servers. The error was: "Cannot
open your default e-mail folder" to "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete".
Everything else worked fine during the cutover. OWA 2013 login page proxied 2010 logins properly, Outlook 2011 could connect with EWS fine, Active-Sync worked without issues too.
It was only the Outlook 2010 and 2013 clients that could not connect.
We rolled back and everything is working as it was before with the separate namespace. That leads me to think it's something with Outlook Anywhere (RPC/HTTPS)
but the settings seem correct unless I'm missing something. Any help is appreciated.
Thanks!

Hard to say. I've had to change the router to point to the old server as mail wasnt getting in. But OWA did seem ok, although I couldn't send messages... I could only see the inbox and contacts etc.

Similar Messages

Exchange 2013 upgrade from 2010 and no mail flow and cannot move mailboxes

I am in the process of moving to Ex 2013 from 2010. I have installed Ex 2013 SP1 on a new server 2012 R2. All of my Ex 2010 servers are SP3 RU 5. Ex 2013 is running and I can connect through the EAC and see all other Exchange servers and connectors that
were already in existence. Several puzzling things are happening now that the servers are in coexistence:
1) As soon as Ex 2013 was installed on the network, many Outlook users are continuously being prompted to enter their domain credentials. They can cancel the prompt and Outlook still sends/receives email. No user mailboxes are on Ex 2013 yet.
Why is this happening?
2) I am following the Ex 2013 Deployment Assistant and I get to the step to move the Ex 2010 Arbitration mailbox to Ex 2013 and the move does not happen--it just says "syncing" and never completes. I tried moving a test mailbox from Ex 2010
to the 2013 database and I get the same result. I created the move request on the Ex2013 server and I see it as queued on the Ex2010 server, so I know they are "talking" to each other. However, when reviewing the status of the move I
see "MapiExceptionNoAccess: Unable to open message store".
3) There seems to be no mail flow on the same Ex2013 server or between the Ex 2010 and 2013 servers. I created two new test user mailboxes in Ex 2013. The Ex2013 mailboxes cannot send/receive to each other or to Ex 2010 users. This
seems strange, unless I am completely missing something in the Ex 2013 install?
I know this is a lot in one post, but following the Deployment assistant, I was hoping this would be something that others have faced. Thanks for any input here.

Does the below points already fit for you.
Exchange 2013 Supported with the following minimum versions of Exchange:
1) Exchange*** 2010 SP3 on all Exchange 2010 servers in the organization, including Edge Transport servers.
2) Exchange 2013 CU2 or later on all Exchange 2013 servers in the organization.
*** If you want to create an EdgeSync Subscription between an Exchange 2010 Hub Transport server and an Exchange 2013 SP1 Edge Transport
server, you need to install Exchange 2010 SP3 Update Rollup 5 or later on the Exchange 2010 Hub Transport server.
Thanks Prem P Rana MCSA Messaging 2003 MCSE 2003 Server MCTS MCITP Exchange 2007, 2010 Gurgaon, India http://blogs.msexchange-experts.com

Exchange 2013 Migration from 2010 Test (Shared split DNS)

Hi
Im testing a migration from Exchange 2010 to 2013. I have tried to run a single DNS name to both servers, so externally mail.test.com resolves to the external IP and that NAT's to the new Exchange 2013. Then internally mail.test.com resolves both to EXC13
and EXC10 ip adresses (Round Robin).
I have moved some mailboxes to 2013. If the IP resolves to the new Exchange and i try to login to a mailbox on the old server i get redirected as im supposed to. If the IP resolves to the old Exchange and i try to login with a mailbox on the new server i
get:
A server configuration change is temporarily preventing access to your account. Please close all Web browser windows and try again in a few minutes. If the problem continues, contact your helpdesk.
Should this be possible, or do i need to change the intarnal URL on all virtual directories on the old server to the local netbios name or what to do?

You should never use the server name in any of the URLs. You should use either a CNAME or a load-balanced VIP with a generic name like mail.company.com or webmail.company.com. Then you just point this name to the new server. If
you're currently using a server name, it's about time to change that first before trying to switch to Exchange 2013.
Curently im using a generic name, mail.test.com. But that's just a normal A record on the internal DNS. So i cannot use that on both?

Exchange 2013 transition from 2010

I have installed a single 2013 CAS server and a single 2013 MB server in my testlab. I already have a 2010 cas server, Hub Server, and mb server in the testlab. After installing 2013, and redirecting my mail to the 2013 CAS server, mail is flowing to
the 2013 MB server. In the Queue Viewer for the 2013 DB server, I see the message with the next hop being SITE:mysite; Version:14, Delivery Type is SMTP Relay to Mailbox Delivery Group; Status is Retry;
Error:
"Wednesday, June 19, 2013 12:11:19 PM" "[{LRT=6/19/2013 12:10:19 PM};{LED=451 4.4.0 Primary target IP address responded with: ""451 5.7.3 Cannot achieve Exchange Server authentication."" Attempted failover to alternate
host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was (IP of 2010 Hub:25};{FQDN=2010 Hub Server FQDN};{IP=2010 Hub Server}]"
Submission Undefined Ready 0
I am at a loss on how to correct this. Is there a jedi master out there that can help?

I know it has been a year since this thread, but I wanted to say thank you. This worked for me after many hours of troubleshooting. I thought just checking Anonymous users under the Permission Groups would work. But that isn't the case, I needed to add
"Exchange Server authentication" under the Authentication tab. I was able to telnet fine with the anonymous users, hence my hours of troubleshooting. Your post did it so THANK YOU!

Journaling mailbox - Exchange 2013 Migrations from 2010

hi guys
i am about to start mailbox movement from Exchange 2010 to 2013. my setup is working fine. i have enabled journaling from Exchange 2010 and as ii found, automatically journaling rules will be reflected to exchange 2013. i had very big journaling mailbox
and then newly created New Exchange 2010 journaling mailbox. now new journaling mailbox is configured for journaling and that also still on 2010(both Old and new journaling mailbox ), new mailx is couple of weeks old (6-8 GB) and old one is 2.6 TB. So i will
move old one at the end .
my questions is if i move new journaling mailbox to 2013 before start normal Mailboxes, it will cause some issues for journaling. i use premium journaling . is it okay to move journaling mailbox at the begin ??
thank you
Indunil

Hi,
Based on my test, journal rules will be synchronized in Exchange 2013 after you create in Exchange 2010. If you create in Exchange 2013, then the rule will be synchronized in Exchange 2010.
And I did create a rule to send message to a Exchange 2013 jounal mailbox for Exchange 2010 users. It worked.
So you can migrate journal mailbox to Exchange 2013 firstly based on this test.
Best regards,
Belinda Ma
TechNet Community Support

How to find out what server the outlook client is connected to/change it automatically

Hi,
I am performing a server migration from Exchange 2010 to Exchange 2010 (the previous installation was installed by an outsourced provider and is rubbish so I'm configuring it properly). On the of things the existing server lacks is a CAS array configured,
so I have built the new Exchange 2010 server, configured a new DB and CASArray. I have created a brand new mailbox for a new user and the user's outlook shows it is connected to casarray.domain.local, I have migrated my own mailbox but internally my outlook
shows it is connected to oldserver.domain.local (under the account settings when you go to change the settings for the account), this is on a domain joined internal desktop. But at home on my personal laptop non-domain joined, it has appeared to reflect the
new casarray.domain.local. The outlook client is 2007 in both situations.
When I run the following command, it shows my mailbox is indeed connected to the new exchange server, but this is not true in outlook
Get-LogonStatistics -Server "new-exch2010" | where {$_.clientname -eq "new-exch2010"}| ft username,servername,clientname
If I run the above command against the old server my name shows on that list as well. When I look at the connection status of my outlook it shows that it is connected to casarray for directory, but the old server for mail.
A couple of other things:
Mailflow is now going to the new exchange server from the gateway over port 25, the autodiscover record in the internal DNS is now also pointing to the new exchange server, outlook clients and users computers have been completely restarted but still don’t
seem to pick up the new settings, both the old server and new server functions as a multi-role exchange having the Hub, CAS and MBX roles.
Now that you have all that background info my question is two parts:
What is the correct powershell command I can run on the exchange server to ensure that all my outlook clients are connected to the new exchange server for all connection types (or identify those which are connected against the old server)?
How do I get the outlook clients to automatically pick up the casarray servername once their mailboxes have been migrated?
I am considering removing the CAS from the old server which may force outlook to find it’s new server but am unsure whether this will work or not, and I think I should migrate all the mailboxes into the new DB before I do this.
Other than that, I am out of ideas.
Appreciate, any help. Thanks
Steve

I had already run the command Get-MailboxDatabase | FL Identity,RpcClientAccessServer
and it only identified the old database as being tied to the server name, the new database has the correct casarray and all mailboxes are in this new database. should I also set the old database to point to my casarray as the second command indicates? can't
do any harm right?
also, I have outlook 2007 and 2013 at home and both of them had automatically reconfigured
themselves to point to casarray, my problem is with the internal clients.
today I have also noticed in DNS there is a Zone which points to autodiscover.domain.co.uk
and in there it points to my old server.
a few things to note about the above:
1. the zone is pointing to the .co.uk domain not the .local - is this correct?
2. should that zone even be in our internal DNS, i hadn't noticed on previous implementation
of Exchange I have done
3. if i change the record within that zone to point to my new server, will this likely show
up the popup message shown in this link http://www.rackspace.com/apps/support/portal/1218 I havent yet got a certificate for the new exchange server (few more days) and i dont want users seeing any kind of untrusted unsecure connection box or it
will only lead to panic and flooding the helpdesk
many thanks
Steve

After install KB2889927 Outlook client cannot load Offline address book.

After install KB2889927 Outlook client cannot load Offline address book. Client says: Offline address book Connecting to Microsoft Exchange, and does nothing.
After Uninstall KB2889927 Outlook clent download address book successfully.
Somebody has a problem with KB2889927?
P.S. Exchange 2013 SP1 RU6

Hi,
According to your description, I noticed that the issue occurred after install KB2889927 for October 2014 Office 2013 updates.
I read the
November 2014 Office Update Release and find that the following KB can resolve the OAB download issue in Outlook 2013, please install it to have a try:
For Office 2013: http://support2.microsoft.com/kb/2899493
Or for Outlook 2013: http://support2.microsoft.com/kb/2899504
Regards,
Winnie Liang
TechNet Community Support

Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence?

Hi Team,
I am in the phase of upgrading Exchange 2010 to 2013, and introduced 4 MBX and 2 CAS of 2013 servers in co-existence.
Only one production mailbox of 2010 moved to 2013. The owa of the mailbox moved to 2013, is working OK internally coz only internally configured, but when I configure outlook using 2010 settings, it got configured but when I open outlook it doesn't
open and throws an error of some "cannot open set of folders".
Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence? because I havnt configured 2013 CAS servers yet.
Kindly share some KB or tip. Any help is appreciated. Thank You.
Muhammad Nadeem Ahmed Sr System Support Engineer Premier Systems (Pvt) Ltd T. +9221-2429051 Ext-226 F. +9221-2428777 M. +92300-8262627 Web. www.premier.com.pk

I'll change Adam's wording slightly - you *MUST* install a CAS 13 server into every site where there is a MBX 13 server.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

New-Pssession client cannot connect to the destination specified

I've used the following cmdlets to connect powershell to our tenant for months and now I cannot open a possession with the same commands.
I've searched on some of the error text show below without any great progress. We have a pair of Hybrid servers and we get the same result on either.
Any suggestions are appreciated.
Bruce
Import-module msonline
$O365Cred = Get-Credential
$O365Session = New-PSSession –ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $O365Cred -Authentication Basic -AllowRedirection
Import-PSSession $O365Session
Connect-MsolService –Credential $O365Cred
[email protected]
working password at the MicrosoftOnline Portal
$O365Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $O365Cred -Authentication Basic –AllowRedirection
WARNING: Your connection has been redirected to the following URI:
https://pod51038psh.outlook.com/powershell-liveid?PSVersion=4.0
New-PSSession : [pod51038psh.outlook.com] Connecting to remote server pod51038psh.outlook.com failed with the following error message : The client cannot connect to the destination specified
in the request. Verify that the service on the destination is running and is accepting 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". For more information, see the about_Remote_Troubleshooting Help topic.
+ $O365Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUr ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
Import-PSSession $O365Session
Import-PSSession : Cannot validate argument on parameter 'Session'. The argument is null. Provide a valid value for the argument, and then try running the command again.
At line:1 char:18
+ Import-PSSession $O365Session
+
~~~~~~~~~~~~
+ CategoryInfo
: InvalidData: (:) [Import-PSSession], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.ImportPSSessionCommand
Connect-MsolService -Credential $O365Cred

You are using the outdated URI string, which is known to cause problems. Should be: https://outlook.office365.com/powershell-liveid/
Just follow the instructions in the TechNet article:
https://technet.microsoft.com/en-us/library/jj984289(v=exchg.150).aspx

Outlook Client Issues following Exchange 2010 Rollup 8

Update Rollup 8 For Exchange 2010 SP3 (KB2986475) was applied to our Exchange server last night.
All appears to be fine, but users are having all kind of trouble using the Outlook Client to connect to their mailboxes.
Randomly they can't view certain folders (Inbox/Sent Items). Can no longer save to their Calendars. Errors relating to permissions and Outlook notifications?!?!?!?!
This is ONLY when using the Outlook Client - webmail works fine.
There are also no issues when running Outlook in safe mode.
Any advice would be very much appreciated.
Thanks
David

The following has been posted onto the Exchange team site:
http://blogs.technet.com/b/exchange/archive/2014/12/09/exchange-releases-december-2014.aspx
Update 12/10/2014:
An issue has been identified in the Exchange Server 2010 SP3 Update Rollup 8. The update has been recalled and is no longer available on the download center pending a new RU8 release. Customers should not proceed with deployments of this update until the
new RU8 version is made available. Customers who have already started deployment of RU8 should rollback this update.
The issue impacts the ability of Outlook to connect to Exchange, thus we are taking the action to recall the RU8 to resolve this problem. We will deliver a revised RU8 package as soon as the issue can be isolated, corrected, and validated. We will publish
further updates to this blog post regarding RU8.
This issue only impacts the Exchange Server 2010 SP3 RU8 update, the other updates remain valid and customers can continue with deployment of these packages.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

8.8 Client cannot connect to Windows Server 2008 error -1102

SAP Business On 8.8 on PL 18
This is not the first time I have had this issue with Windows Server 2008.
however everytime the resolution was diffrent. Now this site is causing trouble.
The issue is the client cannot connect. We have the log on window, can see the company list. type on the password and we get a -1102 error.
The client on the Server itself can log on. It is the cleints that cannot.
I checked these below.
1 SQL Native client is installed and ok.
2. Licence server is configured and ok
3. The user has admin access to locl PC
4. The SAP user name and password are correct ( client on server can connect fine )
5. The ports 1433, 30000 and 30001 are open on the server.
6. Through SQL server configuration the named pipes and TCP are enabled.
7. SQL server browser is running
The only things I have not tried are
The Firewall is running on the server and I have not yet stopped it. Will try that tomorrow.
Do you have any other ideas please ?

I have got this working but I am not confidant of the outcome - yet - I really need your expert advise here.
This is what I did. In that order.
1.     As Owen suggested I checked if there was a specified Port for the instance. What I found was TCP Dynamic ports were enabled ( SQL server config manager | network configuration | tcp properties ) and there was no TCP port specified. Assuming ( ai may be wrong) that the system assigns a dynamic port to this instance I set it up so the Dynamic port does not happen and manually specified the Port 1433. Restarted the SQL Service. ( still having the Port 1433 open in the firewall). This did not solve the issue.
2.     With the above setting still on, switched off the firewall. Went to the PC client and SAP can log on now. Now keeping the SAP client running, switched on the Firewall on the server. Log off SAP on PC client and log back in ( with firewall off ). SAP now can log on.
3.     I had to do the above step for all PCs to get them working.
4. Currently the firewall is on and clients can connect
So what could be happening? I have no clue. It is apparent there is some setting that gets saved within the PCs ( may be user profile) after the first log on with the Firewall off - to say its safe ?
However I have no idea what will happen if the server is restarted u2013 this server we cannot restart any time we want as itu2019s a critical server and runs other things.
I would still like to get to the bottom of this to understand what is happening.
I have a SAP message running too and will ask them this same question.

ODI Client cannot connect the datebase after the datebase IP changed

ODI Client cannot connect the datebase after the datebase IP changed.
1,the datebase on mac A,the mac changed ip
2,on the client, tnsping db is ok.
3,use pl/sql ,can connect on the db
4,with odi,changed the repostry URL to the new db IP,throw the exception below
java.sql.SQLException: Io Exception: The Network Adapter could not establish the connection
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:162)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:274)
     at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:328)
     at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:361)
     at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:151)
     at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
     at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:595)
     at com.sunopsis.sql.SnpsConnection.u(SnpsConnection.java)
     at com.sunopsis.sql.SnpsConnection.c(SnpsConnection.java)
     at com.sunopsis.sql.h.run(h.java)
Is anything we need to config after change db machine IP?

yeah,I got it.Everything is ok now.
After change IP,we must open TopologyManager:change the JDBC connection of workrepository which must chose in Designer.
when we open the Designer ,it will connect to db.then coonect to workrepository with original IP.So,we must rechange workrepository's JDBC first!

I cannot connect to Nokia Account from my Lumia 92...

I cannot connect to Nokia Account from my lumia 920. I have done a reset which allowed account details set up but although I can get to the sign in page that is as far as it goes. I can however connect via the website from this phone. does anyone have a simple solution.

Me too facing same problem.Can anyone plz help me.

The client cannot connect to the server

we just installed the boe but found that the client cannot connect to the server.
server: windows server 2008
boe xi3
client: window xp sp3
the server and client are in same dns
all components are work in server but client.
any idea on this?
ps: i can ping the server name successful.
thanks
ada
Edited by: Ada_Wei on Oct 29, 2010 10:12 AM

Can you please try to stop and disable the Windows firewall service on your client machine?
WHich client do you use and which error message do you get exactly?
Regards,
Stratos

HT3529 cannot connect to itunes store from iphone error message

cannot connect to itunes store from iphone error message

More than likely its your router. You need to make sure that the router's firewall, if enabled(most are by default), permits connection to these domains as trusted:
* itunes.apple.com
* ax.itunes.apple.com
* albert.apple.com
* gs.apple.com
This article may prove helpful in identifying the problem:
http://support.apple.com/kb/HT3501

Outlook clients cannot connect Exchange 2013 cutover from 2010

Similar Messages

Maybe you are looking for