KB ID : 117044
Products :
Published : Dec. 5, 2018
Created : Dec. 5, 2018
Last Modified : Dec. 28, 2018

Cause:

When prerequisite for cluster nodes are not satisfied will end up in error “Error while adding cluster host” i.e., Unable establishing a connection to the target nodes of the cluster

Prerequisite:

1) Access to the remote share [ admin$]

2) Access to Windows Management Instrumentation

3) Access to Remote Registry

4) Supported Platform

5) Virtual Machine evaluation

6) Confirmation Test: WBEM Test Verification

Note: Make sure you perform the prerequisite on all nodes of the cluster

1) access to the remote share

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 “Vembu BDR” or “Vembu VMBackup" had been installed.

   Go to 'run' and type the following \\Hostname[node]\admin$ 
   Example : \\Node1\admin$

Note: In case of cluster nodes, use only machines names of each node to check for UNC validation

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, below 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

   Server Service 
   Windows Remote Management (WS -management)

When Case1 and Case 2 are verified, try UNC access again as mentioned above from your Server/Client machine in order to confirm successful UNC validation.

2) Access to Windows Management Instrumentation

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

3) Access to Remote Registry

Since we are installing VIS agent in your target machine [Remote], we need access to your remote registry as well

Check for Remote Registry service in your services.msc and make sure the status of “Remote Registry” is running

4) Supported platform

Make sure the target host which you are trying to add falls under the Supported Platforms list:

Microsoft Hyper-V : System Requirements

Microsoft Windows Server\Desktops : System Requirements

5) Virtual Machine evaluation

In case of Target agent being Virtual Machine then VIS push is not supported

6) Confirmation Test : WBEM Test Verification

Note: In case of cluster nodes, use only machines names of each node to check for UNC validation

When Above mentioned prerequisites are verified, perform a pre-test using the WBEM utility.

Step 1: Open “wbemtest” in your server/client machine

Step 2: In the namespace text box provide Target hostname : \machinenamenode\root\cimv2

Example: \node-1\root\cimv2

Step 3: Provide the username and password and click on connect

Note: 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 prerequisite and wait until the wbem test becomes successful

Once successful, please proceed to add the desired Host

edit retag flag offensive close merge delete