COMMAND EVERYTHING.

Test-NfsMappedIdentity

Verifies that a mapped identity is correctly configured.

PowerShell · Risk: Low · Documentation Verified

Last verified: 2026-10-26

Microsoft NFS reference: Verifies that a mapped identity is correctly configured. The syntax and selected example below are adapted from the pinned Windows Server 2025 reference. Module availability, target configuration and delegated permissions determine whether it can run in your environment. Documentation and parameter text: Microsoft, CC BY 4.0; formatting adapted by Cmdlet World. No execution testing is claimed.

Test-NfsMappedIdentity [-MappingStore <MappingStoreType>] [-UserIdentifier <Int32>] [-GroupIdentifier <Int32>]
 [-AccountName <String>] [-AccountType <AccountType>] [-SupplementaryGroups <String>] [<CommonParameters>]

Copied 0 times

Required permissions

Use an account with the target resource permissions documented for Test-NfsMappedIdentity. Modifying administrative cmdlets may require elevation or delegated administration. This catalog does not assert that ordinary users can execute the command.

Supported environments

Windows / NFS · Windows Server 2025 documentation; feature/module prerequisites apply

Parameters

-AccountName: Specifies the SAMAccountName of the Windows user account or group account of a mapped identity.
-AccountType: Specifies the Windows account type of a mapped identity. Valid values are: User and Group.
-GroupIdentifier: Specifies the group identifier of a mapped identity.
-LdapNamingContext: Specifies the Lightweight Directory Access Protocol (LDAP) naming context of an NFS identity mapping store. You can use this parameter to search for mapped identities in a specified naming context.
-MapFilesPath: Specifies the path of the passwd and group map files from which the Test-NfsMappedIdentity cmdlet obtains a mapped identity.
-MappingStore (required): Specifies the type of identity mapping store from which the Test-NfsMappedIdentity cmdlet gets a mapped identity. When this parameter is not specified, the Test-NfsMappedIdentity cmdlet obtains the store configuration settings from the NFS server configuration. Valid values are: AD, LDAP, and MapFiles.
-Server: Specifies the LDAP server name of the store that NFS server uses. This can be a domain name, Active Directory Lightweight Directory Services (AD LDS) server name, or LDAP server name. When this parameter is not specified, the Test-NfsMappedIdentity cmdlet tries to connect to either the LDAP store on the local computer at port 389 when *MappingStore* is LDAP, or the Active Directory domain of the computer when *MappingStore* is Active Directory.
-SupplementaryGroups: Specifies a comma-separated list of group names to verify the group membership of an account.
-UserIdentifier: Specifies the user identifier of a UNIX user account from which the Test-NfsMappedIdentity cmdlet obtains a mapped identity.

Prerequisites

Windows with the NFS module and the Windows feature or management tools that provide it. Confirm target connectivity and version compatibility using the linked Microsoft reference.

Security considerations

This is a read-oriented cmdlet; protect any sensitive results and check the documented effects of your selected parameters.

Examples

Example 1: Verify a mapped identity that is stored in a AD LDS instance

Test-NfsMappedIdentity -MappingStore "LDAP" -AccountName "JCool" -AccountType "User" -Verbose

This command verifies a mapped identity that is stored in a AD LDS instance on a server where this command is run.. Source: Microsoft, CC BY 4.0; transcript prompt/output removed. This example was not executed.

Sources

https://github.com/MicrosoftDocs/windows-powershell-docs/blob/b7645dd8c687139b28e845119da30ec670526507/docset/winserver2025-ps/NFS/Test-NfsMappedIdentity.md

https://learn.microsoft.com/powershell/module/nfs/test-nfsmappedidentity?view=windowsserver2025-ps

Personal collections

Explain or customize this command with AI

Related commands