rstuemke
asked on
Problem With Outlook Users Connecting To Exchange Server 2010
Hello,
We have 3 Exchange 2010 SP3 servers running on Win 2012 Server.
Server 436, Server BYD, Server 50R. All servers are mailbox, client access and hub transport.
We are running a DAG between all 3 for the mailbox. Works great - no problems.
The users are all running Outlook 2013. When a user is set up for Outlook, we enter the generic name of the server - mail.calvaryspringfield.or
Under normal circumstances this works fine. Users connect to Server BYD thru Outlook.
However, if for some reason, Server BYD hangs up, then the users cannot connect to Exchange and their Outlook hangs up or when they try to start Outlook, it hangs loading profile. We have a problem, that were are working with the vendor on, where our backup program will sometimes it will hang when backing up the Exchange Database. (I might mention that Server BYD is normally a mailbox backup server.)
So, when this backup hang occurs, users are shut out and cannot use Outlook. Having said all that, here is my questions:
1) Is there a way to force users to connect to a specific Exchange Server when setting up Outlook. I have tried entering the names of the other two servers and it always changes it to Server BYD.
2) Is there a way for users to connect to a "generic" server name and which will then connect to any of the 3 servers. Similar to multiplexing connections between the 3 Exchange Servers?
Please advise. Thanks.
We have 3 Exchange 2010 SP3 servers running on Win 2012 Server.
Server 436, Server BYD, Server 50R. All servers are mailbox, client access and hub transport.
We are running a DAG between all 3 for the mailbox. Works great - no problems.
The users are all running Outlook 2013. When a user is set up for Outlook, we enter the generic name of the server - mail.calvaryspringfield.or
Under normal circumstances this works fine. Users connect to Server BYD thru Outlook.
However, if for some reason, Server BYD hangs up, then the users cannot connect to Exchange and their Outlook hangs up or when they try to start Outlook, it hangs loading profile. We have a problem, that were are working with the vendor on, where our backup program will sometimes it will hang when backing up the Exchange Database. (I might mention that Server BYD is normally a mailbox backup server.)
So, when this backup hang occurs, users are shut out and cannot use Outlook. Having said all that, here is my questions:
1) Is there a way to force users to connect to a specific Exchange Server when setting up Outlook. I have tried entering the names of the other two servers and it always changes it to Server BYD.
2) Is there a way for users to connect to a "generic" server name and which will then connect to any of the 3 servers. Similar to multiplexing connections between the 3 Exchange Servers?
Please advise. Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Clarification on question #2...... understand running of the single database. Just wanted to be able to connect to any server to get to it.
You mention a very important issue.... why can't the users auto switch to other members of the DAG, when this one hangs up. The mailboxes swap over fine when a server has a problem or is restarted. The users do not.
One more item, I forgot to mention. Server BYD also has its own database, which is just the journal mailbox. This mailbox is also part of DAG and copy resides on the other backup server - 50R.
Results of test-replication health on Server BYD:
Server Check Result Error
1730WBYD39Y1 ClusterService Passed
1730WBYD39Y1 ReplayService Passed
1730WBYD39Y1 ActiveManager Passed
1730WBYD39Y1 TasksRpcListener Passed
1730WBYD39Y1 TcpListener Passed
1730WBYD39Y1 ServerLocatorService Passed
1730WBYD39Y1 DagMembersUp Passed
1730WBYD39Y1 ClusterNetwork Passed
1730WBYD39Y1 QuorumGroup Passed
1730WBYD39Y1 DBCopySuspended Passed
1730WBYD39Y1 DBCopyFailed Passed
1730WBYD39Y1 DBInitializing Passed
1730WBYD39Y1 DBDisconnected Passed
1730WBYD39Y1 DBLogCopyKeepingUp Passed
1730WBYD39Y1 DBLogReplayKeepingUp Passed
Ran on other servers. All passed.
You mention a very important issue.... why can't the users auto switch to other members of the DAG, when this one hangs up. The mailboxes swap over fine when a server has a problem or is restarted. The users do not.
One more item, I forgot to mention. Server BYD also has its own database, which is just the journal mailbox. This mailbox is also part of DAG and copy resides on the other backup server - 50R.
Results of test-replication health on Server BYD:
Server Check Result Error
1730WBYD39Y1 ClusterService Passed
1730WBYD39Y1 ReplayService Passed
1730WBYD39Y1 ActiveManager Passed
1730WBYD39Y1 TasksRpcListener Passed
1730WBYD39Y1 TcpListener Passed
1730WBYD39Y1 ServerLocatorService Passed
1730WBYD39Y1 DagMembersUp Passed
1730WBYD39Y1 ClusterNetwork Passed
1730WBYD39Y1 QuorumGroup Passed
1730WBYD39Y1 DBCopySuspended Passed
1730WBYD39Y1 DBCopyFailed Passed
1730WBYD39Y1 DBInitializing Passed
1730WBYD39Y1 DBDisconnected Passed
1730WBYD39Y1 DBLogCopyKeepingUp Passed
1730WBYD39Y1 DBLogReplayKeepingUp Passed
Ran on other servers. All passed.
The DAG only protects the mailbox database, it has nothing to do with the client access - which includes Outlook.
Therefore if you want completely transparent high availability you need load balancers.
The behaviour you are seeing with the clients not moving across is what I would expect to see.
Simon.
Therefore if you want completely transparent high availability you need load balancers.
The behaviour you are seeing with the clients not moving across is what I would expect to see.
Simon.
ASKER
I did not have a client access array set up. However, I have deployed it and tested it for connectivity with Outlook. Working thru the issue with Outlook getting disconnected when it changed client access name. Seems to be a known problem for already established databases and outlook clients.
ASKER
OK. Followed the instructions for setting up Client Access Array.
Have DNS host record for casarray.calvaryspringfiel
Created a new mailbox database and set the RPC Client Access Server to point to
casarray.calvaryspringfiel
Moved a test user mailbox to that database. In account settings in Outlook, the server name is casarray.calvaryspringfiel
Have DNS host record for casarray.calvaryspringfiel
Created a new mailbox database and set the RPC Client Access Server to point to
casarray.calvaryspringfiel
Moved a test user mailbox to that database. In account settings in Outlook, the server name is casarray.calvaryspringfiel
ASKER
Supplemental information:
[PS] C:\exchangescripts>get-cli
RunspaceId : f66a95af-29c8-4862-8ff6-34
ExchangeLegacyDN : /o=Calvary Temple/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Confi
=casarray.calvaryspringfie
Fqdn : casarray.calvaryspringfiel
Site : calvaryspringfield.org/Con
SiteName : Default-First-Site-Name
Members : {1730W50RXBX1, 1730W436QPS1, 1730WBYD39Y1}
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : CTCC_ClientAccesArray
DistinguishedName : CN=CTCC_ClientAccesArray,C
tive Groups,CN=Calvary Temple,CN=Microsoft Exchange,CN=Services,CN=Co
eld,DC=org
Identity : CTCC_ClientAccesArray
Guid : 47e0f020-c798-4824-9206-53
ObjectCategory : calvaryspringfield.org/Con
ObjectClass : {top, server, msExchExchangeServer, msExchClientAccessArray}
WhenChanged : 2/10/2014 1:00:37 PM
WhenCreated : 2/10/2014 1:00:37 PM
WhenChangedUTC : 2/10/2014 7:00:37 PM
WhenCreatedUTC : 2/10/2014 7:00:37 PM
OrganizationId :
OriginatingServer : 1730WDCX1VF1.calvaryspring
IsValid : True
[PS] C:\exchangescripts>Get-Mai
Name : Mailbox Database 436
RpcClientAccessServer : 1730W436QPS1.calvaryspring
Name : Journal Database BYD
RpcClientAccessServer : 1730W436QPS1.calvaryspring
Name : Mailbox Database 50R
RpcClientAccessServer : casarray.calvaryspringfiel
Name : User Mailbox Database
RpcClientAccessServer : casarray.calvaryspringfiel
User Mailbox Database is the one I moved the test user mailbox to.
[PS] C:\exchangescripts>get-cli
RunspaceId : f66a95af-29c8-4862-8ff6-34
ExchangeLegacyDN : /o=Calvary Temple/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Confi
=casarray.calvaryspringfie
Fqdn : casarray.calvaryspringfiel
Site : calvaryspringfield.org/Con
SiteName : Default-First-Site-Name
Members : {1730W50RXBX1, 1730W436QPS1, 1730WBYD39Y1}
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : CTCC_ClientAccesArray
DistinguishedName : CN=CTCC_ClientAccesArray,C
tive Groups,CN=Calvary Temple,CN=Microsoft Exchange,CN=Services,CN=Co
eld,DC=org
Identity : CTCC_ClientAccesArray
Guid : 47e0f020-c798-4824-9206-53
ObjectCategory : calvaryspringfield.org/Con
ObjectClass : {top, server, msExchExchangeServer, msExchClientAccessArray}
WhenChanged : 2/10/2014 1:00:37 PM
WhenCreated : 2/10/2014 1:00:37 PM
WhenChangedUTC : 2/10/2014 7:00:37 PM
WhenCreatedUTC : 2/10/2014 7:00:37 PM
OrganizationId :
OriginatingServer : 1730WDCX1VF1.calvaryspring
IsValid : True
[PS] C:\exchangescripts>Get-Mai
Name : Mailbox Database 436
RpcClientAccessServer : 1730W436QPS1.calvaryspring
Name : Journal Database BYD
RpcClientAccessServer : 1730W436QPS1.calvaryspring
Name : Mailbox Database 50R
RpcClientAccessServer : casarray.calvaryspringfiel
Name : User Mailbox Database
RpcClientAccessServer : casarray.calvaryspringfiel
User Mailbox Database is the one I moved the test user mailbox to.
ASKER
WHOA! Maybe I found the problem. The name may does not match the DNS record.
Access spelled wrong on the array name. So I fixed the DNS record to match the array name.
Did a repair on the Outlook account - Successful.
Did not fix Outlook........
Now Outlook says DISCONNECTED, when I try to go online. Still cannot get it to connect.
Need assistance. I am surely missing something. Please advise....
Access spelled wrong on the array name. So I fixed the DNS record to match the array name.
Did a repair on the Outlook account - Successful.
Did not fix Outlook........
Now Outlook says DISCONNECTED, when I try to go online. Still cannot get it to connect.
Need assistance. I am surely missing something. Please advise....
ASKER
Ugh oh!! Found a mistake. DNS record had the name of the CAS and not the FQDN
Fixed the DNS record.
So did another repair and now Outlook goes into TRYING TO CONNECT for a while then goes into a DISCONNECTED state. Now, I need assistance. Thanks.
Fixed the DNS record.
So did another repair and now Outlook goes into TRYING TO CONNECT for a while then goes into a DISCONNECTED state. Now, I need assistance. Thanks.
It could just be cached information, particularly with DNS entries, and you either need to wait for the cache to expire or flush the cache. Ensure the DNS entry for the CAS Array has a TTL time that is very short.
Simon.
Simon.
ASKER
Ok..... go the test user to work when I deleted the Outlook profile and recreated it. Do not want to have to do that for 100+ users. Hoping to get it to change and work automatically.
Still testing, now with my journal user mailbox. Moved it to a new database which uses the Client Access Array, cleared DNS cache on the PC which runs its outlook. Did a account repair. Trying to connect. Will let it set for awhile and see what happens.
Still testing, now with my journal user mailbox. Moved it to a new database which uses the Client Access Array, cleared DNS cache on the PC which runs its outlook. Did a account repair. Trying to connect. Will let it set for awhile and see what happens.
There is no way to get the change to happen automatically.
The CAS Array only applies on a new profile or doing a repair of the profile. That will mean each machine has to be visited.
Personally I would change all of the databases. It will not affect any existing users, but any new profiles created will be using the new address.
Simon.
The CAS Array only applies on a new profile or doing a repair of the profile. That will mean each machine has to be visited.
Personally I would change all of the databases. It will not affect any existing users, but any new profiles created will be using the new address.
Simon.
ASKER
Ok.... one more question if you please.......
I have got this to work on only 1 user that was moved to this new database. I moved 3 other users over there. Tried just a repair and it finds the casarray.calvaryspringfiel
In MORE SETTINGS, I have tried a few changes, such as unchecking CONNECT TO MICROSOFT EXCHANGE USING HTTP. Nothing seems to make a difference. Cannot get it to connect. How can I fix this problem???? Any help would be greatly appreciated. Thanks.
I have got this to work on only 1 user that was moved to this new database. I moved 3 other users over there. Tried just a repair and it finds the casarray.calvaryspringfiel
In MORE SETTINGS, I have tried a few changes, such as unchecking CONNECT TO MICROSOFT EXCHANGE USING HTTP. Nothing seems to make a difference. Cannot get it to connect. How can I fix this problem???? Any help would be greatly appreciated. Thanks.
Check whether Autodiscover is working correctly.
Hold down CTRL while right clicking on the Outlook icon in the system tray. Choose Test EMail Autoconfiguration.
Switching to a CAS Array shouldn't be this difficult, because it is just a DNS entry and small configuration in Exchange. The DNS entry needs to point to a server with the CAS role.
Simon.
Hold down CTRL while right clicking on the Outlook icon in the system tray. Choose Test EMail Autoconfiguration.
Switching to a CAS Array shouldn't be this difficult, because it is just a DNS entry and small configuration in Exchange. The DNS entry needs to point to a server with the CAS role.
Simon.
ASKER
Changed the DNS entry to point to an existing CAS server and it worked. The documentation I found seemed a bit confusing on this issue and I had it just pointing to a reserved, unused IP address. Thanks for all the help.
My apologies to Will, I meant to divy out some of the points to you also, but forgot to do that. Sorry.
My apologies to Will, I meant to divy out some of the points to you also, but forgot to do that. Sorry.
This is not how a DAG should work. If it is happening I would check the status/health of the DAG first. It is obviously not failing over to the other members.
Answers below...
1. There is no way to force a client to connect to another Mailbox server. You need to have this setup properly on the backend when using DAG. If you DAG is not failing over properly your users will continue to look at the DAG member that is in a "hung"state and not work until this member is back online.
2. Answer to this is no. When you have a mailbox database in a DAG scenario this database is the primary database on this DAG member. A single database cannot be split as active across different DAG members.
What I would recommend is checking the health status of your DAG using the below commands.
Get-MailboxDatabaseCopySta
and
Test-ReplicationHealth
I would also recommend that you check your logs on the database servers as well, and also check the Failover Clustering Logs as this is probably where the issue is happening as the members are not failing over properly. If the DAG members are configured correctly the others DAG member servers (that host the database will become active and start hosting the database) users will then be able to connect.
Will.