Note performance counter permission distinction for interactive logons #3744
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I noticed that users in interactive sessions can always view counter data, and only non-interactive logon sessions need to be in the Performance Monitoring Users group in order to view counter data, but the documentation here made no mention of the interactive vs non-interactive distinction, so I have added that information. I noticed that this exception for interactive sessions was introduced in Vista SP1. In Vista RTM, users in interactive sessions had to be in the Performance Monitoring Users group in order to view counter data. I believe that is why this documentation does not mention the interactive session exception, because this documentation was probably written when Vista RTM was released and not updated since.
I noticed that users in interactive sessions can always view counter data, and only non-interactive logon sessions need to be in the Performance Monitoring Users group in order to view counter data, but the documentation here made no mention of the interactive vs non-interactive distinction, so I have added that information. I noticed that this exception for interactive sessions was introduced in Vista SP1. In Vista RTM, users in interactive sessions had to be in the Performance Monitoring Users group in order to view counter data. I believe that is why this documentation does not mention the interactive session exception, because this documentation was probably written when Vista RTM was released and not updated since.
|
|
|
I just want to note that I submitted a similar pull request for the Win32 documentation, which was recently merged into master and is live: MicrosoftDocs/win32#174 https://docs.microsoft.com/en-us/windows/win32/perfctrs/limited-user-access-support |
mairaw
added
the
✨ 1st-time dotnet-api-docs contributor!
|
ping @carlossanlop Can you help get this reviewed? |
carlossanlop
requested review from
tarekgh,
Anipik and
noahfalk
and removed request for
krwq and
wtgodbe
|
Adding the new area owners of PerformanceCounter: @tarekgh @Anipik @tommcdon @noahfalk . Can you please help review this change? |
|
@Anipik can you please review? |
Anipik
approved these changes
Jul 21, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
I noticed that users in interactive sessions can always view counter data, and only non-interactive logon sessions need to be in the Performance Monitoring Users group in order to view counter data, but the documentation here made no mention of the interactive vs non-interactive distinction, so I have added that information.
I noticed that this exception for interactive sessions was introduced in Vista SP1. In Vista RTM, users in interactive sessions had to be in the Performance Monitoring Users group in order to view counter data. I believe that is why this documentation does not mention the interactive session exception, because this documentation was probably written when Vista RTM was released and not updated since.