Skip to content

docs: document the PowerShell engine selector for script tasks #30

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.

Sign up for GitHub

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

Open
mirbach wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: document the PowerShell engine selector for script tasks #30

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/04-Console/13-profiles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,6 +100,12 @@ If you want to install or uninstall an MSI file using WinGet, you’ll need to s

When you add a task to execute a PowerShell script **you can choose between running the script only once or running it every time the endpoint applies the profile**. If you choose to **run the script once** an entry will be created in the agent’s config file **if the script was successfully executed**, if not **it will run again the next time the profile is applied**.

You can also choose which PowerShell engine runs the script:

- **Windows PowerShell 5.1** (default): the built-in engine present on every Windows endpoint.
- **PowerShell 7+ (pwsh)**: uses the modern, cross-platform PowerShell engine. If the endpoint doesn't have PowerShell 7+ installed, the task fails with a clear error instead of silently running under 5.1.
- **Auto**: uses PowerShell 7+ if it's installed on the endpoint, otherwise falls back to Windows PowerShell 5.1.

## Notes about profiles

### Max profile running duration
Expand Down