CommVault 7 and Exchange 2007

I don't know how many of you out there use the commvault backup system however I know the process of getting it to grab Exchange 2007 mailboxes on Windows Server 2008 is quite the ordeal. However after much frustration I have a resolution and will document the steps.

1. Build Windows Server 2008
2. Install and configure Exchange 2007 mailbox role <-- important if you anticipate backing up Exchange data :)
3. Install and Patch the 64bit CommVault File System and Exchange database iData agents (the 64bit file system agent will be used to backup the file system)
4. Add the following Registry Hive: HKLM\SOFTWARE\Wow6432Node\GalaxyInstallerFlags
5. Add the following Registry keys underneath: DWORD bAllow32BitInstallOn64Bit = 1 DWORD bAllowMultiInstances = 1
6. Download and install the Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1
7. Disable UAC
8. Create a User account for the CommVault backup. The account must hold the following exchange roles: Exchange Org Admin, Exchange View Only Admin, Exchange Server Admin on the mailbox server.
9. Install 32bit CommVault mailbox, public folders (if using) and file system (required) iData Agents.
10. Make sure all iData agents are up to date.

That's it! 10 steps I know but when they aren't documented it's alot of guess work to go wrong.

Post UNO

So I've decided to start blogging. For those of you that know me you probably guessed by the title it will be job related. For those that don't here's a synopsis for what I do.

Title: Sr. Infrastructure Administrator (for now we're in a merger could change who knows)
Job Functions: EVERYTHING! more specifically:

MS Windows Server 2k - 2k8
MS Exchange 2k3 - 2k7
VMware ESX server 3.5
VMware VDI
SCOM
SCCM
SMS
Blackberry
Cisco IP Tel
Cisco WAN
Cisco LAN
Cisco WiFi
MS OCS
MS Sharepoint <-- hopefully passing off please dear god :)
Server Provisioning
Desktop / Laptop Tier 3 Support
Video Conferencing
QoS

I am sure there are other things but for now that's what pops into my head. So expect to see this blog fill with technical detail regarding these and other topics.