Powershell version required for VADA?

PowerShell
,
1

I’ve been trying to run a VADA discovery against a Windows 2008 server that hasn’t had its Windows Management Framework updated, ever, so I suspect the problem I’m having is due to an older version of PowerShell running on that OS. Before I force the platform owner to update, is there a documented minimum version required so that I can shut down any resistance?

Here’s the error output from the VADA discovery (note, I get a 404 when attempting to run to the VADA discovery errors help @ https://support.squaredup.com/v3/troubleshooting/vadadiscoveryerrors)

3/20/2017, 1:41:22 PM SERVERNAMEWASHERE – SCOM_TASK_ERROR:
The callback method DeliverDataToModule failed with exception “Could not load type ‘System.Management.Automation.Runspaces.InitialSessionStateEntryCollection`1’ from assembly ‘System.Management.Automation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’.” in the module Microsoft.EnterpriseManagement.Modules.PowerShell.PowerShellProbeActionModule.

Workflow: Community.DataOnDemand.GetNetstatCsv

Instance: INSTANCEREMOVED

Instance ID: {386F7C4B-0760-24C6-5C38-B3692984EC4F}

Management Group: MG REMOVED

Full Exception Text:
System.TypeLoadException: Could not load type ‘System.Management.Automation.Runspaces.InitialSessionStateEntryCollection1’ from assembly ‘System.Management.Automation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’.</em> <em> at Microsoft.EnterpriseManagement.Modules.PowerShell.PowerShellProbeActionModule.OnNewDataItems(DataItemBase dataItem, DataItemAcknowledgementCallback acknowledgedCallback, Object acknowledgedState, DataItemProcessingCompleteCallback completionCallback, Object completionState)</em> <em> at Microsoft.EnterpriseManagement.HealthService.Internal.InputPortCallbacks.InputStreamAcknowledgedCallbackHandler1.InputPortCallbackImplementation(DataItemBase[] dataItems, Boolean isBatchLogicalSet, DataItemAcknowledgementCallback acknowledgementCallback, DataItemProcessingCompleteCallback completionCallback)
at Microsoft.EnterpriseManagement.HealthService.Internal.ModuleContainer`1.Microsoft.EnterpriseManagement.HealthService.Internal.IModuleContainer.DeliverDataToModule(UInt32 inputPortNumber, DataItemBase[] dataItems, Boolean isBatchLogicalSet, DataItemAcknowledgementCallback acknowledgementCallback, DataItemProcessingCompleteCallback completionCallback)
at Microsoft.EnterpriseManagement.HealthService.Internal.ManagedHostHelper.Microsoft.EnterpriseManagement.HealthService.Internal.IManagedHostHelper.DeliverBatchedDataToModule(UInt32 inputPortNumber, Object moduleInputReference, DataItemBase[] dataItems, UInt32 dataIt
________________________________________________________________________________

2

The pack is hosted on Github here:

https://github.com/squaredup/Community.DataOnDemand.MP

but does not list the minimum requirements for PS unfortunately. I think it’s likely a question for support as I’m running a 2012R2+ environment, so I can’t test.

3

The script (as per Jelly’s answer – you can get it on github, direct link here) contents specify version 2.0 of PowerShell using the #Requires statement:

#Requires -Version 2.0
Set-StrictMode -Version 2.0

The latest version you can go to will be PS 3.0 on 2008 (v4.0 and later require 2008 R2) and you’ll need to update .Net as well (requires .Net 4.0). If you can swing 3.0 there is little reason to only put 2.0 in place, other than the server hosting an MS application that doesn’t support 3.0 (check the WMF release notes).

Hope that helps!

1 Like