Recreate Exchange 2013 Health Mailboxes

MS Exchange

How to recreate health mailboxes in Exchange 2013?

A new type of mailbox that is available in Exchange 2013 is the health mailbox and is used for monitoring the server itself.

Running Get-Mailbox –Monitoring will list all the health mailboxes in your 2013 organization.

Get health mailboxes

There will be two health mailboxes created for every mailbox database – one is used for mailbox and the other for public folder.

I had to recreate these mailboxes for fixing the issue of health manager service not starting automatically. So, how to get the job done?

The health mailboxes account will be listed in ADDomain.Local/Microsoft Exchange System Objects/Monitoring Mailboxes. In my case it is HOWLYNCWORKS.LAB/Microsoft Exchange System Objects/Monitoring Mailboxes.

Health mailbox location in AD

Select all accounts and delete them!

Delete health mailbox AD accounts

Restart the Exchange Health Manager service or the server itself. The service will recreate the health mailboxes it requires (give it a minute). If you have more than one mailbox server and you deleted all health mailbox accounts from AD, restart the same service on all the mailbox servers for it to be re-created.

And yes, the health mailboxes are back.

Health mailbox recreated 

But no, they don’t have the same name as the deleted ones ;)

Other Popular Articles

MS Exchange

Keep Track Of Exchange 2013 Database Failovers

MS Exchange

Playing With Exchange 2013 Performance Logs

MS Exchange

Tackle .Net Framework 4.6.1 On Exchange Servers

  1. I dont even have monitoring mailboxes container in my on exchange (did select advance in view)
    I try to run setup.exe /preparead /IAccept……….. but it fails when gets to Organization Preparation at 46%

    elcome to Microsoft Exchange Server 2013 Cumulative Update 9 Unattended Setup
    ou need to accept the license terms to install Microsoft Exchange Server 2013. To read the license agreement, visit htt
    :// To accept the license agreement, add the /IAcceptExchangeServerLicenseTerm
    parameter to the command you’re running. For more information, run setup /?.
    PS] C:\Windows\system32>setup.exe /preparead /IAcceptExchangeServerLicenseTerms

    elcome to Microsoft Exchange Server 2013 Cumulative Update 9 Unattended Setup

    erforming Microsoft Exchange Server Prerequisite Check

    Prerequisite Analysis COMPLETED

    onfiguring Microsoft Exchange Server

    Organization Preparation FAILED
    The following error was generated when “$error.Clear();
    # O15# 2844081 – Create PartnerApplication “Exchange Online” in DC and On-Premise
    $exch = [Microsoft.Exchange.Data.Directory.SystemConfiguration.WellknownPartnerApplicationIdentifiers]::Exch
    $exchApp = Get-PartnerApplication $exch -ErrorAction SilentlyContinue -DomainController $RoleDomainControlle
    | Where { $_.UseAuthServer };
    if ($exchApp -eq $null)
    $exchAppName = “Exchange Online”;
    $exchApp = New-PartnerApplication -Name $exchAppName -ApplicationIdentifier $exch -Enabled $RoleIsDatace
    ter -AcceptSecurityIdentifierInformation $false -DomainController $RoleDomainController;

    # Create application account for Exchange
    $appAccountName = $exchApp.Name + “-ApplicationAccount”;
    $appAccount = Get-LinkedUser -Identity $appAccountName -ErrorAction SilentlyContinue -DomainController $Role
    if ($appAccount -eq $null)
    $appAccountUpn = $appAccountName.Replace(” “, “_”) + “@” + $RoleFullyQualifiedDomainName;
    $appAccount = New-LinkedUser -Name $appAccountName -UserPrincipalName $appAccountUpn -DomainController $
    Set-PartnerApplication -Identity $exchApp.Identity -LinkedAccount $appAccount.Identity -DomainController

    foreach ($roleName in (“UserApplication”, “ArchiveApplication”, “LegalHoldApplication”, “Mailbox Search”, “T
    amMailboxLifecycleApplication”, “MailboxSearchApplication”))
    $roleIdentity = Get-ManagementRole $roleName -DomainController $RoleDomainController;
    $roleAssignment = Get-ManagementRoleAssignment -Role $roleIdentity.Identity -RoleAssignee $appAccount.Id
    ntity -DomainController $RoleDomainController;
    if ($roleAssignment -eq $null)
    New-ManagementRoleAssignment -Role $roleName -User $appAccount.Identity -DomainController $RoleDomai
    ” was run: “Microsoft.Exchange.Data.Directory.ADObjectAlreadyExistsException: Active Directory operation failed
    n MY DOMAIN NAME. The object ‘CN=Exchange Online-ApplicationAccount,CN=Users,MY DOMAIN NAME’ already exists
    —> System.DirectoryServices.Protocols.DirectoryOperationException: The object exists.
    at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, Resu
    tAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
    at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
    at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOpe
    ation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
    at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest reques
    , ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
    — End of inner exception stack trace —
    at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRe
    uest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
    at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest reques
    , ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
    at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest reques
    , ADObjectId originalId, Boolean emptyObjectSessionOnException)
    at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean by
    at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.Save(ADRecipient instanceToSave)
    at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.NewTaskBase`1.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.NewADTaskBase`1.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.Task.b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePip

    he Exchange Server setup operation didn’t complete. More details can be found in ExchangeSetup.log located in the
    SystemDrive>:\ExchangeSetupLogs folder.
    PS] C:\Windows\system32>

    Need HELP please

  2. Dear All,

    I need that all the valuable idea of everyone.

    What ı want to do , we have been using exchange server 2013 with cu7 in our organization. So my question is , we’d like to delete all the healthy mailbox and the healthy mailbox should’t have been re-created again.

    İf it’s possible can you let me understand that the healtly mailbox might delete forever or not .

    Thanks for your efforts to inform me about the topic.


  3. Recently recreated the health mailboxes and now MS System Center Operations Manager (SCOM) is going crazy with alerts. It looks like SCOM still wants to use the old health mailboxes that are no longer there. Is there some additional step that needs to be taken before the recreated health mailboxes are recognized as *the* health mailboxes?

  4. If I have a EWSCtpMonitor Unhealthy due to EWSCtpProbe authentication failure (401 Unauthorized), would recreating the health mailboxes correct this?

  5. I upgraded to CU6 a couple of weeks ago and I just happened to look in the health mailboxes OU and there are 40 objects in there. I know I can delete them and restart the service, but I’m curious as to why so many are there in the first place. Thoughts?

  6. When you say “setup /p” did the job recreating the mailboxes are you referring to this?

    C:\Program Files\Microsoft\Exchange Server\V15\Bin\setup.exe /p

    • HI Michael,

      It looks like a bug and re-creating the health mailboxes was the workaround. Looks like more and more people are having the issue. Hopefully MS will fix it soon!

  7. Hi,
    I’m not sure if your guidance is related to certain Exchange 2013 build, but mine CU2 version does not recreated mailboxes even I restarted the server.
    After restart Health service was not running, I should start it manually, but since that time stil running.
    Is there any other way how to recreate health mailboxes?


Leave a Comment

Disable Windows Copilot Using Intune

Windows Copilot is Microsoft’s take on making life easier for Windows users using the power of AI. This article explains how to disable the feature using Intune, if your organization is not ready yet to walk into the AI world.

Disable Windows Copilot Using Intune

We need to create a Configuration Profile for Windows devices in the Intune portal to disable Windows Copilot. Below are the steps that we need to create the profile.

Launch the Intune Portal and login as a Global Admin or Intune Admin.

Navigate to Devices -> Windows -> Configuration Profiles.

Windows Configuration Profile Intune

Click on Create -> New Policy.

Select Windows 10 & later as the platform and Settings Catalog as the profile type & click on the Create button.

Settings Catalog Intune CoPilot

Give the policy a meaningful name & description and click Next.

Policy Name Disable CoPilot

Within the configuration settings, click on the Add Settings option.

Add Settings Disable CoPilot

Search for ‘copilot’, Windows AI will come up as the category. Click on Windows AI and the Turn off Copilot in Windows (User) setting will come up. Check the box and click Next.

Turn off CoPilot Setting Intune
Turn off CoPilot Setting Intune Summary 1

Specify scope tags if required and click Next.

Select tags CoPilot Intune

Select who this policy should apply to in the Assignments section. I have selected to add all users. If you want to test the setting, you can create a test group and select that group here.

Similarly, you can also exclude certain group from disabling AI (say IT team) if required.

Add all users disable copilot intune

A summary of selected settings will be displayed. Click on the Create button to setup the policy to disable Windows Copilot.

Create configuration policy disable CoPilot Intune 1

Wait for the replication to complete in the cloud backend and login to your machine. Your chatty Copilot should now be disabled.

Disable Windows Copilot On Windows 11 Pro

Follow the steps below to disable Copilot on a personal Windows 11 Pro machine (say your own laptop).

Search for ‘group’ in Windows 11 and click on Edit Group Policy option.

Group Policy Windows 11 Disable Copilot

Navigate to User Configuration -> Administrative Templates -> Windows Components -> Windows Copilot.

Windows Copilot GPO setting

Double click on Turn off Windows Copilot setting on the right pane.

Select Enabled and click OK.

Turn off copilot gpo Windows 11 Pro 1

Close the Group Policy Editor. This will disable Windows Copilot on a Windows 11 Pro machine.


We have learned to disable Windows Copilot using Intune and Group Policy on Windows 11 machines.

Please let me know if you have any questions in the comments section.

Promote Windows Server 2025 To Domain Controller

Domain controllers are the backbone of any Active Directory domains in the Microsoft world. Any Windows server can be promoted to be a domain controller. In this article, we will go through the steps of promoting a Windows 2025 Server to be a domain controller.

Windows Server 2025

The latest version of the server operating system has been named Windows Server 2025. You can start with a 2025 Server & create an AD domain or you can promote a member server that is already a part of a domain.

The Windows Server 2025 needs to be installed on a machine before it can be promoted to be a domain controller.

Promote Windows Server 2025 To Domain Controller

If you have been working with Windows servers long enough, everything starts with the Server Manager app. Promoting a server to a domain controller is no different.

Launch ‘Server Manager’ & click on Add roles and features.

Windows 2025 Server Manager

You land on the summary page that explains what is required to run this wizard successfully. Click Next.

Windows Server 2025 Add Remove Roles

Select Role-based or Feature-based installation and click Next.

Windows Server 2025 Role Based Install

Select the server that needs to be promoted and click Next.

Windows Server 2025 Destination Server

Select Active Directory Domain Services (second option) and click on Add Features.

Windows Server 2025 AD Domain Services

Go with the default options for features that need to be installed.

Windows Server 2025 AD Domain Services Features

A summary of AD DS pops up next, click next to continue.

Windows Server 2025 AD DS

Select Restart the server automatically if required and click Install.

Windows Server 2025 AD Restart Server

You get to keep an eye on the progress of the installation.

Windows Server 2025 AD Install Progress

Once the role has been installed, you will find an exclamation mark on the top right corner of the Server Manager. Click on that and select Promote this server to be a domain controller.

Windows Server 2025 AD Install Continue

You get an error straight away (which you have never seen before) – Error determining whether the target server is already a domain controller. Role change is in progress or this computer needs a restart.

Windows Server 2025 Domain Controller Setup Error

We never needed to restart the server after installing the role in the DC promotion process. Given that it is an insider build of Server 2025, I am hoping that this will get fixed before the public release.

Restart the server, launch Server Manager and click on the Promote this server to be a domain controller option again.

Windows Server 2025 AD Install Continue 1

I am setting up a brand new AD forest and hence I select the third option (Add a new forest) and enter my root domain name.

Windows Server 2025 Add a forest

Next window brings the option to set your forest & domain functional level and the DSRM password. In the insider build, it shows what looks like a variable (the Windows server version on which the you are working).

Windows Server 2025 Forest Functional Level

You can leave the default options in the DNS options wizard and click next.

Windows Server 2025 DNS Options

Enter the netbios name of the domain in the next window and click next.

Windows Server 2025 Netbios Domain Name

You can stick with the default paths for the AD database, log & sysvol folder or pick a location of your choice.

Windows Server 2025 AD Paths

Review the selections that you have made so far and click next.

Windows Server 2025 Options Review

Wait for the green check mark on the prerequisites page and click next.

Windows Server 2025 Pre reqs Check

Click Install in the final window & wait for the magic to happen. Once the machine gets restarted (which it will do automatically), you will have a brand new domain controller based on Windows Server 2025.

Windows Server 2025 AD Snap In


Promoting a Server 2025 to a domain controller follows pretty much the same steps as previous operating systems. The Insider build has few errors that needs to be fixed, but hey, it is an insider build!

Please let me know if you have any questions in the comments section.

Install Windows Server 2025 – Full Guide

Microsoft has released an insider preview of it’s next server operating system named Windows Server 2025. We will have a look at the installation steps involved in setting up a 2025 server.

Windows Server 2025

Microsoft has gone with the same look and feel of Windows 11 operating system in it’s current server operating system – Windows Server 2025. As the product is in insider preview, there might be slight changes before it hits the public shelves.

It is refreshing to see a ‘modern’ feel in the installation process of a server operating system. Gone are the days where the installation of a consumer based OS felt much better compared to it’s server counterpart.

Installing Windows Server 2025

Let’s take a look at the steps involved in setting up a Windows Server 2025 machine. First step is to download the ISO from the Windows Insider portal.

Next step is to boot the virtual / physical machine from the ISO which will kick off the installation of Server 2025.

First option to select is the language settings. Pick the one based which relates to you and click next.

Windows Server 2025 language settings

Select the keyboard settings in the next screen and click next.

Windows Server 2025 keyboard

You get the option to select whether you want to Install Windows Server or Repair the installation. The bottom left corner also has the option to go to the previous version of setup.

Windows Server 2025 setup option

You are asked to enter the product key, which is available in the Windows Insider portal.

Windows Server 2025 product key

Next option to choose is the type of image you want to install – Windows 2025 core or full blown desktop experience.

Windows Server 2025 Desktop

You need to agree to the licensing terms to move forward in the next step.

Windows Server 2025 Agreement License

Select the partition on which the server OS should be installed and click next. You also have the option to slice the partitions the way you see fit in the same screen.

Windows Server 2025 Disk Partitions

The Ready to Install window comes up, click the install button.

Windows Server 2025 Install 1

Installation of Server 2025 is underway and you get to see the progress.

Windows Server 2025 Install Progress

Once the installation is complete, you need to enter an administrator password of your choice to finalize the setup.

Windows Server 2025 Password

And there you go! You see a Windows 11 login screen staring at you ;-)

Windows Server 2025 Login Screen

After logging in, you get to set the options around sending diagnostic data to Microsoft, which I always set as ‘required only’.

Windows Server 2025 Diagnostic Data

The Windows Server 2025 desktop looks similar, doesn’t it? ;-)

Windows Server 2025 Desktop Feel scaled

Now that the server is up and running, you can promote it to be a domain controller.


The Windows Server 2025 has the same look and feel as a Windows 11 operating system. The installation options also provide that modern ‘feel’ and makes it a bit soothing to the eyes!

Please let me know if you have any questions in the comments section.