Error message during execution on a laptop about meerkat HOT 10 CLOSED

Hi,

I have tried the new build and it works fine :)

Thanks a lot

Yossi

from meerkat.

You'll likely need to enable winrm, as specified in the error. try this

PsExec.exe -s \\$TargetComputer -accepteula powershell -ExecutionPolicy ByPass -nologo -command "Enable-PSRemoting -Force"

... where $TargetComputer is your target

another option is using "winrm quickconfig"

I'll look into adding this into the tool directly OR partially removing WinRM dependencies (e.g. no WinRM requirement when called via the psexec module)

from meerkat.

I've found a way to remove the WinRM requirement when doing a local collection or using the psexec wrapper. Will be reflected in next major update.

from meerkat.

All modules were adjusted to no longer require WinRM when either scanning the local system OR using the psexec wrapper Invoke-THR_PSExec

from meerkat.

Hi,

Thank you for your efforts

I will try the new build.

Regards

Yossi

from meerkat.

I see similar errors when running Meerkat from master. Is there a flag or something to enable for this fix?

from meerkat.

zwass,
One of the core requirements of remoting with Meerkat is that WinRM be enabled and the endpoint (if remote) be reachable. There is one alternative provided in the psexec wrapper, mentioned above.

If you want to post the command and error I'll be able to see if it's this issue or another.

from meerkat.

Ah, I didn't realize that Meerkat was attempting to reach out to remote machines. Is it possible to run it to just collect the results on the local machine? Could this be done without enabling WinRM?

from meerkat.

If you run the command below it will run locally using Invoke-Command, so it's subject to all invoke-command requirements, which includes WinRM. If you're getting an error, please send it up and I'll take a look.
Invoke-Meerkat

Optionally, you can run the modules directly and bypass Invoke-Command
get-computerdetails | export-csv c:\temp.csv -NoTypeInformation

I will look into making something like Invoke-Meerkat-Local that completely drops the Invoke-Command dependency.

To resolve your issue, you can set up winrm on your system as outlined above or here
https://github.com/TonyPhipps/Powershell/blob/master/Enable-WinRM.ps1

from meerkat.

https://github.com/TonyPhipps/Meerkat/projects/1#card-31127749

from meerkat.