Powershell-Script in SCOM-Server does not recogniz Connect-MicrosoftTeams cmdlet

Question

Hi there

Since 6 months we use a power-shell script in SCOM to check and to modify some telephone numbers in Teams.
Of course, we use Connect-MicrosoftTeams cmdlet.
It worked fine.
But since today, we have this error:

The term 'Connect-MicrosoftTeams' 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.

Reboot server(of course ;))
If I us this cmdlet with my personal account it works.
If I login with the service-account running the runbook, the cmdlet works.
'Reinstall' of the module
Retyping it in the powershell-command in SCOM, if there is any issue after copy/paste (for example, we had lost many special characters during copy/past-error)

Since it still doesn't work, i'm asking for your advice.

Best Regards
Freddy

Answer 1

Hi,

SCOM =System Center Operations Manager
SCO = System Center Orchestrator

Based on my understanding, our question is related to the SCO.

The first consideration is to check the current PowerShell version in Orchestrator. By default, the Run .Net Script activity runs scripts with PowerShell 2.0, which lacks many features of newer versions.

https://social.technet.microsoft.com/wiki/contents/articles/30721.powershell-system-center-orchestrator-best-practice-template.aspx

Answer 2

Hi @Freddy Neuhaus ,

I guess your post is related to Operations Manager (SCOM) not to Orchestratorl. So the wuestion will be better in: https://learn.microsoft.com/en-us/answers/topics/msc-operations-manager-general.html

Nevertheless I guses this will help you: scom-action-account-cannot-run-powershell-cmdlet-within-scom-but-can-outside-of-scom

Regards,
Stefan

Answer 3

Hi there

My bad, it System Center 2019 Orchestrator :-)

I'm going to try invoke command to localhost, as suggested by XinGuo-MSFT

BR,
Freddy

Answer 4

Thanks @XinGuo-MSFT
Merged our script with the template, working fine.

By change I found:
https://social.technet.microsoft.com/Forums/lync/en-US/bda22a17-c274-4799-9624-97588fdf4357/orchestrator-2016-powershell-not-importing-modules?forum=scogeneral

"...make "Run .Net Script" Activity to exceute the available version of PowerShell on the Orchestrator Runbook Server:..."

Best Regards
Freddy