Quick tip: If you have a DAG with a ContentIndexState showing failed, you can fix it with a simple command in the Exchange Management Shell (EMS): Update-MailboxDatabaseCopy -Identity “DAGNAME\store” -CatalogOnly This will then start a re-seed and it should return to a healthy state once complete. Advertisements
Ever wanted to quickly find all mailboxes and view the mailbox rights for each of those? Now you can with a PowerShell command that will show it to you. Here is the command below: ForEach($mailbox in (Get-Mailbox)) { Get-MailboxFolderPermission -Identity “$($mailbox):\calendar” | fl Identity,AccessRights,FolderName } There you have the output, I only have 3 accounts […]
Here is a quick tip on how you can check the health of your server that is part of a database availability group (DAG). The command to run is as follows using the Exchange Management Shell (EMS): Test-ReplicationHealth -Identity <ServerName> Below is the 2010 one: and now for the Exchange 2016 one: If there is […]
Removing an Exchange Database copy or a database should not be hardwork, especially when it can be done with the Exchange Management Shell. **Take note, if you have circular logging enabled, you need to firstly disable it before you can remove an Exchange database copy** To remove a mailbox database copy, you can run the […]