KB ID : 115083
Products :
Published : July 23, 2018
Created : July 23, 2018
Last Modified : Nov. 30, 2018

Summary

  1) Service logon check

  2) UNC path validation 

  3) Agent Credentials validation

  4) Support Platform

  5) Access to Windows Management Instrumentation

  6) Access to Remote Registry 

  7) Hyper-V Evaluation

        a) Hyper-V role evaluation

        b) SMB role evaluation

        c) Virtual Machine evaluation

  8) Confirmation test: wbem test

1) Service logon check

Make sure VembuBDR / Vembu VMBackup client services are running with either one of the following privileges, in order to proceed with remote installation of VIS.

  • Administrator
  • A user having administrator privilege

Steps to add/verify Service logon on your Server / Client machine

Step 1: Go to "Run" and type “Services.msc”

Step 2: On Services.msc check for “VembuBDR” or “VembuVMBackup” service accordingly from where VIS push is about to take place

Step 3: Right-click the service [ VembuBDR/VembuVMBackup” ] and click properties and navigate to “Logon”

Step 4: Here provide your user details in “This Account” column

Example: If your user is “Administrator” and password in “Test123$”, then provide

  **This account** = .\Administrator 

  **Password** = Test123$

  **Confirm Password** = Test123$

Step 5: Once user account details are updated, proceed by giving “Apply” and then “OK”.

Step 6: Restart the respective service for the changes to apply.

Note: In case you face issues during service restart, then recheck the user credentials provided during logon update.

2) UNC Path validation [ Admin$ ] access for remote share

Applicable: Hyper-V & Windows Server

Note: In case of pushing VIS to cluster then below mentioned verification to be performed in all available nodes of the cluster

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.

  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 and you don’t see any network connectivity issue - it confirms 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

  Server Service 
  Windows Remote Management (WS -management)

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

3) Agent Credentials Verification

Try validating the user credentials of the target machine

  **Recommended User privilege for Hyper-V:** Domain administrator
  **Supported User privilege for Hyper-V:** Administrator / User with administrator privilege 
  **Supported User privilege for Windows Server:** Administrator for Remote installation and Non-administrator for Manual VIS installation

4) Supported Platforms

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) Access to Windows Management Instrumentation

Applicable: Hyper-V & Windows Server

Note: In case of pushing VIS to cluster then below mentioned verification to be performed in all nodes listed in cluster

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 Settings
  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 the following service is running in your target machine

  Window Management Instrumentation

6) Access to Remote Registry

Applicable: Hyper-V & Windows Server

Note: In case of pushing VIS to cluster then below mentioned verification to be performed in all nodes listed in cluster

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.

7.A) Hyper-V role evaluation

Applicable: Hyper-V

Note: In case of pushing VIS to cluster then the below-mentioned verification part is to be performed in all nodes listed in cluster

If you are trying to push VIS from “Add Hyper-V Server" (StandAlone) make sure Hypervisor is enabled in your target machine

7.B) SMB role evaluation

Applicable: Hyper-V - SMB

If you are trying to push VIS from “Add SMB Server" make sure SMB role [FileServer] is enabled in your target machine

7.C) Virtual Machine evaluation

Applicable: Hyper-V

Note: In case of pushing VIS to cluster then below mentioned verification part to be performed in all nodes listed in cluster

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

8) Confirmation Test: WBEM Test Verification

When the above-mentioned prerequisites are verified, perform a pretest 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 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 any error, recheck the prerequisites and wait until the wbem test becomes successful

Once successful, please proceed to add the desired Host

edit retag flag offensive close merge delete