You usually have to use the Carbon module or write complex WMI/CIM scripts to replicate what ntrights does in one line. Because of this, ntrights remains a staple for administrators who want a zero-dependency solution.
| Privilege Constant | Description | |-------------------|-------------| | SeInteractiveLogonRight | Log on locally | | SeNetworkLogonRight | Access this computer from the network | | SeBatchLogonRight | Log on as a batch job | | SeServiceLogonRight | Log on as a service | | SeBackupPrivilege | Back up files and directories | | SeRestorePrivilege | Restore files and directories | | SeShutdownPrivilege | Shut down the system | | SeDebugPrivilege | Debug programs (highly sensitive) | ntrights
Have you used ntrights in your environment? Do you prefer it over modern PowerShell modules? Let us know in the comments! You usually have to use the Carbon module
The utility is straightforward. You are essentially telling the system: Do you prefer it over modern PowerShell modules
The utility requires administrative privileges to run and uses a specific syntax for adding or removing rights: ntrights +r [RightName] -u "[AccountName]" Revoke a right: ntrights -r [RightName] -u "[AccountName]"
: In troubleshooting scenarios, administrators can use NTRights to reapply standard rights if security settings have been inadvertently changed.