troubleshooting Question

Microsoft Exchange Installation Error  at step 14 out of 18 Mailbox Role: Mailbox Service

Avatar of saphireneil
saphireneilFlag for United Kingdom of Great Britain and Northern Ireland asked on
Server SoftwareEmail ServersExchange
6 Comments1 Solution749 ViewsLast Modified:
Migrating from a SBS 2008 Exchange physical Server to Hyper-V Win Server 2012 R2 with Exchange 2013.

 AD Prep completed.

 Initially I used the Exchange 2013 Download link from Volume Licensing, Had multiple issues. Destroyed the VM and created new VM, same setup but using CU5. Then Encountered Certificate issues resulting in ECP blank screen after login. To resolve this Microsoft recommended CU6 release date 26/8.

 Now at installation point 14 out of 18 Mailbox Role: Mailbox Service I have the following error:

 The following error was generated when "$error.Clear();
           if (!$RoleIsDatacenter -and !$RoleIsDatacenterDedicated)
           $arbUsers = @(get-user -Filter {lastname -eq "MSExchApproval 1f05a927-3be2-4fb9-aa03-b59fe3b56f4c"} -IgnoreDefaultScope -ResultSize 1);
           if ($arbUsers.Length -ne 0)
           $mbxname = $arbUsers[0].name;
           $mbxs = @( get-mailbox -arbitration -Filter {name -eq $mbxname} -IgnoreDefaultScope -resultSize 1 );
           if ( $mbxs.length -eq 0)
           $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
           if ($dbs.Length -ne 0)
           enable-mailbox -Arbitration -identity $arbUsers[0] -database $dbs[0].Identity;
         " was run: "Microsoft.Exchange.Management.Tasks.RecipientTaskException: The user's Active Directory account must be logon-disabled for linked, shared, or resource mailbox.
    at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
    at Microsoft.Exchange.Management.RecipientTasks.EnableMailbox.PrepareRecipientObject(ADUser& user)
    at Microsoft.Exchange.Management.RecipientTasks.EnableRecipientObjectTask`2.PrepareDataObject()
    at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
    at Microsoft.Exchange.Configuration.Tasks.RecipientObjectActionTask`2.InternalValidate()
    at Microsoft.Exchange.Management.RecipientTasks.EnableMailbox.InternalValidate()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

 I have a feeling that the initial failed and destroyed Exchange box may be a contributing factor but that might be a red herring as have removed all evidence via ADSIEdit.

 Does anyone have any thoughts?

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 1 Answer and 6 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 6 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros