- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2016 01:19 PM
Hi everyone,
I've got a custom PowerShell script that I'm attempting to use for discovery. The script needs specific credentials, which I have added as 'windows' credentials. However whenever I test the probe it always returns with the following error:
Authentication failure with the local MID server service credential.
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)
In the script I'm using the $cred variable for supplying the credentials to the command being run. If I set the $cred variable in a PowerShell session on the MID server and run the script manually it runs successfully and outputs the XML data that I'm looking to get back from the probe.
Has anyone run into a similar issue with a PowerShell probe? How can I further troubleshoot the issue?
Thanks,
David Bernard
Solved! Go to Solution.
- Labels:
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-04-2016 05:48 AM
The script file on the MID server 'Credentials.psm1' performs a WMI query to validate credentials for the source. In my case since this was not a Windows server the WMI queries would all fail making it seem like it couldn't connect to the source.
To correct the issue I added a new function to the script file to validate credentials for my type of CI and then on the PowerShell probe I added a parameter to specify the credtype parameter as that same type. For this to work natively the function should be named 'testCredential' with your type appended at the end. In my instance I named the function 'testCredentialpure'.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2016 01:36 PM
David,
Sounds as if you are having problems getting on the host in the first place.. can you confirm if you have discovered the computer first?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2016 04:21 AM
Hi Doug,
The PowerShell module that I'm using is for a Pure Storage array. It currently isn't being discovered. The probe I built was in an attempt to add functionality for properly discovering the storage device. The cmdlets in the module have parameters that allow me to specify the host by IP and the credentials to use for the connection. In the script I've written I'm using the $computer and $cred variable for these parameters.
I'm using the 'Test Probe' link on the probe's form to test the output of the probe against an array, which is where I'm getting the error.
Thanks,
David Bernard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2016 01:55 AM
Hi David,
is the WMI Service running on the target windows server you wish to discover? Is file and print sharing allowed on the target?
Otherwise it might be a firewall issue. As Doug mentioned, can you discover the target at this moment?
Kind regards,
Stijn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2016 04:34 AM
Hi Stijin,
The target system is a Pure Storage array. I don't believe it is a firewall issue as in a PowerShell session on the MID server I can run the script manually using the same credentials I have specified in my instance and it runs successfully giving me the XML output that I'm expecting the probe to return. I'm assuming that the PowerShell session that is started to run the script is opened on the MID server and not the target CI (in my case the Pure Storage array), is that correct?
Is there something I can do to further troubleshoot what is occurring at runtime? What credentials are being used, etc?
Thanks,
David Bernard