What is the Backend process behind the Test Credential ?

Anmol8
Mega Guru

Backend process behind the Test Credential ?

1 ACCEPTED SOLUTION

Rahul Priyadars
Giga Sage
Giga Sage

In background a session is opened with the host depending on WMI or SSH and command is fired at run time which we supplied using GUI.

For windows it looks like this- 

The PowerShell command use during test credential is something as below:

Get-WmiObject -Class Win32_ComputerSystem -ComputerName $computer -Credential $cred

You can also check the same by using below steps

Windows Credential

A simple Powershell WMI query directly from the MID Server to the remote machine can be used to test access and permissions. 

Open a PowerShell command line on the host where the MID server is being used and run the following:

gwmi win32_operatingsystem -computer 192.168.200.14 -credential 'LOCALDOMAIN\mid'

Substitute LOCALDOMAIN\mid by the credential to test, and 192.168.200.14 with the target IP address. The expected result would be similar to:

SystemDirectory : C:\Windows\system32
Organization    :
BuildNumber     : 6001
RegisteredUser  : Windows User
SerialNumber    : 12345-OEM-1234567-12345
Version         : 6.0.6001

If the WMI command above fails, either the credential is incorrect or lacks permission. We advise your windows admin team to further investigate the issue. If basic WMI queries from the MID server to the target hosts fails, then discovery and orchestration activities would not be successful.

Regards

RP

View solution in original post

2 REPLIES 2

suvro
Mega Sage
Mega Sage

This thread will answer your question

https://community.servicenow.com/community?id=community_question&sys_id=e25c67751b477894d01143f6fe4bcb13

Rahul Priyadars
Giga Sage
Giga Sage

In background a session is opened with the host depending on WMI or SSH and command is fired at run time which we supplied using GUI.

For windows it looks like this- 

The PowerShell command use during test credential is something as below:

Get-WmiObject -Class Win32_ComputerSystem -ComputerName $computer -Credential $cred

You can also check the same by using below steps

Windows Credential

A simple Powershell WMI query directly from the MID Server to the remote machine can be used to test access and permissions. 

Open a PowerShell command line on the host where the MID server is being used and run the following:

gwmi win32_operatingsystem -computer 192.168.200.14 -credential 'LOCALDOMAIN\mid'

Substitute LOCALDOMAIN\mid by the credential to test, and 192.168.200.14 with the target IP address. The expected result would be similar to:

SystemDirectory : C:\Windows\system32
Organization    :
BuildNumber     : 6001
RegisteredUser  : Windows User
SerialNumber    : 12345-OEM-1234567-12345
Version         : 6.0.6001

If the WMI command above fails, either the credential is incorrect or lacks permission. We advise your windows admin team to further investigate the issue. If basic WMI queries from the MID server to the target hosts fails, then discovery and orchestration activities would not be successful.

Regards

RP