Thanks @ :D
Thank you Petr. 😃
Awesome Petr! Thank you! Have a great day!:D
Thank you Petrovic!
This update doesn't appear to be being offered to our WSA clients which is odd as it was released 3 days ago...
The majority of agent versions are 9.0.18.34 (75%+) with a small number on 9.0.18.44 (<10%). Zero are on the new 9.0.19.36 version. I don't appear to have any control over when agents upgrade through the console.
Can you offer any insight or guidance re: why this might be the case and how we can accelerate this version upgrade?
Thanks,
Richard.
The response I received from Webroot Business Support: As planned, Webroot began releasing the latest Webroot SecureAnywhere build on January 9th 2018. As is customary, for this type of agent release, we are throttling and distributing this version in predefined distribution pools. The final push is due to complete during the 1st week of February.
Thanks Robert.
This isn't ideal... not having this new version (and the registry key it creates) effectively blocks the Meltdown/Spectre Windows Updates from being detected as applicable to a particular system.
@ wrote:
Thanks Robert.
This isn't ideal... not having this new version (and the registry key it creates) effectively blocks the Meltdown/Spectre Windows Updates from being detected as applicable to a particular system.
If you want the new version right away just download and install over top and you will have it:
http://anywhere.webrootcloudav.com/zerol/wsainstall.exe
Can we manually create the registry key to enable to Windows Update patch on versions prior to this one, or do we HAVE to have the 9.0.19.36 for the key to be auto created?
Kaseya have released a procedure to create the key, but want to ensure Webroot will allow for it.
@ to set the key see here for more info as Webroot made a download to run and it will set the key for you:
Webroot Knowledge Base article
@,
You can definitely set the registry key manaully. The existing release (9.0.18.44) works fine with the registry key set and Microsoft patch applied. Webroot has a self executing file to help you do it - you can find it here:
https://answers.webroot.com/Webroot/ukp.aspx?pid=12&app=vw&vw=1&login=1&json=1&solutionid=2837
You should be able to add the registry key using Agent Commands: Agent Commands -> Advanced -> Run a registry command.
If you're using Connectwise Automate (formerly Labtech) like me, this is really useful:
https://github.com/gavsto/ConnectWise-Automate-Meltdown-and-Spectre-Detection-Scripts
Great thanks guys. Yeah I received the email last night from Webroot listing the new version will be deployed to our fleet, and also had a link to that KB article.
Good to know the current version supports the patch, so will work through deploying where applicable.
Cheers
Marty
Great and thanks for replying! 😉
Has anyone seen this new version, released 2 weeks ago, yet?
I haven't, and I have 250 agents installed in 14 sites. Clients are asking about Meltdown/Spectre and I can't get any replies on the topic from WR.
If there's a reason it hasn't been released yet, could you explain? Maybe give a date?
Thanks.
@ wrote:
Has anyone seen this new version, released 2 weeks ago, yet?
I haven't, and I have 250 agents installed in 14 sites. Clients are asking about Meltdown/Spectre and I can't get any replies on the topic from WR.
If there's a reason it hasn't been released yet, could you explain? Maybe give a date?
Thanks.
The best thing you can do is
Submit a Business Support Ticket and they will give you the correct information!
Or:
CALL US
1-866-254-8400
Thanks,
Daniel
Thanks. Submitted a case, but haven't heard back yet. To be fair, not much time has passed.
Anyway, the link provided previously in this thread has provided me with the latest version.
Not completely sure how the licensing would work - I presume if it's installed on a computer with a previous version and valid license, it will be fine.
Wow. That's unacceptable for a security company. I have 97 servers running Webroot 9.0.18.34. They won't update to 9.0.19.36, so I must be in a later "pool". There is no way to manually update through the console ( A HUGE FLAW IN MY OPINION!). So the answer is "there's a big security flaw, but give us a month or so and we'll get you an update"?!?
Last year Webroot messed up an update and took down thousands of computers worldwide.
Webroot needs to ramp up their investment in support of enterprise customers. I'm beginning to seriously question my choice of this product to protect our servers . . .
@ wrote:
Wow. That's unacceptable for a security company. I have 97 servers running Webroot 9.0.18.34. They won't update to 9.0.19.36, so I must be in a later "pool". There is no way to manually update through the console ( A HUGE FLAW IN MY OPINION!). So the answer is "there's a big security flaw, but give us a month or so and we'll get you an update"?!?
Last year Webroot messed up an update and took down thousands of computers worldwide.
Webroot needs to ramp up their investment in support of enterprise customers. I'm beginning to seriously question my choice of this product to protect our servers . . .
Maybe
@ or
@ can comment on your issue. But please
Submit a Business Support Ticket and they will give you the correct information!
Or:
CALL US
1-866-254-8400
Thanks,
Daniel
@ &
@ I second
@'s advise on opening a support case. I'm pretty sure that this is for the PC Release for general consumers. The business side is handled a bit differently, and you should be following this thread:
https://community.webroot.com/t5/WSA-Release-Candidate-PC-Group/Now-available-WSA-9-0-19-36-and-WTS-1-6-release-candidates/gpm-p/311495
On the business side, the candidate version number has already changed from X.36 to X.43
Additionally, there are a few posts in the forums outlining how to manually set the correct registry key settings so you can proceed with installing the the windows patch. Webroot has a self executing file that you could probably script, you can use agent commands or if you have a management solution for your clients there may be other ways to script out the registry settings and apply the patches. There are also Microsoft articles outlining the proper registry key settings for each type of system (workstations, servers & Hyper-V).
The point being, you shouldn't be waiting for Webroot's next release to increase your security posture. 9.0.18.34 is compatible with the Microsoft patches as long as you set the required registry keys first.
Lastly, there is a feature request for an update client agent command here:
https://community.webroot.com/t5/Feature-Requests/Add-Update-Upgrade-functionality-to-Agent-Command-Menu/idc-p/311448#M2623
wrote:
@ & @ I second @'s advise on opening a support case. I'm pretty sure that this is for the PC Release for general consumers. The business side is handled a bit differently, and you should be following this thread:
https://community.webroot.com/t5/WSA-Release-Candidate-PC-Group/Now-available-WSA-9-0-19-36-and-WTS-1-6-release-candidates/gpm-p/311495
On the business side, the candidate version number has already changed from X.36 to X.43
This seems to be a 404.
