Problem: Remote GetPreq Command Failure about atomic-red-team

[cyberbuff]

Hello @jj-cmyk . I ran this on a Win11Pro machine and this seems to work fine.

Can you provide me the versions of powershell-yaml and invoke-atomicredteam you are using ?
You can find those by running the following command

 Get-Module invoke-atomicredteam, powershell-yaml

[robertstrom]

One thing that I have found with elevated prompts is that they do not seem to inherit the PowerShell profile. If you put something like this into your profile

Import-Module "C:\AtomicRedTeam\invoke-atomicredteam\Invoke-AtomicRedTeam.psd1" -Force
$PSDefaultParameterValues = @{"Invoke-AtomicTest:PathToAtomicsFolder"="C:\AtomicRedTeam\atomics"}

# Add this line to ensure that all future PowerShell sessions use TLSv1.2
# In some situations Atomic Red Team launches hidden PowerShell windows that will not use TLSv1.2 unless this command is run for every PowerShell session launched

[Net.ServicePointManager]::SecurityProtocol += [Net.SecurityProtocolType]::Tls12

I have found that if I open an elevated PowerShell prompt those settings do not appear to be imported. I have take to opening the elevate PowerShell prompt and then running

## That is . (period) space $PROFILE to invoke the execution of the profile

.  $PROFILE

After sourcing the profile I have found that the downloading of prereqisites is much more reliable ... locally. I have yet to run Atomic Red Team against a remote system so I do not know what requirements may exist when doing that.

[jj-cmyk]

Hi @cyberbuff please see the below output when running Get-Module invoke-atomicredteam, powershell-yaml
ModuleType Version Name ExportedCommands

---

Script 2.1.0 Invoke-AtomicRedTeam {Get-AtomicTechnique, Get-PreferredIPAddress, Get-Schedule, Invoke-AtomicRunner...}
Script 0.4.7 powershell-yaml {ConvertFrom-Yaml, ConvertTo-Yaml, cfy, cty}

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue was closed because it has been stalled for 5 days with no activity.