Old School - Exchange Exports

We can’t always perform mailbox moves, cross forest moves or use web based mail migration service, such as Migrationwiz.com. From time to time we just have to get our hands dirty a shift PST files around.

If you have ever tried to use Exmerge to export a large (around 2GB) mailbox you will have run in to errors. Luckily Glen Scales http://gsexdev.blogspot.com/2007/01/exporting-mailbox-larger-then-2-gb-and.html and Michael Smith http://theessentialexchange.com/blogs/michael/archive/2009/10/16/exporting-mailboxes-larger-than-2-gb-on-an-exchange-server.aspx came to the rescue years ago.

I really like Michaels solution, I just edit the 3 lines below and run from the command prompt with cscript ExMBspanPst.vbs mailboxname.

servername = "EX01"
bfBaseFilename = mbMailbox
pfFilePath = "c:\PST\"

I thought I had seen the last of PST files, but we became reacquainted this weekend.

vCloud & NIC binding

When adding additional NICs to existing VMs using vCloud Director I have observed the bind order in Windows can end up wrong potentially leading to issues when services start up.

This is simply corrected under Advanced > Advanced Settings in the Network Connections window.

I found a useful PowerShell link to check and set the bind order here, http://www.peetersonline.nl/index.php/powershell/check-nic-bind-order/

Exchange 2010 SP2 Update – IIS6 WMI requirement

Having recently completed a round of Exchange 2010 SP2 upgrades I haven’t really found any gotchas, assuming you read the documentation first.

One item I think could catch a few people out is the requirement for “IIS 6 WMI Compatibility” to be installed of CAS role servers. This can easily be installed as part of the upgrade using:

setup.com /m:upgrade /installwindowscomponents

If you choose to run the GUI (setup.exe) you will need to install the IIS6 WMI Compatibility component of IIS or run the following PS:

Import-Module ServerManager
Add-WindowsFeature Web-WMI