UPDATED: Feb 26, 2014, updated script to accommodate Exchange 2013 Now that Update Rollup for Exchange Server 2010 is available, I have updated my previous script to check for Update Rollup versions on both Exchange Server 2007 and Exchange Server 2010. No need to have two versions of script. Just download this one! Here’s what has changed between versions: Product GUID has changed to AE1D439464EB1B8488741FFA028E291C (Exchange 2010) from 461C2B4266EDEF444B864AD6D9E5B613 (Exchange 2007). Exchange writes installation information to HKLM\SOFTWARE\Microsoft\ExchangeServer\v14\Setup instead of “HKLM\SOFTWARE\Microsoft\Exchange\Setup” The script below will do the work for you so…read more
When you try to apply managed mailbox folder policy to a mailbox using set-mailbox, you would run a command like this: set-mailbox -identity mailboxA -ManagedFolderMailboxPolicy "MFPolicy" This would result in a confirmation prompt Confirm Are you sure you want to perform this action? … To avoid the prompt, you instead run command set-mailbox -identity mailboxA -ManagedFolderMailboxPolicy "MFPolicy" –confirm:$false However, you will get prompted again with the following: Confirm When assigning a managed folder mailbox policy… To put it in perspective, the first confirmation…read more
This is one question that gets asked around many times! The article “Exchange Server 2007: Platforms, Editions and Versions” gives important information to identify the build numbers for each Rollup Updates, however, it is unclear where to look for this information. To solve that problem, I have come up with a script which looks at Exsetup.exe version and registry entries for each Rollup Update installed… Uh, what happened to the rest of this post? Well, since I wrote a better script that handles both Exchange 2010 and Exchange 2007, I…read more
I wanted to mount All mailbox databases from all servers that had them. This was a scenario where I had servers recovered with no DB files. I did not need them, I was going to start with empty databases. The command was going to be simple: Get-MailboxDatabase | Mount-Database -Confirm:$false Except that this command had a major flaw. Can you guess?