VMware Backup Limitation: Resolving WMI Repository Access Issue | Vembu Backup for Microsoft Hyper-V

WMI Repository Access Issue in BDRSuite Backup for Microsoft Hyper-V

KB ID: 117002
The problem arises when there are difficulties in accessing the Windows Management Instrumentation (WMI) repository in the target host. This can occur due to various reasons:
1. The target host is not reachable.
2. Issues with accessing WMI on the target host.
3. Attempting to add a Standalone Hyper-V Host under Hyper-V Cluster.
4. Backup failure after installing Windows Update KB5014692 on Hyper-V Server, leading to remote WMI connectivity issues.
For Cause 1: Target host is not reachable
The remote share "Admin$" on the target host is required to copy the BDRSuite Integration Services (BIS) installer (which operates as BDRSuite Delegation Service - BDS) to the target machine.
To validate UNC access manually:
1. Press 'Win + R' and enter the command: \\<Hostname or IPAddress>\admin$
   Replace "Hostname or IPAddress" with the actual details.
 2. If successful, proceed. If not, troubleshoot as follows:
          Case 1: Firewall Settings
  1. Open Control Panel and go to System and Security > Windows Firewall > Advanced Setting.
  2. Click Inbound rules > New rule > Predefined option
  3. Select “Remote Service Management” rule and enable it.
         Case 2: Verify Services
   Ensure the following services are running:
  1. Server Service
  2. Windows Remote Management (WS-management)
For Cause 2: WMI Access Issue on the Target Host
Case 1: Firewall Settings
  1. Open Control Panel and go to System and Security > Windows Firewall > Advanced Setting.
  2. Click Inbound rules > New rule > Predefined option.
  3. Select “Windows Management Instrumentation” rule and enable it.
Case 2: Verify Services
Ensure the following service is running:
Windows Management Instrumentation 
 Case 3: NAT Configuration
  1.  Allow WMI port in NAT firewall
  2. Configure WMI to use a fixed port if needed.
WMI port can be static or dynamic, by default WMI port is dynamic.
  1. If your WMI is running in a static port, then directly add the WMI port into NAT firewall.
  2. If your WMI is running in a dynamic port, add the WMI port range into your NAT firewall. The range is from 1024 to 65535.

If not feasible, then convert the WMI port into a static port and add that static port into the firewall setting of NAT.

Note: Make sure both the source and target host operating systems are updated
Steps to convert the WMI port from dynamic to static
1. Set the DCOM config to use a static port:
Step 1: Open Run and type ‘dcomcnfg’ → Enter
Step 2: Navigate the tree to My Computer → DCOM Config → Windows Management and Instrumentation, select properties of that folder.
Step 3: Select the Endpoint tab under Windows Management and Instrumentation properties.
Step 4: Select the Properties button for Connection-oriented TCP/IP
Step 5: Use static endpoint, set the port.
2. Configure WMI to use a fixed port: Follow the steps in the link Change the WMI port to fixed
Confirmation test:
When the above mentioned solutions are verified, perform a pre-test using WBEM utility.
Step 1: Open “wbemtest” in your server/client machine
Step 2: In the namespace text box provide the following: \\Target Hostname (or) IPAddress\root\cimv2
Example: \\root\cimv2
Step 3: Provide the username and password and click on connect
Note: If the target machine you are trying to push is a local machine then do not provide any username and password, just proceed to connect
Step 4: In case of error, then recheck the solution again and wait until the wbem test becomes successful
Once successful, please proceed to add the desired Host.
For Cause 3: Adding Standalone Hyper-V Host under Hyper-V Cluster
Ensure that a standalone host is added on the appropriate page, not on the Hyper-V Cluster page.
For Cause 4: Backup Failure after Windows Update KB5014692
After installing Windows Update KB5014692 on Hyper-V Server, remote WMI connectivity failure may lead to backup issues.
1. Add the following registry key value:
  1. Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole\AppCompat
  2. Value Name: "RequireIntegrityActivationAuthenticationLevel"
  3. Type: dword
  4. Set the value as 0x00000000
Refer to Microsoft KB5004442 for more details.
Note: Apply the changes to all Hyper-V Servers configured for backup with the Windows update KB5014692.
After implementing the appropriate solutions, perform a pre-test using the "wbemtest" utility to ensure successful resolution before proceeding to add the desired host.