DiscoverySearchMailbox has been corrupted and it is in an inconsistent state

DiscoverSearchMailbox {Guid} has been corrupted and it is in an inconsistent state. The following validation errors have occurred:

Warning:
The value of the property ‘RecipientTypeDetails’,536870912, is not defined in the Enum type ‘RecipientTypeDetails’.

==========================================

We will see the above two warnings while we plan for Migration from Exchange Server 2007 SP3 RU10 to Exchange Server 2013. This is a Common warning and it appears while opening EMC as shown  below.

Figure 1: Warning Message
Warning while opening EMC in 2007 server.

Figure 2: Warnings
No action is required since the mailbox is of higher version and the warning can be safely ignored.

Figure 3: Mailbox Details in 2013 EMS

In figure 3 the Mailbox is accessible and it is able to perform Discovery Search from Exchange Server 2013 for 2013 Mailboxes.

Conclusion : The above warnings can be safely ignored.

==========================================

Note:-

In my experience , I have seen that this issue occurs a clobber reinstallation where the administrator has manually removed the mail databases and the binary files. post which a ndw mbx server is clobbered on . This error happens because the homemdb attribute is not set on the mailbox.
This issue can be resolved by adding a DN of a mailbox on the homeMdb attribute. restart the msexchangeis service on the homemdb filed in adsiedit > domain> users > discovertsearchXXX.XXXX…..rt click on it . on the home mdb tab , you might get anSID value instead of the new mailboxes.
Change the homeMdb attribute to the DN of any active mailbox. restart the IS service.

Worst case scenario you might or reboot the server . ideally this should resolve the issue .

RCA tool .This generally happens when ,lets say 2ek10 is installed on top of the legacy mailbox server , in the org and the customer has done a manual uninstall all of exchange and has forgotten to mention the DN of the discoverysearchmailbox > please try to check the homeMDB attribute.If its a points to a SID, for the database.

Ideally it should show the DN of the any of the mailbox database..

restart the msexchangeIS svc and try to check if the discovery search mailbox shows up or not.

It should ideally work , but as an extreme alternative , delete the existing discoverysearchmailbox and run a setup.com /ps && setup.com /p ,

Exchange Server 2010 Disaster Recovery using Active Directory System State Backup

In this blog we will be learning the steps on how to recover Exchange Server 2010 if the Server Object is missing from Active Directory.

The steps described in this article would benefit small business customers with 50-100 user mailboxes. Single Exchange Server and Single Active Directory Domain.

Pre-requisites
Valid Active Directory System State Backup
Working knowledge on Active Directory and Its Backup
Directory Service Restore Mode Password
Good Understanding of Authoritative and Non-Authoritative Restore Terminology

ScenarioSingle Exchange Server 2010 SP3
Single Active Directory Domain
====================================
Recovery will succeed only if the following conditions are met
1) Valid Active Directory Backup Exists and it was fully tested.
2) Configuration Objects for Exchange Server has been deleted accidently using ADSIEDIT.
2) Exchange Server is intact without any changes (Member Server).
3) Exchange Services are up.
4) Valid Exchange Database Copy as a precautionary step.

Lets ExploreBefore Deletion

Figure 1: Clients Connected

Figure 2: Exchange Server 2010 is Online
====================================
After Deletions

Figure 3: Disconnected
In figure 3 the symptoms will show as Disconnected. As a first steps in troubleshooting we can start by looking at Exchange Services.

Figure 4: Services
In figure 4 one of the key important service for client connectivity “Microsoft Exchange Address Book” Service is stopped. When you try to start it will fail. Although other services are up and running. Some serious issues from Active Directory end.

Figure 5: EMC Error

Figure 6: EMS Error
In figure 6 EMS error clearly states that the server is missing and it says “Enter the server FQDN where you want to connect”.

Looking at the above error. It is obvious that some deletions has took place from Active Directory End. Lets see how to get the server back.

Please Note : The scenario is for Single Site with Single Exchange Server and Active Directory.====================================
Recovery
For restoring the backup I have used Windows Server Backup Feature.

Permission RequiredThe account must be a member of Domain Admins and Enterprise Admin

Login in to the Domain Controller and go to Start > Run > and type Msconfig as shown below.

Figure 7: msconfig

Figure 8: System Configuration
We have to boot the DC in Safe Boot “Active Directory Repair” mode.

Figure 9: Restart

Figure 10: DSRM Login
In figure 10 we are logging in with DSRM logging. Since it is a DC. Once recovery is completed we have to revert it to normal logging.

Figure 11: Windows Server Backup
In figure 11 we have two backups. We can select the latest one for minimal impact on end users as well as on server. Select Recover.

Figure 12: Getting Started

Figure 13: Available Backups

Figure 14: Recovery Type

Figure 15: Select Location
In figure 15 Original Location was selected since it’s a single DC. Also Non-Authoritative Restore option was selected.

Figure 16: Warning Alert

Figure 17: Select Automatically Reboot

Figure 18: Warning

Figure 19: Recovery Progress

The server will reboot automatically. Please follow instructions for logging in as shown in figure 10 above.

Figure 20: Successfully Completed

Now that the restore is completed time to login to the DC in normal mode. Please follow instructions to disable Safe Boot mode as shown in figure 7 and 8. The system will be rebooted. Post which login with Domain Admin Credentials.
Post logging in. Open ADSI Edit.msc tool as shown below.

Figure 21: ADSI Edit
Now that we are able to see Exchange Server Object. Its time to reboot the Exchange Server Box.

Figure 22: Exchange Services are up

Figure 23: EMC Opened

Figure 24: EMS Opened

And Finally Clients are Connected

Figure 25: Clients Showing Connected

Conclusion: System State backup plays an Important role. It is very important to perform a thorough check on System State Backup of a DC on a regular interval.

I hope it was helpful. Do share your thoughts or any comments and we will be more than glad to respond.

==================================

Transition from Exchange Server 2003 to Exchange Server 2010 – Part 3

Final part includes Moving mailboxes and Public folders and then decommissioning the last Exchange Server 2003 from the ORG.

Before replicating Public Folders please perform a complete database backup. Both online and offline copy.

Important : Never perform MoveAllReplicas operation. Although the option is available but it may turn to a catastrophe and you may end up losing data.

Go slow by adding replicas on each folders manually or you can follow the built in script available in Exchange Server 2010.

Run the below command to get the basic information. You have to run the command from Exchange Server 2010 Powershell window.

Figure 1 : Confirming PF replicas

To add the Public folder relicas follow the below commands.

Figure 2 : Setting the location

In figure 2 we have set the location for script folder, since it holds all the built in script.

Now run the below commands.

First to add the replicas on each folders.

• AddReplicatoPFRecursive.ps1 –TopPublicFolder “\FolderName” -ServerToAdd NewServerName

Second confirm by running the below command.

• Get-Publicfolder –recurse | fl name,replicas

Third Confirm if all folders are in sync. Post which remove replicas by running the following command.

• RemoveReplicaFromPFRecursive.ps1 –TopPubicFolder “\FolderName” –Server toRemove servername

Now again confirm the PF replica status.

Figure 3 : Replica status

Confirm with test mailbox if all is accessible including FB data.

Post confirmation delete the PF store in Exchange Server 2003. Login to ESM and right click PF database and select Delete.

F

Figure 4 : Deleting the PF Store

Figure 5 : Selecting the new PF Store.

In Figure 5 we are associating the PF store with the PF hierarchy.

Figure 6 : Click Yes

Figure 7 : Removal Succeeded

Figure 8 : PF Database not visible in ESM

Now that PF is replicated and PF database is removed completed. Its time to move the mailboxes.

Login to Exchange Server 2010 and open EMC. Navigate to Mailbox under Recipient Configuration.

Figure 9 : Move Mailbox

Figure 10 : Options

Figure 11 : Completion

Now Move OAB. To do that Navigate to Organization Configuration and select Mailbox > In the right hand pane select “Offline Address Book” tab.

Figure 12 : OAB

Right click the default OAB and select move.

Figure 13 : Move

In figure 13 select Browse

Figure 14 : Select Mailbox Server

Figure 15 : Move Completed

Figure 16 : Finish

Enable distribution mechanism. In 2010 we can have both PF and Web based.

Figure 16 : Changing the distribution.

Now its time to create connectors for sending and receiving emails from Internet.

Go to Organization Configuration and Select Hub Transport. In the right pane Select Send Connectors Tab

Figure 17 : Default Send Connectors

Click on New Send Connector on the Actions Pane.

Figure 18 : New Send Connector Wizard

Figure 19 : Address Space

Figure 20 : Network Settings

Figure 21 : Source Server

Figure 22 : Completion

Now its time to configure Default Receive Connector

Go to Server Configuration and Select Hub Transport

Figure 23 : Default Receive Connector Properties.

Under permission groups. Select as shown above.

Post which now its time to Decommission Exchange Server 2003. Before removing the server there are certain checks needs to be performed.

• Delete the RGC from Exchange Server 2010 Shell by running “Get-RoutingGroupConnector | Remove-RoutingGroupConnector”
• Delete both Domain Rus and Enterprise Rus. This can be done from ADSIEDIT.

Figure 24 : Delete Domain RUS and Enterprise RUS

Now we are at the final stage of Removing Exchange Server 2003.

Login to Exchange Server 2003 and Go to Control Panel. Add remove programs.

Select Microsoft Exchange.

Figure 25 : Wizard will open

Figure 26 : Component Selection

Figure 27 : Remove

Figure 28 : Summary

Figure 29 : Locate the Setup Disk or Setup file (mandatory)

Figure 30 : Successful

Transition Completed