Posts tagged ‘exchange 2013’
Unable to move mailboxes via ECP/EAC
When you are migrating from Exchange 2013 to Exchange 2019 you may notice that you are not able to migrate the mailboxes from the Exchange 2013 to Exchange 2019 via the EAC.
The workaround in this situation is to use the New-MoveRequest or New-MigrationBatch Exchnage Powershell commands. Even though , when you these commands the move request may fail in some cases and may not appear in the EAC. You could refer MS articles on how to create the CSV for migration batches and use it with these command line tools.
In breif:
- Create a CSV file using the EAC
Then modify the CSV file as below:
Run the below commands to initiate the migration and get the statistics
New-MigrationBatch –Name –CSVData ([System.IO.File]::ReadAllBytes(“”)) –Local –TargetDatabase
Get-MigrationUser | Get-MigrationUserStatistics
Let’s go back to the original problem and let’s see how can we fix it. You need to find out the System Mailboxes (especially the Migration mailbox) from the older version of Exchange server and transfer it to a database in the newer version of exchange.
Get-Mailbox -Server “OLD Exchange Server ” -Arbitration | New-MoveRequest -TargetDatabase “”Database in the Newer Exchange”
That’s it you can happily use the EAC to migrate the mailboxes.
The public folder database ‘Public Folder Database 0206806109″ cannot be deleted
If you are migrating from an earlier version of Exchange to a newer version , you may come across a situation where you are not able to decommission the old exchange server due to the inability to delete the Public Folder databases with the below error message.
Public Folder Database 0206806109
Failed
Error:
The public folder database “Public Folder Database 0206806109” contains folder replicas. Before deleting the public folder database, remove the folders or move the replicas to another public folder database. For detailed instructions about how to remove a public folder database, see http://go.microsoft.com/fwlink/?linkid=81409&clcid=0x409.
You may opt to use the ADSI edit to forcibly delete the Public folder. But , I would not recommend this approach as the ADSI Tool there is no error check or validation is performed.
You can use the below powershell commands to safely delete the replicas of the remaining Public folders and System public folders after ensuring all the needed Public Folders are migrated to the new exchange servers.
Get-PublicFolder-ServerExch-2010 "\NON_IPM_SUBTREE"-Recurse-ResultSize:Unlimited | Remove-PublicFolder-ServerExch-2010-Recurse-ErrorAction:SilentlyContinue
Now you could remove the Publice folder dataabsae
Remove-PublicFolderDatabase “Public Folder Database 0206806109”
Source:https://blog.rmilne.ca/2020/09/30/unable-to-remove-exchange-2010-public-folder-database/
How to recover from FWS and DAG Member failure in 2 Node DAG
Hi Folks
Recently we had a situation where one of our customer was affected with a malware and most of his servers became unusable. The impact caused the File Witness Servers( a Domain Controller) and one of the Exchange Node from the 2 Node DAG environment to become instable.
So after studying the impact we decided to do the below ;
- Remove the Failed Node from the DAG and rebuild it from scratch and attach it to the DAG again.
- Change the FWS to another server.
But unfortunately we were not able to proceed as we expected because the cluster service on the remaining node was not able to reach any cluster defined. When I opened the Failover Cluster Manager I was not able to reach or connect it to the DAG Cluster (As it was not able to reach any the Quorum in our case it is the FWS. The same was confirmed by the below command:
- cluster node
This will show the failed node as down and the survived DAG node in Joining state
To overcome the problem you have to restart the cluster without quorum to do that type the below command on the Exchange server
net stop clussvc
net start clussvc /fq
Boom .. everything returned normal with Windows Clustering on the remaining node ( you could verify it with the same command ; cluster node) . I was able to connect it to the DAG cluster via the Windows Clustering Manager.
Now the cluster is restored and I had to move the FWS to another server so I ran the command below which set the new FWS ( Source: https://practical365.com/exchange-server/recovering-a-failed-exchange-2016-database-availability-group-member/)
Set-DatabaseAvailabilityGroup -Identity “DAG-Name” -WitnessDirectory c:\FWS -WitnessServer “New Server Name”
Now we were able to proceed with the remaining steps that is to
– remove the Mailbox Copies from the Failed Server
– Move the Active Mailboxes from the Failed Server to the active Server
The commands I used are
- Get-MailboxDatabaseCopyStatus -Server “Failed Exchange Server Name” | Remove-MailboxDatabaseCopy -Confirm:$false
- Move-ActiveMailboxDatabase “Mailbox Database Name” -ActivateOnServer “Exchange Server Name” -SkipHealthChecks -SkipActiveCopyChecks -SkipClientExperienceChecks -SkipLagChecks -MountDialOverride:BESTEFFORT
Thereafter you could proceed with the remaining steps as mentioned below;
To remove the failed server from the DAG (-ConfigurationOnly switch will execute the command without trying to contact the failed server)
- Remove-DatabaseAvailabilityGroupServer -Identity “DAG Name” -MailboxServer “Failed Exchange Server Name” -ConfigurationOnly
Thereafter you need to remove the failed server from the Cluster Group to do that;
- Get-ClusterNode “Failed Exchange Server Name” | Remove-ClusterNode
Once you are able to pass through all the steps , the only thing left is to rejoin the Failed Exchange Server to the same DAG. (Refer Article:https://practical365.com/exchange-server/recovering-a-failed-exchange-2016-database-availability-group-member/)
Hope this will help someone in a similar situation.
Good Luck
Muralee
How to perform a Local Mailbox Move Request on Exchange 2013
Dears
I have prepared the below screen cast to guide you through the steps of moving an Active Mailbox.
1) Create a new Move Request via Exchange Shell (Orange2 Mailbox has been moved to MailDB1 Database)
2) Initialize or Start the Move Request
3) Check the Status of the Request.
Exchange 2013 GRT Fails with Symantec Backup Exec 2014 SP1
Dear Folks
Recently we deployed Symantec Backup Exec 2014 V-Ray Edition and as per the Guidelines we installed the Agent on Exchange Server(Single Server) and configured all the prerequisites as below;
1) Add the BackupExec User to the below groups
-
Public Folder Management
-
Recipient Management
- Server Management
2) Enter the below commands in Powershell
new-RoleGroup -Name BackupExecRoles -Roles @(“Database Copies”, “Databases”, “Exchange Servers”, “Monitoring”, “Mail Recipient Creation”, “Mail Recipients”, “Recipient Policies”, “Mail Enabled Public Folders”, “Public Folders”)
Add-RoleGroupMember -Identity BackupExecRoles -Member BackupExecUser
3) This is for GRT
New-ManagementRole -Name “SymantecEWSImpersonationRole” -Parent ApplicationImpersonation
New-ManagementRoleAssignment -Role “SymantecEWSImpersonationRole” -User BackupExecUser -Name “BackupExecUser-EWSImpersonation”
New-ThrottlingPolicy -Name “SymantecEWSRestoreThrottlingPolicy” -EwsCutoffBalance Unlimited -EwsMaxBurst Unlimited -EwsMaxConcurrency Unlimited -ExchangeMaxCmdlets Unlimited -MessageRateLimit Unlimited -PowershellCutoffbalance Unlimited -PowershellMaxBurst Unlimited -PowershellMaxCmdlets Unlimited -PowershellMaxConcurrency Unlimited -PowershellMaxOperations Unlimited -RecipientRateLimit Unlimited -ThrottlingPolicyScope Regular
Set-Mailbox -Identity BackupExecUser -ThrottlingPolicy “SymantecEWSRestoreThrottlingPolicy
Set-ThrottlingPolicyAssociation -Identity BackupExecUser -ThrottlingPolicy “SymantecEWSRestoreThrottlingPolicy”
4) Test EWS Connectivity for the BackupExec User
test-webservicesconnectivity -MailboxCredential $(get-credential) -TrustAnySSLCertificate | FL
It will produce a logon prompt, enter the backup exec user credentials it will output some html tags without an error.You may face an error in the Powershell in Exchange 2013 and you need to run the command shown in the output and enter a password , thereafter if you run the original command it will not reproduce the error.
After all the above steps you may face the below error during the restore
Assuming if you have done all the prerequisites correctly , you must try the below
1) Restart both the Backup Exec and the Exchange Server
2) Reconfigure the Backup Exec Job credential for the Exchange Server as below (This worked for us)
Domain Name\BackupExec User
Good Luck !!!
Hope you like it.. 