I have a client reporting a problem when attempting to install Exchange 2016 CU16 Enterprise. Hoping someone can provide some advice. Here's the issue reported by the client:
They currently have Exchange 2010 server running on Server 2012 (they'll migrate mailboxes to 2016 once 2016 becomes available)
Plans: Exchange 2016 CU16 on Server 2016 Datacenter (VMware 6.5), AD functional level 2012. Two Domain Controllers, both Server 2016, both Global Catalog servers, both reachable from the server they are installing Exchange on.
They've run the install from the GUI and from the command line, with no difference in the end results.
All prerequisite checks pass, and ADPrep completes with no issues.
The install program fails at Step 7 of 14: Mailbox role: Transport service
The progress bar indicates 100% then the following error is displayed:
Error: The following error was generated when "$error.Clear(); if (![String]::IsNullOrEmpty($RoleDomainController)) { $masSid = add-ManagedAvailabilityServerGroupMember -DomainController $RoleDomainController -ServerName $RoleNetBIOSName } " was run: "Microsoft.Exchange.Data.DataValidationException: You must provide a value for this property. at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation) at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADConfigurationSession.Save(ADConfigurationObject instanceToSave, String callerFilePath, Int32 callerFileLine, String memberName) at Microsoft.Exchange.Management.Tasks.AddManagedAvailabilityServerGroupMember.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.b__91_1() at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Setup logs indicate that Domain Controllers are very reachable in all previous installation steps.
Exchange 2016 installs quite easily in a different (clean) domain which goes a long way toward ruling out a hardware or virtualization issue.
Apparently, they've been working with Microsoft support for some time with no resolution, so we're just kind of hoping someone here may have knowledge of this problem and/or a suggestion.
