Quantcast
Channel: Windows PowerShell Forum
Viewing all articles
Browse latest Browse all 2314

pssession, allowclobber

$
0
0

moin,

kann man diesen Hinweis ignorieren. Es wird anscheinend trotzdem ausgeführt. Künftig soll das Script auf einem anderen eigenen JOB Server laufen.

# verbindung zu Exchange herstellen
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://company/PowerShell/ -Authentication Kerberos

Import-PSSession $Session

Import-PSSession : No command proxies have been created, because all of the requested remote commands would shadow existing local commands.  Use the AllowClobber parameter if you want to shadow

existing local commands.

At C:\jobs\SetOWA.ps1:7 char:1

+ Import-PSSession $Session

+ ~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : InvalidResult: (:) [Import-PSSession], ArgumentException

    + FullyQualifiedErrorId : ErrorNoCommandsImportedBecauseOfSkipping,Microsoft.PowerShell.Commands.ImportPSSessionCommand


WARNING: The command completed successfully but no settings of 'company/Win ...


PS C:\jobs> $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://server/PowerShell/ -Authentication Kerberos -Allowclobber


New-PSSession : A parameter cannot be found that matches parameter name 'Allowclobber'.

At line:1 char:130

+ ... ation Kerberos -Allowclobber

+                    ~~~~~~~~~~~~~

    + CategoryInfo          : InvalidArgument: (:) [New-PSSession], ParameterBindingException

    + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.NewPSSessionCommand



Chris


Viewing all articles
Browse latest Browse all 2314

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>