On Prem Exchange 2016 Installation Failure

%3CLINGO-SUB%20id%3D%22lingo-sub-1382365%22%20slang%3D%22en-US%22%3EOn%20Prem%20Exchange%202016%20Installation%20Failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1382365%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20trying%20to%20setup%20a%20new%20Exchange%202016%20instance%20on%20Windows%20Server%202016%2C%20however%20the%20installation%20fails%20on%20setting%20up%20the%20Mailbox%20Service.%20Before%20running%20the%20installation%20I%20have%20prepared%20AD%2C%20allowed%20for%20replication%20and%20installed%20all%20the%20required%20Window%20components%2C%20.Net%20Framework%204.8%2C%20Visual%20C%2B%2B%20Redstributable%20for%20Visual%20Studio%202012%2F13%20and%26nbsp%3BUCMA%204.0%20runtime%20as%20per%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fprerequisites%3Fview%3Dexchserver-2016%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fprerequisites%3Fview%3Dexchserver-2016%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20error%20that%20shows%20in%20the%20Setup%20log%20is%20showing%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUpgrade%20the%20discovery%20mailboxes%20to%20R5%20version%2C%20this%20will%20fix%20the%20RecipientDisplayType%20property%20of%20the%20discovery%20mailbox%20which%20was%20wrong%20in%20R4.%3C%2FP%3E%3CP%3Eget-mailbox%20-RecipientTypeDetails%20DiscoveryMailbox%20-DomainController%20%24RoleDomainController%20%7C%20where%20%7B%24_.IsValid%20-eq%20%24false%7D%20%7C%20set-mailbox%20-DomainController%20%24RoleDomainController%3CBR%20%2F%3E%24name%20%3D%3CBR%20%2F%3E%5BMicrosoft.Exchange.Management.RecipientTasks.EnableMailbox%5D%3A%3ADiscoveryMailboxUniqueName%3B%3CBR%20%2F%3E%24dispname%20%3D%20%5BMicrosoft.Exchange.Management.RecipientTasks.EnableMailbox%5D%3A%3ADiscoveryMailboxDisplayName%3B%3CBR%20%2F%3E%24mbxs%20%3D%20%40(%3CBR%20%2F%3Eget-mailbox%20-Filter%20%7Bname%20-eq%20%24name%7D%20-IgnoreDefaultScope%20-resultSize%201%20)%3B%3CBR%20%2F%3Eif%20(%20%24mbxs.length%20-eq%200)%3CBR%20%2F%3E%7B%3CBR%20%2F%3E%24dbs%20%3D%20%40(get-MailboxDatabase%20-Server%3A%24RoleFqdnOrName%20-DomainController%20%24RoleDomainController)%3B%3C%2FP%3E%3CP%3Eif(%24dbs.Length%20-ne%200)%3CBR%20%2F%3E%7B%3CBR%20%2F%3E%24mbxUser%20%3D%20%40(get-user%20-Filter%20%7Bname%20-eq%20%24name%7D%20-IgnoreDefaultScope%20-ResultSize%201)%3B%3CBR%20%2F%3Eif%20(%24mbxUser.Length%20-ne%200)%3CBR%20%2F%3E%7B%3CBR%20%2F%3Eenable-mailbox%20-Discovery%20-identity%20%24mbxUser%5B0%5D%20-DisplayName%3CBR%20%2F%3E%24dispname%20-database%20%24dbs%5B0%5D.Identity%3B%3CBR%20%2F%3E%7D%3CBR%20%2F%3E%7D%3CBR%20%2F%3E%7D%3CBR%20%2F%3E%7D%3CBR%20%2F%3Eelse%3CBR%20%2F%3E%7B%3CBR%20%2F%3Ewrite-exchangesetuplog%20-info%20%22Skipping%20creating%20Discovery%20Search%20Mailbox%20because%20of%20insufficient%20permission.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20confirmed%20that%20the%20Arbitration%20mailboxes%20our%20within%20the%20AD%20environment%20and%20the%20account%20that%20the%20setup%20was%20ran%20with%20was%20part%20of%20Domain%2C%20Enterprise%20and%20Schema%20admin%20groups.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHopefully%20someone%20can%20point%20me%20in%20the%20right%20direction%20of%20resolving%20this%20error%20as%20I%20have%20tried%20everything%20I%20can%20possibly%20think%20of.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1382365%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1393112%22%20slang%3D%22en-US%22%3ERe%3A%20On%20Prem%20Exchange%202016%20Installation%20Failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1393112%22%20slang%3D%22en-US%22%3EThe%20%22insufficient%20permissions%22%20error%20at%20the%20end%20makes%20me%20suspect%20that%20your%20account%20may%20not%20be%20a%20member%20of%20a%20needed%20Exchange%20Server%20RBAC%20permission%20group.%20Is%20your%20account%20an%20Org%20Admin%20in%20Exchange%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1473379%22%20slang%3D%22en-US%22%3ERe%3A%20On%20Prem%20Exchange%202016%20Installation%20Failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1473379%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F664578%22%20target%3D%22_blank%22%3E%40rjc8703%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20check%20the%20HomeMDB%20attribute%20for%20the%20arbitration%20mailbox.%20if%20it%20is%20empty%20-%20copy%2Fpaste%20the%20value%20of%20database%20from%20a%20working%20mailbox.%20this%20should%20fix%20the%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethis%20has%20fixed%20for%20me%20with%20exchange%202010%2C13%2C16%20versions.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

I am trying to setup a new Exchange 2016 instance on Windows Server 2016, however the installation fails on setting up the Mailbox Service. Before running the installation I have prepared AD, allowed for replication and installed all the required Window components, .Net Framework 4.8, Visual C++ Redstributable for Visual Studio 2012/13 and UCMA 4.0 runtime as per https://docs.microsoft.com/en-us/exchange/plan-and-deploy/prerequisites?view=exchserver-2016

 

The error that shows in the Setup log is showing:

 

Upgrade the discovery mailboxes to R5 version, this will fix the RecipientDisplayType property of the discovery mailbox which was wrong in R4.

get-mailbox -RecipientTypeDetails DiscoveryMailbox -DomainController $RoleDomainController | where {$_.IsValid -eq $false} | set-mailbox -DomainController $RoleDomainController
$name =
[Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
$dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
$mbxs = @(
get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
if ( $mbxs.length -eq 0)
{
$dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);

if($dbs.Length -ne 0)
{
$mbxUser = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($mbxUser.Length -ne 0)
{
enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName
$dispname -database $dbs[0].Identity;
}
}
}
}
else
{
write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox because of insufficient permission."

 

I have confirmed that the Arbitration mailboxes our within the AD environment and the account that the setup was ran with was part of Domain, Enterprise and Schema admin groups.

 

Hopefully someone can point me in the right direction of resolving this error as I have tried everything I can possibly think of.

 

 

 

 

2 Replies
Highlighted
The "insufficient permissions" error at the end makes me suspect that your account may not be a member of a needed Exchange Server RBAC permission group. Is your account an Org Admin in Exchange?
Highlighted

@rjc8703 

 

Please check the HomeMDB attribute for the arbitration mailbox. if it is empty - copy/paste the value of database from a working mailbox. this should fix the issue.

 

this has fixed for me with exchange 2010,13,16 versions.