As grasshopper pointed out the psremoting is not required for this. The asset scan completed with errors. The asset scan has two parts. The software scan is not WMI based, but the hardware is. Adam was having you do that to confirm it was definitely WMI that was causing the issue. You can try the telnet test from the KB Adam sent to confirm that 135 is available. If that is open and WMI service is started then we will likely have to know more about your situation. OS of the target? Is it domain joined? Can you perform this script against any machines in your environment (or an asset hardware scan)?
Asset scans require port 135, while patch normal scans do not.
- Verify if Port 135 is listening on the Target Machine.
- Verify if you are able to successfully Telnet to port 135. For example, Telnet MachineName 135. You can use the IP address instead of the machine name for this test.
- Check if you receive a Connection Refused error or see a blank screen with a flashing cursor. The blank screen with a flashing cursor indicates success.
- If firewalls are enabled, - port 135 and other required scanning ports must have an exception.
Regards,
Chris Goettl