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.
What’s Fixed?
I can only find five named fixes:
- “500: Unable to process request” error and hybrid configuration fails
- Can’t modify Skype account in Skype for Business Server 2019 through MACP
- Skype for Business Server 2019 admin center loads slowly
- Q&A doesn’t work in Skype for Business Server 2019
- Can’t sign in to Skype for Business Server with FIPS enabled
What’s New?
Nothing noted. There are no new cmdlets in the SfB PowerShell module.
What’s Changed?
Nothing noted.
Known Issues
Nothing noted.
Download
Note that the download link also has a “PersistentChatUpdateInstaller.exe”, which might also be relevant.
Don’t forget to run bootstrapper, as that’s when the new EMS is installed. You’ll usually find bootstrapper in C:\Program Files\Skype for Business Server 2019\Deployment\.
Installation
Here’s the “before” view of it going on to my Lab’s Standard Edition Front-End:
Reboot?
The installer didn’t prompt me to reboot, but I always like to give it one for good measure.
Revision History
31st December 2024: This is the initial release.
– G.
In need of advice here – what kind of groups are needed for account which will install the update?
I ve seen advices that needed are :
Administrators; CSAAdministrator; Domain Admins; Enterprise ;Schema Admins; RTCCComponentsUniversalServices; RTCHSUniversalServices; RTCUniversalConfigReplicator; RTCUniversalAdmins and let the last one to close the door.
My problem: the man that installed sfb2019 is no longer available, though i am sure he installed product with domain admin/schema admin account.
in between our AD entered “tiering model”, in which Skype is tier1, while Schema admin is Tier 0 … and thus we have GPO such that T0 account cannot login to T1 server… I need confirmation in order to require temp exceptoion :)
Hope what I wrote makes sense :)
I think you’re confusing the rights to install a new deployment with those to update an existing one.
Paraphrasing what the kb says, just make sure you right-click and run the installer as Admin.
\- Greig.