Resolve-Nfs
Mapped
Identity
Syntax
Resolve-NfsMappedIdentity
[[-AccountType] <WindowsAccountType>]
[-Id] <UInt32>
[-CimSession <CimSession[]>]
[-ThrottleLimit <Int32>]
[-AsJob]
[<CommonParameters>]
Resolve-NfsMappedIdentity
[-AccountName] <String>
[[-AccountType] <WindowsAccountType>]
[-CimSession <CimSession[]>]
[-ThrottleLimit <Int32>]
[-AsJob]
[<CommonParameters>]
Description
The Resolve-NfsMappedIdentity cmdlet queries a Network File System (NFS) server to resolve the mapping of a Windows user account or group account to a UNIX identifier.
When Resolve-NfsMappedIdentity queries the local NFS server, the local NFS server searches its cache. If the NFS server finds the mapping, the information is returned. If the NFS server mapping does not find the mapping in the server cache, the NFS server queries the configured mapping store. If the NFS server finds the mapping in the mapping store, the mapping is returned, locally cached, and periodically refreshed.
The main purpose of Resolve-NfsMappedIdentity is to perform mapping diagnostics. Administrators can determine whether the NFS server can successfully get the correct mappings for users and groups by using its current configuration.
For more information about NFS, see Network File System Overview . For more information about NFS account mapping, see NFS Account Mapping Guide and Identity Management for UNIX .
Examples
Example 1: Resolve a Windows user account to a UNIX UID
PS C:\> Resolve-NfsMappedIdentity -AccountName "PSPinto" -AccountType "User"
Windows Account : PSPinto
Account Type : User
Identifier : 402
This command resolves the Windows user account PSPinto to UNIX user identifier 402. The output reflects the identity mapping that the local NFS server returns.
Required Parameters
Specifies the account name of the user or group to resolve. You can use the AccountType parameter to specify whether the AccountName parameter value represents a user or a group.
Type: | String |
Position: | 0 |
Default value: | None |
Accept pipeline input: | True (ByPropertyName) |
Accept wildcard characters: | False |
Specifies the UNIX identifier to resolve to a Windows account name. You can use the AccountType parameter to specify whether the Id parameter value is a user or a group.
Type: | UInt32 |
Aliases: | uid, gid, Identifier |
Position: | 0 |
Default value: | None |
Accept pipeline input: | True (ByPropertyName) |
Accept wildcard characters: | False |
Optional Parameters
Specifies the type of Windows account name or identifier to resolve. Valid values are User and Group.
Type: | WindowsAccountType |
Aliases: | type |
Parameter Sets: | User, Group |
Position: | 1 |
Default value: | None |
Accept pipeline input: | True (ByPropertyName) |
Accept wildcard characters: | False |
Indicates that this cmdlet runs the command as a background job on a remote computer. Use this parameter to run commands that take an extensive time to finish.
When you use the AsJob parameter, the command returns an object that represents the job, and then displays the command prompt. You can continue to work in the session while the job finishes. To manage the job, use the Job cmdlets. To get the job results, use the Receive-Job cmdlet.
The AsJob parameter resembles using the Invoke-Command cmdlet to run a Start-Job command remotely. However, with AsJob , the job is created on the local computer, even though the job runs on a remote computer, and the results of the remote job are automatically returned to the local computer.
For more information about Windows PowerShell background jobs, see about_Jobs and about_Remote_Jobs .
Type: | SwitchParameter |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Runs the cmdlet in a remote session or on a remote computer. Enter a computer name or a session object, such as the output of a New-CimSession or Get-CimSession cmdlet. The default is the current session on the local computer.
Type: | CimSession[] |
Aliases: | Session |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Specifies the maximum number of concurrent operations that can be established to run the cmdlet.
If this parameter is omitted or a value of
0
is entered, then Windows PowerShell® calculates an optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the computer.
The throttle limit applies only to the current cmdlet, not to the session or to the computer.
Type: | Int32 |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Outputs
Microsoft.Management.Infrastructure.CimInstance#root/microsoft/windows/nfs/MSFT_NfsMappedIdentity