Skip to content

update doc to reflect change in telemety opt out #2316

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

Merged
merged 1 commit into from
Apr 9, 2018
Merged

update doc to reflect change in telemety opt out #2316

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
5 changes: 2 additions & 3 deletions reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-Core-60.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -378,9 +378,8 @@ For a complete list of fixes and changes, check out our [changelog][] on GitHub.
- the OS platform (`$PSVersionTable.OSDescription`)
- the exact version of PowerShell (`$PSVersionTable.GitCommitId`)

If you want to opt-out of this telemetry, simply delete `$PSHome\DELETE_ME_TO_DISABLE_CONSOLEHOST_TELEMETRY`
or create `POWERSHELL_TELEMETRY_OPTOUT` environment variable with one of the following values: `true`, `1` or `yes`.
Deleting this file or creating the variable bypasses all telemetry even before the first run of PowerShell.
If you want to opt-out of this telemetry, simply create `POWERSHELL_TELEMETRY_OPTOUT` environment variable with one of the following values: `true`, `1` or `yes`.
Creating the variable bypasses all telemetry even before the first run of PowerShell.
We also plan on exposing this telemetry data and the insights we glean from the telemetry in the [community dashboard][community-dashboard].
You can find out more about how we use this data in this [blog post][telemetry-blog].

Expand Down