Copy Receive Connectors from one server to another

When you’re deploying Exchange 2010 Hub Transport servers, oftentimes you need to replicate the Receive Connectors on one server to multiple other servers.  This isn’t such a dawnting task when you have just a few receive connectors or if the Remote IP Ranges isn’t a long list of IP addresses and/or subnets. 

In those cases, manually creating them on each hub transport can be a nightmare.

You can use the following PowerShell commands to help speed up this process.

1. Get a list of all the non-default Receive connectors (i.e everything BUT the Default [SERVERNAME] and Client [SERVERNAME] connector)

$ReceiveConnectors = Get-ReceiveConnector -Server <SOURCE TRANSPORT SERVER> | where {!($_.Name -like “Client*”) -and !($_.name -like “Default*”)}

2. Then use this list to create identical receive connectors on another server.  Repeat this command for each Target Transport Server you want.

foreach ($Connector in $ReceiveConnectors) {New-ReceiveConnector -Server <TARGET TRANSPORT SERVER> -Name $Connector.name -Bindings $Connector.bindings -RemoteIPRanges $Connector.remoteipranges}

3. If you have other unique settings other than the default ones like Authentication and Permissions Groups, you can add those parameters inside the braces {} to copy those settings as well.

Advertisements

Upgrade Windows 2008 R2 Edition from Standard to Enterprise via Command Line

Have you ever installed Exchange 2010 on a Windows 2008 R2 server that came from an image, gotten all the way through installation and then discover that you can’t create the DAG because the OS is installed as Standard Edition and not Enterprise Edition (Entperprise being required for Cluster services to support the DAG).

It’s really disheartening to think you have to start over with re-installing the operating system.

Well, you don’t have to.  Windows 2008 R2 comes with a tool called DSIM – the Deployment Image Servicing and Management tool.  One of this tools amazingly useful features is the ability to upgrade the installed edition of the operating system without media.

To verify/determine the current edition, from a command line type:

DISM /online /Get-CurrentEdition

To upgrade the current edition to Enterprise, from a command line type:

DISM /online /Set-Edition:ServerEnterprise /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

Once you’ve upgraded the OS edition to Enterprise, you can re-install Exchange and create a DAG.

You can find out more about this tool from this TechNet article.

Exchange 2010 EMC tries to connect to non-existent servers

The Exchange Management Console isn’t very intuitive when it comes to decommissioning servers in your environment.  If you’ve opened the EMC and it last connected to a server that you then subsequently decommission, it will try to reconnect to that server the next time you open it, and fail.

Fortunately this issue seems to be limited to the user profile.  To resolve this, close the EMC, then open the registry editor and navigate to HKCUSoftwareMicrosoftExchangeserverv14AdminTools
and remove the
NodeStructureSettings
key.

Reopen EMC and it will search for another Exchange server to connect to.