Mailbox move and dag members

Hello,
Exchange 2010 sp3 ru6
windows 2008R2 enterprise
I have 2 servers in HQ and 1 servers in DR site - all members of DAG
MailboxServer1
MB1 5 databases - Active node - HQ
db1 950GB
db2 200GB
db3 100GB
MailboxServer2
MB2 5 databases - passive node - HQ
db1 950GB
db2 200GB
db3 100GB
DRMailboxServer1
MB3 5 databases - passive node - DR site
db1 950GB
db2 200GB
db3 100GB
db1 is 950GB large and contains 800 mailboxes. I am planning to move users from db1 to db2 and db3, to keep db1 from growing beyong 1TB.
When I start moving users, I understand it will generate transactions logs on the active node, and the same transaction logs also gets transfeered
to db2 and db3 depending on where the mailboxes are being moved to. Is my understanding correct ?
What other impacts will this have on other members of the dag ?
What are some best practices and gotchas, I should be looking for ?
Thanks!
JOe

Hi,
Agree with Willard. Although the source server logs the record deletions, which are small, the target server must write all transferred data first to transaction logs. If you generate 10 GB of log files in one day, and keep a three-day buffer of 30 GB,
moving 50 2-GB mailboxes (100 GB) would fill your target log LUN and cause downtime. In cases such as these, you may have to allocate additional capacity for the log LUNs to accommodate your move mailbox practices.
I recommend you move a percentage of user mailboxes on a nightly or weekly basis to different databases.
Here is a related article for your reference.
http://technet.microsoft.com/en-gb/library/ee832796(v=exchg.141).aspx
Best regards,
Belinda Ma
TechNet Community Support

Similar Messages

Mailbox move during DAG failover is stuck

I have a DAG setup on exchagne 2010. I had several mailbox moves going, some in progress and some queued. The destination mailbox database failed over to a different server. Now the inprogress and queued moves are stuck and I cant
suspend them. Any suggestions would be great.
Thank you

I have a DAG setup on exchagne 2010. I had several mailbox moves going, some in progress and some queued. The destination mailbox database failed over to a different server. Now the inprogress and queued moves are stuck and I cant
suspend them. Any suggestions would be great.
Thank you
At some point they should resume.
What does get-moverequeststatistics show for the status?
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Mailbox move requests remain in Queued status

My server is part of a two member DAG. DAG shows to be healthy. I have turned logging up to Expert level but no useful data is generated (only shows that the move request was created; no problems are indicated)
Server is Exchange 2010 SP 3

Hi,
Please check the database copy status under management tab on source database and target database. This can be that one or more of those databases you are moving mailboxes to has a failed or suspended copy and its failing the DataMoveReplicationConstraint
check.
Refer to this blog about Exchange 2010 Mailbox Moves and Mailbox Resiliency
http://blogs.technet.com/b/exchange/archive/2011/05/06/exchange-2010-mailbox-moves-and-mailbox-resiliency.aspx
In addition, please check the event log on the Client Access server running the instance of the Microsoft Exchange Mailbox Replication service that's processing the failed move request.
Best Regards.

Exchange 2010 mailbox moves get stalled

I am Experiencing an issue with Exchange 2010 SP3 UR2 two node DAG environment (server01 and server02). While moving mailboxes from old Exchange 2007 environment I get following errors.
Move for mailbox xxxxxxxxxxxx is stalled because DataMoveReplicationConstraint is not satisfied for the database 'MDB01' (agent MailboxDatabaseReplication). Failure Reason: Database does not satisfy constraint SecondCopy. Throttling completion as database copies
are falling behind.
Get-MailboxDatabaseCopyStatus informs me that server02 Copy and ReplayQueue length on the passive copy are getting big (from 10-500) while moving and the throttling will always pause the move for a while and then start again until it stops again because the
second copy is falling behind. This only happens when I move mailboxes to databases that have active copy of the database on my server01 and passive on server 02. If the active copy is moved to server02 and server01 is the passive copy this does not happen.
So this leads to a conclusion that there is something wrong with server02 replication from server01.
I've traced the replication network and there are no issues. What could be the reason that only the second node suffers from falling back during moves? I would not like to se the datamovereplicationconstraint value to none since this is the only Exhchange
2010 DAG environment where I am facing this issue and the replication should keep up while mailbox moves.

Hello,
" I would not like to see the datamovereplicationconstraint value to none". Do you mean you set
DataMoveReplicationConstraint to SecondCopy? If so, I recommend you use test-replicationhealth cmdlet to check all aspects of the replication and replay status.
Please check if you
configure a lagged database copy.
Please check if there is a witness server, and whether the witness is online.
If not, please set DataMoveReplicationConstraint to SecondCopy.
Besides, please check if there is any error in application log.
Here are some articles for your reference.
http://technet.microsoft.com/en-us/library/dd335158(v=exchg.150).aspx
http://blogs.technet.com/b/exchange/archive/2011/05/06/exchange-2010-mailbox-moves-and-mailbox-resiliency.aspx
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Exchange 2010 - 2013 Mailbox move - Syncing with no progress (Stalled?)

I'm in the process of moving mailboxes from Exchange 2010 to Exchange 2013, the major of the mailboxes have moved successfully, however I did not anticipate the additional space required by Exchange 2013 and ran out of disk space during the mailbox move,
and some mailboxes did not move successfully.
I have since added additional space but can't seem to get the remaining mailboxes to sync.
I have tried :
Rebooting
Clearing out migration batches and recreating
Stopping and resuming batches.
I see nothing helpful in the Migration log files.
2013-05-20T23:59:57.904Z,14,MigrationServicelet,Information,",827890ff-522d-4c13-9f42-96fbfefb57f4,,","Job type ExchangeLocalMove, status SyncStarting, result Working, length 0.2724593, job :827890ff-522d-4c13-9f42-96fbfefb57f4:ExchangeLocalMove:Staged:4::SyncStarting:2013-05-17
2:59:12 PM::"
When I download the report for one of the users I see this, but don't know what it means :
The job is currently stalled due to 'Content Indexing' lagging behind on resource 'CiAgeOfLastNotification(Mailbox Database 2065686096)'
For one of the other users the downloaded report only shows :
2013-05-16
2:11:18 PM '' created move request.
DWW
Additional Info: I followed the info located here in regards to creating the ContentSubmitters group:
http://www.bullspit.co.uk/2013/04/08/exchange-2013-content-indexing-during-migration/
My mailbox database currently has Content index state: FailedAndSuspended
I only have one database, I am not using DAG

I had already created the contentsubmitters and it helped with the speed of the mailbox moves. We have a SMB with >100 users and everything was working great, migrating from 2007 to 2013. If I had it to do over, maybe it would have been better
to go to 2010 on a 2008 R2 box but decided to jsut go straight to 2013 on a 2012 R2 server. But the one thing I REALLY wish I had to do over again is to allocate about 3 times more space to the drive that was to hold the mailbox database. Everything
was working so well until a mailbox was being moved - a batch of several, I was doing maybe 5 at a time for the larger mailboxes - the disk filled up. Also, before I realized what was going on, I ran some cmdlets thinking my receive connectors weren't
right. I recovered the database - at first it would not mount at all... but after eseutil /r and /p (and allocating more disk space) I could mount the database and open the mailboxes. But from then on, nothing is being received and if you send,
it goes to sent items - doesn't hang in outbox, but never goes anyhere except into a queue. I have MS support working on it and it's been escalated to the top. If they fix it I will try to post any helpful information I can learn from it. But one
lesson - I will read the planning and preparations documentation thoroughly from now on.
Oh, and also, I keep getting this message in the ECP when navigating to the Recipients>migration applet:
Cannot open mailbox /o=<Organization>/ou=Exchange Asministrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/CN=<yourExchangeserver>/cn=Microsoft System Attendant.
If you did the same thing, (and didn't hang yourself or jump in front of a speeding locomotive), you are stronger than I. Not that I have taken the path of the Samurai network admin or anything....
And if you were able to fix it, I am impressed and would love to know how you fixed this.
Thanks and best,
Sam

Time remaining for a mailbox move

Hi All,
I am using Primal form to monitor my mailbox moves and have the following script
$outputbox.text = get-moverequest| get-moverequeststatistics |Sort-Object PercentComplete -Descending | ft displayname, @{label=" % "; expression="percentcomplete"},@{l="Size";e={$_.Totalmailboxsize.ToString().SubString(0,($_.totalmailboxsize.ToString().IndexOf("MB")))}}
,@{l="Moved";e={$_.BytesTransferred.ToString().SubString(0,($_.BytesTransferred.ToString().IndexOf("MB")))}},@{l="Rate";e={$_.BytesTransferredPerMinute.ToString().SubString(0,($_.BytesTransferredPerMinute.ToString().IndexOf("MB")))}}
,statusdetail -AutoSize| Out-String
I would like to add another column that gives me an estimated remaining time for the move. I can do the maths easily enough but don't know how to write it as a simple script that could be added as an extra column in the form
Any ideas?
TIA
Andy

This will give you an idea of how this kind of scripting works. You copied things wrong and have not understood computer fields.
$outputbox.text = get-moverequest|
get-moverequeststatistics |
Sort-Object PercentComplete -Descending |
Format-Table displayname,
@{L=' % '; E={ $_.percentcomplete }},
@{L='Size(Gb)'; E={ $_.Totalmailboxsize.Value.ToGb().ToString('N2') }},
@{L='Moved(Gb)'; E={ $_.BytesTransferred.Value.ToGb().ToString('N2') }},
@{L='Rate(Gb)'; E={ $_.BytesTransferredPerMinute.Value.ToGb().ToString('N2') }},
StatusDetail -AutoSize |
Out-String
Study how to do "computed/calculated properties". Also look up how to use exchange large integer values.
http://msdn.microsoft.com/en-us/library/microsoft.exchange.data.bytequantifiedsize.aspx
http://technet.microsoft.com/en-us/library/ff730948.aspx
¯\_(ツ)_/¯

Mailbox Move Issues and Errors - Exchange 2010 to 2013

I'm trying to move mailboxes from 2010 to 2013, but I'm experiencing a lot of issues.
My move batches keep hanging (stalled) for minutes and hours on end, and I can't seem to keep them going consistently.
I have two DAG's, one for Archive boxes, and one for Primary mailboxes. Each DAG has three members with DB copies of each DB. The npdes and the clusters themselves are up and healthy. However, at random some of the DB's Content Index state will go to Failed
or SuspendedandFailed. At which point I force a catalog refresh and DB index update, and it goes to healthy.
I've created the "ContentSubmitters" AD group (and assigned it permissions), reset the Search and Host controller services on each server, and restarted the Replication service. I also deleted and recreated the Index for each DB prior to restarting
services. No dice. I've also already moved the system mailboxes over to the 2013 databases.
I'm also getting some "Transient" errors in the user move log, things like this:
Transient error ResourceUnhealthyException has occurred. The system will retry"
5/4/2014 8:43:55 AM [exmb1] The job encountered too many transient failures (60) and is quitting.
5/4/2014 8:43:55 AM [exmb1] Fatal error ResourceUnhealthyException has occurred.
Error: MigrationPermanentException: Warning: Target mailbox unlock operation was not replicated. If a lossy failover occurs after the target mailbox was unlocked, the target mailbox could remain inaccessible. Error details: The store ID provided isn‎'t an ID of an item. --> MapiExceptionNetworkError: Unable to open entry ID. ‎(hr=0x80040115, ec=0)‎ Diagnostic context: Lid: 45025 Lid: 45345 StoreEc: 0x80040115 Lid: 22894 Lid: 24942 StoreEc: 0x80040115
Any ideas would be appreciated!!!

Hi
I would suggest you to run the below command for this "My move batches keep hanging (stalled) for minutes and hours on end" issue and see the result
Get-MoveRequest -Identity "Mailbox Name" | Get-MoveRequestStatistics -IncludeReport | FL Report
Just check if the MRS health is fine by running the below command
Test-MRSHealth -Identity "CAS Server" -MonitoringContext $true | Export-CliXml "C:\temp\CAS_MRSHealth.xml" and look at the xml file to get more information
When I run the Test command against either of my CAS servers, I get: " 'EXCH1' does not have the right Exchange Server version or role required to support this operation."
Run i run that command against any of the mailbox servers, it completes and generates the XML file, but I'm not sure what I need to be looking for within that file.
The first command spits out a ton of data, here's a little excerpt:
5/5/2014 8:59:28 AM [exmb1] Transient error ResourceUnhealthyException has occurred. The system will retry
(2/60).
5/5/2014 9:00:02 AM [exmb1] The Microsoft Exchange Mailbox Replication service 'exmb1.contoso.com'
(15.0.847.31 caps:03FF) is examining the request.
5/5/2014 9:00:07 AM [exmb1] Connected to target mailbox 'Primary (072dc240-bd79-495c-b7f2-c571e8f910f2)',
database 'newmbi', Mailbox server 'Exmb1.contoso.com' Version 15.0 (Build 847.0).
5/5/2014 9:00:07 AM [exmb1] Connected to target mailbox 'Archive (812ee554-4a1e-4feb-b591-a435fcbdee16)',
database 'newarci', Mailbox server 'EXARC2.contoso.com' Version 15.0 (Build 847.0), proxy server
'EXARC2.contoso.com' 15.0.847.31 caps:1FFFCB07FFFF.
5/5/2014 9:00:07 AM [exmb1] Connected to source mailbox 'Primary (072dc240-bd79-495c-b7f2-c571e8f910f2)',
database 'exmbi', Mailbox server 'Chsexmb2.contoso.com' Version 14.3 (Build 181.0).
5/5/2014 9:00:08 AM [exmb1] Connected to source mailbox 'Archive (812ee554-4a1e-4feb-b591-a435fcbdee16)',
database 'Exarci', Mailbox server 'CHSEXARC1.contoso.com' Version 14.3 (Build 181.0)
5/5/2014 9:00:12 AM [exmb1] Request processing continued, stage LoadingMessages.
5/5/2014 9:00:36 AM [exmb1] Messages have been enumerated successfully. 6657 items loaded. Total size:
332.3 MB (348,411,982 bytes).5/5/2014 9:06:14 AM [exmb1] The long-running job has been temporarily postponed. It will be picked up
again when resources become available.

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--

Seed mailbox database copy through replication network (DAG members on different subnets in different sites)

Good afternoon
I currently operate a two node DAG in our primary site supporting one mailbox database. I plan to introduce a third DAG node in our datacenter which is in a different Active Directory site. Both current DAG members replicate over a dedicated replication
network to keep the traffic separate from the MAPI traffic. The third DAG member will also have a dedicated replication network adapter (of course, on a different subnet). Ideally I would like to seed the database at a time of my choosing, rather than at the
moment I add the mailbox database copy (I know how to achieve this), but I would like to specify which network the data replicates over.
According to the following (see below link) under the 'Seeding and Networks' section as my two DAG members will be on different subnets in different sites Exchange will make the decision to use the MAPI network adapters of the target and source server.
'If the source server and target server are on different subnets, even if a replication network that contains those subnets has been configured, the client (MAPI) network will be used for seeding.'
http://technet.microsoft.com/en-us/library/dd335158%28v=exchg.150%29.aspx
Am I able to force Exchange to use the replication network adapters of both source and target server when I initiate the seeding process? I have a 200+ GB mailbox database that will need to replicate over a 100Mbps internet connection to our secondary
site and I would like to keep that traffic to the replication network I have configured.
Any insight would be helpful.

Hi,
If you want to specify the networks for seeding, you can use the
Network parameter when running the
Update-MailboxDatabaseCopy cmdlet and specify the DAG networks that you want to use.
If you don't use the Network parameter, then the system uses the following default behavior for selecting a network to use for the seeding operation:
If the source server and target server are on the same subnet and a replication network has been configured that includes the subnet, the replication network will be used.
If the source server and target server are on different subnets, even if a replication network that contains those subnets has been configured, the client (MAPI) network will be used for seeding.
If the source server and target server are in different datacenters, the client (MAPI) network will be used for seeding.
So please use the Update-MailboxDatabaseCopy cmdlet with
NetWork parameter to specify which DAG network should be used for seeding.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Mobile and remote Outlook access do not work after mailbox move

We recently moved our mailboxes to a different datastore. We are not unable to access our mailboxes using our cell phones or Outlook remotely. testconnectivity.microsoft.com gives me a http 500 error for both the Exchange virtual directory and the RPC.
Any ideas?

Was this a migration to another version of Exchange or simply mailbox move from the same version of Exchange?

Mailbox Move from Exchange 2007 to Exchange 2013

I was surpprised to see that when I move mailboxes from exchange 2007 to Exchange 2013, that the mailbox being moved does not get disconnected during the move process (client Outlook connection). That is great news but supprising to me. I know
moving from 2010 - 2013 or 2013 - 2013 is a background process. Did something change with this recently or has it always been this way? Does the mailbox move flag inside the mailbox just jet ignored?
Thanks

When you do a mailbox move it stays connected during the initial sync. Once the initial sync is performed, there is another phase where it completes the mailbox move (basically updates some AD attributes) when this piece happens users will not be able
to access their mailboxes.
You can control this behavior by setting the SuspendWhenReadyToComplete
switch either by command line when creating the move request via the EMS
https://technet.microsoft.com/en-us/library/dd351123%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
Or if you are doing this via the the EAC select "Manually Complete the batch" option before starting the move.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

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

Mailbox Move ForceOffline Parameter

Hell all,
scenario: Exchange 2013 RTM CU3, Exchange 2013 SP1 DAG
I'm trying to find a way to speed up Mailbox moves (local - from the RTM to the DAG environment) and I've pretty much exhausted all options I am aware of (MRS parameters, TCP Chimney, RSS etc.).
The one thing I haven't tried is the ForceOffline parameter, but unfortunately this switch appears to be very poorly documented.
Does anyone have any experience doing mailbox moves in "offline mode"? Does it speed up the transfer? Are the mailboxes automatically put back in "online mode" after the move?
Thx in advance!
M.

Hi,
ForceOffline forces a mailbox move to be performed in offline mode, meaning the user will have no access to email during the mailbox move. There is no official article explaining that it speeds up the migration using ForceOffline parameter. Your understanding
will be appreciated.
What's more, after finishing the migration, users will have access to email. In other words, mailboxes put back in "online mode".
Hope my clarification can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Exchange 2013 Windows Server 2012 NLB and DAG on the same server

Hi all, I am installing Exchange 2013 infrastructure with two servers.
Both servers have the CAS and Mailbox roles.
For mounting on High Availability, will create a DAG.
Client Access I have no external Network Load Balancer.
I thought about installing the NLB servers in the DAG members, this could not be done before.
I do not know if in Windows Server 2012 and Exchange 2013
Can I install NLB on members of a DAG?
regards
Microsoft Certified IT Professional Server Administrator

Hi,
I’m afraid that WNLB and DAG cannot coexist in the same server. Because WNLB is incompatible with Windows failover clustering. If we're using an Exchange 2010 DAG and we want to use WNLB, we need to have the Client Access server role and the Mailbox server
role running on separate servers.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/ff625247(v=exchg.141).aspx
Thanks,
Angela Shi
TechNet Community Support

Exchange OWA Page Blank For Random Users After Mailbox Moves

We have three Exchange server. msexch1, msexch2, msexch3. msexch1 is currently offline. msexch1 and msexch have the CAS and MBX roles installed and are in a DAG. We moved all mailboxes from msexch1 to the other two servers. Since then we have users reporting
that when they logon to owa they get a blank page. The resulting url is owa/auth.owa. The domain we use is exchange.ourdomain.com. The fqdn of each exchange server is msexch2.ourdomain.com, etc. We use round robin dns for our exchange servers, therefore we
have two entries for exchange.ourdomain.com. For the purposes of this question lets say the ip of msexch2.ourdomain.com is 10.10.10.52 and msexch3.ourdomain.com is 10.10.10.53 and we have two entries in our dns for exchange.ourdomain.com, one for 10.10.10.52
and the other 10.10.10.53.
When a user experiences this issue I have found that when I ping exchange.ourdomain.com to determine which exchange server they are "connected" to; if I force them to use the other one they are then able to access owa just fine. For example, I
have a user whom is getting a blank page after they logon to owa. I ping exchange.ourdomain.com which returns 10.10.10.52 for an ip address, which tells me they are connected to msexch2.ourdomain.com. When I enter in the url https://msexch3.ourdomain.com/owa
to force them to logon using the other server, they are able to owa owa without any issues. When I use the url https://msexch2.ourdomain.com they receive a blank page after logon (as expected because this is the server they are trying to contact via dns exchange.ourdomain.com)
I have tried recreating both owa virtual directories which did nothing. I am at my wits end here and would greatly appreciate any assistance.

Hi,
According to your description, I understand that OWA get blank after move mailbox to another mailbox server, and you deploy DNS round robin in your environment.
If I misunderstand you concern, please do not hesitate to let me know.
It may be caused by OWA proxy cannot work correctly, please try below steps to double check:
1. Get a mailbox place in msexch3 and login OWA with
https://msexch3.ourdomain.com/owa.
2. Get other mailbox place in msexch2 and login OWA with
https://msexch3.ourdomain.com/owa.
If the steps 2 cannot proxy URL to https://msexch2.ourdomain.com/owa, it may be the key reason.
Please clarify the environment of your Exchange:
1. Which version are you used?
2. Check the authentication of OWA: Get-OwaVirtualDirectory | FL Identity,*URL*,*Auth*
OWA is configured to use integrated windows authentication on each virtual directory, and the external URL under is blank.
Also, please run below command to double check the health of Outlook Web App service:
Get-ServerHealth “msexch3” |?{$_.AlertValue –Eq “Unhealth”}
Thanks
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]
Allen Wang
TechNet Community Support

Mailbox move and dag members

Similar Messages

Maybe you are looking for