Forum Discussion

JRE77's avatar
JRE77
Copper Contributor
Apr 19, 2021

Statement separator within scriptblock

Running Exchange 2013 CU23. I created a session to Exchange 2013 and saved it as a variable. After running the following command...:   Invoke-Command -Session $SessionVariable -ScriptBlock ...
2013
Exchange Server
MichaelHogendoorn_CP's avatar
MichaelHogendoorn_CP
Copper Contributor
Apr 21, 2021
We have the same behavior JRE77. Did you find a solution yet?
  • JRE77's avatar
    JRE77
    Copper Contributor
    Apr 22, 2021

    MichaelHogendoorn_CP 

    Take a look at "Known Issues" section in https://techcommunity.microsoft.com/t5/exchange-team-blog/released-april-2021-exchange-server-security-updates/ba-p/2254617.

     

    "After application of the Exchange Server April security update CMDlets executed against the Exchange Management Console using an invoked runspace might fail with the following error message:
    The syntax is not supported by this runspace. This can occur if the runspace is in no-language mode.
    This behavior is expected; please change any code using .AddScript() to use .AddCommand() for continued compatibility."

     

    I'm just an amateur Powershell scripter, so I have no idea how to use .AddScript() and .AddCommand()

Resources