Tree: bbac9ac289

master

4.2.6

4.2.4

4.2.3

5.0.0-rc9

5.0.0-rc8

5.0.0-rc7

5.0.0-rc6

5.0.0-rc5

5.0.0-rc4

5.0.0-rc3

5.0.0-rc2

5.0.0-rc1

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'bbac9ac289'

${ noResults }

Commit Graph

4 Commits (bbac9ac289ad35739c1a4dccce33fa9ca2339a37)

Author	SHA1	Message	Date
Raimund Andree	53e5bc06cf	fix: fall back to this computer when -ServerName is unreachable 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>	4 weeks ago
Raimund Andée	dd883f889b	new upload	10 years ago
Raimund Andée	8c176ef431	cleanup before full new upload	10 years ago
Raimund Andée	d42b871972	Initial upload	10 years ago