Posts Tagged ‘Exchange 2007’

Export Exchange 2007 Mailbox Users Sorted By size

Tuesday, November 20th, 2012

Let’s say you need to run a report in Exchange 2007 containing the following items:

  • AD Display Name
  • Mailbox Size
  • Mailbox Item Count
  • Current Storage Limit (if applicable)

And you need this list sorted by Mailbox Size, descending, you would run the following command in Exchange Management Shell, on the Exchange 2007 server, using AD/Exchange admin rights:

Get-MailboxStatistics | where {$_.ObjectClass –eq “Mailbox”} | Sort-Object TotalItemSize –Descending | ft @{label=”User”;expression={$_.DisplayName}},@{label=”Total Size(MB)”;expression={$_.TotalItemSize.Value.ToMB()}},@{label=”Items”;expression={$_.ItemCount}},@{label=”StorageLimit”;expression={$_.StorageLimitStatus}} -auto >c:\mx_size_report.txt

The above will output to a txt file called “mx_size_report.txt”

Let’s say you want to view this in Excel, simply open Excel and import this TXT file.  You will now have an Excel manageable file with the report values you just generated.

Mail Archival

Saturday, November 7th, 2009

There are a number of messaging solutions that allow for automated message archiving. Message archiving can save space, while freeing up valuable resources and can also help to maintain Sarbanes-Oxley compliance (as well as achieve a number of other objectives). But not all messaging solutions allow for automated archival. Enter Mail Archiva into the picture.

Mail Archiva is an open source project aimed at bringing messaging archival to Microsoft Exchange, Zimbra, Mac OS X Server, Postfix, SendMail, IpSwitch, Axigen and a number of other messaging servers.

If you are in need of mail archival then feel free to reach out to us for more information on Mail Archiva today!

Using LCR for Exchange 2007 Disaster Recovery

Thursday, April 16th, 2009

Local Continuous Replication (LCR) is a high availability feature built into Exchange Server 2007.  LCR allows admins to create and maintain a replica of a storage group to a SAN or DAS volume.  This can be anything from a NetApp to an inexpensive jump drive or even a removable sled. In Exchange 2007, log file sizes have been increased, and those logs are copied to the LCR location (known as log shipping) and then used to “replay” data into the replica database (aka change propagation).

LCR can be used to reduce the recovery time in disaster recovery scenarios for the whole database, instead of restoring a database you can simply mount the replica.  However, this is not to be used for day-to-day mailbox recovery, message restores, etc.  It’s there to end those horrific eseutil /rebuild and eseutil /defrag scenarios.  Given the sizes that Exchange environments are able to get in Exchange 2003 R2 and Exchange 2007, this alone is worth the drive space used.

Like with many other things in Windows, LCR can be configured using a wizard.  The Local Continuous Backup wizard (I know, it should be the LCR wizard) can be accessed using the Exchange Management Console.  From here, browse to the storage group you would like to replicate and then click on the Enable Local Continuous Backup button.  The wizard will then ask you for the path to back up to and allow you to set a schedule.  Once done, the changes will replicate, but the initial copy will not.  This is known as seeding and will require a little PowerShell to get going.  Using the name of the Storage Group (in this example “First Storage Group”) you will stop LCR, manually update the seed, then start it again, commands respectively being:

Suspend-StorageGroupCopy –identity “First Storage Group”

Update-StorageGroupCopy –identity “First StorageGroup”

Resume-StorageGroupCopy –identity “First StorageGroup”

Now that your database is seeded, click on the Storage Group in the Exchange Management Console and you should see Healthy listed in the Copy Status column for the database you’re using LCR with.  Loop through this process with all of your databases and you’ll have a nice disaster recovery option to use next time you would have instead done a time consuming defrag of the database.

Unraveling Unified Messaging

Friday, March 13th, 2009

There’s been a lot of talk the past year or two about unified messaging. You may remember the old ATT All in One commercial where a person was golfing and his important call would find him, and he wouldn’t miss the call. Or have you ever had a job where every morning you had to check your e-mail, then your voicemail on your phones, and then walk to the fax machine to check your faxes? Well, Google this week released a new service called Google Voice. Google Voice is just a revamp of their system called Google GrandCentral. You have one number that people will call, and Google will route the call to all of your phones to try and locate you, and allow you to essentially ignore the call or accept it. You can also search your emails, voicemails, and SMS messages from the web. Microsoft Exchange offers a system that will allow you to get all your email, voicemail and faxes in one centralized location. Weaver just released a service in February that will allow Asterisk users to have their voicemail transcribed automatically and e-mailed to them. Below is a chart of services offered by Google, Asterisk, and Microsoft Exchange 2007 Unified Messaging to give you a better understanding of what technology route you may want to go.

Microsoft Exchange 2007 Unified Messaging
Microsoft’s Exchange 2007 Unified Messaging goal is to tie in Email, Fax and Phone into one manageable place. An example that Microsoft uses is that first thing in the morning most people check their email, then check their voicemail, and after check their faxes. Exchange Unified Messaging has the ability to tie together all three of these communication technologies into a single place for management.

Exchange Unified Messaging on it’s own cannot serve a PBX function, but harnesses a current PBX infrastructure into Exchange for end users to have a seamless place to manage their communications. The current iteration of Exchange Unified Messaging is with Exchange 2007. To leverage the entire suite of features, you must use Outlook 2007.

Google Voice
Google Voice is a communication infrastructure much like Exchange Unified Messaging, but seems to be targeted for non-business consumers. Google Voice is the current iteration of what was once known as Google GrandCentral. Its purpose is unified messaging as well, as it ties in your Gmail, SMS and incoming phone calls into your phone account created on Google Voice. Google Voice is an IP-PBX (VoIP) that allows you to make and receive calls with unified messaging capabilities.

Receiving calls can be done through any cell phone that you have, or through their Google Voice web interface. Making calls can be done via GoogleVoice (web-based), or through any other phone (landline or cell phone). The price point is very good (as in free). The price is free for all calls made to US numbers (long distance charges to other countries apply, of course). It requires no additional hardware.

Asterisk is an open source IP-PBX (VoIP) platform based on Linux. It requires a computer to run on and can tie in your existing land line with almost any VoIP provider of your choice. Call pricing depends on your phone carriers.


Google Voice


Exchange 2007


Yes, stored on Google’s PBX Server.

Yes, stored on PBX Server.

Yes, originating from current PBX, but forwarded and stored in Exchange


Yes, integrated with Gmail.

Yes, SMTP’d to host of your choice.

Yes, integrated with Exchange and Outlook

Transcribing VoiceMail


Yes, not natively as it needs to use VoiceScribe[1] and then emails you the trasncript

No, but allows the user to take notes (including manually transcribing voicemail) to allow voicemail to be searchable via Outlook


The use is free, and calls to US numbers are free.  Your cell provider rates still apply, and Google has their own price for long distance calling[2].

Free to install and use, and configure.  The call price rate depends on your local and/or VoIP carrier.

Phone calls rates are based on your PBX/Call Provider.  Only certain PBXs are supported[3].  The price for Exchange is $699 for Standard or $3,999 for Enterprise depending on how many storage groups and databases per mailbox server role you need.[4]  Both come with unified messaging.

Can call more than one of your phones at a time to try to locate you.


Yes, but you need to purchase additional trunks (VoIP or PSTN)

Depends on PBX

Can automatically locate you and route calls depending on bluetooth proximity.




Native Address Book

Yes, integrated with your Google Account.


Yes, integrated with Exchange Contacts

Call Management

Yes, via your phones (and possibly through Google Voice)

Yes, via your phones or through HUD

Yes, through Outlook and possibly through your PBX Software



Yes, but it’s through VoIP, and not realiable[5]

Yes, through a standard fax line




Depends on PBX

Listen to voice messages without changing their context to another application

Yes, integrated with Google Voice

No – you need to use whatever sound application is installed on your computer

Yes integrated with Outlook


Unknown, but since it’s web based, it may work on Linux, Mac, and Windows.

Yes – Linux, Mac, and Windows

No, just Windows with Outlook 2007. You can play messages in Entourage, but may either have to change file type in Exchange from *.wma to *.wav, or have Mac users install WMP 9 for OS X[6]

Configure individual voice mail settings

Via phone or web

Via phone or web

Yes integrated with Outlook

View all voicemail in one location




Distinguish voice and fax messages from email messages within mailbox

No, just voice mail from email, and only through Google Voice


Yes integrated with Outlook

Determine whether a voice message has already been played



Yes integrated with Outlook

Add notes to a voicemail message natively



Yes integrated with Outlook

Reply to a voice mail with email

Unknown – not sure if it can work with blocked numbers or telephone numbers not in contacts.


Yes integrated with Outlook

Add telephone numbers received to Contacts natively



Yes integrated with Outlook

Share VoiceMail




Adding a user

Free.  Requires that each user is registered with a Google account.

Free.  Just create a new extension for IP phones.  For non-IP hard phones, you must buy a FXS card (or to connect a regular phone to an ATA).

You must buy CALs for each user.  For unified messaging, you must have both the Exchange Standard AND Entprise CAL.  Exchange Standard CAL is $67, Exchange Enterprise CAL is $35.[7]  You must purchase both CALs for each user.  You also need to add a user to your PBX – pricing and licensing depends on PBX provider.

There are some things that may catch your eye (or not) when you first see this chart. Exchange Unified Messaging is expensive, but offers a lot of features that the other two don’t. From a “birds eye view” it may also fit your enterprise better if your companies’ locations use different types of PBXs, but you want to “unify” all of the communication in Exchange.

If you have a heterogeneous environment or non Windows environment, Asterisk or Google Voice may be a better route for you.

If you are concerned with regulatory compliance, Google Voice may not be your best choice since you do not have a centralized location of all your communication readily available.

When determining which choice is a better fit for your business, carefully weigh your options (price, compliance and room for expansion to name a few). It will be exciting to see how the technologies are managed, and what the future holds for unified communications. If you plan to roll out any of these services, or are in need of consultation, please don’t hesitate to let us know. We’re here to help.