Exchange Solutions

Recently, while working on a Public Folder migration from Exchange 2007 to 2013, I ran into the following error.

 C:\Program Files\Microsoft\Exchange Server\Scripts>.\Export-PublicFolderStatistics.ps1 "C:\PFMigration\PublicFolderStats.csv"  Ex2007.domain.local 
Parameter declarations are a comma-separated list of variable names with optional initializer expressions. 
At C:\Program Files\Microsoft\Exchange Server\Scripts\Export-PublicFolderStatistics.ps1:16 char:168 
+         HelpMessage = "Full path of the output file to be generated. If only filename is specified, then the output file will be generated in the current directory.")] <<<<

It had me scratching my head for a couple of minutes. Then I quickly realized what I had forgotten. I needed PowerShell 2.0 to run this script.

If you are having this same error then make sure you download the Windows Management Framework Core pack from Microsoft. The pack includes PowerShell 2.0 and WinRM 2.0.

You can find it here.

The install won’t require a reboot. Once installed rerun your script.

With the rapid whirlwind of technological advancements its easy to forget the nuances of older operating systems.

Ever run into this error? You may see it when performing a cumulative update. I ran across it when upgrading Exchange 2013 to CU7.

Error: The Windows component RSAT-Clustering-CmdInterface isn’t installed on this computer and needs to be installed before Exchange Setup can begin.

There are a couple of ways to resolve this error; PowerShell or GUI. Let’s explore both.

I was helping a friend patch Exchange 2010 recently. They were getting up to speed with Service Pack 3.

Every time we ran through setup we encountered this error.

Setup cannot continue with the upgrade because the ‘bbwinsdr’ process has open files. Close the process and restart Setup.

This error can be found in the Exchange Setup log. (Located at %SYSTEMDRIVE%\ExchangeSetupLogs\ExchangeSetup.log.)

A quick Bing search determined the process belonged to Barracuda’s backup solution.

Backups Running?

Unfortunately, we didn’t have visibility into Barracuda’s dashboard. What we did have was much better. Event Viewer.

Recently, I was upgrading an Exchange 2010 environment to Service Pack 3. I ran into a slew of different errors.

Five in fact.

Every time I fixed one, another pesky one cropped up.

Very frustrating!

Lots of research and troubleshooting later I was able to get it going. With Service Pack 2 going end of life back on April 8th I wanted to pass that knowledge on.

This article offers a comprehensive guide to the errors I received and how to fix them.