Windows discovery error

Pranita2
Kilo Guru

Hi,

 

While discovering few windows servers, they are failing with following errors:

launchWMI : Access is denied. (Exception from HRESULT: 0x80070005(E_ACCESSDENIED))At D:\SIAM City Thailand DC  MID ServerAgent\scripts\PowerShell\WinRMAPI\ExecuteRemote\ExecuteRemote.psm

 

Credentials are getting validated successfully.

Can anyone help in resolving this issue?

 

Thanks,

Pranita

1 ACCEPTED SOLUTION

HI,

Check this things:

https://hi.service-now.com/kb_view.do?sys_kb_id=74e16b16db6ebb006064eeb5ca9619dd&sysparm_rank=1&sysp...

https://docs.servicenow.com/bundle/madrid-it-operations-management/page/product/discovery/reference/...

 

This is important:

https://hi.service-now.com/kb_view.do?sys_kb_id=16eb857edbde9bc04816f3231f9619a5&sysparm_rank=6&sysp...

Here from MID Server you can trigger few queries to check the connection:

Common Exploration Phase Errors


Below is a list of common exploration phase issues as well as suggestions on how to resolve them.

  • WMI and Powershell
    • The impersonation of the user failed.
    • Ensure that the domain is specified, along with the username in the credentials.
  • Connection failed to WMI service and other common Windows (WMI/Powershell) error messages:

    Error: The remote server machine does not exist or is unavailable

    Failed to access target system. Please check credentials and firewall settings on the target system to ensure accessibility: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

    Failed to access target system. Please check credentials and firewall settings on the target system to ensure accessibility: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

    • WMI, does the mid server service account have access to the targeted machine? What if a domain admin account is used as the mid server service account?
    • From the command prompt on the mid server host, execute for runner_type=WMI

      wmic /node:"<target>" /user:"<user>" /password:"<password>" path win32_operatingsystem
       
    • From within a Powershell console on the mid server host, execute for runner_type=Powershell

      gwmi win32_operatingsystem -computer <ip> -credential '<username>'
       
    • It is possible that probe is timing out while waiting for a response. If the command is successful from a command prompt, try extending the wmi_timeout value of the probe.

Thanks,
Ashutosh

View solution in original post

7 REPLIES 7

HI,

Check this things:

https://hi.service-now.com/kb_view.do?sys_kb_id=74e16b16db6ebb006064eeb5ca9619dd&sysparm_rank=1&sysp...

https://docs.servicenow.com/bundle/madrid-it-operations-management/page/product/discovery/reference/...

 

This is important:

https://hi.service-now.com/kb_view.do?sys_kb_id=16eb857edbde9bc04816f3231f9619a5&sysparm_rank=6&sysp...

Here from MID Server you can trigger few queries to check the connection:

Common Exploration Phase Errors


Below is a list of common exploration phase issues as well as suggestions on how to resolve them.

  • WMI and Powershell
    • The impersonation of the user failed.
    • Ensure that the domain is specified, along with the username in the credentials.
  • Connection failed to WMI service and other common Windows (WMI/Powershell) error messages:

    Error: The remote server machine does not exist or is unavailable

    Failed to access target system. Please check credentials and firewall settings on the target system to ensure accessibility: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

    Failed to access target system. Please check credentials and firewall settings on the target system to ensure accessibility: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

    • WMI, does the mid server service account have access to the targeted machine? What if a domain admin account is used as the mid server service account?
    • From the command prompt on the mid server host, execute for runner_type=WMI

      wmic /node:"<target>" /user:"<user>" /password:"<password>" path win32_operatingsystem
       
    • From within a Powershell console on the mid server host, execute for runner_type=Powershell

      gwmi win32_operatingsystem -computer <ip> -credential '<username>'
       
    • It is possible that probe is timing out while waiting for a response. If the command is successful from a command prompt, try extending the wmi_timeout value of the probe.

Thanks,
Ashutosh

Azim Kazi
Giga Guru

Hi Pranita,

have a look at blog which is given below:

 

  • WMI and Powershell
    • Ensure that the domain is specified, along with the username in the credentials.
  • The remote server machine does not exist or is unavailable
    • Failed to access target system. Please check credentials and firewall settings on the target system to ensure accessibility: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
    • Failed to access target system. Please check credentials and firewall settings on the target system to ensure accessibility: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
      • From the command prompt on the mid server host, execute for 

        wmic /node:"<target>" /user:"<user>" /password:"<password>" path win32_operatingsystem
         
      • From within a Powershell console on the mid server host, execute for runner_type=Powershell

        gwmi win32_operatingsystem -computer <ip> -credential '<username>'
         

It is possible that probe is timing out while waiting for a response. If the command is successful from a command prompt, try extending the wmi_timeout value of the probe.

 

 

 

Hope this will help you!!

If my response helps you then kindly mark my answer helpful 👍and correct ✔otherwise if any query 🤔 feel free to ask further.

 

Regards,

Ajim.

Azim Kazi
Giga Guru

Hi Pranita,

Have a look at blog which is given below:

 

  • WMI and Powershell
    • Ensure that the domain is specified, along with the username in the credentials.
  • The remote server machine does not exist or is unavailable
    • Failed to access target system. Please check credentials and firewall settings on the target system to ensure accessibility: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
    • Failed to access target system. Please check credentials and firewall settings on the target system to ensure accessibility: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
      • From the command prompt on the mid server host, execute for 

        wmic /node:"<target>" /user:"<user>" /password:"<password>" path win32_operatingsystem
         
      • From within a Powershell console on the mid server host, execute for runner_type=Powershell

        gwmi win32_operatingsystem -computer <ip> -credential '<username>'
         

It is possible that probe is timing out while waiting for a response. If the command is successful from a command prompt, try extending the wmi_timeout value of the probe.

 

 

 

Hope this will help you!!

If my response helps you then kindly mark my answer helpful 👍and correct ✔otherwise if any query 🤔 feel free to ask further.

 

Regards,

Ajim.