Question Accès refusé avec Invoke-command

Je n'ai encore jamais utilisé l'option EnableNetworkAccess, d'ailleurs je ne connaissais pas. C'est nouveau

-EnableNetworkAccess


Adds an interactive security token to loopback sessions. The interactive token lets you run commands in the loopback session that get data from other computers. For example, you can run a command in the session that copies XML files from a remote computer to the local computer.

A \"loopback session\" is a PSSession that originates and terminates on the same computer. To create a loopback session, omit the ComputerName parameter or set its value to \".\", \"localhost\", or the name of the local computer.

By default, loopback sessions are created with a network token, which might not provide sufficient permission to authenticate to remote computers.

The EnableNetworkAccess parameter is effective only in loopback sessions. If you use the EnableNetworkAccess parameter when creating a session on a remote computer, the command succeeds, but the parameter is ignored.

You can also allow remote access in a loopback session by using the CredSSP value of the Authentication parameter, which delegates the session credentials to other computers.

To protect the computer from malicious access, disconnected loopback sessions that have interactive tokens (those created with the EnableNetworkAccess parameter) can be reconnected only from the computer on which the session was created. Disconnected sessions that use CredSSP authentication can be reconnected from other computers. For more information, see Disconnect-PSSession.

Ce paramètre est introduit dans Windows PowerShell 3.0.

Bon, de ce que je comprends, ce commutateur permet uniquement d'utiliser les chemins UNC en local (loopback).