Mailbox server Removed

hi
I have 2 mailbox server Exchange 2013 as DAG member
2 cas servers
1 of our mailbox vm deleted by mistake , what is the steps to recover this mailbox although it was memeber of DAG ?
Need suggestion please
MCP MCSA MCSE MCT MCTS CCNA

http://technet.microsoft.com/en-us/library/dd638206(v=exchg.150).aspx
Recover a database availability group member server
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Similar Messages

Get-Mailbox –Server "abc" | Get-MailboxPermission | Export-csv C:\permissions.csv

I am new to exchange command shell, I need to get a list of all security permissions per mailbox, we have executed the following command:
get-mailbox -server "removed" | get-mailboxpermission | export-csv c:\permissions.csv
The command ran ok, and has exported 9 fields, pscomputername, runspaceid, accessrights, deny, inhertiance, user, identity, isinherited, isvalid.
My question is, which field in the above lists which mailbox the permissions are for? is it the "identity" field?

Hi,
Sorry for delayed reply. Did you mean the access rights do not appear correctly in the output CSV file, with the microsoft.exchange.management.recipienttasks.mailboxrights[], instead of the actual mailbox rights?
If so, I recommend you check the article DareDevil57 provided.
How to List all Users Who Have Access to Other Exchange Mailboxes
http://exchangeserverpro.com/list-users-access-exchange-mailboxes/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Removing mailbox server from Exchange 2010 DAG - Node not fully cleaned up

Hi,
We are in the process of decommissioning some old Exchange 2010 servers. I have just attempted to remove one of our mailbox servers and have received a number of errors, related to its removal from the DAG.
I have already removed the Public Folder replicas and all mailbox database copies. I then tried to evict the server from the DAG and received the following warning:
I then ran the command that was recommended, from another server and in an administrative command prompt:
I have looked in this log on both the server I ran the command on, a CAS server, and the mailbox server itself and can see no evidence of this error 2 that is listed here.
If I run the Powershell command to look at the DAG I cannot see it there any more. I am assuming that this error message might only be an issue if I was planning on re-using this server somewhere else in Exchange or perhaps adding this server to another
DAG. But I just want to decommission it.
Can anyone put my mind at rest as to whether this is a genuine concern or not. If not my next step is to uninstall Exchange 2010 from this server and turn it off.

Hi Belinda,
I get the following:
[PS] C:\Windows\system32>Get-DatabaseAvailabilityGroup
Name Member Servers
Operational Servers
DAG01 {WSR-EX-01, WSR-EX-101, WSR21}
It doesn't look like that server is part of the DAG any more as far as I can see. I just can't explain that error message reported from the cluster command. As far as I can see the server is isolated. I already removed its database copies as a pre-requisite
before removing it from the DAG as per this guide:
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_27039933.html
I found a nice little script that gave reports on your Public Folder configuration and it highlighted that some of our folders were not being replicated properly across our mailbox servers. This helped me in removing these services from the server.
It is currently doing nothing at this time as far as Exchange Services are concerned.

Removing mailbox server exchange 2010

Dear all,
I have two mailbox servers, when I try to uninstall mailbox server roll on the exchange 2010 Mailbox server1 I get below error msg.
Failed
Error:
This Mailbox server is responsible for generating an Offline Address Book. Removal of the Mailbox role is not permitted
If I move an offline Address book from Mailbox server1 to Mailbox server2 then I guess it should be okay?
Also get below error msg as well, do I need to take care of anything else before I remove the mailbox server role ?
Error:
Setup cannot continue with the uninstall because the 'beremote' () process (ID: 2076) has open files. Close the process and restart Setup.
Thanks !!!

Hi Ms-2010,
Before you uninstall the first Exchange 2010 Server, you need to fix few prerequisites warning/errors for a clean uninstallation.
Four points should be considered:
1. Change the OAB (Offline Address Book) generation role to other available server.
2. Remove the server from DAG membership.
3. Move the Arbitration mailboxes to another available Mailbox Server.
4. Ensure that none of the databases are using public folder of this server as default and Move Public folder replica to other available mailbox server.
Hope it is helpful.
Best regards,
Eric

How to Remove a bad mailbox server and add new mailbox server to DAG and copy mailboxes over

DAG
2- cas - VM
2- mbx- physical blade (mbx1, mbx2)
5- mailbox databases
OS: Win 2008 SP2
Exchange 2010SP3
Storage: Tegile Disk jbod Luns
We have bad disks on mbx1. our plan is to get a new blade to replace the bad one named mbx3. we need to do this asap since we are running on 1 server without failover capability
How can I safely:
1. Add a new mailbox server to the DAG
2. Copy\Move the databases from the old (passive) server to the new server
3. Remove the bad mailbox server from DAG

You'll want to make sure that the new server is on all the same networks that the server you are removing is on, specifically networks that are DAG networks. Also, you'll want to avoid using Windows Network Load Balancing on the new mailbox server
since it will be part of the DAG. Also, just as you did with the current DAG members, ensure that the disk drive letters match the existing disks that hold databases & logs. Other than that, it's as simple as you have stated.
1.) Once you have the new mbx server built & configured with the mailbox role, you can use:
Get-DatabaseAvailabilityGroup "Name of DAG" | Add-DatabaseAvailabilityGroupServer "Name of New MBX Server"
2.) Add the databases to the new DAG member:
Add-MailboxDatabaseCopy "name of database" -MailboxServer "name of new DAG member" -ActivationPreference "[you decide based on the server replacing mbx1]"
3.) Once your databases are Mounted and/or Healthy on the new DAG member, you'll want to remove the databases from the "bad" server (make sure they are all passive on the server first):
Get-MailboxDatabaseCopy "SERVER\Database" | Remove-MailboxDatabaseCopy
4.) Once all of the databases are removed from the "bad" DAG member, remove him from the DAG:
Get-DatabaseAvailabilityGroup "Name of DAG" | Remove-DatabaseAvailabilityGroupServer "Name of old MBX Server"
Before you pull the blade, uninstall Exchange Server gracefully, as this will save you AD & Exchange headaches later on.
Petri has a pretty good GUI walk-through for some of the above steps here:
How to Configure Database Availability Group for Exchange Server 2010
Woody Colling, MCITP Exchange 2010
--The incentive for the experts to answer posts is to get their replies marked as helpful, or as the answer to our questions, help them help us, mark posts accordingly--

Decommission Exchange 2007 Mailbox Server from Cluster

Hi! I realize this is an Exchange 2013 forum, however as I do not see any forums for older flavors of Exchange I'm going to post this here. If a better forum exists please let me know and I'll happily move to that forum for my answers.
I am just finishing a migration from Exchange 2007 to Exchange 2013. In the Exchange 2007 environment I have 2 CCR Mailbox Clusters. While working to decommission the first of the two clusters I successfully evicted the passive node, however
I mistakenly evicted the active node rather than removing it by running the Exchange Setup Wizard as outlined in the TechNet article "How to Remove the Active Mailbox Role from a CCR Environment".
Now, when attempting to uninstall Exchange 2007 using the Setup Wizard in Add/Remove Program I get the following error during the prerequisite check for the 'Mailbox Role':
Error:
Exchange server FQDN was not found. Please make sure you have typed it correctly."
Setup then completes.
Is there a way to cleanly uninstall Exchange 2007 and clean-up Active Directory?
Thanks!

Hi Jesse,
Thank you for your question.
We could run “ADsiedit.msc” in run, then navigate
Configuration [<domainController>.contoso.com]> CN=Configuration,DC=contoso,DC=com> CN=Services> CN=Microsoft Exchange> CN=<OrganizationName> CN=Administrative Group> CN=Exchange Administrative Group>CN=Server
We could check if mailbox server is existed in this container, we could remove it.
Notice: Before we remove it, we could make a backup for AD database. We suggest you call MS engineer for help.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Exchange 2013 issue with High memory Usage on Mailbox server post SP1 update.

So we have been chugging along fine since Feb 2 2014.
I performed a migration from 2010 from the UK to the US doing "incremental" mailbox moves. (get in contact with me if you want to know how. But we moved 400 Mailboxes averaging at 2gb a piece from the UK to the US, over the transcontinental link.
& then the weekend of the final, had everyone & everything done by the end of the cutover weekend)
Any woot.
So I applied the 2013 SP1 a few weeks back, & have intermitantly been alerted to the memory spiking over 95%. For me (and for any exchange admin) when i get those types of alerts i drop everything & run to the nearest PC to see what is going on.
Now the first & second time, it was an issue with logs filling up the drives, & my clean log script not running to remove any logs older than 30 days. But since then it has been legitimate 95%+ memory usage.
For the most part its been 95-97 max, with 1 or 2 times hitting 98. After some time, the memory does drop back down to 94.
this is ....umm "fine" however it is becoming a nuisance, since most of the time it corrects itself. What i dont want to happen is get into the groove of saying "ah bah! its nothing" & letting it go.
the server has 16gb of memory in it, it is the Mailbox server (CAS /Frontend is on a seperate server)
below is a screen shot, so i know the Storeworker grabs whatever it feels like grabbing, however it does NOT EVER release memory. I also see the NodeRunner.exe (2 of them) is always around 900 almost a MB
now if i could somehow get the first 2 Storeworkers to drop down to 900ish, then that should alleviate my memory issues.
what I am m looking for is some type of "magic bullet" to put my memory issues at ease..

thats the problem & seems to be a misconception.
Exchange NEVER releases the memory when other things need it. As the users state in your thread you linked. (i came across that early in my search for a resolution). An example is if another admin & myself log into the backend server at the same
time & begin clicking around opening things, etc..Memory will go to 100% which = No Buenos.
There are numerous post all over the internet from people who say it releases, but them 5 more comments to that 1 saying that it does not.
I know what the process's do, however it seems like the SP1 has increased memory usage, as typically the Store.exe would only grab about 900-1000.
in terms of the noderunner, once again i know its role, however we are now 2 months+ live on 2013 post migration, I do not think it is still indexing all those emails.
all DB's report healthy.
Name Status CopyQueue ReplayQueue LastInspectedLogTime ContentIndex
Length Length State
WBAC1\EXCHBE001 Mounted 0 0
Healthy
WBAC2\EXCHBE001 Mounted 0 0
Healthy
WBAC3\EXCHBE001 Mounted 0 0
Healthy
WBAC4\EXCHBE001 Mounted 0 0
Healthy
WBAC5\EXCHBE001 Mounted 0 0
Healthy

How to decomission a Exchange 2007 Mailbox server

Hello,
We are running Exchange 2007 SP3 servers. We currently have a Mailbox server we want to decommission. I'd like help on how to achieve this. I want to make sure that all mailboxes have been moved from that server and remove the Public Folder database as well.
I understand that the Public Folders needs to stop replicating to this server, can someone please guide me on how to do that?
All kinds of help are appreciated. Thanks!

For the public folder stuff, see these scripts: https://technet.microsoft.com/en-us/library/aa997966(v=exchg.141).aspx
The system folders can be replicated with the '\non_ipm_subtree' identifier, but some system folders are per-server and don't need to replicate. OAB distribution however
is one that might matter.
Mike Crowley | Microsoft MVP
Baseline
Technologies

Fail to add Mailbox server to DAG

I'm Setting up Exchange Server 2013 Mailing system, the schema that i'm deploying includes two CAS servers : 3S-CAS1 and 3S-CAS2 for load balancing access authentication;
and two mailbox servers 3S-MBX1 and 3S-MBX2. A File share server 3S-FW is used as a witness for the DAG . the Exchange Trusted Subsystems AD Group is added as member ofthe File witness local administrators. A computer account EDAG is created on AD and
then disabled as recommended.
my Network configuration is the following :
3S-CAS1 : 172.16.192.7
3S-CAS2 : 172.16.192.8
3S-MBX1: 172.16.192.9 (prod trafic)
 10.0.0.1 (replication interface)
3S-MBX2: 172.16.192.10 (prod interface)
 10.0.0.2 (replication interface)
EGAG : 172.16.192.20
the issue is when i try to create a DAG (Database Availability Group) i'm getting the following error message
[PS] C:\Windows\system32>New-DatabaseAvailabilityGroup -Name EDAG -WitnessServer 3S-FW -WitnessDirectory c:\shares\fws_dag -DatabaseAvailabilityGroupIpAddresses 172.16.192.20
WARNING: Unable to access file shares on witness server '3S-FW.3s.com.tn'. Until this problem is corrected, the database availability group may be more vulnerable to failures. You can use the Set-DatabaseAvailabilityGroup cmdlet to try the operation again.
Error: The network path was not found
After that i'm giving up using witness server since creating a DAG without specifying a witness server would elect one from CAS servers that do not contain the mailbox role.
[PS] C:\Windows\system32>New-DatabaseAvailabilityGroup -Name EDAG -DatabaseAvailabilityGroupIpAddresses 172.16.192.20
Name Member Servers
Operational Servers
EDAG {}
and all things seems to be ok. but when adding the first Mailbox server (3S-MBX1) to the DAG i get the following error :

[PS] C:\Windows\system32>Add-DatabaseAvailabilityGroupServer -Identity EDAG -MailboxServer 3S-MBX1
WARNING: The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-02-11_14-35-14.226_add-databaseavailabiltygroupserver.log".
A server-side database availability group administrative operation failed. Error The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster
operation. Error: Cluster API '"CreateCluster() failed with 0x57. Error: The parameter is incorrect"' failed.. [Server: 3S-MBX1.3s.com.tn]
 + CategoryInfo : InvalidArgument: (:) [Add-DatabaseAvailabilityGroupServer], DagTaskOperationFailedException
 + FullyQualifiedErrorId : [Server=3S-MBX1,RequestId=d774dd8b-0d03-41a1-a3d9-5d2a09432e58,TimeStamp=11/02/2014 14:35:22] E84D00B4,Microsoft.Exchange.Management.SystemConfigurationTasks.AddDatabaseAvailabilityGroupServer
 + PSComputerName : 3s-mbx1.3s.com.tn
The error indicates that erors may result from incorrectly configured static addresses. i joined the log file related to the DAG tasks and the first mailbox server ip configuration.
<fieldset class="mimeAttachmentHeader"><legend class="mimeAttachmentHeaderName">dagtask_2014-02-11_14-35-14.226_add-databaseavailabiltygroupserver.log</legend></fieldset>
add-databaseavailabiltygroupserver started on machine 3S-MBX1.
[2014-02-11T14:35:14] add-dagserver started
[2014-02-11T14:35:14] commandline: $scriptCmd = {& $wrappedCmd @PSBoundParameters }
[2014-02-11T14:35:14] Option 'Identity' = 'EDAG'.
[2014-02-11T14:35:14] Option 'MailboxServer' = '3S-MBX1'.
[2014-02-11T14:35:14] Option 'DatabaseAvailabilityGroupIpAddresses' = ''.
[2014-02-11T14:35:14] Option 'WhatIf' = ''.
[2014-02-11T14:35:14] Process: w3wp w3wp.exe:612.
[2014-02-11T14:35:14] User context = 'NT AUTHORITY\SYSTEM'.
[2014-02-11T14:35:14] Member of group 'Everyone'.
[2014-02-11T14:35:14] Member of group 'BUILTIN\Users'.
[2014-02-11T14:35:14] Member of group 'NT AUTHORITY\SERVICE'.
[2014-02-11T14:35:14] Member of group 'CONSOLE LOGON'.
[2014-02-11T14:35:14] Member of group 'NT AUTHORITY\Authenticated Users'.
[2014-02-11T14:35:14] Member of group 'NT AUTHORITY\This Organization'.
[2014-02-11T14:35:14] Member of group 'BUILTIN\IIS_IUSRS'.
[2014-02-11T14:35:14] Member of group 'LOCAL'.
[2014-02-11T14:35:14] Member of group 'IIS APPPOOL\MSExchangePowerShellFrontEndAppPool'.
[2014-02-11T14:35:14] Member of group 'BUILTIN\Administrators'.
[2014-02-11T14:35:14] Updated Progress 'Validating the parameters.' 2%.
[2014-02-11T14:35:14] Working
[2014-02-11T14:35:14] Mailbox server: value passed in = 3S-MBX1, mailboxServer.Name = 3S-MBX1, mailboxServer.Fqdn = 3S-MBX1.3s.com.tn
[2014-02-11T14:35:14] LogClussvcState: clussvc is Stopped on 3S-MBX1.3s.com.tn. Exception (if any) = none
[2014-02-11T14:35:14] The IP addresses for the DAG are (blank means DHCP): 172.16.192.20
[2014-02-11T14:35:14] Looking up IP addresses for EDAG.
[2014-02-11T14:35:14] EDAG = [ 172.16.192.20 ].
[2014-02-11T14:35:14] Looking up IP addresses for 3s-mbx1.
[2014-02-11T14:35:14] 3s-mbx1 = [ ::1, 172.16.192.9, 10.0.0.1 ].
[2014-02-11T14:35:14] Looking up IP addresses for 3S-MBX1.3s.com.tn.
[2014-02-11T14:35:14] 3S-MBX1.3s.com.tn = [ ::1, 172.16.192.9, 10.0.0.1 ].
[2014-02-11T14:35:14] DAG EDAG has 0 servers:
[2014-02-11T14:35:14] Updated Progress 'Checking if Mailbox server '3S-MBX1' is in a database availability group.' 4%.
[2014-02-11T14:35:14] Working
[2014-02-11T14:35:14] GetRemoteCluster() for the mailbox server failed with exception = An Active Manager operation failed. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"OpenCluster(3S-MBX1.3s.com.tn) failed with 0x6d9. Error: There are no more endpoints available from the endpoint mapper"' failed.. This is OK.
[2014-02-11T14:35:14] Ignoring previous error, as it is acceptable if the cluster does not exist yet.
[2014-02-11T14:35:14] DumpClusterTopology: Opening remote cluster EDAG.
[2014-02-11T14:35:14] DumpClusterTopology: Failed opening with Microsoft.Exchange.Cluster.Replay.AmGetFqdnFailedNotFoundException: An Active Manager operation failed with a transient error. Please retry the operation. Error: The fully qualified domain name for node 'EDAG' could not be found.
at Microsoft.Exchange.Cluster.ActiveManagerServer.AmServerNameCache.<>c__DisplayClass1.<ResolveFqdn>b__0(Object param0, EventArgs param1)
at Microsoft.Exchange.Cluster.ActiveManagerServer.AmHelper.RunADOperationEx(EventHandler ev)
at Microsoft.Exchange.Cluster.ActiveManagerServer.AmServerNameCache.ResolveFqdn(String shortNodeName, Boolean throwException)
at Microsoft.Exchange.Cluster.ActiveManagerServer.AmServerNameCache.GetFqdn(String shortNodeName, Boolean throwException)
at Microsoft.Exchange.Cluster.ActiveManagerServer.AmServerName..ctor(String serverName, Boolean throwOnFqdnError)
at Microsoft.Exchange.Management.SystemConfigurationTasks.DumpClusterTopology..ctor(String nameCluster, ITaskOutputHelper output)
[2014-02-11T14:35:14] Dumping the cluster by connecting to: EDAG.
[2014-02-11T14:35:14] DumpClusterTopology: Not dumping, since the cluster could not be contacted.
[2014-02-11T14:35:14] The new server (3S-MBX1) is not a member of a cluster, nor are the other servers (if there are any other servers).
[2014-02-11T14:35:14] The computer account EDAG does not exist.
[2014-02-11T14:35:14] According to GetNodeClusterState(), the server 3S-MBX1 is NotConfigured.
[2014-02-11T14:35:14] InternalValidate() done.
[2014-02-11T14:35:14] Updated Progress 'Adding server '3S-MBX1' to database availability group 'EDAG'.' 6%.
[2014-02-11T14:35:14] Working
[2014-02-11T14:35:14] Connecting to server '3S-MBX1.3s.com.tn' via WMI...
[2014-02-11T14:35:14] Fetching the network adapters and including the ones without default gateways.
[2014-02-11T14:35:14] 3S-MBX1.3s.com.tn has an address: 10.0.0.1/24 default gateway(s)=<none> [valid]
[2014-02-11T14:35:14] IP address derived that's suitable for clustering DHCP/IPv6: 10.0.0.0/24.
[2014-02-11T14:35:14] 3S-MBX1.3s.com.tn has an address: 172.16.192.9/24 default gateway(s)=172.16.192.254 [valid]
[2014-02-11T14:35:14] IP address derived that's suitable for clustering DHCP/IPv6: 172.16.192.0/24.
[2014-02-11T14:35:14] The address 172.16.192.20 falls under the network (172.16.192.0/24).
[2014-02-11T14:35:14] Updated Progress 'Forming cluster named 'EDAG' on server '3S-MBX1'.' 8%.
[2014-02-11T14:35:14] Working
[2014-02-11T14:35:14] Forming cluster named 'EDAG' on server '3S-MBX1'. The cluster address is/are [172.16.192.20], and the cluster network prefix length is/are [24].
[2014-02-11T14:35:22] The following log entry comes from a different process that's running on machine '3S-MBX1'. BEGIN
[2014-02-11T14:35:22] [2014-02-11T14:35:14] Updated Progress 'Forming cluster named 'EDAG' on server '3s-mbx1'.' 2%.
[2014-02-11T14:35:14] Working
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseInitialize, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 5, szObjectName = EDAG, dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseInitialize, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 5, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateNodeState, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 10, szObjectName = 3S-MBX1.3s.com.tn, dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateNodeState, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 10, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseQueryClusterNameAccount, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 15, szObjectName = EDAG, dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseQueryClusterNameAccount, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 15, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateClusterNameAccount, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 21, szObjectName = EDAG, dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateClusterNameAccount, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 21, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseConfigureClusterAccount, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 26, szObjectName = EDAG in organizational unit CN=Computers,DC=3s,DC=com,DC=tn, dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseConfigureClusterAccount, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 26, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateNetft, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 31, szObjectName = 3S-MBX1.3s.com.tn, dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateNetft, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 31, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateClusDisk, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 36, szObjectName = 3S-MBX1.3s.com.tn, dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateClusDisk, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 36, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:14] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseConfigureClusSvc, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 42, szObjectName = 3S-MBX1.3s.com.tn, dwStatus = 0x0 )
[2014-02-11T14:35:15] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseConfigureClusSvc, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 42, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:15] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseStartingClusSvc, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 47, szObjectName = 3S-MBX1.3s.com.tn, dwStatus = 0x0 )
[2014-02-11T14:35:15] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseStartingClusSvc, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 47, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:15] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFormingCluster, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 52, szObjectName = EDAG, dwStatus = 0x0 )
[2014-02-11T14:35:17] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFormingCluster, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 52, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:17] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseAddClusterProperties, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 57, szObjectName = EDAG, dwStatus = 0x0 )
[2014-02-11T14:35:17] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseAddClusterProperties, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 57, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:17] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseCreateResourceTypes, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 63, szObjectName = EDAG, dwStatus = 0x0 )
[2014-02-11T14:35:17] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseCreateResourceTypes, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 63, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:17] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseCreateGroups, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 68, szObjectName = Cluster Group, dwStatus = 0x0 )
[2014-02-11T14:35:17] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseCreateGroups, ePhaseType = ClusterSetupPhaseContinue, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 68, szObjectName = Available Storage, dwStatus = 0x0 )
[2014-02-11T14:35:17] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseCreateGroups, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 68, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:17] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseCreateIPAddressResources, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 73, szObjectName = Cluster IP Address, dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseCreateIPAddressResources, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 73, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseCreateNetworkName, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 78, szObjectName = EDAG, dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseCreateNetworkName, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 78, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseQueryClusterNameAccount, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 84, szObjectName = EDAG, dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseQueryClusterNameAccount, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 84, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateClusterNameAccount, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 89, szObjectName = EDAG, dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateClusterNameAccount, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 89, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseConfigureClusterAccount, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 94, szObjectName = EDAG in organizational unit CN=Computers,DC=3s,DC=com,DC=tn, dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseConfigureClusterAccount, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseFatal, dwPercentComplete = 94, szObjectName = EDAG in organizational unit CN=Computers,DC=3s,DC=com,DC=tn, dwStatus = 0x57 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseConfigureClusterAccount, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseFatal, dwPercentComplete = 94, szObjectName = å° ÅŠ, dwStatus = 0x57 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFailureCleanup, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 94, szObjectName = Cluster Group, dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFailureCleanup, ePhaseType = ClusterSetupPhaseContinue, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 94, szObjectName = Cluster IP Address, dwStatus = 0x0 )
[2014-02-11T14:35:19] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFailureCleanup, ePhaseType = ClusterSetupPhaseContinue, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 94, szObjectName = 3S-MBX1.3s.com.tn, dwStatus = 0x0 )
[2014-02-11T14:35:22] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFailureCleanup, ePhaseType = ClusterSetupPhaseContinue, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 94, szObjectName = EDAG, dwStatus = 0x0 )
[2014-02-11T14:35:22] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFailureCleanup, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 94, szObjectName = , dwStatus = 0x0 )
[2014-02-11T14:35:22] The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-02-11_14-35-14.226_add-databaseavailabiltygroupserver.log".
[2014-02-11T14:35:22] WriteError! Exception = Microsoft.Exchange.Cluster.Replay.DagTaskOperationFailedException: A server-side database availability group administrative operation failed. Error The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"CreateCluster() failed with 0x57. Error: The parameter is incorrect"' failed.. ---> Microsoft.Exchange.Cluster.Replay.AmClusterApiException: An Active Manager operation failed. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"CreateCluster() failed with 0x57. Error: The parameter is incorrect"' failed. ---> System.ComponentModel.Win32Exception: The parameter is incorrect
--- End of inner exception stack trace ---
at Microsoft.Exchange.Cluster.ClusApi.AmCluster.CreateExchangeCluster(String clusterName, AmServerName firstNodeName, String[] ipAddress, UInt32[] ipPrefixLength, IClusterSetupProgress setupProgress, IntPtr context, Exception& failureException, Boolean throwExceptionOnFailure)
at Microsoft.Exchange.Cluster.ClusApi.ClusterFactory.CreateExchangeCluster(String clusterName, AmServerName firstNodeName, String[] ipAddress, UInt32[] ipPrefixLength, IClusterSetupProgress setupProgress, IntPtr context, Exception& failureException, Boolean throwExceptionOnFailure)
at Microsoft.Exchange.Cluster.Replay.DagHelper.CreateDagCluster(String clusterName, AmServerName firstNodeName, String[] ipAddresses, UInt32[] netmasks, String& verboseLog)
--- End of inner exception stack trace (Microsoft.Exchange.Cluster.Replay.AmClusterApiException) ---
at Microsoft.Exchange.Cluster.Replay.DagHelper.ThrowDagTaskOperationWrapper(Exception exception)
at Microsoft.Exchange.Cluster.Replay.DagHelper.CreateDagCluster(String clusterName, AmServerName firstNodeName, String[] ipAddresses, UInt32[] netmasks, String& verboseLog)
at Microsoft.Exchange.Cluster.ReplayService.ReplayRpcServer.<>c__DisplayClass40.<RpcsCreateCluster>b__3f()
at Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.RunRpcServerOperation(String databaseName, RpcServerOperation rpcOperation)
--- End of stack trace on server (3S-MBX1.3s.com.tn) ---
at Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.ClientRethrowIfFailed(String databaseName, String serverName, RpcErrorExceptionInfo errorInfo)
at Microsoft.Exchange.Cluster.Replay.ReplayRpcClientWrapper.RunCreateCluster(AmServerName rpcServerName, String clusterName, AmServerName firstNode, String[] ipaddrs, UInt32[] netmasks, String& verboseLog)
at Microsoft.Exchange.Management.SystemConfigurationTasks.AddDatabaseAvailabilityGroupServer.FormCluster()
[2014-02-11T14:35:22] Updated Progress 'Done!' 100%.
[2014-02-11T14:35:22] COMPLETED
add-databaseavailabiltygroupserver explicitly called CloseTempLogFile().
<fieldset class="mimeAttachmentHeader"><legend class="mimeAttachmentHeaderName">ip-config.txt</legend></fieldset>
C:\Windows\system32>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : 3S-MBX1
Primary Dns Suffix . . . . . . . : 3s.com.tn
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : 3s.com.tn
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection
Physical Address. . . . . . . . . : 00-50-56-83-21-13
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 172.16.192.9(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.16.192.254
DNS Servers . . . . . . . . . . . : 172.16.192.6
172.20.10.21
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Ethernet 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection #3
Physical Address. . . . . . . . . : 00-50-56-83-22-C9
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.0.0.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter Local Area Connection* 11:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter
Physical Address. . . . . . . . . : 02-3D-2A-2B-56-56
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{E3787791-A3D8-43D2-97F5-C941B8532445}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{C041FA54-1E89-40DA-B8AE-ABE8DF80208E}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Hi,
Please check if cluster name object (CNO) setting is correct. Make sure you have pre-staged the CNO object if you are running Windows Server 2012 for the DAG members. When you add the first node to DAG, you should assign Full Control permissions to the CNO.
For more details about this, you can refer to the following article.
Pre-Stage the Cluster Name Object for a Database Availability Group
http://technet.microsoft.com/en-us/library/ff367878(v=exchg.150).aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2013 CU3 Databases only activate on one mailbox server

Hi, guys
I have two Exchange 2013 CU3 Mailbox servers installed, one DAG, 5 databases, each has one copy. I found that if I activated three databases on Mailboxserver1 or Mailboxserver2, then after a few hours, all databases will be activated on the mailbox
server which has three databases activated. All the databases can be activated on Mailboxserver1 or Mailboxserver2, and they work well. I disabled DAC mode for preventing Event 4133 and 4376. And it has the same problem if I enable DAC mode.
From the event log, I found the log when activate one database on another mailbox server, it is Event 3169:
Managed availability system failover initiated by Responder=OutlookMapiHttpDeepTestFailover Component=Outlook.
This caused the database activated on another server.
And I got the message from SCOM, like this:
Alert: Health Set unhealthy
Source: test-mbx - Outlook.Protocol
Path: test-mbx.contoso.local;test-mbx.contoso.local
Last modified by: System
Last modified time: 11/12/2013 5:15:46 AM Alert description: EMSMDB.DoRpc(Logon) step of OutlookRpcDeepTestProbe/DB-01 has failed against test-mbx.contoso.local proxying to test-mbx.contoso.local for [email protected].
Latency: 00:00:00.0320000
ActivityContext:
Outline: [30] EMSMDB.Connect(); [1][FAILED!] EMSMDB.DoRpc(Logon); Likely root cause: Momt
Details:
Error: Error returned in LogonCallResult. Error code = WrongServer (0x00000478)
Log: Mailbox logon verification
 EMSMDB.Connect()
 Task produced output:
 - TaskStarted = 11/12/2013
5:15:25 AM
 - TaskFinished = 11/12/2013
5:15:25 AM
 - ErrorDetails =
 - RespondingRpcClientAccessServerVersion
= 15.0.712.4012
Latency = 00:00:00.0303884
 - ActivityContext =
 EMSMDB.Connect() completed successfully.
 EMSMDB.DoRpc(Logon)
 Task produced output:
 - TaskStarted = 11/12/2013
5:15:25 AM
 - TaskFinished = 11/12/2013
5:15:25 AM
 - Exception = Microsoft.Exchange.RpcClientAccess.RopExecutionException:
Error returned in LogonCallResult. Error code = WrongServer (0x00000478)
 - ErrorDetails =
 - Latency = 00:00:00.0018801
 - ActivityContext =
 EMSMDB.DoRpc(Logon) failed.
 Task produced output:
 - TaskStarted = 11/12/2013 5:15:25 AM
 - TaskFinished = 11/12/2013 5:15:25 AM
 - Exception = Microsoft.Exchange.RpcClientAccess.RopExecutionException:
Error
States of all monitors within the health set:
Note: Data may be stale. To get current data, run: Get-ServerHealth -Identity 'test-mbx' -HealthSet 'Outlook.Protocol'
State Name
TargetResource HealthSet
AlertValue ServerComponent
NotApplicable OutlookMapiHttpDeepTestMonitor
Outlook.Protocol Unhealthy None
NotApplicable OutlookRpcDeepTestMonitor
Outlook.Protocol Healthy None
NotApplicable OutlookRpcSelfTestMonitor
Outlook.Protocol Healthy None
NotApplicable OutlookMapiHttpSelfTestMonitor Outlook.Protocol
Healthy None
NotApplicable PrivateWorkingSetWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol Healthy
None
NotApplicable PrivateWorkingSetError....rpcclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol Healthy
None
NotApplicable ProcessProcessorTimeWarning....ienta... microsoft.exchange.rpcclientacc... Outlook.Protocol Healthy
None
NotApplicable ProcessProcessorTimeError....clienta... microsoft.exchange.rpcclientacc... Outlook.Protocol Healthy
None
NotApplicable ExchangeCrashEventError....pcclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol Healthy
None
NotApplicable LongRunningWatsonWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol Healthy
None
NotApplicable LongRunningWerMgrWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol Healthy
None
This test is a cause that mailbox databases in DAG is doing failover to another server
Log Name: Application
Source: MSExchangeRepl
Date: 12.11.2013 4:49:46
Event ID: 3169
Task Category: Service
Level: Information
Keywords: Classic
User: N/A
Computer: test-mbx-2
Description:
(Active Manager) Database DB-01 was successfully moved from test-mbx.contoso.local to test-mbx-1.contoso.local. Move comment: Managed availability system failover initiated by Responder=OutlookRpcDeepTestFailover Component=Outlook.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
 <Provider Name="MSExchangeRepl" />
 <EventID Qualifiers="16388">3169</EventID>
 <Level>4</Level>
 <Task>1</Task>
 <Keywords>0x80000000000000</Keywords>
 <TimeCreated SystemTime="2013-11-12T00:49:46.000000000Z" />
 <EventRecordID>1606248</EventRecordID>
 <Channel>Application</Channel>
 <Computer>test-mbx-2.contoso.local</Computer>
 <Security />
</System>
<EventData>
 <Data>DB-01</Data>
 <Data>test-mbx.contoso.local</Data>
 <Data>test-mbx-1.contoso.local</Data>
 <Data>Managed availability system failover initiated by Responder=OutlookRpcDeepTestFailover Component=Outlook.</Data>
</EventData>
</Event>
I don't know why, anyone know what's the problem?
Thank you.
Nile Jiang- Please mark the post as answer if it answers your question.
http://www.usefulshare.com

Hi,
After deleting all the health mailboxes and restart
the Exchange Health Manager service, the health mailboxes are recreated successfullly, but when I check the outlook.protocol health, the OutlookRpcDeepTestMonitor or the OutlookMapiHttpDeepTestMonitor is still unhealthy. How can I fix it?
[PS] C:\Windows\system32> Get-ServerHealth -Identity 'MAILBOX1' -HealthSet 'Outlook.Protocol' | ft server,state,name,ale
rtvalue -AutoSize
Server state Name AlertValue
MAILBOX1 OutlookRpcDeepTestMonitor Healthy
MAILBOX1 OutlookMapiHttpDeepTestMonitor Unhealthy
MAILBOX1 OutlookRpcSelfTestMonitor Healthy
MAILBOX1 OutlookMapiHttpSelfTestMonitor Healthy
MAILBOX1 PrivateWorkingSetWarning....cclientaccess.service Healthy
MAILBOX1 PrivateWorkingSetError....rpcclientaccess.service Healthy
MAILBOX1 ProcessProcessorTimeWarning....ientaccess.service Healthy
MAILBOX1 ProcessProcessorTimeError....clientaccess.service Healthy
MAILBOX1 ExchangeCrashEventError....pcclientaccess.service Healthy
MAILBOX1 LongRunningWatsonWarning....cclientaccess.service Healthy
MAILBOX1 LongRunningWerMgrWarning....cclientaccess.service Healthy
Nile Jiang- Please mark the post as answer if it answers your question.
http://www.usefulshare.com

Performing Exchange Server patching & service pack for mailbox server without losing some data during the rollback ?

People,
I'd like to know how can I safely apply the Exchange Server service pack or cumulative update to the Mailbox Server role (no DAG) without losing some email during the downtime and rolling back the snapshot ?
Can I do the following:
1. Stop all of the Exchange Server services.
2. Disconnect the vNIC in Mailbox server
3. Take VM snapshot
4. Apply the Exchange Server service Pack / Cumulative Update or Windows Update
5. Reboot
6. Reconnect the vNIC, if the server back online again with no issue, commit / delete the snapshot, if not, then disconnect the vNIC followed by roll back.
would that be make sense or supported from both Vmware and Microsoft http://www.vmware.com/files/pdf/exchange-2010-on-vmware-support-and-licensing-guide.pdf ?
If yu have any other suggestion, please let me know here.
Thanks in advance.

Hey AlbertWT,
I'll start off by saying that I wouldn't do it. Microsoft is explicit that snapshots are not supported with Exchange when virtualized. See below (from Exchange 2013 virtualization: Exchange 2013 Help):
Some hypervisors include features for taking snapshots of virtual machines. Virtual machine snapshots capture the state of a virtual machine while it's running. This feature enables you to take multiple snapshots of a virtual machine and then revert the virtual machine to any of the previous states by applying a snapshot to the virtual machine. However, virtual machine snapshots aren't application aware, and using them can have unintended and unexpected consequences for a server application that maintains state data, such as Exchange. As a result, making virtual machine snapshots of an Exchange guest virtual machine isn't supported.
Even if we ignore the support statement on snapshots this is still not a good idea. Here are some things to consider.
1) Cumulative updates for Exchange make changes to the Active Directory Schema. Rolling back the snapshot on the Mailbox server will not roll back the changes to AD, which could cause functional and supportability issues. See this link to give you an idea of how there are AD schema updates in every Exchange CU and service pack: Exchange 2013 Active Directory schema changes: Exchange 2013 Help
2) It is possible for email to come in during the time that you're testing the update, and if you need to roll back you would need a plan to get that email back. Third party services could work, or you could prevent email from coming into your environment completely during that time, but those are not ideal solutions.
A far better solution would be to create a lab environment that is isolated from production. You could either take clones of your Exchange and AD VMs and put them into a network fenced environment, or create a lab and import your AD structure so it matches production. I think this is a far better way to test than trying to rely on snapshots in production.
Hope that helps!
Matt

Federated free busy information - the recipients mailbox server could not be contacted

Hi guys, really hoping someone can help with a free busy issue I'm having.
I've configured a new forest with exchange 2013 installed in preparation for moving all AD objects to the newly created forest to resolve a single label domain issue. The source forest has exchange 2010 SP2 installed. I've setup a trust between
the forests and dns is resolving okay. Federation has been setup for each of the forests and sharing configured but free busy info isn't available. When trying to retrieve FB from the new exchange 2013 mailboxes i get "the recipients mailbox
server could not be contacted" Trying to lookup FB from new forest to source "the recipients server could not be contacted" I've followed the troubleshooting steps in the following link: http://johanveldhuis.nl/en/troubleshooting-federared-sharing/
which are all okay except when I run Test-FederationTrust -UserIdentity [email protected] On the exchange 2013 forest all tests are successful, on the exchange 2010 forest all tests are successful with the exception of token request which
returns: failed to request validation token. Any help on this really appreciated

Just check the application log again and found this:
Process 5660: ProxyWebRequest FederatedCrossForest from S-1-5-21-672479773-2712238020-2201217990-2314 to
https://mail.contoso.com/ews/exchange.asmx/WSSecurity failed. Caller SIDs: WSSecurity. The exception returned is Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException:
System.Net.WebException: The request failed with HTTP status 401: Unauthorized.
 at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
 at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)
 at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)
 at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, Service service, IAsyncResult asyncResult)
 at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)
 at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling():. The request information is ProxyWebRequest type = FederatedCrossForest, url =
https://mail.contoso.com/ews/exchange.asmx/WSSecurity
Mailbox list = <<a href="mailto:[email protected]>SMTP:[email protected]">[email protected]>SMTP:[email protected], Parameters: windowStart = 27/01/2014 00:00:00, windowEnd = 10/03/2014 00:00:00, MergedFBInterval = 30, RequestedView = MergedOnly
. ---> System.Net.WebException: The request failed with HTTP status 401: Unauthorized.
 at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
 at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)
 at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)
 at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, Service service, IAsyncResult asyncResult)
 at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)
 at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling()
 --- End of inner exception stack trace ---
. Name of the server where exception originated: "MailServer". Make sure that the Active Directory site/forest that contain the user's mailbox has at least one local Exchange 2010 server running the Availability service. Turn up logging for the Availability
service and test basic network connectivity.

Mailboxes reference old mailbox server name

Exchange 2010 SP2 RU7
We are preparing to decommission one of our mailbox servers in a DAG and it currently contains no mailboxes or database copies. However, when we run get-mailbox -server OLDSERVER there seems to be a few mailboxes that still reflect this server in their
ServerName and ServerLegacyDN attributes. The Database value for every one points to the correct database, which does not have a copy on OLDSERVER (but used to as of last week).
We haven't gotten any reports of user issues, and all databases have the CAS array as the RPC Client Access Server. Should these values eventually update on their own? Exchange is still running on OLDSERVER - should these values be manually updated prior
to decommission?
Running an Update-Recipient on a few of these mailboxes had no effect. All Exchange services have been restarted on OLDSERVER.

Did some more digging, and the Server attribute seems to pull from homeMTA and ServerLegacyDN attribute from msExchHomeServerName.
Looks like these attributes are not used by 2010 any more:
http://blogs.technet.com/b/timmcmic/archive/2011/09/26/exchange-2010-homemta-and-msexchhomeservername-are-not-updated-on-mailboxes.aspx

Recommended number mailbox server exchange 2010

Hello,
What are the number of recommended mailbox server needed for 9000 mailbox of 1Go size and 2 copies/DAG ?
Regards

Hi,
It's hard to give a recommended number of Mailbox servers, it's based on your environment.
If you want to deploy a DAG, you need to have at least two Mailbox servers.
Here are two related articles about Mailbox Server planning and performance for your reference.
http://technet.microsoft.com/en-us/library/ee712771(v=exchg.141).aspx
http://technet.microsoft.com/en-gb/library/dd346701(v=exchg.141).aspx
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

When does a work cycle on a mailbox server actually start in Exchange 2010/2013?

So the question came up in work today as to when a work cycle on a mailbox server (e.g. ManagedFolderWorkCycle) actually starts. For example if it's set for 7 days, what 7 days does it choose? Is the first day the day the server was last
restarted? Or is it the day the MSExchangeMailboxAssistants service was restarted? Is there some set day and hour considered the start? Or something else i'm not thinking of? I've checked various technet
library articles but it doesn't state how the exact start date and time is derived.

Hi Iczersigma,
According to your description, it seems ManagedFolderAssistantSchedule
that Ed mentioned is the great method to specify the date of service restarting. And I notice that this parameter also used in both Exchange 2010 and Exchange 2013, not only for 2010 RTM.
Detailed information about this parameter as below:
The ManagedFolderAssistantSchedule parameter specifies the intervals each week during which the Managed Folder Assistant applies messaging records management (MRM) settings to managed folders. The format is StartDay.Time-EndDay.Time. You can use the following values for the start and end days:
•Full name of the day
•Abbreviated name of the day
•Integer from 0 through 6, where 0 = Sunday
The start time and end time must be at least 15 minutes apart. Minutes are rounded down to 0, 15, 30, or 45. If you specify more than one interval, there must be at least 15 minutes between each interval.
The following are examples:
•"Sun.11:30 PM-Mon.1:30 AM"
•6.22:00-6.22:15 (The assistant will run from Saturday at 10:00 PM until Saturday at 10:15 PM.)
•"Monday.4:30 AM-Monday.5:30 AM","Wednesday.4:30 AM-Wednesday.5:30 AM" (The assistant will run on Monday and Wednesday mornings from 4:30 until 5:30.)
•"Sun.1:15 AM-Monday.23:00"
If the managed folder assistant doesn't finish processing the mailboxes on the server during the time that you've scheduled, it automatically resumes processing where it left off the next time it runs.
For your reference:
http://technet.microsoft.com/en-us/library/aa998651(v=exchg.150).aspx
http://technet.microsoft.com/en-us/library/aa998651(v=exchg.141).aspx
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Mailbox server Removed

Similar Messages

Maybe you are looking for