Technical Exchange bLog

When you try to delete first database created by Microsoft Exchange 2010 server during installation, usually named Mailbox Database xxxxxxxxxx, you get “The mailbox database 'Mailbox Database xxxxxxxxxx' cannot be deleted” error stating that the database includes some user’s mailboxes and/or arbitration mailboxes. More info on arbitration mailboxes can be found here - http://technet.microsoft.com/en-us/library/dd297936.aspx . In order to delete the database, you need to move user’s mailboxes by using: get-mailbox -Database “Mailbox Database xxxxxxxxxx”  | New-MoveRequest -TargetDatabase “NEW Mailbox database” –Confirm Then move arbitration mailboxes: get-mailbox -Database “Mailbox Database xxxxxxxxxx” -arbitration | New-MoveRequest -TargetDatabase “NEW Mailbox database” –Confirm If “NEW Mailbox Database” is in good state (no seeding errors; everything is Healthy), mailboxes will be moved. To check this:  

When running Microsoft Exchange Pre-Deployment Analyzer before installing Exchange 2010 into environment with Exchange 2007 installed, an informational error is shown saying that some legacy connector, you probably never heard of, exists. In my case the environment was Exchange 2007 and the connector was found in Exchange Administrative group (FYDIBOHF23SPDLT) using following steps: Connect to your DC In the Active Directory Sites and Services Microsoft Management Console (MMC), double-click Active Directory Sites and Services . Click on top level in the hierarchy tree aka Active Directory Sites and Services (yourdc.yourdomain.com) On the View menu, click Show Services Node. Double-click Services , double-click Microsoft Exchange , and then double-click the Exchange Organization name. Double-click Administrative Groups , and then double-click the administrative group - OLD one (Exchange 5.5 or 2003) OR Exchange Administrative group (FYDIBOHF23SPDLT) – This connector can be

During to transition to newer version of Exchange from Exchange 2007, receive connector might include lots of IP addresses and ranges which you want to transfer to your new server. While you can find some scripts on the web which let you export IP addresses to txt file and import it from that same file on your new server, the easiest way to do this is to pipeline with PowerShell. Set-ReceiveConnector ”SERVERNAME2\CONNECTORNAME” -RemoteIPRanges ( Get-ReceiveConnector “SERVERNAME1\CONNECTORNAME” ).RemoteIPRanges Where SERVERNAME2 is the name of your new HUB server and SERVERNAME1 is the name of your old server from where you want IP addresses to be extracted. Information provided thanks to: http://scottsitramblings.wordpress.com/2011/06/23/copypaste-send-or-receive-connectors-exchange-2010/ Check it out for more info!