For anybody looking for a PowerShell script, this ought to do it:
It gets the list of users who have a profile on the local machine, determines their names from the SID, and invokes - as recommended by Ramhound - on them. Each user's record starts with the username in format, contains each right on a line, and ends with a blank line. (SID translation courtesy of this article.) You can dump its stuff to a file with the redirection operator, .
A caveat of AccessChk is that it seems to produce an empty list for domain users that don't have local admin rights. Therefore, this version that produces the above information for every known user in the domain and on the machine is a little lame, but may become useful with a future version of the tool:
If you're wondering what is talking about, it's just getting the list of principals (in SID form) to which the rights have been assigned in User Rights Assignment (see ). Therefore, you'll usually see the SIDs for groups like Users or Administrators rather than specific people.
answered Apr 13 '16 at 17:15
|Windows Server 2012||Yes|
|Windows Server 2012 R2||Yes|
|Windows Server 2008 R2||Yes|
|Windows Server 2008||No|
|Windows Server 2003||No|
This script is tested on these platforms by the author. It is likely to work on other platforms as well. If you try it and find that it works on another platform, please add a note to the script discussion to let others know.
Online peer support For online peer support, join The Official Scripting Guys Forum! To provide feedback or report bugs in sample scripts, please start a new discussion on the Discussions tab for this script.
Disclaimer The sample scripts are not supported under any Microsoft standard support program or service. The sample scripts are provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample scripts and documentation remains with you. In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if Microsoft has been advised of the possibility of such damages.