Forcing disconnected mailboxes to show up in Microsoft Exchange 2010

So you've disabled a bunch of mailboxes and you accidentally got rid of one that was still in use. Here's how to make them show up.

1. Open the Exchange Management Shell.
2. Run Clean-MailboxDatabase on the database in question. If you're like me and didn't take note of the database then you can run it on all of them:
   Get-MailboxDatabase | Clean-MailboxDatabase
3. Give it few minutes depending on the number and size of your databases. Your freshly disconnected mailboxes should all appear in the Disconnected Mailboxes section of the Exchange Management Console pretty soon.

Now you need to reconnect it to the AD object. You cannot reconnect a mailbox to a disabled account. That stumped me for a bit.

Scheduling a mailbox move in Exchange 2010

Remember how Exchange 2007 used to have that handy feature via the GUI that would allow you to schedule a mailbox move? Exchange 2010 seems to have done away with that. Here's how I schedule mailbox moves with Exchange 2010:

1. Create a suspended move request via the Exchange Management Shell. Here's an example where I'm creating three move requests.
   
   New-MoveRequest -Identity Person1 -TargetDatabase DB1 -BadItemLimit 50 -Suspend;
   New-MoveRequest -Identity Person2 -TargetDatabase DB2 -BadItemLimit 50 -Suspend;
   New-MoveRequest -Identity Person3 -TargetDatabase DB3 -BadItemLimit 50 -Suspend;
2. Now those people are all queued up and ready to go. We want to move them in, say, 6 hours. Enter this command which pings localhost for 21600 seconds (6 hours) then fetches a list of suspended move requests and passes them on to the Resume-MoveRequest command. Note the semicolons after each command. These execute in series, not in parallel.
   
   ping localhost -n 21600; Get-MoveRequest | Resume-MoveRequest;

Free/Busy and Out of Office (OOO) Issues When Migrating from Exchange 2007 to Exchange 2010

I'm in the process of migrating from Exchange 2007 to Exchange 2010. (Wait, was this post written in 2016? Yes, I know. There are extenuating circumstances.) Instead of configuring lots and lots of servers to send email to the IP of the new Exchange 2010 server, I decided to swap IPs between the Exchange 2007 and 2010 server.

I went through and adjusted the URLs under all the Client Access categories: Outlook Web App, Exchange Control Panel, Exchange ActiveSync, etc. After making the changes I ran into two issues:

1. Issue: Exchange 2007 wasn't able to find itself via DNS.
   Fix: Turns out the person who built it put in a host file and hard coded the IP in that.
   Here's where to look for that:
   C:\Windows\System32\drivers\etc\hosts
2. Issue: Free/Busy information wasn't working for mailboxes on the Exchange 2007 server and Out of Office messages couldn't be set.
   Fix: There are URLs for the Web Services Virtual Directory that need to be updated but are not available (as far as I know) via the Exchange Management GUI.
1. I opened Exchange Management Shell
2. I ran this command to see the URLs assigned to each EWS.
   Get-WebServicesVirtualDirectory | select Identity, *url* | fl
   
   Identity             : Exch07\EWS (Default Web Site)
   InternalNLBBypassUrl : https://Exch07.my.biz/ews/exchange.asmx
   InternalUrl          : https://mail.my.biz/ews/exchange.asmx
   ExternalUrl          : https://mail.my.biz/ews/exchange.asmx
   
   Identity             : Exch10\EWS (Default Web Site)
   InternalNLBBypassUrl : https://Exch10.my.biz/ews/exchange.asmx
   InternalUrl          : https://Exch10.my.biz/EWS/Exchange.asmx
   ExternalUrl          : https://mail.my.biz/ews/exchange.asmx
3. Clearly mail.my.biz isn't going to work for two different servers. I needed to fix the internal URL and the external URL on my old 2007 server.
   
   Set-WebServicesVirtualDirectory –Identity “Exch07\EWS (Default Web Site)” –InternalUrl: https://Exch07.my.biz/ews/exchange.asmx
   
   Set-WebServicesVirtualDirectory –Identity “Exch07\EWS (Default Web Site)” –ExternalUrl: https://Exch07.my.biz/ews/exchange.asmx
   
   NOTE: You need the quotes and the whole string from the Identity field.
4. Then I restarted IIS on my Exchange 2007 server.
   It took a few minutes but the Free/Busy information started to populate and my ability to set Out of Office responses came back.