Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update PowerShell Transcripts default location #943

Merged

Conversation

Qazeer
Copy link
Contributor

@Qazeer Qazeer commented Jun 15, 2024

Description

Update the default location of PowerShell transcripts to C:\Users\%user%\Documents\ (from C:\Users\%user%\Documents\20*\).

According to MS documentation and personnal tests, the transcripts files are directly placed into a user documents folder by default. Tested on PowerShell 2.0 (on Windows XP), PowerShell 4.0 (on Windows Server 2012R2), PowerShell 5.1 and PowerShell 7.2 (on Windows 10).

Checklist:

Please replace every instance of [ ] with [X] OR click on the checkboxes after you submit your PR

  • I have generated a unique GUID for my Target(s)/Module(s)
  • I have placed the Target(s)/Module(s) in an appropriate subfolder in Targets or Modules. If one doesn't exist, I have either added it to the Misc folder or created a relevant subfolder with justification
  • I have set or updated the version of my Target(s)/Module(s)
  • I have verified that KAPE parses the Target(s)/Module(s) successfully via kape.exe, using --tlist/--mlist and corrected any errors
  • I have validated my Target(s)/Module(s) against test data and verified they are working as intended
  • I have made an attempt to document the artifacts within the Target(s) or Module(s) I am submitting. If documentation doesn't exist, I have placed N/A underneath the Documentation header

@AndrewRathbun AndrewRathbun self-assigned this Jun 15, 2024
@AndrewRathbun AndrewRathbun merged commit fd845e1 into EricZimmerman:master Jun 15, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants