Problems Moving or Removing MS Transporter Suite
When using MS Transporter Suite for Directory Sync and Free Busy there can be instances when you need to use the product on a different Exchange 2007 Hub Transport Server, which might be in a different AD Site. This could be because you are having technical issues with that server. You may have already configured a new Directory Connector and a new Free Busy Connector (on HUB_Server_A). If you install the MS Transporter Suite on the new Hub Transport Server (HUB_Server_B), you will see the two Connectors that you have already installed.
However, if HUB_Server_A requires removong or re-installing, then these Connectors will drop off the MS Transporter Console on HUB_Server_B. This is because, although the configuration appears as if it is shared, each Connector is “owned” by the Hub Transport Server that it is first configured.
If you break out to the Transporter Shell and run the command:
get-dominodirectoryconnector
You will see that one field shows which server is the owner.
The equivalent command for the Free Busy Connector is:
get-dominofreebusyconnector
One approach, and probably the most reliable, is to take screen shots of your configurations, and remove the Transporter Connectors from the Transporter Console off HUB_Server_A. Then run the get-dominodirectoryconnector and get-dominofreebusyconnector commands from the Transporter Shell to ensure they have been cleaned up. Then wait for AD replication to take place. Next check in the Transporter Console on HUB_Server_B and the two Connectors should have been removed. Also check using the Transporter Shell using the same commands as listed above to ensure that they have gone.
I have seen scenarios where the Connectors are not showing in the Transporter Console, but are showing from the Transporter Shell. This will prevent any new Connectors from being added to the Transporter Console, as you will get an error saying an instance of the Connector already exists. No matter how many times you remove and re-install the MS Transporter application, the situation will remain.
You will need to try the following Transporter Shell command from the Exchange 2007 Hub Transport Server: (make sure you are Enterprise Admin to do this)
remove-dominodirectoryconnector -identity “<enter name of connector here>”
remove-dominofreebusyconnector -identity “<enter name of connector here>”
Get the name of the Connector(s) from the information presented by the following Transporter Shell commands:
get-dominodirectoryconnector
get-dominofreebusyconnector
If you get really stuck then you can use the following Transporter Shell commands to set any missing attributes, such as the “Name” field. I have seen instances where this value has become dropped, and this is preventing the Connectors removal.
set-dominodirectoryconnector -Name “<enter the name here>”
set-dominofreebusyconnector -Name “<enter the name here>”
Microsoft provide a full reference to the command parameters for the above.
This information should provide enough clues to tidy up any troublesome Transporter Suite issues. The product works well for the DirSync and FreeBusy functions, but is certainly prone to error if you have to start removing it from a Hub Transport Server onto another, especially in a different AD Site. Watch out for AD replication as well – always ensure it has taken place before making any further changes.
This entry was posted on Saturday, July 17th, 2010 at 7:34 am and is filed under Transporter. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.