Skip to main content


Showing posts from March, 2012

Featured Post

Exchange Admin Center language

Depending on your computer language settings, Exchange Admin Center can take those and open in a language you actually don't want to use.
You'll Google that this can be changed if administrator/ admin user has mailbox by openening OWA settings and changing Regional parameters.

But usually Admin user does not have mailbox or you don't want her/him to have it. You will search again and find that you can add mkt=en-US (as an example) to the URL of the Exchange Admin Center (https://yourexchangehostname/ecp?ExchClientVer=15&mkt=en-US)

Third option you have is opening Internet Explorer settings (I am using Windows 2016)

Click languagesClick Set Language Preferences

Add language you want to use by clicking Add language
Use Move up or Move Down options to put desired language on topClose Internet ExplorerOpen it again and login again to Exchange Admin Center

The mailbox database 'Mailbox Database xxxxxxx' cannot be deleted. - This mailbox database contains one or more mailboxes, mailbox plans, archive mailboxes, or arbitration mailboxes.

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 -
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” –ConfirmThen move arbitration mailboxes:
get-mailbox -Database “Mailbox Database xxxxxxxxxx” -arbitration | New-MoveRequest -TargetDatabase “NEW Mailbox database” –ConfirmIf “NEW Mailbox Database” is in good state (no seeding errors; everything is Healthy), mailboxes will be moved. To check this:

Exchange Development Kit (EDK) connector 'Text Messaging Delivery Agent Connector' was found in the organization. Exchange Server 2010 does not support EDK connectors. This connector will need to remain on existing Exchange 2003 servers.

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 ( 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 found in diffe…

Copy IP addresses from Exchange Receive connector

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:
Check it out for more info!