Forum Discussion
Skype for Business Server: Announcing the general availability of Modern Admin Control Panel
- May 19, 2021
Hi Eric Marsi, Remote PowerShell issue has been fixed and released, and it has been verified by customers, who raised the support issue.
Can you please restart the machine or do IIS reset and try again. If the issue still persists, please report the same to Microsoft support and provide more details so our team can investigate it further. Thanks.
Eric Marsi Thanks for reporting the issue. We tried to reproduce the issue at our end but unable to do so. Can you please report this issue through Microsoft support and provide more details so our team can do investigate it further. Thanks.
Unfortunately this is my personal lab environment. I have validated that this in fact an issue on a new installation as well so not sure how it is unreproducible. Is there any options available for me?
Also, I did find another bug in Skype for Business 2019 CU5 (Left), When creating a new Standard Edition FE Pool, no SQL Store is generated and you cannot continue. On CU4 (Right), this is not an issue and you can see its automatically populated and the wizard is able to continue.
- Ravindra_Singh_BishtMay 18, 2021Microsoft
Hi Eric Marsi, Remote PowerShell issue has been fixed and released. Please download the latest installer from here.
- Eric MarsiMay 18, 2021MVP
Ravindra_Singh_Bisht Thanks for tagging me. I have just installed this to find that it unfortunately did not resolve any issues with remote PS. The below image shows that it fails to start the PS Session, but if I remote into a older CU4 FE, it works as expected. Thoughts?
Also The other issue two posts above regarding topology builder is still there and not resolved.
- Ravindra_Singh_BishtMay 19, 2021Microsoft
Hi Eric Marsi, Remote PowerShell issue has been fixed and released, and it has been verified by customers, who raised the support issue.
Can you please restart the machine or do IIS reset and try again. If the issue still persists, please report the same to Microsoft support and provide more details so our team can investigate it further. Thanks.