Tuesday, 30 June 2015

Know How to Check Mailbox Size in Exchange 2007

While undergoing a transition from Exchange server 2003 to version 2007, there has been a significant change in the way of managing things at server level. Prior to Exchange server 2007, things remained as an option in GUI. However, with the introduction of PowerShell commands in Exchange server 2007, there has been gains and losses for users for people. For example, the capability to view the mailbox statistics has been a long-standing feature that was available with Exchange server 2003 is no longer with Exchange server 2007.
In case of Exchange Server 2007, you cannot easily view the mailbox statistics; we have to execute some PowerShell commands. Therefore, here we are going to have a look on the detailed procedure for how to check the mailbox size in Exchange Server 2007.

Viewing Mailbox Size in Exchange Server 2007

The main reason for Microsoft eliminating the feature for displaying the mailbox statistics from Exchange Management Shell of Server 2007 is due to the overall change in the management process of the management console. The recipient configuration present in Exchange server 2007 does give you the list about the number of user mailbox, groups, or contacts present in the server but it will not provide you with the specific details like the quantity of items in the mailbox and their size.

To get the information regarding the size of the mailbox, you have to start constructing PowerShell commands. If a user is looking for a basic report that comprise of the user mailbox size then use the PowerShell command “Get Mailbox Statistics.

Here is how to get the mailbox size, type the given command

The first impression of Get-MailboxStatistics cmdlet is that the command is going to fetch data in volumes from the server.
The above cmdlet provides the size of the mailbox in bytes. The field StorageLimitStatus indicates the status of a specific mailbox. The Output can be BelowLimit, which means that the size of the mailbox is below the IssueWarningQuota

If the mailbox size is above IssueWarningQuota but below the ProhibitSendQuota, then the status of the mailbox is changed to IssueWarning.

How to Get the Mailbox Size in KB?

For getting the output regarding the size of the mailbox in KB, use the following cmdlet

How Can You Obtain The Output Information On PC?

If a user is interested to save the output information regarding the mailbox size and other details, then they can do so by importing the result in CSV file format. For importing the output in CSV file format, use the following cmdlet. 


The above content fairly describes the way for how you can check the mailbox size in Exchange Server 2007. Further, you can also use other PowerShell cmdlet for extracting other type of information regarding the mailbox. Some of which may include last login time of the user and storage limit status.

Thursday, 18 June 2015

How to Convert OST to PST Manually?

MS Exchange server application comprises an added facility of creating an offline local file comprising of complete account data like emails, contacts, journals, notes, etc. This local file is created when the Outlook cached mode is enabled while configuring the Exchange application. User is allowed to use this local OST file without any dependence in network connectivity. When user establishes the connection of Outlook application with Exchange account, this OST file gets synchronized and the email data is synched accordingly. Although this OST file has some restrictions for its usage and because of these restrictions users can demand to convert OST to PST manually.

What Demands OST to PST Conversion?

There are many scenarios which demand such conversion. For instance; the file size difference between Exchange mailbox and the local replica OST file call for archiving or storing the OST email data to another file format. This will keep a check on the size limit of OST file which is very limited as compared to Exchange database. There are many other reasons like OST file cannot be accessed in any other system by mere copying it or importing it in another system’s Outlook application. The file is bound to original MAPI Exchange profile and hence it cannot be accessed in any other system.
All such situations demand to assemble email data to another file format which can also be accessed like OST and emails can be viewed with similar interface and usage. OST being an Outlook application storage file, one can convert OST to PST manually so that the email data can be accessed in Outlook application easily. The basic factor responsible for performing manual conversion of OST file to PST file is that the OST file should not be orphan or corrupted. An active and stable file can be easily converted to PST file by following the below mentioned steps. The steps have been performed on MS Outlook 2010 application.

Steps for Manual OST to PST Conversion

Step 1: Open MS Outlook with Exchange profile.

Step 2: Go to File menu and click on Open option. Here select Import in order to export the emails to PST file.

Step 3: Another Import & Export wizard window will open where you can choose the action to be performed. Choose “Export to a file” option in order to export data from OST file and click Next.

Step 4: Here select the destination file to which you want to export the email data. Choose Outlook Data File (.pst) as an Export option and click Next.

Step 5: Select the folders from which the email data has to be exported. You can also add the filters for advanced and organized email export. Once folders are selected, click Next

Step 6: Here by default the exported file is saved to “C:\Users\Username\Documents\Outlook Files” folder location with name as backup.pst file. You can click on Browse and change the location. There are various sub-options which can be selected related to duplicate email items. Once done, click Finish.


The exported PST file will be saved to the provided path location which will carry the existing email data. In this way the space allocated for OST file can be free and new email data can be stored in this file now. 

Saturday, 13 June 2015

Find Out How You Can Prevent Lync from Locking Outlook’s .ost File

Unified communication platforms have proffered businesses with a wider set and options to make their communication better. Lync along with Outlook does just that by providing a wider range of options communication on the confined environment of Microsoft Outlook. This includes communication via, text, video, voice, and streaming of media. However, a stable synchronization between both the services is an ultimate requirement which is fulfilled with correct configuration and settings applied. Similarly, in this blog we will cover the tips on how to prevent Lync from locking Outlook’s .ost file along with the reason provided on why it does so in the first place.
Prevent Lync from Locking Outlook’s .ost File without Service Termination
Most users who have confronted the issue and got stuck with it chose to terminate either of the two services to get rid of the issue. But what about those who run businesses dependent on Lync services and can’t just quit it?

We will outline the troubleshooting tips that will not only prevent Lync from locking the Offline Storage Table file but also let you continue using the unified communication service.
When using Lync services with Microsoft Office (Outlook), one can save conversation directly to their Outlook Data File. However, in order to do the same Lync has set its own rules, i.e. it will need accessing the account’s OST file.
This is how connection of Lync and Outlook involves the usage and possibility of locking OST file. The process usually works in an absolutely proper manner and remains unnoticed to the end user, but only under normal circumstances.
What happens in this case is exactly what happens in any case when some issue takes place, error. You will receive an error every time you try accessing something on your Outlook or within the OST data file. Some of the errors that are common to appear are illustrated as follows:

The worst that can happen is Outlook will crash.


Finding out how to prevent Lync from locking Outlook’s .ost file is not a difficult part. Given below is the solution to fix the issue and tips to prevent it from reoccurring in future.

First of all, the issue arises because Outlook is probably running in a Windows compatibility mode. Compatibility mode option may have been provided with Outlook but you are not required to use it, especially when you are using any of the latest Windows versions (as we assume you are).

TIP: This mode is only applicable on applications that are extremely old. So, if the option is enabled, disable it and if it isn’t enabled do not even consider enabling it.

If errors are being received that ‘the file cannot be accessed as it is in use on some other program’ (Lync) then you need to check the compatibility settings of the program.
  1. To disable the mode or just check its status find the Outlook setup file. Right click on the ‘exe’ and click on Properties.
  2. Click on the tab for Compatibility. Now uncheck if the checkbox for Compatibility mode is checked.
  3. Also uncheck the checkbox for running program as Administrator as it should not be used unless very necessary.

In Case The Issue Is Unresolved…
If the issue still remains unresolved then you are advised to follow the steps given below that will repair your Office 365 installation.
  1. Close all the applications of MS Office, i.e. Outlook and Lync too.
  2. Start Task Manager and check whether all Office processes are closed.
  3. Go to the Control Panel and select Programs and Features. Click on Microsoft Office 365.
  4. Click on Change and select the Quick Repair option followed by Repair.
  5. When asked to close programs click on Close All.
  6. After repair run Outlook and then open Lync to check if the issue has been rectified.
Conclusion: This is how you get rid of the errors and issues cropping up in a unified communication platform of Lync and Outlook. Always make sure that when using both the services, run Outlook first and then Lync. This will prevent Lync from locking Outlook’s .ost file. You will no longer see any errors because, before Lync could access OST, Outlook already has access to it.