Exchange 2016 Hub Transport Role failing to install on Server 2012R2

I cant get Hub Transport to be installed.
Getting this error:

Error:
The following error was generated when "$error.Clear();
      new-ExchangeServer

" was run: "System.ArgumentNullException: Value cannot be null.
Parameter name: Cannot get child of ADObjectId:      this is a GUID based ADObjectId.
   at Microsoft.Exchange.Data.Directory.ADObjectId.GetChildId(String prefix, String unescapedCommonName)
   at Microsoft.Exchange.Data.Directory.ADDataSession.IsConfigScoped(ADScope scope)
   at Microsoft.Exchange.Data.Directory.ADDataSession.GetConnection(String preferredServer, Boolean isWriteOperation, String optionalBaseDN, ADObjectId& rootId, ADScope scope)
   at Microsoft.Exchange.Data.Directory.ADDataSession.GetReadConnection(String preferredServer, String optionalBaseDN, ADObjectId& rootId, ADRawEntry scopeDeteriminingObject)
   at Microsoft.Exchange.Data.Directory.ADDataSession.InternalFind[TResult](ADObjectId rootId, String optionalBaseDN, ADObjectId readId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, Boolean includeDeletedObjects)
   at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADTopologyConfigurationSession.<GetAdministrativeGroup>b__66()
   at Microsoft.Exchange.Data.Directory.Diagnostics.ADScenarioLog.InvokeWithAPILog[T](DateTime whenUTC, String name, Guid activityId, String implementation, String caller, Func`1 action, Func`1 getDcFunc)
   at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADTopologyConfigurationSession.InvokeWithAPILogging[T](Func`1 action, String memberName)
   at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADTopologyConfigurationSession.<GetAdministrativeGroupId>b__67()
   at Microsoft.Exchange.Data.Directory.Diagnostics.ADScenarioLog.InvokeWithAPILog[T](DateTime whenUTC, String name, Guid activityId, String implementation, String caller, Func`1 action, Func`1 getDcFunc)
   at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADTopologyConfigurationSession.InvokeWithAPILogging[T](Func`1 action, String memberName)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeServer.PrepareDataObject()
   at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
   at Microsoft.Exchange.Configuration.Tasks.Task.ProcessTaskStage(TaskStage taskStage, Action initFunc, Action mainFunc, Action completeFunc)
   at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()".
error.PNG
Eugene DunayevAsked:
Who is Participating?
 
Todd NelsonConnect With a Mentor Systems EngineerCommented:
Edge isn't supposed to be able to be installed on a server with any other roles ... not supported from Exchange 2007 to now.

You wouldn't be confusing the Hub Transport role with the Edge Transport role?

With Exchange 2016 there is only one role that is installed within the internal network (domain-joined) and that's the Mailbox role.  The other is the Edge Transpost role is supported on a stand-alone server in the perimeter network (DMZ).

References...
0
 
Todd NelsonSystems EngineerCommented:
Does the Exchange setup log provide any clue to why the install failed?

Have you tried to install from the command prompt?
0
 
Eugene DunayevAuthor Commented:
Attached Exchange Logs. These files contain only the last few entries. Let me know if you need more.

I have tried to install it from command prompt too, I tried:
     Setup.exe /mode:install /roles:HT /IAcceptExchangeServerLicenseTerms

Thank you.
-ExchangeSetup.log
-ExchangeSetupWatson.log
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Todd NelsonSystems EngineerCommented:
You are aware that there are only 2 roles with Exchange 2016, right?  Mailbox or Edge Transport.

Could that be why it's failing ... an incorrect switch?

https://technet.microsoft.com/en-us/library/aa997281(v=exchg.160).aspx

Is this a new Exchange organization or add to an existing one?

Are you installing the Exchange server in a child domain or the forest root?
0
 
Eugene DunayevAuthor Commented:
Maybe, I was using the GUI setup for the most part, thats the one i would wish to figure out.

Let me try the command line with correct switch this time. Good catch by the way.
     Setup.exe /mode:Install /r:EdgeTransport /IAcceptExchangeServerLicenseTerms

I currently have exchange 2010 that Im running in parallel on another server.
I'm trying to migrate to 2016 with both being in parallel for few weeks. (Slow migration)
0
 
Eugene DunayevAuthor Commented:
I guess I learn something new everyday....

The Edge Transport server role cannot be installed on the same computer with other server roles.
Please select at least one server role to install. Make sure that the specified roles aren't already installed.

The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
0
 
Todd NelsonSystems EngineerCommented:
That is true.  Edge has never been able to be installed with the other roles--and must be installed in a DMZ.

It's an easy mistake to make via the command line but I do find it odd that the GUI setup let you choose the Edge Transport role if Mailbox role was already installed.
0
 
Eugene DunayevAuthor Commented:
On Exchange 2010, they work well together. I just tried to duplicate the same setup just on the newer server.
0
 
Eugene DunayevAuthor Commented:
I guess its the Hub Transport, not Edge Transport. Not sure if they are exactly the same.

Name                 : MAIL3
ServerRole           : Mailbox, ClientAccess, HubTransport
Edition              : Enterprise
AdminDisplayVersion  : Version 14.3 (Build 123.4)
IsClientAccessServer : True

this is my old exchange server. 2010.
0
 
Eugene DunayevAuthor Commented:
You are absolutely right.

Thank you for catching that mistake.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.