Saturday, 15 February 2014

PowerShell Access Denied only for Local user who is also Admin but not for domain user who is local admin -


We are trying to set up a machine for PSRemoting using the following command

 < code> Set-PSSessionconfiguration -nam Microsoft.PowerShell -showSecurityDescriptorUI  

it only works when we open powershell in a domain context of the user who is a local administrator for some reason.

  psc: \ windows \ system32 & gt; Set-PSSession configuration -name Microsoft.PowerShell -showSecurityDescriptorUI Confirm Are you sure you want to perform this action? Execution of Operation "Set-PSSessionConfiguration" on the target "Name: Microsoft.PowerShell" [Y] Yes [A] Yes for all [N] No [L] Not all [S] Suspended [?] Help (default " Y "is): An entry is prohibited. On line 15, four: 26 + if (($ pluginName) -or & lt; & lt; & lt; & lt; (test track "$ pluginDir")!) + CategoryInfo: InvalidOperation: (:) [], InvalidOperationExcept Ion + Fully Qualified Error Id: Inclusion in WsManError - Access: Inhibition is denied. In line: 22 characters: 35 + $ pluginFileNamePath = join-paths & lt; & Lt; & Lt; & Lt; "$ PluginDir" 'FILENAME' + CategoryInfo: NotSpecified: (:) [Join-Path], InvalidOperationE xception + FullyQualifiedErrorId: System.InvalidOperationException, Microsoft.Power Shell.Commands.JoinPathCommand Test Path: logic parameter can not be enforced 'Path' because it is an empty string on line I: 23 four: 19 + if ((the test path << $ lp; & lt; & lt; "$ pluginFileNamePath")!) + CategoryInfo: InvalidData: (:) [Test-path], ParameterBindingVa lidationException + FullyQualifiedErrorId: ParameterArgumentValidationErrorEmptyStringNotAl permission, Microsoft. PowerShell Commands Testpath contact a parameter argument 'Litrlpath' can not be enforced because it is an emp ty string I in line: 29 characters: 43 + $ Plginfailnam = get-item Litrpath & lt; & Lt; & Lt; & Lt; "$ PluginFileNamePath" + Series Info: Amanideta: (:) [gate-item], Paramitrbankingaiting Akspasn + Fulkwaiclaijd Arraidi: Paramatrarjentvalideshnarraptistontanl Elite, Microsoft. PowerShell Commands: GateTime Commands Set-PSS Configuration: Session Configuration "Microsoft Power Shell" is not a Ta PowerShell based shell. In line: 89 four: 27 + set-PSSession configuration & lt; & Lt; & Lt; & Lt; $ Args [0] $ args [1] $ args [2] $ args [3] $ args [4] $ args [5] $ args [6] $ args [7] $ args [8] + CategoryInfo: NotSpecified: (:) [Right-Error], WriteErrorExcep tion + FullyQualifiedErrorId: Microsoft.PowerShell.Commands.WriteErrorExceptio N, Set-PSSessionConfiguration Psc: \ Windows \ system32>  

It seems to me that there is something that is blocking access to wsman: \ localhost \ plugin , but it can not figure out how to fix it can go. It is only in our test bed, but in our development environment we have no such problem.

Is there any clue about what additional user access to this order is not a local administrator user?

Here is an article that explains how to solve this problem ... basically it To correct you set TrueAccountTokenFilterPolicy to the right in the registries.


No comments:

Post a Comment