Failed CU19 on exchange 2013

Hi, we've got a problem with an exchange 2013 cu13 which we tried to update to cu19 but it failed half way with this error (attached)
What is the best course of action to take pls? Exchange is currently down so its urgent. Any help will be very much appreciated, thanks!Error
QuarmAsked:
Who is Participating?
 
QuarmConnect With a Mentor Author Commented:
Update on the situation:
We had to re-create the FederationEmail as suggested as well as few other things and re-run the Update
Sorry to unable provide more details as fixed by somebody else.
Thanks for your assistance
0
 
Jose Gabriel Ortega CConnect With a Mentor CEO J0rt3g4 Consulting ServicesCommented:
Well the solution implies the use of the ADSI.

On a domain controller click start, run and then type in adsiedit.msc and hit enter.

Right click the "ADSI Edit" at the top left and choose "Connect To". In the center under the "Select a well known naming context" select "Default naming context" from the drop down.

Now on the left expand your domain, and then the CN=Users container, scroll through that and see if you can find a federated mailbox and if there is more than one.

Source: https://community.spiceworks.com/topic/460051-exchange-2013-installation-error


The path is to remove the FederatedEmail user, and recreate it,
*Before Delete it take note of the name because you will need it*

New-Mailbox -Arbitration -Name FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 -UserPrincipalName FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042@default_accepted_domain

Open in new window

0
 
QuarmAuthor Commented:
Hi, thanks for the prompt response, there isnt any it seems, the link you've provided suggest re-creating it by using

New-Mailbox -Arbitration -Name FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 -UserPrincipalName FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042@default_accepted_domain

command but my Exchange powershell doesnt work so how can I do that?
Untitled.png
0
 
Jose Gabriel Ortega CConnect With a Mentor CEO J0rt3g4 Consulting ServicesCommented:
You just need to run this in a regular Powershell console with administrative privileges (copy and paste it) (the load of the snap-in).

#Load Exchange pssnapin it's not loaded
if (-not (Get-PSSnapin | Where-Object {$_.Name -like "Microsoft.Exchange.Management.PowerShell.E2010"})){ 
    Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010 
}
$GUID =$[System.GUId]::NewGuid().tostring()
New-Mailbox -Arbitration -Name "FederatedEmail.$GUID" -UserPrincipalName "FederatedEmail.$GUID"@default_accepted_domain

Open in new window

0
 
QuarmAuthor Commented:
Fixed it ourselves
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.