Error – The Cluster Service Cannot Be Started. An Attempt To Read Configuration Data From Windows Registry Failed With Error ‘2’.

MS Exchange

While doing a Exchange DR test, Exchange mailbox servers in the primary datacentre failed to add itself back into the DAG’s underlying cluster.

The error message I got is shown below.

Log Name:      System

Source:        Microsoft-Windows-FailoverClustering

Event ID:      1090

Task Category: Startup/Shutdown

Level:         Critical

User:          SYSTEM

Computer:      EX01.HEW.LOCAL

Description:

The Cluster service cannot be started. An attempt to read configuration data from the Windows registry failed with error ‘2’. Please use the Failover Cluster Management snap-in to ensure that this machine is a member of a cluster. If you intend to add this machine to an existing cluster use the Add Node Wizard. Alternatively, if this machine has been configured as a member of a cluster, it will be necessary to restore the missing configuration data that is necessary for the Cluster Service to identify that it is a member of a cluster. Perform a System State Restore of this machine in order to restore the configuration data.

While running the Start-DatabaseAvailabilityGroup “DAG Name” cmdlet which will add the “evicted” DAG members back into the cluster, the process fails with the error above. I noticed that the cluster service was set to disabled. Trying to start it manually failed. The following steps were taken to fix the issue.

  1. Make sure that the cluster files are excluded in the AV scanning. If not, exclude the folder (C:\Winnt\Cluster). I tried stopping the AV service to “unlock” the cluster files.
  2. Try a force cleanup of the cluster from the failed server. Run Cluster Node “ServerName” /forcecleanup from an elevated command prompt.
  3. Once the cleanup is successful, open Failover Cluster Manager and add the failed server manually back into the cluster. You can also try running Start-DatabaseAvailabilityGroup “DAG Name” –MailboxServer “FailedServer”.

Other Popular Articles


MS Exchange

Scripting Agent Initialization Failed: “File is not found” Error During Exchange 2016 Setup

MS Exchange

EAC Access While Co-Existing Exchange 2013 With 2010

MS Exchange

Delete All Calendar Entries In An Exchange 2010 Mailbox

  1. we trayed to force cleanup. But problem is not resolve
    We have 3 mailbox Server 1 in DR 2 in DC.
    Mailbox Server 1 Is Syncd DR To Dc.
    But Mailbox Server 2 Is not start the cluster service.
    We are Run Cluster Cleanup command in mailbox server2 command run is successfully
    but run Start Dag Command :-Start-DatabaseAvailabilityGroup -Identity DAGNAME -mailboxserver Faild Mailbox Server Name

    after run getting the error Event Id 1090 Please suggest

    Reply
  2. The Cluster service cannot be started. An attempt to read configuration data from the Windows registry failed with error ‘2’. Please use the Failover Cluster Management snap-in to ensure that this machine is a member of a cluster. If you intend to add this machine to an existing cluster use the Add Node Wizard. Alternatively, if this machine has been configured as a member of a cluster, it will be necessary to restore the missing configuration data that is necessary for the Cluster Service to identify that it is a member of a cluster. Perform a System State Restore of this machine in order to restore the configuration data. Event Id 1090

    Reply
  3. Hi Steen.

    I’m in your similar situation.
    But when i try to remove node from dag i get an error that says “unable to form quorum for database avialability group”

    Any suggestion ?

    Reply
  4. I have two node cluster .Node1 and Node2 ,but on both the node cluster service is failing to start and giving error like

    The Cluster service cannot be started. An attempt to read configuration data from the Windows registry failed with error ‘2’. Please use the Failover Cluster Management snap-in to ensure that this machine is a member of a cluster. If you intend to add this machine to an existing cluster use the Add Node Wizard. Alternatively, if this machine has been configured as a member of a cluster, it will be necessary to restore the missing configuration data that is necessary for the Cluster Service to identify that it is a member of a cluster. Perform a System State Restore of this machine in order to restore the configuration data.

    Reply
    • Thank you for the useful posts.
      Unfortunately in my case we had a 2 node Exchange 2013 DAG where both nodes had lost their cluster configuration and we had this error on both nodes when trying to start the cluster service. Datacenter Activation Coordination (DAC) mode was enabled on the database and Stop-DatabaseAvailabilityGroup had been run against both AD sites (warning: please note this command actually clears the clusterconfigurations – it’s not just a “stop and do nothing” command). The original filesharewitness (third site) was unavailable. Restore-DatabaseAvailabilityGroup, Start-DatabaseAvailabilityGroup, net start clussvc /forcequorum (/fq) and lots of other tricks failed.
      Eventually we had to:
      1. Remove database replica from one node
      2. Remove the node from the original DAG
      3. Create a new DAG on the now “clean” node
      4. Mount the database in the new DAG using database portability feature – see: http://technet.microsoft.com/en-us/library/dd876926(v=exchg.150).aspx
      This involved:
      4a. An ESEUTIL /R E00 command against the old database
      4b. Create a new database (used gui)
      4c. Set-MailboxDatabase -AllowFileRestore $true against new database
      4d. Move E00* and *.edb files from old database to new database directory and rename the edb file to its new name
      4e. Mount-Database
      4f. Get-Mailbox -Database |where {$_.ObjectClass -NotMatch ‘(SystemAttendantMailbox|ExOleDbSystemMailbox)’}| Set-Mailbox -Database
      (at this point the mail service was re-established, Outlook clients started connecting again and queued mail was delivered to mailboxes)
      4g. Get-Mailbox -Database -Arbitration | Set-Mailbox -Database -Arbitration
      5. Remove the remaining remants of the original database and the original DAG from the second node
      6. Join the second node to the new DAG
      7. Re-establish database replication

      Note: we used the cluster node /forcecleanup and -ConfigurationOnly switch a few times for the above procedures to work.
      Theoretically I would have thought the Restore-DatabaseAvailabilityGroup command should have given a “clean” cluster node (cluster node /forcecleanup) its cluster configuration based on the DAG configuration stored in Active Directoy but it seems that’s not how it works. Creating a new DAG works though so there must be some underlying commands in the Restore-DatabaseAvailabiltyGroup command that requires the cluster configuration to be at least partly present. Luckily creating a new DAG and using the database portability feature saved the day for us – definitely something I will remember if I’m ever involved in a similar disaster again.

      Reply
  5. I am having the same issue I cannot add the node one of DAG ,it gives unable to successfully cleanup , I forcecleanup the node which ran sucessfully but when I ran the following command it gives me the following error ……….how can I resolve any help would be appreciated.

    [PS] C:\Windows\system32>start-databaseavailabilitygroup DAG01 -mailboxserver trgemail01
    WARNING: The operation wasn’t successful because an error was encountered. You may find more details in log file
    “C:\ExchangeSetupLogs\DagTasks\dagtask_2013-09-02_12-51-36.416_start-databaseavailabilitygroup.log”.
    You can run this command on a database availability group (DAG) only when the DatacenterActivationMode parameter for th
    e DAG is set to DagOnly, which is not true for DAG TRGDAG01.
    + CategoryInfo : InvalidArgument: (:) [Start-DatabaseAvailabilityGroup], TaskCanOnlyRunOnDacException
    + FullyQualifiedErrorId : ADF00ECA,Microsoft.Exchange.Management.SystemConfigurationTasks.StartDatabaseAvailabilit
    yGroup

    Reply
  6. I have just experienced the same problem in my environment. On step 2 I receive this output:

    H:\>cluster ucpsdag node ucpsmnbx1 /forcecleanup

    Attempting to clean up node ‘ucpsmnbx1’ …
    The first error encountered is shown below. For a complete list of errors
    and suggestions for recovery, see the Failover Clustering application event
    log using Event Viewer on the node.
    System error 1722 has occurred (0x000006ba).
    The RPC server is unavailable.

    Reply

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.

Summary

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

Summary

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.

Summary

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.