2  * Windows 2012 servers fail to create PowerShell workflow sessions, normal new-pssession works. Same command works on other computers. Tried Enable-PSremoting -force to reapply settings.

$psversiontable

Name                           Value
----                           -----
PSVersion                      4.0
WSManStackVersion              3.0
SerializationVersion           1.1.0.1
CLRVersion                     4.0.30319.18408
BuildVersion                   6.3.9600.16406
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0}
PSRemotingProtocolVersion      2.2

$wfsession = New-PSWorkflowSession -ComputerName XXXXXXX

New-PSSession : Access is denied
At C:\windows\system32\windowspowershell\v1.0\Modules\PSWorkflow\PSWorkflow.psm1:59 char:9
+         New-PSSession -ConfigurationName Microsoft.PowerShell.Workflow @PSBoundP ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], RemoteException
    + FullyQualifiedErrorId : PSSessionOpenFailed

$Error |select -first 1 | fl * -force


writeErrorStream      : True
PSMessageDetails      :
Exception             : System.Management.Automation.RemoteException: Access is denied
TargetObject          : System.Management.Automation.RemoteRunspace
CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], RemoteException
FullyQualifiedErrorId : PSSessionOpenFailed
ErrorDetails          :
InvocationInfo        : System.Management.Automation.InvocationInfo
ScriptStackTrace      : at New-PSWorkflowSession<Process>, C:\windows\system32\windowspowershell\v1.0\Modules\PSWorkflow\PSWorkflow.psm1: line 59
                        at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {0, 1}

User is a domain admin so has local admin access. Tried adding the user explicitly to local admin as well as remote management users group on affected server.

Have run through the https://technet.microsoft.com/en-us/library/hh847850.aspx

Firewall is turned off, tried explicit credentials.

Can't see any config problems in the wsman provider.

Tried a reboot!

Any thoughts?

Run this on both ends:

Get-PSSessionConfiguration

Look at workflow permissions.

Same on both ends and with default values.

PS C:\Windows\system32> Get-PSSessionConfiguration


Name          : microsoft.powershell
PSVersion     : 4.0
StartupScript :
RunAsUser     :
Permission    : BUILTIN\Administrators AccessAllowed, BUILTIN\Remote Management Users AccessAllowed

Name          : microsoft.powershell.workflow
PSVersion     : 4.0
StartupScript :
RunAsUser     :
Permission    : BUILTIN\Administrators AccessAllowed, BUILTIN\Remote Management Users AccessAllowed

Name          : microsoft.powershell32
PSVersion     : 4.0
StartupScript :
RunAsUser     :
Permission    : BUILTIN\Administrators AccessAllowed, BUILTIN\Remote Management Users AccessAllowed

Name          : microsoft.windows.servermanagerworkflows
PSVersion     : 3.0
StartupScript :
RunAsUser     :
Permission    : NT AUTHORITY\INTERACTIVE AccessAllowed, BUILTIN\Administrators AccessAllowed

Tried to explicitly add my domain account to the microsoft.powershell.workflow to the access list using Set-PSSessionConfiguration -Name microsoft.powershell.workflow -ShowSecurityDescriptorUI but still access denied.

The only thing I can think of is to check logs for authentication issues.

You can also try restarting both systems which has solved subtle issues like this in some cases.

Does local workflow work on both systems?

Can't see anything in the logs that is relevant. Have rebooted one of the systems, not accessible from multiple other clients.

Local workflow works on both systems.

Yeah it's quite an odd one. Wondering if its a bug or something.