en Passant

This little script helps me out with the ongoing mailbox moves we're doing. I'll kick off the moves on one of the servers, hop on to another box and fire off this script, then head on home. The script does three things for me.

1. While move requests are processing, it displays and average time to complete as a status bar on the screen.
2. Every few minutes, it will send out an email to me telling me the status so far.
3. When completed, it will send out a new email to me and my team that the moves are completed.

We recently had our Forefront 2010 license expire on all our Exchange servers. I found the Forefront 2010 cmdlet "set-fselicensing" will fill this need, but it doesn't work remotely (no -server option). I wrote this little wrapper to set the new license info on all our Exchange servers. This worked if I had remote sessions configured (winrm). Otherwise we had to touch each by hand.

By enclosing a recursive function into another, I am able to clean-up the results and only return a single copy of each name. This fixes some of the problems with my previous script.

I use it like:
$allStaff = get-dlsubmembers "All Staff"

This code will generate a HTML report detailing the activation preference.

We are starting to move our users in mass to our Exchange 2010 environment. As part of the request, one customer would like to move users based on their locations.

Update (5/1/2013) - I've re-uploaded the script to include my latest revisions. The script now supports a process to 'fill to 250' mailboxes, then move to next db. You set the mailbox db selection method in the script.

Just spent way too long troubleshooting this issue. I am moving my own mailbox to a new server in order to test the environment. I kept getting the following error when I'd try to kick off the move.

Error:

Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:12

Woodford, Eric
Failed

Error:
Failed to communicate with the mailbox database.

MapiExceptionShutoffQuotaExceeded: Unable to save changes. (hr=0x80004005, ec=1245)
Diagnostic context:
Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called [length=2194]

Legal question came up in the office. Management wants a break down of all the mailboxes that a specific user has access to. This uses an AD directory searcher to perform the work, so it's much faster than using a straight get-mailbox query like:

get-mailbox -resultsize unlimited | ?{get-mailboxpermission -identity $_.identity -user "domain\user"}

Wanted to determine why a certain sender sat in the queues for 45 minutes. This script reads the message tracking logs on the current server and then generates a detailed report of message traffic coming into the server.

Found that we had a number of our HP servers, severely out of date on NIC driver updates. While trying to find someone with access to the HP Insight manager console, I did a little research and put together this script.

Ref: http://social.technet.microsoft.com/Forums/en-US/ITCG/thread/c29bc303-e6...

I've been working to fine-tune my script to search message tracking logs, then worked on another script to find out which 'accepted domains' have actual email addresses behind them.

This is my current code to query AD, and determine if an email address exists in the OU you asked it.