Home » Exchange 2010
Category Archives: Exchange 2010
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:
- Launch a command prompt.
- 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)
- 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”.
- 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.
- 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.
- 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.
- Once the storage group is restored, you can successfully mount the databases in the storage group.
Steps to Restore Database in an Inconsistent State:
- Launch the command prompt.
- Reach to the location – Drive:\Program Files\Exchsrvr\Bin folder.
- Enter the following command in the command prompt:
eseutil /p “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”
- 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.
- 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
- 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.
- Repeat the steps from 3 to 6 for each database in the storage group.
- 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.
The connection to the server ‘Server URL’ could not be completed during mailbox migration
When you try to Migrate a mailbox from Exchange On Premise to Exchange we faced the below error
to be able to get more information about this issue , open the power shell and run the below command
Test-MigrationServerAvailability -ExchangeRemoteMove -Remoteserver “Server URL”
And got the below error
We found that something is not working perfectly with the certificate published to the internet , we fix the certificate and re run the same command again but with credentials for accessing the servers URL
As you see it works fine now , after fixing the Certificate publishing issue
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:
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
Update Rollup 8 v2 For Exchange 2010 SP3 Republished
Update Rollup 8 v2 For Exchange 2010 SP3 Republished after fixing the first version of the rollup
The Rollup V1 has bug is in the MAPI RPC layer and now it is fixed
Update Rollup 8 v2 for Exchange Server 2010 Service Pack 3 (SP3) resolves issues that were found in Exchange Server 2010 SP3 RU7 since the software was released. This update rollup is highly recommended for all Exchange Server 2010 SP3 customers.
For a list of changes that are included in this update rollup, see KB2986475
For download the rollup Download
- .
Exchange Server 2010 SP3 Update Rollup 8 has been recalled due to bug in MAPI RPC layer
An issue has been identified in the Exchange Server 2010 SP3 Update Rollup 8. The update has been recalled and is no longer available on the download center pending a new RU8 release. Customers should not proceed with deployments of this update until the new RU8 version is made available. Customers who have already started deployment of RU8 should rollback this update.
The issue impacts the ability of Outlook to connect to Exchange, thus we are taking the action to recall the RU8 to resolve this problem. We will deliver a revised RU8 package as soon as the issue can be isolated, corrected, and validated. We will publish further updates to this blog post regarding RU8.
The bug is in the MAPI RPC layer, clients that use other protocols such as ActiveSync (EAS), Outlook Web App, BlackBerry, and even IMAP4/POP3 all continued to work. Somewhat confusingly, some users reported that Outlook worked just fine or that clients started to work after a while.
This issue only impacts the Exchange Server 2010 SP3 RU8 update, the other updates remain valid and customers can continue with deployment of these packages.
Source: Exchange releases: December 2014 , Windows IT Pro
Note: The issue has been fixed on 12th December,2014 Update Rollup 8 v2 For Exchange 2010 SP3 (KB2986475)
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:
- Open the Office 365 portal and browse to the Exchange Admin Center
- choose Recipients
- Then choose Migration
- Then press press on the + sign
- Choose migrate to Exchange Online then press next as below
- Choose Remote move migration then next
- Then select the users you want to migrate , press the + sign
- Search for the user ,choose it then press ADD
- In the next page , just press next
- Choose the name of this migration
- Choose the domain , by default it will be domainame.mail.onmicrosoft.com
- You can move the mailbox and its archive or only move the archive
- Then you can decide the number of the Bad Item and the large item limits
- Choose the recipient to receive the alerts and reports related to this migration batch
- You can start to start this migration patch manually or automatic
- You can also decide to finalize this script manually or automatic
- Then press new
- You can now watch the migration batch Syncing or Completed
2- The other way to do that is using the Power shell commands
- Find Power Shell ,right click to ‘Run as Administrator
- $cred = Get-Credential ( Enter your Office 365 credentials)
- $s = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $cred -Authentication Basic -AllowRedirection
- $importresults = Import-PSSession $s -AllowClobber
- $RemoteCredential= Get-Credential (Enter your on premise Exchange credentials)
-
- 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
Released: Update Rollup 7 for Exchange Server 2010 Service Pack 3
The Exchange team is announcing today the availability of Update Rollup 7 for Exchange Server 2010 Service Pack 3. Update Rollup 7 is the latest rollup of customer fixes available for Exchange Server 2010 Service Pack 3. The release contains fixes for customer reported issues and previously released security bulletins. Update Rollup 7 is not considered a security release as it contains no new previously unreleased security bulletins. A complete list of issues resolved in Exchange Server 2010 Service Pack 3 Update Rollup 7 may be found in KB2961522.
Customers running any Service Pack 3 Update Rollup for Exchange Server 2010 can move to Update Rollup 7 directly.
Download: Update Rollup 7 For Exchange 2010 SP3
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.
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
2- Press on phone on the options page
3- Just mark the device you want to wipe and press on wipe as below
4- Confirm the wipe operation by pressing on Yes as below
5- You will find that the wipe operation is pending waiting for the mobile to connect
Once the device is connected it will be wipe
Same steps for Exchange 2013 and Exchange 2010
