Our 7.0.2046.548 March 2025 update so close on the heels of Christmas’s 7.0.2046.545 looks to be a “whoops” fixup.
I can only find ONE named fix (albeit across two files):
Nothing noted. There are no new cmdlets in the SfB PowerShell module.
Nothing noted.
Nothing noted.
It seems a lot of Windows users encounter problems with Edge and/or Chrome not responding for 10+ seconds at a time. The mouse moves, you can engage with other apps, just not the browser. When it resumes responding, some of your previous mouse clicks (e.g. failed attempts to switch tabs) are belatedly actioned.
The search results all take you to “useful” posts that suggest you try a repair, upgrade to the latest version, and if that doesn’t work, a reinstall. Dig further and others suggest you trash your cache, history, and all the other stuff you’ve carefully curated.
The fix is to disable graphics acceleration: an option common to both browsers, presumably because they’re running the same underlying Chromium engine.
Continue reading ‘Win 11: Edge and Chrome stop responding’ »
I rebuilt my machine this week, and hasn’t that been fun!
One issue that took me an eternity to resolve was getting the touch recognition to work on both monitors. Out of the box, touching EITHER monitor resulted in the first one responding.
My search hits all took me to options that no longer exist in Windows 11.
The fix came from Stack Exchange. Thank you Pierre Courtois Delecour!
Just run this in a PowerShell window, and it will prompt you to touch each monitor in turn, associating the touch with each screen:
cmd /C multidigimon -touch
– Greig.
I will admit I missed this year’s Christmas present from Microsoft to those die-hards still running an on-premises installation of Skype for Business 2019, but here it is. This update (7.0.2046.545) is the only one we’ve seen in more than twelve months, replacing October 2023’s Security Update to 7.0.2046.530.
I can only find five named fixes:
This Security update for SfBS 2019 is build 7.0.2046.530, up from July’s 7.0.2046.524. It updated two components on my Standard Edition Front-End.
KB5032429 Description of the security update for Skype for Business Server: October 10, 2023
This security update resolves vulnerabilities in Microsoft Skype for Business Server. To learn more about these vulnerabilities, see the following security advisories:
Nothing noted. No cmdlets have been added to the SfB module in this update.
Nothing noted.
Continue reading ‘SfB 2019 Server Security Update – October 2023’ »
This security update for SfBS 2015 is build 6.0.9319.869, up from August’s 6.0.9319.853. It updated two components on my Standard Edition Front-End.
KB5032429 Description of the security update for Skype for Business Server: October 10, 2023
This security update resolves vulnerabilities in Microsoft Skype for Business Server. To learn more about these vulnerabilities, see the following security advisories:
Nothing noted. No cmdlets have been added to the SfB module in this update.
Nothing noted.
Continue reading ‘SfB 2015 Server Security Update – October 2023’ »
In June we saw an update for SfBS 2019 that added the new “Emergency Mitigation Service”, and now it’s 2015’s turn. This is build 6.0.9319.853, up from last December’s 6.0.9319.842. As expected, it’s only updating two components on my Standard Edition Front-End and delivers only one fix.
This article announces the arrival of the Emergency Mitigation Service, with some companion commandlets.
Microsoft takes security very seriously and we continue to work hard to protect your systems and data from cyber threats and to comply with evolving regulations. In line with this, we have introduced the Skype for Business Server Emergency Mitigation Service to help protect your servers from potential threats. This service provides a temporary and interim mitigation until you can install an update that fixes the vulnerability.
Hot on the heels of last month’s update to 7.0.2046.521 comes another.
Today we see build 7.0.2046.524, which updated three components on my Standard Edition Front-End.
All three components updated contain the same fix:
The above fixes support the replacement of the old “CSCP”, the Communication Server Control Panel – a name that goes back to before Lync was Lync – with the Modern Admin Control Panel (MACP).
The story is documented in the article Disable Legacy Control Panel (CSCP).
After you run the PowerShell script included in the above article, launching the old CSCP instead pops a browser and the MACP.
The script includes an uninstall option if you want to revert.
Nope.
Nothing (else) noted.
Enphase has caused an ongoing kerfuffle by changing the authorisation mechanism of their Envoy solar controllers, usually without notice, by virtue of a firmware update.
Where previously you could login to your Enphase solar setup with basic username and password authorisation, now you need to provide an authorisation token created by the Enphase website.
We fell foul of the same update and have lost some data, but here I present the updated version of the script.
If you’re still running v5, this script is the one you need. To determine your own Envoy version, login to the Enlighten website, click the hamburger then System / Devices / Gateway.
The pre-requisites for this script are the same as for v5, but with some extras:
You’ll find the script Get-EnphaseProduction-v7.py on Github.
The PRTG side of things is unchanged from the v5 version here.
Where the v5 version had your *local* credentials baked into the script, now it requires your *online* cred’s, as outlined above. Don’t forget to edit the script with these details before proceeding. You’ll find them at around line 30.
26th July 2023. This is the initial publication.
– Greig.
