mirror of https://github.com/raandree/NTFSSecurity
Browse Source
Get-NTFSEffectiveAccess -ServerName with a computer that can't be resolved or reached returned no access, while it warned that it had calculated the result on this computer. In that case, AuthzInitializeRemoteResourceManager fails with RPC_S_SERVER_UNAVAILABLE (1722); the code fell back to the local authorization manager only for EPT_S_NOT_REGISTERED (1753), and GetEffectiveAccess swallowed the exception. It now falls back for 1722 as well, as the cmdlet page describes. The live tests in a lab found it; the new test in Access.Tests.ps1 reproduces it on any computer. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: AI Assistant <ai@example.com>pull/114/head
5 changed files with 26 additions and 3 deletions
Loading…
Reference in new issue