John Yassa's Blog

Home » Exchange 2013

Category Archives: Exchange 2013

HOW TO RESTORE THE EXCHANGE DATABASE FROM A BACKUP FILE IN STATE OF INCONSISTENCY?

How to Restore the Exchange Database from A Backup File in state of inconsistency?

For restoring the database on Exchange Server, the user needs to have an up-to-date and usable backup in hand, because an incomplete or even no backup can create a troublesome situation during the database the process of restoration. Additionally, Microsoft Information Store needs to be in a healthy state to mount the database successfully.

With an unmounted Exchange Store, the users face several issues such as restricted access to the data and the mail flow. In order to smoothly restore your database on Exchange Server, it is important to perform certain tests to verify the database consistency.

Pre-assessment Phase: Verify the State of the Database on Exchange

Use the following steps to verify the state of the database:

  1. Launch a command prompt.
  2. Move to the Drive:\Program Files\Exchsrvr\Bin

(The default location of the of Exchange 2000 Server program files are located in this folder)

 

Move to Drive:\Program Files\Microsoft\Exchange Server\V15\Bin

(When using Exchange 2013/2016, then use the above-mentioned default path)

 

  1. Enter the below-mentioned command:

eseutil /mh “drive:\program files\exchsrvr\mdbdata\database_name.edb”

Note: The default location of database files is on this Drive:\Program Files\Exchsrvr\MDBDATA folder. The public database file can be found with the name: “Public.edb”, whereas the mailbox store database file can be found with the name: “Priv1.edb”.

  1. Read the Output, in order to verify the state of the database. If the database appears in the state of inconsistency, then the output will appear, as:

State: Dirty Shutdown

Restoration Phase: How to Restore the database from a backup file

Upon using the pre-assessment phase, if the database appears in a consistent state, then simply restore the backup using the file.

Steps to Restore Database in A Consistent State:

Implement the following steps to restore the database from the backup file.

  1. Transfer the E00.log file to an another path or simply rename it.

The default location of E00.log file can be found on this Drive:\Program Files\Exchsrvr\MDBDATA folder.

  1. Restore the storage group and the log files from the backup file.

Note: Do not remove the existing log files, until you have performed the restore operation. Upon completing the restore operation, the log files are restored, and replay inside the restored database. This is how, the user can bring the database into a consistent state without involving the E00.log file.

  1. Once the storage group is restored, you can successfully mount the databases in the storage group.

Steps to Restore Database in an Inconsistent State:

  1. Launch the command prompt.
  2. Reach to the location – Drive:\Program Files\Exchsrvr\Bin folder.
  3. Enter the following command in the command prompt:

eseutil /p “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”

  1. To use the database in a productive environment, try to defragment and then rebuild the database. Use the below mentioned command to proceed:

eseutil /d /t:x “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”

Note: ‘x’ is a temporary drive location in the above-mentioned command.

  1. To determine the state of the database, enter the following command, and then read the output:

eseutil /mh “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”

When database is consistent, the output will appear, as:

State: Clean Shutdown

  1. Use the Microsoft’s Store Integrity utility (Isinteg.exe) to fix the logical corruption issues in the database. Use the following commands to repair it:

Isinteg –s exchange_server_name –fix –test alltests

After executing the command, the user is prompted to choose the database in the utility. Repeat the aforementioned command until no errors or fixes are appeared in the output.

However, if zero errors are not displayed for a database that  you want to repair, then the other option is to rebuild the database. To do that create a new mailbox store on either the existing Exchange server or new server and then transfer all the mailboxes to that one. However, if you are still unable to create a new mailbox store, then try to rebuild the database from the following method. To do it, try to export all mailbox information to PST files, and delete the database, and finally import the data.

  1. Repeat the steps from 3 to 6 for each database in the storage group.
  2. Mount the databases.

Once the database is restored and you can also perform an online backup of the storage group. However, if the database is not restored or rebuilt in the state of inconsistency, then try using a third-party Exchange recovery software like Kernel for Exchange Server to perform accurate recovery of lost information from corrupt EDB and STM files, and without requiring log files. The Exchange mailbox items can be successfully restored to live Exchange Server, Office 365 mailbox or to Outlook PST files.

https://www.kerneldatarecovery.com/exchange-server-recovery.html

Article Summary:

When Exchange database creates mounting troubles, then try to investigate the issues hampering the restore operation. Verifying the shutdown state (whether consistent or inconsistent) of the database becomes important, and Eseutil can be helpful in this scenario, but with certain restrictions.

Notice about certificate expiration for Exchange 2013 Hybrid customers (MUST be completed before 4/15/2016)

If you’re running Exchange 2013 and you’ve configured a hybrid deployment with Office 365, this post contains important information that might impact you. Please evaluate this information and take any necessary action before April 15, 2016. If your latest run of the Hybrid Configuration Wizard was initiated from Exchange 2010 than you are NOT affected.

On April 15 2016, the Office 365 TLS certificate will be renewed. This certificate is used by Office 365 to provide TLS encryption between Office 365 and external SMTP servers. The new certificate, which will help improve the security of mail sent to and from Office 365, will be issued by a new Certificate Authority and it will have a new Issuer and Subject.

This change has the potential to stop hybrid mail flow between Office 365 and your on-premises Exchange servers if one of the following conditions applies to you:

  • Your on-premises Exchange servers are running Exchange 2013 Cumulative Update 8 (CU8) or lower.
  • You’ve upgraded the Exchange 2013 servers that handle hybrid mailflow to Exchange 2013 CU9 or higher. However, since upgrading to CU9, you HAVE NOTre-run the Hybrid Configuration wizard (either from the Exchange Admin Center or via the direct download link).

How to keep hybrid mail flowing (MUST be completed before 4/15/2016)

Let the new Hybrid Configuration wizard do it for you

You can use the latest Hybrid Configuration wizard (HCW) to configure your Exchange 2013 servers to work with the new TLS certificate. Just follow these steps:

  1. If the Exchange 2013 servers handling hybrid mail flow are running Exchange 2013 CU8 or lower, follow the instructions in Updates for Exchange 2013 to install the latest cumulative update on at least one server.
  2. After you install the latest cumulative update, download the new HCW application and run the wizard following the instructions here .
Manual update

If you can’t upgrade Exchange 2013 to latest cumulative update right now (although we would like to remind you of our support policy), you can manually configure your servers to work with the new TLS certificate. On each Exchange 2013 server that’s used for hybrid mailflow, open the Exchange Management Shell, and run the following commands:

$rc=Get-ReceiveConnector |where {$_.TlsDomainCapabilities -like “*<I>*”}

Set-ReceiveConnector -Identity $rc.Identity -TlsDomainCapabilities “mail.protection.outlook.com:AcceptCloudServicesMail”

Source: The Exchange Team Blog

Understand and Control AutoDiscover methods for Outlook

Did you ever ask yourself how Outlook connects to your servers

Outlook uses AutoDiscover service to connect to Exchange online or you on premise Exchange

In some scenarios, you may want to control the methods that are used by Outlook to find the AutoDiscover service. This depends on the client/server topology, but these are the methods that are used by Outlook:

SCP lookup
HTTPS root domain query
HTTPS AutoDiscover domain query
HTTP redirect method
SRV record query

By default, Outlook uses one or more of these methods to reach the AutoDiscover service. For example, for a computer that is not joined to a domain, Outlook tries to connect to the predefined URLs (for example, https://autodiscover.contoso.com/autodiscover/autodiscover.xml) by using DNS. If that fails, Outlook tries the HTTP redirect method. If that does not work, Outlook tries to use the SRV record lookup method. If all lookup methods fail, Outlook cannot obtain “Outlook Anywhere” configuration and URL settings.

 

Lets understand the 5 methods that outlook uses:

SCP lookup
Outlook performs an Active Directory query for Service Connection Point (SCP) objects.

Root domain query 
Outlook uses the root domain of your primary SMTP address to try to locate the AutoDiscover service. Outlook tries to connect to the following URL based on your SMTP address: https://<smtp-address-domain>/autodiscover/autodiscover.xml

AutoDiscover domain Query
Outlook uses the AutoDiscover domain to try to locate the AutoDiscover service. Outlook tries to connect to the following URL based on your SMTP address: https://autodiscover.<smtp-address-domain>/autodiscover/autodiscover.xml
HTTP redirect
Outlook uses HTTP redirection if Outlook cannot reach the AutoDiscover service through either of the secure HTTPS URLS:
https://<smtp-address-domain>/autodiscover/autodiscover.xml
https://autodiscover.<smtp-address-domain>/autodiscover/autodiscover.xml

SRV record query
Outlook uses an SRV record lookup in DNS to try to locate the AutoDiscover service.

 

Now how can you control these methods

You can do this and enable/disable these methods for outlook through registry keys

Outlook 2010 :
HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover

Outlook 2013 :
HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\AutoDiscover

Outlook 2016:
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover

You can change the various options from the registry file as well. They are:

“ExcludeScpLookup”=dword:00000001
“ExcludeHttpsRootDomain”=dword:00000000
“ExcludeHttpsAutoDiscoverDomain”=dword:00000000
“ExcludeHttpRedirect”=dword:00000000
“ExcludeSrvRecord”=dword:00000000

Above the SCP lookup is disabled.

 

Source : Support Article , DISABLE AUTODISCOVER METHODS IN OUTLOOK 2013

 

 

 

This mailbox exceeded the maximum number of corrupted items that were specified for this request

While trying to migrate mailboxes to Office 365 within a Hybrid configuration, we have run across this error:

This mailbox exceeded the maximum number of corrupted items that were specified for this request”

 

The default number of ‘corrupted items’ or ‘large items’ is 10 per mailbox. Once this is reached,  the migration will fail.

You can overcome this problem by 2 ways:

1- Run the migration from the Office 365 portal:

  1. Open the Office 365 portal and browse to the Exchange Admin Center
  2. choose Recipients
  3. Then choose Migration
  4. Then press press on the + sign
  5. Choose migrate to Exchange Online then press next as below1
  6. Choose Remote move migration then next
    2
  7. Then select the users you want to migrate , press the  + sign
    3
  8. Search for the user ,choose it then press ADD
    4
  9. In the next page , just press next
    5
  10. Choose the name of this migration
  11. Choose the domain , by default it will be domainame.mail.onmicrosoft.com
  12. You can move the mailbox and its archive or only move the archive
  13. Then you can decide the number of the Bad Item and the large item limits
    6
  14. Choose the recipient to receive the alerts and reports related to this migration batch
  15. You can start to start this migration patch manually or automatic
  16. You can also decide to finalize this script manually or automatic
  17. Then press new
    7
  18. You can now watch the migration batch Syncing or Completed
    8

 

2- The other way to do that is using the Power shell commands

  1. Find Power Shell ,right click to ‘Run as Administrator
  2. $cred = Get-Credential ( Enter your Office 365 credentials)
  3. $s = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $cred -Authentication Basic -AllowRedirection
  4. $importresults = Import-PSSession $s -AllowClobber
  5. $RemoteCredential= Get-Credential (Enter your on premise Exchange credentials)
    1. New-MoveRequest -Identity <username or mailbox identity here> -Remote -RemoteHostName <hybrid Exchange FQDN> -TargetDeliveryDomain <your target domain e.g. domainname.mail.onmicrosoft.com> -RemoteCredential $RemoteCredential -BadItemLimit 999 -LargeItemLimit 999

 

 

 

 

Litigation Hold vs In Place Hold

In the previous versions of Exchange (Exchange 2010) and Exchange online (Office 365) previous service version , the term litigation hold is introduced

Litigation Hold , is to allow you to immutably preserve mailbox content to meet long term preservation and eDiscovery requirements. When a mailbox is placed on Litigation Hold, mailbox content is preserved indefinitely.

In the new version of Exchange (Exchange 2013) and Exchange online (Office 365) existing service version , a new term has been released which is In Place Hold

In Place Hold, is called query-based and time-based In-Place Hold for the mailbox

After the release of Exchange 2013 and the new Exchange Online, there were some documentation that mentioned that Litigation Hold was being deprecated , this is not true and both terms are available 

Both types are available for use and you should use the hold feature that best meets your needs.  Here are some scenarios to help you choose between the two holds.

 image_050D85EA

 

Source : TechNet Blogs

 

How to Wipe your mobile device from OWA

Did you ever think about what will happen to your critical data if your active sync mobile has been stolen , What will happen to your e-mail data ?

Now from Exchange 2010, Exchange 2013 and Office 365 you can wipe your device remotely through OWA,

below we will show you how to do that from Office 365 OWA

1- Open the option from the OWA

 

1

 

2- Press on phone on the options page

2

3- Just mark the device you want to wipe and press on wipe as below

3

4- Confirm the wipe operation by pressing on Yes as below

4

5- You will find that the wipe operation is pending waiting for the mobile to connect 

 5

Once the device is connected it will be wipe

Same steps for Exchange 2013 and Exchange 2010 

Error When enable archiving on mailbox hosted on office 365

When you try enable archiving on any mailbox hosted on Office 365 (withing hybrid deployment with exchange 2010) , you face the below error

1

“The following error occurred during validation in agent ‘Windows LiveId Agent’: ‘Unable to perform the save operation. ‘Fayis Khader’ is not within a valid server write scope.”

This problem occurs because recipient management must be performed from the on-premises environment when you’re using Active Directory synchronization.

To resolve this issue, enable archiving for the mailbox from the on-premises Exchange server. To do this, use one of the following methods.

Method 1: Use the Exchange Admin Center or the Exchange Management Console

In Exchange 2013
  1. Open the Exchange Admin Center.
  2. Click recipients, and then click mailboxes,
  3. Click the mailbox that you want to change, click Enable under In-Place Archive, and then click yes.
  4. Wait for two cycles of directory synchronization to run (about six hours). to force directory synchronization follow this article Force directory synchronization
In Exchange 2010
  1. Open the Exchange Management Console.
  2. In the console tree, expand Recipient Configuration, and then click Mail Contact.
  3. Right-click the contact that you want to change, and then click Enable Hosted Archive.
  4. Wait for two cycles of directory synchronization to run (about six hours).to force directory synchronization follow this article Force directory synchronization

Method 2: Use the Exchange Management Shell

  1. Open the Exchange Management Shell, and then run the following cmdlet:
    Enable-RemoteMailbox <UserName> -Archive
  2. Wait for two cycles of directory synchronization to run (about six hours). to force directory synchronization follow this article Force directory synchronization

Released: Exchange Server 2013 Cumulative Update 5

The Exchange team is announcing today the availability of our most recent quarterly servicing update to Exchange Server 2013. Cumulative Update 5 for Exchange Server 2013 and updated UM Language Packs are now available on the Microsoft Download Center. Cumulative Update 5 represents the continuation of  Exchange Server 2013 servicing and builds upon Exchange Server 2013 Service Pack 1. The release includes fixes for customer reported issues, minor product enhancements and previously released security bulletins. A complete list of customer reported issues resolved in Exchange Server 2013 Cumulative Update 5 can be found in Knowledge Base Article KB2936880. Customers running any previous release of Exchange Server 2013 can move directly to Cumulative Update 5 today. Customers deploying Exchange Server 2013 for the first time may skip previous releases and start their deployment with Cumulative Update 5 as well.

We would like to call your attention to a couple of items in particular about the Cumulative Update 5 release:

  • Based upon customer feedback, we have introduced improvements to OAB management for distributed environments. You can read more about this in a post by Ross Smith IV on the Exchange Team blog. Customers who have deployed Multiple OAB Generation Mailboxes are advised to read this post to help avoid unnecessary OAB downloads.
  • Cumulative Update 5 includes a Managed Availability probe configuration that is frequently restarting the Microsoft Exchange Shared Cache Service in some environments. The service is being added to provide future performance improvements and is not used in Cumulative Update 5. More information is available in KB2971467.

Cumulative Update 5 includes Exchange related updates to Active Directory schema and configuration. For information on extending schema and configuring the active directory please review the appropriate TechNet documentation. Also, to prevent installation issues you should ensure that the Windows PowerShell Script Execution Policy is set to “Unrestricted” on the server being upgraded or installed. To verify the policy settings, run the Get-ExecutionPolicy cmdlet from PowerShell on the machine being upgraded. If the policies are NOT set to Unrestricted you should use the resolution steps in KB981474 to adjust the settings.

Reminder: Customers in hybrid deployments where Exchange is deployed in-house and in the cloud, or who are using Exchange Online Archiving with their in-house Exchange deployment are required to maintain currency on Cumulative Update releases

Download here : Cumulative Update 5 for Exchange Server 2013

Source : Exchange Blog

%d bloggers like this: