Release Management vNext Powershell Could not load file or assembly System.Management.Automation Version=3.0.0.0

Question

Hi,
I'm running TFS2013.4 with a number of build servers and all working fine. 
I'm also running Release Management with update 4 (12.0.31101.0) and am running into trouble when trying to run my first dummy release.
I have setup my servers, stages, releases paths, components and release template (all vNext) with out issue.
When I run my Release Template (Deploy Using PS/DSC) I'm getting the following error :-
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.AggregateException: One or more errors occurred. ---> System.IO.FileNotFoundException:
Could not load file or assembly 'System.Management.Automation, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies.
The system cannot find the file specified.
   at Microsoft.VisualStudio.Services.DevTestLabs.Deployment.Deployment.PowershellExecutor.DisposeCurrentSession()
   at Microsoft.VisualStudio.Services.DevTestLabs.Deployment.Deployment.RemoteDeploymentHelper.Dispose()
   at Microsoft.VisualStudio.Services.DevTestLabs.Deployment.Deployment.DeploymentClient.<RunAsync>d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Services.DevTestLabs.Deployment.Deployment.DeploymentClient.<RunPowerShellAsync>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.TeamFoundation.Release.EnvironmentProvider.OnPrem.Implementation.OnPremDeploymentProvider.<CopyBuildsLocally>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.TeamFoundation.Release.EnvironmentProvider.OnPrem.Implementation.OnPremDeploymentProvider.<RunScript>d__0.MoveNext()
   --- End of inner exception stack trace ---
   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
   at Microsoft.TeamFoundation.Release.MonitorServices.Dsc.OnPrem.OnPremDeploymentActions.InvokePlatform(String activityId, MachineSpecification machineSpecification, StorageSpecification storageSpecification, String scriptPath, String configurationPath,
Dictionary`2 configurationVariables)
   at Microsoft.TeamFoundation.Release.MonitorServices.Dsc.OnPrem.OnPremDeploymentActions.RunScript(DscComponent dscComponentParameters, String serverName, String userName, String password, String componentName, String scriptPath, String configurationPath,
String useCredSecuritySupportProvider, String useHttps, String skipCACheck)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at Microsoft.TeamFoundation.Release.DeploymentAgent.Services.Deployer.Dsc.DscComponentInstaller.InvokeMethodByReflection(String methodArguments)
I can't work out if my target machine (2008 R2 SP1) has a problem with WMA 3.0 or if the Release Template can't find the powershell script that I'm trying to call.  I figured that the relative path to the script could be wrong and have tried numerous
iterations to no effect.  The error clearly points to a problem with WMA right?
The target machine has .Net Framework 4.0, WMA Framework 3.0 and I can run Enter-PSSession to remote to it etc...
Before I trash and rebuild my target machine I hoping someone may have some insight to my problem?
Thanks in Advance
Jason
shroomie

Answer 1

Daniel,
The PS Script is taken from an MSDN blog and is fairly standard.  I'm sure it will run fine when executed, but I've not run it as it requires environment variables ($applicationPath) that will be present in the Release Management session calling it. 
Here's the script :-
configuration InstallModules
    param
        # Target nodes to apply the configuration
        [string[]]$NodeName = 'localhost',
        # Source Path for Modules
        [String]$SourcePath = "$applicationPath\Deploy\Modules",
        # Destination path for Modules
        [String]$DestinationPath = "$env:ProgramFiles\WindowsPowershell\Modules"
    Node $NodeName
        # Copy the Modules
        File ModuleContent
            Ensure          = "Present"
            SourcePath      = $SourcePath
            DestinationPath = $DestinationPath
            Recurse         = $true
            Type            = "Directory"
InstallModules
Thanks
Jason
shroomie