You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Modules/Invoke-Meerkat.psm1
+4-4
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ function Invoke-Meerkat {
8
8
9
9
Invoke-Meerkat takes advantage of the `export-csv` cmdlet in this way by exporting ALL enabled modules to csv. The basic syntax is `Invoke-Meerkat -Computer [Computername] -Modules [Module1, Module2, etc.]` (details via `get-help Invoke-Meerkat -Full`).
10
10
11
-
When running a single function against a single endpoint, the typical sytnax is 'Get-[ModuleName] -Computer [ComputerName]', which returns objects relevant to the function called. All modules support the pipeline, which means results can be exported. For example, 'Get-[ModuleName] -Computer [ComputerName] | export-csv "c:\temp\results.csv" -notypeinformation' will utilize PowerShell's built-in csv export function (details via 'get-help Get-[function] -Full').
11
+
When running a single function against a single endpoint, the typical sytnax is 'Get-[ModuleName] -Computer [ComputerName]', which returns objects relevant to the function called. All modules support the pipeline, which means results can be exported. For example, 'Get-[ModuleName] -Computer [ComputerName] | export-csv "c:\temp\results.csv" -NoTypeInformation -Encoding UTF8' will utilize PowerShell's built-in csv export function (details via 'get-help Get-[function] -Full').
12
12
13
13
.PARAMETERComputer
14
14
Computer can be a single hostname, FQDN, or IP address.
0 commit comments