Is there any issues testing cu for hybrid in a lab?

Phil Ready 1 Reputation point
2021-03-07T08:03:29.73+00:00

I used to test our on-prem 2016 Exchange CU in a lab. I would disk2vhd to clone Exchange and AD and 'lab test' any new CU before applying in Production. We are now using a Hybrid with all User Mailboxes in M365. I can still 'clone' to a Lab, but would the CU still apply correctly without the M365 connection? I gave it a go, but getting a weird error: upgrade the discovery mailboxes to R5 version skipping creating discovery search mailbox because of insufficient permission

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,498 questions
Microsoft Exchange Hybrid Management
Microsoft Exchange Hybrid Management
Microsoft Exchange: Microsoft messaging and collaboration software.Hybrid Management: Organizing, handling, directing or controlling hybrid deployments.
1,998 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Ashok M 6,506 Reputation points
    2021-03-07T10:02:58.817+00:00

    Hi @Phil Ready ,

    To my knowledge, since the VM's are cloned, AD will have information about Exchange Hybrid and you might need to run the Setup /PrepareSchema with /TenantOrganizationConfig and then /PrepareAD.

    However, with the error message you shared, it looks like either the account you are using is not part of "Discovery Management" role in Exchange or an issue with Arbitration mailboxes. For the former, add your account to Discovery Management using Exchange Admin center and for the latter, check the below

    https://www.petenetlive.com/KB/Article/0001221

    If the above suggestion helps, please click on "Accept Answer" and upvote it.


  2. KyleXu-MSFT 26,246 Reputation points
    2021-03-08T08:00:26.867+00:00

    @Phil Ready

    In a hybrid environment, I do not recommend you to test by cloning. The Office 365 will cannot know which one is the correct one. You can deploy a standalone environment to test the update steps.

    Personally, the update steps are the same. You don't need to test all CUs. If you encounter problems, you are welcome to our forum for consultation. Of course, it is easier to understand the process by testing in your lab.

    upgrade the discovery mailboxes to R5 version skipping creating discovery search mailbox because of insufficient permission

    About this error, I would suggest you have a check with System Mailbox in your organization:

    Get-Mailbox –Arbitration | Select Name,Database  
    

    If there exits issue with them, you could recreate them with this article: Recreate missing arbitration mailboxes


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  3. Phil Ready 1 Reputation point
    2021-03-11T08:43:00.353+00:00

    I am not real sure about what set it bombs out at. It is after it has removed the existing services and files. ~Step 17?

    This is the full error that shows:

    Error:
    The following error was generated when "$error.Clear();
    if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))
    {
    if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
    {
    # 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."
    }
    }
    " was run: "Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.".

    Error:
    The following error was generated when "$error.Clear();
    if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))
    {
    if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
    {
    # 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."
    }
    }
    " was run: "Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
    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, Boolean reThrow)
    at Microsoft.Exchange.Configuration.Tasks.DataAccessTask1.Validate(TDataObject dataObject) at Microsoft.Exchange.Configuration.Tasks.SetTaskBase1.InternalValidate()
    at Microsoft.Exchange.Configuration.Tasks.SetRecipientObjectTask3.InternalValidate() at Microsoft.Exchange.Management.Common.SetMailEnabledRecipientObjectTask3.InternalValidate()
    at Microsoft.Exchange.Management.RecipientTasks.SetUserBase3.InternalValidate() at Microsoft.Exchange.Management.RecipientTasks.SetMailboxBase3.InternalValidate()
    at Microsoft.Exchange.Management.RecipientTasks.SetMailbox.InternalValidate()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".