Table of contents
TLS
TOC
Collapse the table of content
Expand the table of content

Test-NfsMappingStore

Brian Lich|Last Updated: 3/8/2017

SYNOPSIS

Verifies that an identity mapping store is configured correctly.

SYNTAX

Test-NfsMappingStore [-CimSession <CimSession[]>] [-ThrottleLimit <Int32>] [-AsJob] [<CommonParameters>]

DESCRIPTION

The Test-NfsMappingStore cmdlet verifies that you correctly set up and configured an identity mapping store. You can use Get-NfsMappingStore to get the mapping configuration of an NFS server.

For an Active Directory Lightweight Directory Services (AD LDS) store or any other Lightweight Directory Access Protocol (LDAP) mapping store, the Test-NfsMappingStore cmdlet verifies that a Network File System (NFS) server can reach a configured AD LDS server and that the identity mapping schema is applied.

For an Active Directory mapping store, the Test-NfsMappingStore cmdlet verifies that an NFS server can reach the relevant domain controller, and that the domain functional level is Windows Server 2003 R2 or later

EXAMPLES

Example 1: Test the configuration of an identity mapping store

PS C:\> Test-NfsMappingStore

This command tests the configuration of an identity mapping store on a local NFS server.

PARAMETERS

-AsJob

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
Parameter Sets: (All)
Aliases: 

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False

-CimSession

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[]
Parameter Sets: (All)
Aliases: Session

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False

-ThrottleLimit

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
Parameter Sets: (All)
Aliases: 

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False

CommonParameters

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.

INPUTS

OUTPUTS

None

NOTES

Get-NfsMappedIdentity

Get-NfsMappingStore

Install-NfsMappingStore

Set-NfsMappingStore

© 2017 Microsoft