Troubleshooting PowerShell discovery issues

Cannot discover a host by using PowerShell

Issue symptom

A host that you expect to find by using PowerShell is not discovered.

Resolution

It is often the case that the Windows Remote Management (WS-Management) service is not running. Verify if the Windows Remote Management (WS-Management) service is running for the target host. To do so, on your local Windows host, use the following PowerShell command:

Enter-PSSession -ComputerName DISC-QA03.test.lab -Credential DOMAINNAME\Administrator

Cannot discover a host by using JEA

Issue symptom

A host that you expect to find by using JEA is not discovered.

Resolution

To diagnose discovery failures when you are using JE, use the following steps: 

1. Verify that JEA is correctly configured on the target host. Check that the session configuration file has the following parameters defined:

   language  =  'FullLanguage'
   session type  = 'Default'
2. Test the connection from any Windows host to target host. In a Windows PowerShell prompt, enter the following commands:
   1. PS C:\> Set-Item WSMan:\localhost\Client\TrustedHosts -Value target-host 
      to add target-host to the trusted hosts list.
   2. PS C:\> Enter-PSSession -ComputerName target-host -ConfigurationName JEA-endpoint-name -Credential PowerShell-User-in-discovery-credential
      to test the connection to target-host.
3. On the Manage > Credentials page, check the credential.

4. Check the logs for messages of the form: Initialising RunspacePool object for configuration <Endpoint name> 

   • For the appliance (from the Administration > Logs), check tw_svc_discovery.log
   • For the Active Directory Windows proxy, check the proxy log discoproxy_worker_<nnnn>, located in:
     C:\Program Files\BMC Software\Discovery Proxy\runtime\<proxy_name>\log\
     For example: C:\Program Files\BMC Software\Discovery Proxy\runtime\AD proxy\log\discoproxy_worker_6392

   • For the BMC Discovery Outpost using a PowerShell credential, check the discovery_worker.name.<ID> log, located in:
     C:\Program Files\BMC Software\Discovery Outpost\log\
     For example : C:\Program Files\BMC Software\Discovery Outpost\log\discovery_worker.cmdbsync-trial.trial.99f5d03bf54b1e28662c0a3f030d0470
   • For the BMC Discovery Outpost using an Active Directory credential, check the discoproxy_worker_<nnnn> log, located in:
     C:\Program Files\BMC Software\Discovery Outpost\runtime\<ID>\log\
     For example : C:\Program Files\BMC Software\Discovery Outpost\runtime\99f5d23bf54c74061e060a3f030d0470\log\discoproxy_worker_7088