Comments on: Content Index State Healthy And Upgrading https://webbanshee.net/content-index-state-healthy/ Your Exchange Server Blog Tue, 25 Aug 2020 13:11:19 +0000 hourly 1 By: WebBanshee https://webbanshee.net/content-index-state-healthy/#comment-1004 Sun, 26 Aug 2018 19:43:54 +0000 http://webbanshee.net/?p=1654#comment-1004 In reply to ALAN.

Hello Alan ,

Thank you!
I appreciate your comment.

Have a nice day!
Sam

]]> By: ALAN https://webbanshee.net/content-index-state-healthy/#comment-1001 Sun, 26 Aug 2018 03:54:10 +0000 http://webbanshee.net/?p=1654#comment-1001 Awesome detail, after the upgrade yours is the only comment about how to track the update process…everyone else talks about its an error so thanks so much!!! LEGEND

]]> By: WebBanshee https://webbanshee.net/content-index-state-healthy/#comment-684 Sun, 13 May 2018 18:39:37 +0000 http://webbanshee.net/?p=1654#comment-684 In reply to MSMS_MSMS.

Hi ,
Nice to hear it helped. Thx for your comment.
We installed the CU first in our test environment. The difference was that there are only a few mailboxes in each mailbox database. The schema-update went through very fast.
So I couldn’t simulate the outcome in an authentic manner, when activating a database copy on an affected mailbox database. I found a lot of related stuff as well, helpful but as you say non of them gave me the peace of mind about what was really going on.
We needed a final vendor statement.

Bests
Sam

]]> By: MSMS_MSMS https://webbanshee.net/content-index-state-healthy/#comment-680 Fri, 11 May 2018 11:19:15 +0000 http://webbanshee.net/?p=1654#comment-680 Thank you for this information. It is the first time I noticed this happen after CU update, but the explanation sounds logical. I found a lot of references on Internet about this “problem”, but you are the only one that included information from Microsoft support.

]]>