- Scanning the email body for SPAM
- Scanning attachments for malware
- Storing contacts
- Managing calendar events and schedules
- Tracking tasks
- Managing and storing distribution lists
- & More!
Below is a list of important PowerShell commands that can be used when the ECP management console fails to respond and a reboot would cause additional inconveniences to users.
Important PowerShell Commands when Exchange ECP Quits Responding
If a user reports they cannot access their email, and after checking to make sure they are online and they are not struggling with a credential issue, verify the mailbox database they are a member of is mounted.
- From within Exchange Powershell, type: Get-MailboxDatabase -status | format-table Name, StorageGroup, Mounted, OnlineMaintenanceinProgress
If a database is dismounted, everyone whose mailbox is in that database will not have access to their email. Instead of rebooting Exchange for a single database, and therefore interrupting every user, try mounting the database first.
If users report they cannot search in their email, whether by sender, recipient or subject matter, check to make sure the index for that database is in a healthy state.
- From within Exchange PowerShell, type: Get-MailboxDatabaseCopyStatus
To fix an index currently in a failed state, stop both Exchange search services.
Once the services are stopped, remove the search index folder from within the affected database folder and restart the search services. This causes the search index for that database to be rebuilt.
NOTE: Do not perform these actions unless you are proficient with Exchange and have an up-to-date, working and tested backup solution.
As always, knowing more than one way to accomplish the same thing is the best way to save time and preserve efficiency!