Exchange Timeline

Search This Blog


Wednesday, September 17, 2014

How to Import Mailbox Data in Exchange Server 2007

A large number of users across the globe use MS Outlook with Microsoft Exchange Server which is one of the most popular, secure, and robust client & server, respectively, of a collaborative client server software platform from Microsoft. 

One can easily create account on Outlook and connect with Exchange server for accessing their emails through personal or shared mailbox. But sometime, it is not possible to access mailbox items due to sudden network failure, server breakdown, viruses, malware attack, or data loss etc., so you may need to again import your mailbox from backup; and sometime it become necessary to import mailbox data into Exchange server. Below are also most common causes when you may need to import mailbox data into Exchange server- 
  • During server migration. When you’re moving from one server to another, then you will need to import existing mailbox data into new Exchange server. 
  •  Secondly, when Exchange server has been damaged or crashed. In this case, you’ll need to restore and import mailbox data in new Exchange Server from backup of edb file.
So in this blog, we are importing mailbox data in Exchange server 2007 by using Exchange PowerShell scripts.  But before discuss the solution of importing mailbox on Exchange; we should know what data we can import by using this method.

The cmdletImport-Mailbox can imports all empty folders, special folders and sub folders to the intend location. Moreover the cmdlet  Import-Mailbox the following functions:
  1.  It imports all messages from the transport dumpster if they exist in the .pst file. 
  2.  It imports all associated folder messages if they exist in the .pst file. Associated messages contain hidden data with information about rules, views, and forms. 
  3.  It imports all message types, including messages, calendar items, contacts, distribution lists, journal entries, tasks, notes, and documents.
In addition, there are two parameters used through which can either include or exclude any type of folder. These are IncludeFoldersand ExcludeFolders.

So, considering a case where a user 'Admin01'want to import data from a .pst file to Peter'smailbox, first he will have to executethis command -

Add-MailboxPermission -Identity peter -User Admin01 -AccessRightsFullAccess

Now run following commands as required- 
            1.   Run the below command, if you want to import mailbox data from a .pst file that is named peter.pst to peter Peoples' mailbox:
Import-Mailbox -Identity –PSTFolderPath C:\PSTFiles\peter.pst
          2. To import all the mailbox data from a .pst file that is named peter.pst and that was received between January 1, 2013 and May 1, 2013, run the  command:  

    Import-Mailbox -Identity -PSTFolderPath C:\PSTFiles\peter.pst -StartDate 01/01/2013 -EndDate 05/01/2013

           3. Run the following to import mailbox data from all .pst files that are located in C:\PSTFiles to the corresponding mailboxes:

    Dir C:\PSTFiles\*.pst | Import-Mailbox -StartDate 01/01/2006 -EndDate 04/01/2006

           4. To import all the mailbox data from the peter.pst file for which is the sender:

    Import-Mailbox -Identity -PSTFolderPath C:\PSTFiles\peter.pst -SenderKeywords

           5. To import only the mailbox data from the peter.pst file that is in the Sent Items folder:

    Import-Mailbox -Identity peter -PSTFolderPath C:\PSTFiles\peter.pst -IncludeFolders '\Sent Items'

          6. Run the following command, if you want to exclude useless folders from the import:

    Import-Mailbox -Identity peter -PSTFolderPath C:\PSTFiles\peter.pst ExcludeFolders "\Junk E-Mail","\Contacts"

          7. Run the following command, if you want to use filters to specify which items in the .pst file to include in the import:

    Identity contoso\peter -PSTFolderPath C:\PSTFiles\peter.pst -ContentKeywords "merger" -AttachmentFilenames "*orgchart*" -StartDate "03/01/2013 12:01:00" -RecipientKeywords

    However, there are many functions which cannot be resolved by built-in commands. So in these critical situations you need a reliable and secure third party tool.
    Stellar Mailbox Extractor for Exchange Server is one such highly professional tool that converts Exchange mailboxes to pst file, and you can also directly export offline edb file into live Exchange Server.
    Try this tool. It is totally worth!

    10 Features of Microsoft Exchange Server 2013

          Email is one of the most important mediums in today’s business world. So initially it is very necessary to have an idea about what email systems are and what they do.By far the most prominent leader of the email industry is Exchange server. Exchange Server 2013 is the most upgraded version, equipped with advance features. It comes with two different versions- 
    •   On Premise version: Supposing a server which is located very nearby you.  
    •   Off Premise version: This version is also known as ‘Cloud’ version in which server is supposed to be ‘Hosted’ by another company. 
    So with this Exchange blog, we’ll discuss about the features/benefits of Exchange Server 2013, and will describe how Exchange 2013 can help you to manage email messaging system in small to big organizations.

    Let’s have a look at the top 10 benefits of using Microsoft Exchange Server 2013, and know how it is going to benefit you or your business. Here it is-

    1)   Protect sensitive data through DLP (Data Loss Prevention):This feature of Exchange Server 2013 provides identity, monitor and protect sensitive data through deep content analysis. In addition to this, Exchange 2013 also offers certain regulatory standards such as PII and PCI which provides extensible support to other policies important to your business.

    2)  Integration of new In-Place eDiscovery: Exchange Server 2103 lets you to stop employees from deleting emails that could be important to a particular case. The eDiscovery center allows administrator to search data in Exchange from one place which helps in identifying, hold and analyzing the emails.

    3)   Keep all your important data in archiving and primary mailbox: The Exchange Server 2013 empowers users with an in-place archiving and the facility to retain large mailboxes in primary mailbox. The Exchange Server 2013 is blended with the powerful and flexible retention policies which offer complete control of storage to keep Exchange users productive.

    4)   Enable users to be more collaborative: Exchange Server 2013 makes it easier for users to manage teams and project communications easily and quickly as it allows users to see old communication on a project and give access to current versions for their team document.

    5)   Protection against email threats: Exchange actively protects your communications with built-in utilities providing defense against email threats. It has multi-layered anti-spam filters comes with regular updates to provide safeguard against virus and spam threats.

    6)  Gives a portability and touch-enabled inbox experience:  Now you can easily enable Exchange users to access their emails from anywhere with clean and uncluttered experience. The same thoughtful design in the Outlook desktop interface has been applied to both the browser and mobile interfaces.

    7)    Move to Cloud with flexible options including Exchange hybrid: The Exchange Server 2013 provides users an unbroken experience including scheduling meetings and sharing calendars between online and on-premises users and doing this will slightly interruption as possible. You'll be still remain in control during testing the cloud's newest enhancements with support for upgrade previews.

    8)    Decrease the amount of time spent in managing systems: With the introduction of EAC (Exchange Administrative Centre), it becomes very easier to manage powerful capabilities including DLP, site mailboxes, and apps for Outlook. With collaboration of RBAC (Role Based Access Control) in Exchange server, you can offer your help desk and expert users with the tools to execute exact tasks without requiring full administrative authorizations.
    9)    Customize Exchange Server by integrating relevant apps:  Exchange Server 2013 version provides users to make their communication experience more powerful by reducing the time spent in switching between apps.

    10)   Bring all contacts together at one place:  Now you can easily bring your all-important contacts at one place, and can also bring your other networks contacts as well at same place. Exchange server will find the contact information of same user across networks and consolidate their information into one contact card without any duplicacy.

    Tuesday, September 16, 2014

    How to fix if OWA is not working for Exchange Server

    OWA (Outlook Web Access) is one of the most significant features of Microsoft Exchange Server which allow Outlook users to access their account online from anywhere in the world. You don’t need to configure Outlook Express account on your desktop or mobile to access your email account, just use any internet browser and connect with OWA.

    However, there are some questions arise by Outlook users, that Outlook is working fine, but they are not able to use OWA or it isn’t working as it’s supposed to.

    So, with this blog we shall go through the reasons why OWA do not work sometimes for Exchange server, and what are the best rectifications we can do to avoid this issue. 

     Below are some common causes and methods to fix if OWA isn’t running properly or not getting data from Exchange server to your computer or mobile browser. Let’s check it-

    IIS connection errors

    Without doubt, it could be the main causes of OWA errors or not working. However, there may be lot of causes behind IIS connection error, but first check that OWA is opening on your system or it is blocked. Try pinging by your full domain and IP address, if it works that’s fine. But if both pings fail, the reason must be firewall. Probably firewall is set to block ICMP packets & that’s why server won’t reply to a ping. 

    However, in some cases IP ping works but the ping by FQDN (fully qualified domain name) fails, it means there is DNS problem with your computer. So you would need to resolve this issue before connecting to OWA server.

    Firewall Issues

    So if you resolved DNS issue but OWA is still not connecting with Exchange, it’s time to check firewall setting. Disable your firewall for a while and retry to connect your OWA server. If you’re not able to connect OWA after disabling firewall, you need to fix firewall problem. Verify that ports 443 and 80 are open to incoming traffic. 

    But after all the setting if same problem still persist, there is must be some problem with IIS. 

    IIS Problems

    Now check IIS setting. Go to 'Start ' and search 'Administrative Tools'. Once you click on Administrative Tools, Windows will launch the 'Service Control Manager'. Now check here following services is running or not –

    Ø  IIS Admin Service
    Ø  Remote Procedure Call (RPC)
    Ø  World Wide Web Publishing Service
    Ø  Protected Storage

    Also check that Exchange related services are running or not. If you found all necessary services are running. Open internet Explore in OWA server and enter OWA server IP address in to browser. If OWA session starts; it means IIS is working perfectly. But if OWA session doesn’t start, you will need to verify IIS is configured to use the correct IP address or not. Click 'Internet Services Manager' from Administrative Tools menu, a new Internet Information Server console will open, now select OWA site from console tree.

    Usually this process fix OWA issues, but if it doesn’t work; there is IP address confliction issue. Your OWA site probably has IP address clash with another website on the server. So, first you need to resolve IP conflict issue. Your OWA site must have a dedicated IP address.

    Note: In case if you find IIS is malfunctioning, it is recommended to reinstall it. You can reinstall it through 'Add/Remove Program’s in Control Panel.

    Authentication Problem

    Authentication is another a very common causes for Outlook Web Access not working. To verify the authentication type for being use in OWA, Open Internet Services Manager and select Properties by right click on OWA Web site. Now select 'Directory Security tab' and click 'Edit' under Anonymous Access and Authentication Control section. A new Authentication Methods dialog box will open.

    Now verify that 'Anonymous Access' check box is unchecked, and also take a look to confirm that only 'Basic Authentication' check box is checked.

    Now click on 'Edit' (right side of the Basic checkbox) to verify that exact authentication domain is checked.
    Now click 'OK' and close all opened dialog boxes and windows. So, you have now specified what type of authentication OWA will use with specific domain.

    Now you can proceed further to final step, ping once again to check that OWA server is configured to use the matching DNS server. 

    If same issue still occurs, probably OWA server may have trouble to retrieving info from Active Directory information.

    How to fix email stuck in Exchange 2007/2010 queue

    It’s really annoying when someone says he/she didn’t get your any email!! Which had already sent it yesterday? It means they are lying…Right? 

    Nope!!! Actually there is a problem with your Exchange server that’s why it is not delivering any email to the corresponding user. Of-course it may confuse any user for a while, but this is an error known as Email Stuck which may occur in any Microsoft Exchange environment. 

    It is one of the most irritating issues on Microsoft Outlook/Microsoft Exchange Server which stuck the emails in remote delivery queue going to any other Exchange server. You can easily look these stuck emails by opening 'Queue Viewer' tool from the 'Toolbox' on Exchange Management Console. You can notice following error code in 'Last Error' field as-

    451 4.4.0 Primary target IP address responded with: "451 5.7.3 cannot achieve Exchange Server authentication." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts.

    So today, we’ll try to troubleshoot email stuck problem which usually occurs on Microsoft Exchange Server 2007 and 2010. But before we start, it would be better if we know the causes why we got this problem and why any email didn’t deliver to receiver. Let’s check it-

    Common causes of email stuck in Exchange Server

    The primary reason of occurring email stuck in Exchange server is that your Exchange server couldn’t authenticate with remote Exchange server. It is required for Exchange server to authenticate for routing email between them. Sender server tries to use X-EXPS command for authentication, but this failure occurs when firewall stops the authentication or remote server doesn’t enable X-EXPS command.

    So fix email stuck issue, make sure that Exchange authentication is enabled for all receive connectors. Also check if any firewall is located between two servers, the Extended SMTP verbs X-ANONYMOUSTLS, GSSAPI, and X-EXPS must be able to pass.

    So, if you checked all above basic setting, follow some given steps fix this problem in Microsoft Exchange server 2010 and 2007. 

    For Microsoft Exchange Server 2010 or Exchange Server 2010 remote servers

    Ø  Open Exchange Management Console. To open Exchange Management Console, make sure PC has administrative privilege. Now go to Start -> All Programs -> Expand Microsoft Exchange Server 2007 or Microsoft Exchange Server 2010, depending on which version of Exchange server you are using on your system. Click Exchange Management Console from the utility list.

    The Exchange Management Console box will launch quickly. You can see there several tools including 'Toolbox', 'Organization Configuration', 'Recipient Configuration' and 'Server Configuration'.
    Ø  Now click on 'Server Configuration' to expand tab, and click 'Hub Transport'.

    Ø  Click on 'receive connector' tab, and find the remote Exchange server receive connector that the email is trying to be sent. You can also review stuck emails in 'send protocol logs' from Exchange server.

    Ø  Now click on 'Properties' by right click on 'receive connector'.

    Ø  Now verify 'Exchange Server authentication' is checked on the 'Authentication' tab.

    That’s it, all setting has been done. By implement these setting your all pending email message will automatically deliver to the corresponding users.

    Now send a test email to other receiver to verify that your emails are delivering to corresponding address.