Powershell Remoting from a TaskScheduler task run under unprivileged user.

Hi,

I have a TaskScheduler task configured to run under unprivileged  account "shutdownscript"

The task starts batch file which in its turn starts powershell script.

The script has a line

Invoke-Command -ComputerName MYREMOTESERVER -ScriptBlock {hostname}

which works fine when the batch file is started from the CMD which started under this user account

But this very line throws the next exception when the batch file is run from task manager (right click on the task->run):

An internal error occurred.   
System.Management.Automation.CmdletInvocationException: An internal error occurred.   ---> System.Management.Automation.PSInvalidOperationException: An internal error occurred.  
   at System.Management.Automation.Remoting.Client.WSManClientSessionTransportManager.Initialize(Uri connectionUri, WSManConnectionInfo connectionInfo)
   at System.Management.Automation.Remoting.Client.WSManClientSessionTransportManager..ctor(Guid runspacePoolInstanceId, WSManConnectionInfo connectionInfo, PSRemotingCryptoHelper cryptoHelper)
   at System.Management.Automation.Remoting.ClientRemoteSessionDSHandlerImpl..ctor(ClientRemoteSession session, PSRemotingCryptoHelper cryptoHelper, RunspaceConnectionInfo connectionInfo, URIDirectionReported uriRedirectionHandler)
   at System.Management.Automation.Remoting.ClientRemoteSessionImpl..ctor(RemoteRunspacePoolInternal rsPool, URIDirectionReported uriRedirectionHandler)
   at System.Management.Automation.Internal.ClientRunspacePoolDataStructureHandler..ctor(RemoteRunspacePoolInternal clientRunspacePool, TypeTable typeTable)
   at System.Management.Automation.Runspaces.Internal.RemoteRunspacePoolInternal..ctor(Int32 minRunspaces, Int32 maxRunspaces, TypeTable typeTable, PSHost host, PSPrimitiveDictionary applicationArguments, RunspaceConnectionInfo connectionInfo)
   at System.Management.Automation.Runspaces.RunspacePool..ctor(Int32 minRunspaces, Int32 maxRunspaces, TypeTable typeTable, PSHost host, PSPrimitiveDictionary applicationArguments, RunspaceConnectionInfo connectionInfo)
   at System.Management.Automation.Runspaces.RunspaceFactory.CreateRunspacePool(Int32 minRunspaces, Int32 maxRunspaces, RunspaceConnectionInfo connectionInfo, PSHost host, TypeTable typeTable, PSPrimitiveDictionary applicationArguments)
   at System.Management.Automation.RemoteRunspace..ctor(TypeTable typeTable, RunspaceConnectionInfo connectionInfo, PSHost host, PSPrimitiveDictionary applicationArguments)
   at System.Management.Automation.Runspaces.RunspaceFactory.CreateRunspace(RunspaceConnectionInfo connectionInfo, PSHost host, TypeTable typeTable, PSPrimitiveDictionary applicationArguments)
   at Microsoft.PowerShell.Commands.PSExecutionCmdlet.CreateHelpersForSpecifiedComputerNames()
   at Microsoft.PowerShell.Commands.PSExecutionCmdlet.BeginProcessing()
   at Microsoft.PowerShell.Commands.InvokeCommandCommand.BeginProcessing()
   at System.Management.Automation.Cmdlet.DoBeginProcessing()
   at System.Management.Automation.CommandProcessorBase.DoBegin()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
   at System.Management.Automation.PipelineNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
   at System.Management.Automation.ParseTreeNode.Execute(Array input, Pipe outputPipe, ExecutionContext context)
   at System.Management.Automation.AssignmentStatementNode.Execute(Array input, Pipe outputPipe, ExecutionContext context)
   at System.Management.Automation.StatementListNode.ExecuteStatement(ParseTreeNode statement, Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)

And the same exception ALSO appears if i use gibberish instead of hostname (unknown hostnames, non-existing IPs)

So it is thrown before the connection is even established.

I also tried first establishing a remote PS Session with New-PSSession cmdlet, but this gives exactly same behaviour.

the user in question has

"log on as a batch job" right

"log on as a service" right

and is also added to the remote powershell users list for the powershell security descriptor

on the remote server by using

Set-PSSessionConfiguration microsoft.powershell -ShowSecurityDescriptorUI

command.

Once again: Everything is fine when running from command prompt, problem is while running from task scheduler.

One more thing. If i reconfigure the task to run under domain admin account, then it also works fine.

So the problem is related to the set of privileges assigned to a process started by task manager. Or it might be just a bug...

Does anyone have a clue how to solve the problem? (and to keep the task running under non-admin account)

Thanks!