KB ID : 117002
Products :
Published : Dec. 4, 2018
Created : Dec. 4, 2018
Last Modified : Feb. 8, 2019

Cause:

1) When added target host is not reachable.

2) When there is an issue in accessing Windows Management Instrumentation [ WMI ] of your target host.

3) When you are trying to add Standalone Hyper-V host in Add Hyper-V cluster.

Solution:

For Cause 1: When added target host is not reachable

Target host Remote share [ Admin$ ] is required for copying the VIS installer to the target machine.

You can confirm UNC validation by verifying the admin$ share access manually from your Machine where “VembuBDR” or “VembuVMBackup" had been installed.

Test for admin$ access

    Go to 'run' and type the following \\IP\admin$ 
    In place of IP provide the “Hostname\IP“ of the target machine 
    **Example:** \\192.168.100.100\admin$

If proceeded further, if you don’t see any network connectivity issue then you can confirm UNC validation is a success.

If you face any network connectivity issue, then here are the steps to troubleshoot:

Case 1: Make sure your firewall does not block following remote connections, if so please add the below rule into your Inbound firewall rules in your target machine

   Step 1: Open control panel 
   Step 2: Navigate to System and Security >Windows Firewall >Advanced Setting
   Step 3: In Windows firewall with advanced security, click Inbound rules.
   Step 4: Inbound rules > click new rule and proceed to opt for Predefined option
   Step 5: In predefined drop-down > select “Remote Service Management “ rule and proceed with the default option to enable it and click finish.

Case 2: Make sure Following services are running in your target machine

   a) Server Service
   b) Windows Remote Management (WS -management)

For Cause 2: When there is an issue in accessing Windows Management Instrumentation [ WMI ] of your target host

Case 1: Make sure your firewall does not block any Windows Management Instrumentation function, if so please add the below rule into your Inbound firewall rules in your target machine

  Step 1: Open control panel 
  Step 2: Navigate to System and Security >Windows Firewall >Advanced Setting
  Step 3: In Windows firewall with advanced security, click Inbound rules.
  Step 4: Inbound rules > click new rule and proceed to opt for Predefined option
  Step 5: In predefined drop-down > select “Windows Management Instrumentation “ rule and proceed with the default option to enable it and click finish.

Case 2: Make sure Following services are running in your target machine

  Window Management Instrumentation

Case 3: If you are using NAT, please make sure WMI port is allowed in NAT firewall

  • WMI port can be static or dynamic, by default WMI port is dynamic.

    I. If your WMI is running in static port, then directly add the WMI port into NAT firewall.
    II. If your WMI is running in dynamic port, add the WMI port range into your NAT firewall. The range is from 1024 to 65535.
    

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

Steps to convert the WMI port from dynamic to static:

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.

Configure WMI to use a fixed port

    Follow steps from below link to change WMI port to fixed:

    https://docs.microsoft.com/en-us/windows/desktop/WmiSdk/setting-up-a-fixed-port-for-wmi

Confirmation test:

When 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 Target hostname\IP : \IP\root\cimv2

Example: \192.168.100.100\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: When you are trying to add Standalone Hyper-V host in Add Hyper-V Cluster

Trying to add standalone Hyper-V IP/Hostname in Add Hyper-V cluster option is not supported.

Prerequisite verification of cluster will fail when standalone Hyper-V IP/Hostname provided.

edit retag flag offensive close merge delete