New-item -ItemType file -path $DBcopyReport1 -force | out-null $DBcopyReport2 = "C:\DBs\ps\$filename.ps1" $DBcopyReport1 = "C:\DBs\bt\$filename.bat" Write-host -f red "Following Databases are in failed state"
Get-MailboxDatabaseCopyStatus $strResponse |? In the normal process, reseeding happends on the single database at a time and you can’t limit how many database you can reseed at a time.
EXCHANGE 2010 POWERSHELL CODE
It tries to take corrective action if the database goes out of sync else administrator may have to fix failed database manually.īelow is the nice piece of code which will request you to enter the DAG Name and it will determine the list of failed database and perform full reseed on each of the failed database. Replication service running on the host machine is responsible for keeping the database in healthy state. There can be various reason for database to fail. When Database goes in failed state or failed and suspended state or database Index goes in to failed state then it needs administrator intervension and force the database reseed. Passive copies can be a failed database or failed Index. Hope this will help people in troubleshooting in their respective environments.Īlso I would like to mention that this activity can be done from the GUI as well.Īll you have to do is open Exchange Management Console, click on the Toolbox section on the left pane and select Message Tracking link.Reseeding is a process of fixing the failed passive copy of the database which basically mean is, the passive database copy is out of sync with active database. Get-Messagetrackinglog -Recipients: -EventID “RECEIVE” -Start “ 9:00:00 AM” -End “ 5:00:00 PM” | Format-Table Timestamp, Source, Sender, Recipients, MessageSubjectĮverything remains same from our previous command, but only the -EventID parameter will change as we want emails that were delivered to the recipient email address.
Then we provided the parameter called -EventID, in our case we wanted the mails that did not deliver, hence the value FAILįinally we formatted the output in table to make it look nice and clean.Ĭondition 2: Get all emails that were successfully received by the recipient email address. Get-Messagetrackinglog -Recipients: -EventID “FAIL” -Start “ 9:00:00 AM” -End “ 5:00:00 PM” | Format-Table Timestamp, Source, Sender, Recipients, MessageSubjectįirst parameter that we provided was the -Recipients, you can provide a valid email address or mail enabled distribution list here. This can also be used if you have multiple Hub transport Servers in your environment.Ĭondition 1: Get all emails that failed or were undelivered. If not, then type Get-TransportServer and pipe it to the rest of the command. Note: Make sure that you typing this commands from the Hub transport Server. Our main concern here is find out that whether emails are being sent successfully or not to mailbox in question. Now, coming to the Powershell cmdlet that will help us with tracking whether the mail is delivered to mailbox is Get-MessageTrackingLog This role is responsible to make sure that all the mails are sent to their respective mailboxes internally as well as external emails. But first, let me tell you that Hub Transport Server role is one of the five distinct roles in Exchange Server 2010. Today I ran across a requirement where in I had to find out whether the emails generated from one mailbox were getting delivered to the recipient mailbox successfully or not.Īs you must be aware that all the mails that are sent or received in an Exchange organization has to be routed from the Hub Transport Server.
0 kommentar(er)
