Unhealthy indexes

Hi @sanjay joshi，

According to my search ,the author of this script says “The script is designed for Exchange 2010 and 2013.” And other users have indicated that this error also exists with using this script in Exchange 2019 environments.

Therefore, we are not sure whether the error is caused by a mismatch in the script.

If possible, please provide the screenshot about it for our better research.

(In order to avoid the disclosure of your privacy, please remember to hide your personal information).

If your error is "database -unhealthy content index count" as shown in the image above, you could refer to the following steps to rebuild the database content index to see if the error persists：

1. Stop below Exchange Services :

Microsoft Exchange Search 

Microsoft Exchange Search Host Controller

2.       Go to the database location – Move the Catalog folder to a different location – Start the above services back.

Then check again if the server is healthy. Alternatively, you can run the following command directly to check whether the database content index is healthy：

Get-MailboxDatabaseCopyStatus -Server E16A | fl *index*

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread