GET-History with PSHELL

[Joe Caverly]

I am using;

  _x64: 1
_admin: 1

TCC  24.02.49 x64   Windows 10 [Version 10.0.18362.116]

Using Get-History via PSHELL /S does not return anything.

I have tried;

e:\utils>pshell /s "Get-History"

...and;

e:\utils>pshell /s "Get-History | out-file 'e:\utils\results.txt'"

e:\utils>type results.txt

...and;

e:\utils>pshell /s "$x = Get-History"

e:\utils>pshell /s "$x"

Is this WAD? I have no problem with the Get-History command working in Powershell.

Joe

 

[AnrDaemon]

Why it should? Normally, history is for typed commands. Not for API calls.

 

[vefatica]

Why it should? Normally, history is for typed commands. Not for API calls.

I think AnrDaemon is correct. Get-History would work if there were some history to get. Try this.

In a PowerShell session, run a few commands and then

Get-history | Export-Csv path\file

Quit PowerShell and in a TCC session

PSHELL /s "Import-Csv path\file | Add-History"
PSHELL /s Get-History

 

[vefatica]

FWIW, these commands, in Microsoft.PowerShell_profile.ps1 (or whatever it's named) will give a history that persists between sessions. This history is loaded when you use PSHELL.

$HistoryFilePath = Join-Path ([Environment]::GetFolderPath('UserProfile')) .ps_history

Register-EngineEvent PowerShell.Exiting -Action { Get-History | Export-Clixml $HistoryFilePath } | out-null

if (Test-path $HistoryFilePath) { Import-Clixml $HistoryFilePath | Add-History }

 

[Joe Caverly]

Hey @vefatica , the Import-CSV does what I want.

After Importing the CSV file, I can run;

pshell /s "2..3 | ForEach {Invoke-History -Id $_ }"

to run commands 2 through 3 from my history.csv file.

Joe

 

[vefatica]

Hey @vefatica , the Import-CSV does what I want.

After Importing the CSV file, I can run;

pshell /s "2..3 | ForEach {Invoke-History -Id $_ }"

to run commands 2 through 3 from my history.csv file.

Joe

I guess that's good. How's the CSV file getting made?

 

[Joe Caverly]

I guess that's good. How's the CSV file getting made?

This is a task that I was running in Powershell using the above technique.

I just wanted to run it via PSHELL, which I can now do, thanks to your solution.

I was hoping that, since PSHELL and TCC share environment variables, that the history would also be shared.

Joe

 

[vefatica]

This is a task that I was running in Powershell using the above technique.

I just wanted to run it via PSHELL, which I can now do, thanks to your solution.

I was hoping that, since PSHELL and TCC share environment variables, that the history would also be shared.

Joe

PSHELL doesn't start PowerShell.exe. The only environment variables involved are TCC's.