AD object "CAUCLU" causing problems on Hyper-V cluster and VMM2016 / Event observer error

BARRE Kevin 1 Reputation point
2022-08-03T13:57:52.53+00:00

Hello, I'm coming to you about several small problems I'm experiencing on a customer's infrastructure, I intervene weekly on site for operation missions, I'll start to present you the customer infrastructure.

We have a hyper-V cluster named CLU-VIR-01 consisting of 6 hypervisors running Windows 2016, the Windows volumes are hosted on a PureStorage array just like the QUORUM. The Vmm 2016 software is used to create Vm or other.

CAUCLU-Vqyx is an AD computer/workstation object present in the OU "user" with the description Failover cluster virtual network name account

There is no DNS entry with this name, and no physical machine or VM with this name on the network at this time.

227733-imagepngb489f656ac2124dd0007764d4b43667b.png

Thinking that this AD object corresponded to an old machine, we started by deactivating the AD object, then we encountered an instability on the information feedback concerning the hypervisors on VMM2016, the hypervisors and Vm appeared in red with as status, error or not found, I don't know. We were surprised and checked the status of the cluster on the "cluster and failover manager", the cluster was healthy, all the hypervisors were online and accessible as well as the VMs, the users on their side declared no production loss. We quickly put in question the AD CAUCLU object that we reactivated, a few seconds later, VMM2016 displayed much more reassuring information the cluster seemed to be operational again (on VMM)

Another aspect that we do not manage to understand, on the 6 hypervisors we have DCOM error events could not communicate with the computer CAUCLU-Vqyx.mondomine.fr using the configured protocols; request of the PID 45 bc (C:\Windows\system32\ServerManager.exe). Moreover, I already proceeded several times to the removal of CAUCLU-Vqyx from the server manager of the 6 hypervisors but they resurface shortly after just like the events of the event viewer.

227639-imagethumbpng769e5d7af8ee5b7d283bb2e20c42a7e9.png

227751-imagethumbpnge9e3856f659bd34a84269a8cd90e8bb0.png
So much mystery about the AD object, if you have a little idea, I'm a taker :)

Thanks to you, nice day.

Kévin

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,389 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,935 questions
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,560 questions
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
962 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Xu Gu (Shanghai Wicresoft Co,.Ltd.) 501 Reputation points Microsoft Vendor
    2022-08-30T09:22:14.557+00:00

    Hello BARREKevin,

    This occurs when a WMI request cannot communicate with a remote node on the target device because of invalid credentials or an invalid WMI namespace.
    My advice is as follows:

    1. Make sure the remote computer is online;
    2. This issue may be the result of the firewall blocking the connection, you can check if the firewall is blocking the remote connection;
    3. For security reasons, it is not recommended to enable COM+ network access by default;
    4. Disable the uninstall SNP function in the registry;
    5. In Component Services, check to see if there are any permissions missing, and if so, you need to complete the permissions, the directory is as follows:
      Console Root-->Component Service-->Computers-->My Computer-->DCOM Config
      After configuring the permissions, restart the service and system.

    Hope my answer helps you!

    Best Regards,
    Xu Gu

    0 comments