On 1 of my agent managed systems i get a lot of errors in the Operations Manager eventlog and they indicate that there's something wrong with the powershell.
Het PowerShell-script is mislukt met onderstaande uitzondering
System.Management.Automation.CommandNotFoundException: The term 'out-default' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and
try again.
at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
at System.Management.Automation.Runspaces.Pipeline.Invoke()
at Microsoft.EnterpriseManagement.Common.PowerShell.RunspaceController.RunScript[T](String scriptName, String scriptBody, Dictionary`2 parameters, Object[] constructorArgs, IScriptDebug iScriptDebug, Boolean bSerializeOutput)
Searching for this error i found that it could be the setting of the variable $env:psmodulepath.
When reading the value of it directly on the system it all seems ok:
PS C:\Users\svc-scom-msaa> $env:psmodulepath
C:\Users\svc-scom-msaa\Documents\WindowsPowerShell\Modules;C:\Windows\system32\WindowsPowerShell\v1.0\Modules\;C:\Program Files\Citrix\PowerShell Modules\;C:\Pro
gram Files\Microsoft Monitoring Agent\Agent\PowerShell\
So being smart (i thought) i created a management pack that just runs a powershell discovery with this script:
$api = new-object -comObject 'MOM.ScriptAPI'
$api.LogScriptEvent('PSModulepath:',20,4,$env:psmodulepath)
$api.LogScriptEvent('PSVersion:',20,4,$PSVersionTable.PSVersion)
and expected to see in the eventlog which version and path is being used. But ofcourse this script generates the same error as above.
Anyone have an idea how to troubleshoot this further?
Versions:
SCOM 2012R2 ur8
Agent manage system Windows 2008R2stdSP1
