Exchange 2010 SP1

Removing an Organization (Remove-Organization)

 In order to remove an Organization from Exchange 2010 multi-tenant you must first delete all mailboxes from the organization. You can delete most of them through the ECP (Exchange Control Panel), but you will still be left with the administrator mailbox you are using, DiscoverySearchMailbox, and some others.

First you must find your organization you want to remove. You can do this by typing:

  • Get-Organization

Next you want to remove all mailboxes from the organization. Like I said above you can delete most of them using ECP or you can remove all the mailboxes quickly by typing:

  • Get-Mailbox-Organization"<ORG NAME HERE>"| Remove-Mailbox

Now that all mailboxes are removed you can type this to remove the organization: 

  • Remove-Organization -Identity "<ORG NAME HERE>"

Give it a minute and you should be able to do another Get-Organization and notice that your organization is gone! I took a picture for your viewing pleasure: 


Exchange 2010 SP1 Multi-Tenant (Step 3 of 3)

Configuring Mailflow


Here is the issue. If you use DNS to route your mail then you will have a problem with sending emails between organizations. In order to make this work you must create a send connector that routes the traffic to and from the organizations. Another way to solve this problem is to use a smart host:

New-SendConnector -Name "Internet" -Usage "Custom" -AddressSpaces "SMTP:*;1" -IsScopedConnector $false -SmartHosts x.x.x.x,x.x.x.x -DNSRoutingEnabled $false -SmartHostAuthMechanism "None" -UseExternalDNSServersEnabled $false -SourceTransportServers "Exchange Server"

New Send Connector


Receive Connector:


Now we must tick the Anonymous box on the default receive connector so internet users can send to the Exchange Server:

Set-ReceiveConnector -PermissionGroups 'AnonymousUsers, ExchangeUsers, ExchangeServers, ExchangeLegacyServers' -Identity 'LABDCEX\Default LABDCEX'

Receive Connector


Setting External FQDN


Our next step will be to make sure we put the external FQDN on all of the virtual directories.



Subscribe to Exchange 2010 SP1