Hi,
The -Credential parameter of the "Connect-NcController" cmdlet has a mandatory value of False and can be used with cached credentials.
See "Get-Help Add-NcCredential -Full"
NAME
Add-NcCredential
SYNOPSIS
Save login credentials for a clustered Data ONTAP controller.
SYNTAX
Add-NcCredential [-Credential <PSCredential>] [-SystemScope] [<CommonParameters>]
Add-NcCredential -Controller <NcController[]> [-Credential <PSCredential>] [-SystemScope] [<CommonParameters>]
Add-NcCredential [-Name] <String> [-Credential <PSCredential>] [-SystemScope] [<CommonParameters>]
DESCRIPTION
Save login credentials for a clustered Data ONTAP controller. The cached credentials are available to
Connect-NcController, Invoke-NaSsh, and other Toolkit cmdlets.
The saved credentials are encrypted for safe storage. By default, a set of credentials is saved using the current
user context, so that only the same Windows user can retrieve them. If an application of the Toolkit must utilize
the cached credentials while running under some other context, specify the -SystemScope parameter. This saves the
credentials such that any process or user on the local system can access them, so this option should only be used
on a system with limited user access.
Any number of Toolkit users may store credentials for a given storage controller in the cache, but a user will
only be able to see and utilize credentials saved using his account identity or the system identity.
/Matt
If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.