Archive for July, 2009

Dude, where’s my mailbox stats?

One of the most frequently used Exchange 2003 mailbox management administrative features was the mailbox size, total item count, last logon time, log off time etc. For some strange reason, this convenient feature has been left out of Exchange Server 2007. If you are reading this blog then you probably are looking for a way to get these stats back.

The Exchange 2007 power shell is power packed to deal with this drawback and you can get all the info you need (displayed just like ESM 2003) in a jiffy by running this command (you will need to substitute MailboxServer01 with your server name):

Get-MailboxStatistics -Server MailboxServer01 | Sort -Property TotalItemsize | Format-Table DisplayName, LastLoggedOnUserAccount, ItemCount, @{expression={$_.totalitemsize.value.ToMB()};label=”Size(MB)”}, LastLogonTime, LastLogoffTime | Export-CSV ExMBXInfo.csv

All this info would get written to a csv file with the filename ExMBXInfo.csv (Edit the file name in the command if you want to call it something else)

The variables used here are DisplayName, LastLoggedOnUserAccount, ItemCount, TotalItemSize, LastLogonTime, LastLogoffTime. There are a host of other variables that can be used to get more information. Here are some of these variables that can be used:

AssociatedItemCount
Database
DatabaseName
DeletedItemCount
DisconnectDate
DisplayName
Identity
ItemCount
LastLoggedOnUserAccount
LastLogoffTime
LastLogonTime
LegacyDN
MailboxGuid
ServerName
StorageGroupName
StorageLimitStatus
TotalDeletedItemSize
TotalItemSize

Drop me a line if this article helped you!

, , , ,

No Comments

The WinRoute tool

WinRoute.exe is a tool that can be used to view and easily understand a complicated Exchange email routing topology. This tool is a recommended first step towards troubleshooting Exchange Email routing issues.

To install the tool, go through the following checklist:

Read the rest of this entry »

, , , , , , ,

No Comments

IPSec Tunnel Netscreen (Juniper) and Cisco ASA

I recently had to setup an IPSec Tunnel between a Netscreen (Juniper SSG5) and a Cisco router running ASA code. There were numerous problems that I came across when deciding on a workable Phase2 proposal. Eventually I found one that worked and am writing this post as a reference for later.

On the Juniper, the salient configuration points are:

  1. Ensure that there is a Proxy ID defined.
  2. Ensure that there is a policy for every proxy ID defined.
  3. Ensure that the Phase2 proposal is pre-g2-3des-md5

On the ASA, the cryptomap should look something like this:

crypto map xohm 3 ipsec-isakmp
set peer <peer ip>
set security-association lifetime seconds 28800
set transform-set <set name>
set pfs group2
match address <addressbook entry>
crypto ipsec transform-set <set name> esp-3des esp-md5-hmac

 

The tunnel should just start working when you start sending traffic after this.

, , , , , ,

No Comments