Forum Discussion
Microsoft Teams PowerShell Module V2.3 - Set-CsUser broken!
We had the same issue today and this is how we got round it:
- Run a PS session as Admin
- Uninstall-Module -Name MicrosoftTeams
- Install-Module -Name MicrosoftTeams -RequiredVersion 2.0.0
- Import-Module -Name MicrosfTeams
This then allowed us to progress and use the Set-CsUser command.
We had the same issue today and this is how we got round it:
- Run a PS session as Admin
- Uninstall-Module -Name MicrosoftTeams
- Install-Module -Name MicrosoftTeams -RequiredVersion 2.0.0
- Import-Module -Name MicrosfTeams
This then allowed us to progress and use the Set-CsUser command.
- Thanks Paul_Wood I can confirm that downgrading to v2.0.0 of the MicrosoftTeams PowerShell module is a workaround and allows running of Set-CsUser -Identity xxx -OnPremLineURI which is needed for customers using Direct Routing.
The Skype Online Connector stopping working today was a surprise to us as our message center post says 15 May 2021 so it should still be working in my opinion.
I have logged with MS Support and urge others to do the same.- MS Support just yesterday got back to us and was unable to understand that the PowerShell Module was broken. They wanted to remote type the command and perform a step recording. At that point we closed the request as this was going nowhere.
Someone botched this transition / upgrade massively. - Message Center clearly states 15 May 2021 for us too!
Thanks a lot Paul_Wood!
- did that and on uninstall I get this error
Uninstall-Module -Name MicrosoftTeams
PackageManagement\Uninstall-Package : Access to the cloud file is denied
The file it selves are: At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\2.2.5\PSModule.psm1:12733 char:21 - Thanks for the solution.
I confirm the command St-CsUser works again with version 2.0.0 of the MicrosoftTeams module. Hi Paul_Wood,
When we tried to go back to 2.0.0 - we are getting the following error message -
Exception calling "GetSteppablePipeline" with "1" argument(s): "Exception calling "GetRemoteNewCsOnlineSession" with "1" argument(s): "Run either Connect-MicrosoftTeams
or new-csonlinesession before running cmdlets.""
At C:\Program Files\WindowsPowerShell\Modules\MicrosoftTeams\2.0.0\net472\SfBORemotePowershellModule.psm1:9474 char:13
+ $steppablePipeline = $scriptCmd.GetSteppablePipeline($myI ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : CmdletInvocationException
Can you provide any insights into what might be causing this? We are trying to do a 'connect-microsoftteams' with AADAccessToken and AccountID params.
Thanks,
--Venkata
- I'm sure you already figured out that you will need to run Connect-MicrosoftTeams after importing the 2.0.0 module
Yes, we were trying to use the Connect-MicrosoftTeams -AadAccessToken $token -AccountId <upn>. The teams commands are working fine. The SFBO commands are failing.
