Managing Database Content Index State

From time to time the search indexes on Database copies in Exchange 2010 will become corrupt.  This will prevent the Activation Manager in the DAG from being able to “fail” the active database to that copy.
 
You can determine if any DB Copies have a Content Index State of failed by running the following cmdlet in the Exchange Management Shell:
 

Get-MailboxDatabase | Get-MailboxDatabaseCopyStatus|where { $_.contentindexstate -like “failed” }

If any copies report as having a failed Content Index State, they will need to be repaired.
 
Mounted Databases cannot be updated with the Update-MailboxDatabaseCopy cmdlet.  All copies reporting as failed can be updated with this cmdlet:

Get-MailboxDatabase | Get-MailboxDatabaseCopyStatus|where { ($_.contentindexstate -like “failed”) -and ($_.status -ne
 “Mounted”) }| Update-MailboxDatabaseCopy -CatalogOnly

error launching exchange 2010 mgmt console

Error message: The attempt to connect using HTTPS protocol “KerberosfailedConnecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found.
resolution: IIS admin service wasn’t started. Started the service and problem was resolved

Customer can’t connect with Outlook Anywhere

Issue: Customer can’t connect with Outlook Anywhere from home without VPN
 
Synopsis: Customer was running Outlook 2007 with SP2. All the settings were right
 
Resolution: had TMG folks run URL test for the mobile 2010 CAS farm and found 3 EB servers that failed on OAB and RPC urls. The 3 servers were removed from the pool and problem was resolved

OutlookAnywhere on Outlook2007 getting logon prompts

Issue:  Outlook 2007 user gets logon prompt from outlook anywhere configuration
 Synopsis: In an exchange 2010/2007 co-existence scenario, where Exchange 2010 is handling all requests to mail.domain.com, some outlook 2007 customers may get persistent prompts to login. Note that not all outlook 2007 users
Resolution/workaround:  While in Outlook 2007, go to exchange proxy settings, and uncheck the checkbox (only connect to proxy servers that have this principal name in their certificate). download this document with the configuration All other settings remain the same

Exchange 2010 server unable to join the DAG

Issue: Exchange 2010 server unable to join the DAG
Cause: IPV6 wasn’t fully disabled via registry. Also, DNS was configured for the replication NIC
Resolution: Disable DNS configuration for replication NIC so that it doesn’t register in AD DNS. Properly disable IPV6 in the registry by doing this:


Launch Regedit.exe

Go to HKLMSystemCurrentControlSetServicesTCPIP6Parameters and Create a new DWORD value named DisabledComponents

Edit DisabledComponents to have a Decimal Value of 4294967295

Reboot the server. When the server comes up, try adding the server to the DAG