Avast Business On-Premise Management Console Version 7.16

Avast Business On-Premise Management Console & Clients
1

Release Notes: Avast Business On-Premise Management Console (October 9, 2019)
Console version: 7.16
Agent version: 4.16
Windows Antivirus: 19.7
Mac OS X Antivirus: 13.13

Release Summary
This release contains improvements and bug fixes to our Avast Business On-Premise Management Console.

Improvements

  1. [CBC-8095] Added support for completely offline networks
  2. [CBC-9213] Updated PostgresSQL to v10.4
    On-Premise Management Console has been upgraded to the current cloud version along with many small or large improvements and bug fixes.

Bugs
3. [CBC-9186] Fixed an issue with a default policy being generated twice
4. [CBC-7107] Fixed an issue with registration of a device which has the console installed on itself
5. [CBC-6731] Fixed an issue with upgrading the on-premise console
6. [CBC-6876] Fixed an issue with upgrading the on-premise console
7. [CBC-6965] Fixed an issue with the password validation so it does not allow using the same e-mail address as for the account
8. [CBC-7052] Fixed an issue with problematic console starts after upgrading to 6.1
9. [CBC-7099] Fixed an issue with showing an error message after putting a wrong password
10. [CBC-6998] Fixed an issue with a session expiration when a browser is closed

Avast Business On-Premise Management Console Version 7.16 Release Notes

Actual installation package is going to be available for upgrade early next week.

2

How is the correct procedure for the update?

3

Dear Avast Support Team/ Friends,

I just download latest " avast business management console on premise " offline installer via avast website,
and after installed, it’s still use 6.0.14 version.

Base on manual,

I read that it will show notification if there is any new update available,
but until now i didn’t get any notification on my avast console to update to 7.16. ;D
It’s normal or i need to do something to trigger the update challange?

If not, Then How to update from 6.0.14 to 7.16? :smiley:

Thanks and Best Regards,
Erwin

4
5

It’s almost middle of week. :wink:

6

Technically, 7.16 is ready. Now it’s under the security inspection procedure which took longer than expected.

Plan was last week, early this week. Now AVAST is working with team on new ETA.

It should be very very soon.

7

Another week, no updates… >:(

8

Almost month… :hourglass:

9

Hello, I have the exact same problem :wink:

@ Avast support team
Is there any update on this new version of the console?

Thank you in advance.

Kind regards,

Mike

10

One month later, complete silence…

11

They released another version for the cloud today… but still nothing for On-Premise… c’mon Avast. >:(

12

I apologize, but we are still testing the newest on-prem console, and the final release is currently scheduled in about week or two (however, this could change). For anyone who’s interested, here’s the test OBC v7.16 (without the complete Offline Update Support at the moment)…

https://share.avg.com/steam/SMB/OBC%207.16%20without%20offline%20support/avast_business_mc_setup.exe

The final version will include the offline support, and you should be able to install this test version directly on-top of the current v6.0.14 on-premise console. Please Submit idea at https://portal.productboard.com/afb/1-avast-business-management-console-and-antivirus/tabs/1-planned

Happy testing! ;D

13

Be advised… upgraded from 6.0… I now have systems showing an error about an Agent Version needing update while others don’t show that field at all (running upgrades did not help)… And it uninstalled Web and Email Shields from ALL settings templates for Windows Servers (I know these were active before this upgrade). Agent Version might be a glitch that I can ignore, but to remove shields like that… on three terminal servers with 40+ users… not good.
And strangely, in the General Settings tab for Windows Workstations, Program Updates has BOTH Automatically and Manually options selected… can’t be changed to one or the other as far as I can tell. I’ll have to try creating a new template and see what that looks like.
Edit: New Template did not help… Program Updates on newly created template shows both options selected.

14

We need offline support ASAP! 7.x without offline is useless!

15

Hi all, I am happy to announce that the update 7.16 of our On-Premise Management Console has been finally released and is available for update.

Also, I’d like to apologise you for the inconveniences related with the postponed release.
Best, Pavel

16

I have critical issue after upgrading On Premise Console to latest version 7.16. Installer finished normally, it just upgraded Postgres, created backup dump, installed MS C++ 2017 and upgraded console, but at the end it refuses to start. Avast Console Service won’t start. Log files shows error:

2019-12-19 00:07:12.740 ERROR o.s.boot.SpringApplication [main]: Application run failed (SpringApplication.java:842)
java.lang.IllegalStateException: java.lang.IllegalStateException: Logback configuration error detected:
ERROR in ch.qos.logback.core.joran.spi.Interpreter@30:31 - no applicable action for [totalSizeCap], current ElementPath is [[configuration][appender][rollingPolicy][timeBasedFileNamingAndTriggeringPolicy][totalSizeCap]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@78:85 - no applicable action for [rollingPolicy], current ElementPath is [[configuration][appender][rollingPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@79:30 - no applicable action for [fileNamePattern], current ElementPath is [[configuration][appender][rollingPolicy][fileNamePattern]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@80:23 - no applicable action for [minIndex], current ElementPath is [[configuration][appender][rollingPolicy][minIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@81:23 - no applicable action for [maxIndex], current ElementPath is [[configuration][appender][rollingPolicy][maxIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@84:89 - no applicable action for [triggeringPolicy], current ElementPath is [[configuration][appender][triggeringPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@85:26 - no applicable action for [maxFileSize], current ElementPath is [[configuration][appender][triggeringPolicy][maxFileSize]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@30:31 - no applicable action for [totalSizeCap], current ElementPath is [[configuration][appender][rollingPolicy][timeBasedFileNamingAndTriggeringPolicy][totalSizeCap]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@78:85 - no applicable action for [rollingPolicy], current ElementPath is [[configuration][appender][rollingPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@79:30 - no applicable action for [fileNamePattern], current ElementPath is [[configuration][appender][rollingPolicy][fileNamePattern]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@80:23 - no applicable action for [minIndex], current ElementPath is [[configuration][appender][rollingPolicy][minIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@81:23 - no applicable action for [maxIndex], current ElementPath is [[configuration][appender][rollingPolicy][maxIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@84:89 - no applicable action for [triggeringPolicy], current ElementPath is [[configuration][appender][triggeringPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@85:26 - no applicable action for [maxFileSize], current ElementPath is [[configuration][appender][triggeringPolicy][maxFileSize]]
at org.springframework.boot.context.logging.LoggingApplicationListener.initializeSystem(LoggingApplicationListener.java:276)
at org.springframework.boot.context.logging.LoggingApplicationListener.initialize(LoggingApplicationListener.java:237)
at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEnvironmentPreparedEvent(LoggingApplicationListener.java:200)
at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEvent(LoggingApplicationListener.java:173)
at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)
at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:127)
at org.springframework.boot.context.event.EventPublishingRunListener.environmentPrepared(EventPublishingRunListener.java:74)
at org.springframework.boot.SpringApplicationRunListeners.environmentPrepared(SpringApplicationRunListeners.java:54)
at org.springframework.boot.SpringApplication.prepareEnvironment(SpringApplication.java:358)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:317)
at com.avast.bc.BusinessConsoleApplication.main(BusinessConsoleApplication.java:50)
Caused by: java.lang.IllegalStateException: Logback configuration error detected:
ERROR in ch.qos.logback.core.joran.spi.Interpreter@30:31 - no applicable action for [totalSizeCap], current ElementPath is [[configuration][appender][rollingPolicy][timeBasedFileNamingAndTriggeringPolicy][totalSizeCap]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@78:85 - no applicable action for [rollingPolicy], current ElementPath is [[configuration][appender][rollingPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@79:30 - no applicable action for [fileNamePattern], current ElementPath is [[configuration][appender][rollingPolicy][fileNamePattern]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@80:23 - no applicable action for [minIndex], current ElementPath is [[configuration][appender][rollingPolicy][minIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@81:23 - no applicable action for [maxIndex], current ElementPath is [[configuration][appender][rollingPolicy][maxIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@84:89 - no applicable action for [triggeringPolicy], current ElementPath is [[configuration][appender][triggeringPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@85:26 - no applicable action for [maxFileSize], current ElementPath is [[configuration][appender][triggeringPolicy][maxFileSize]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@30:31 - no applicable action for [totalSizeCap], current ElementPath is [[configuration][appender][rollingPolicy][timeBasedFileNamingAndTriggeringPolicy][totalSizeCap]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@78:85 - no applicable action for [rollingPolicy], current ElementPath is [[configuration][appender][rollingPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@79:30 - no applicable action for [fileNamePattern], current ElementPath is [[configuration][appender][rollingPolicy][fileNamePattern]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@80:23 - no applicable action for [minIndex], current ElementPath is [[configuration][appender][rollingPolicy][minIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@81:23 - no applicable action for [maxIndex], current ElementPath is [[configuration][appender][rollingPolicy][maxIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@84:89 - no applicable action for [triggeringPolicy], current ElementPath is [[configuration][appender][triggeringPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@85:26 - no applicable action for [maxFileSize], current ElementPath is [[configuration][appender][triggeringPolicy][maxFileSize]]
at org.springframework.boot.logging.logback.LogbackLoggingSystem.loadConfiguration(LogbackLoggingSystem.java:166)
at org.springframework.boot.logging.AbstractLoggingSystem.initializeWithSpecificConfig(AbstractLoggingSystem.java:67)
at org.springframework.boot.logging.AbstractLoggingSystem.initialize(AbstractLoggingSystem.java:57)
at org.springframework.boot.logging.logback.LogbackLoggingSystem.initialize(LogbackLoggingSystem.java:114)
at org.springframework.boot.context.logging.LoggingApplicationListener.initializeSystem(LoggingApplicationListener.java:269)
… 12 common frames omitted
2019-12-19 00:07:12.846 ERROR com.avast.bc.StartupListener [main]: Start failed: java.lang.IllegalStateException: Logback configuration error detected:
ERROR in ch.qos.logback.core.joran.spi.Interpreter@30:31 - no applicable action for [totalSizeCap], current ElementPath is [[configuration][appender][rollingPolicy][timeBasedFileNamingAndTriggeringPolicy][totalSizeCap]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@78:85 - no applicable action for [rollingPolicy], current ElementPath is [[configuration][appender][rollingPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@79:30 - no applicable action for [fileNamePattern], current ElementPath is [[configuration][appender][rollingPolicy][fileNamePattern]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@80:23 - no applicable action for [minIndex], current ElementPath is [[configuration][appender][rollingPolicy][minIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@81:23 - no applicable action for [maxIndex], current ElementPath is [[configuration][appender][rollingPolicy][maxIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@84:89 - no applicable action for [triggeringPolicy], current ElementPath is [[configuration][appender][triggeringPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@85:26 - no applicable action for [maxFileSize], current ElementPath is [[configuration][appender][triggeringPolicy][maxFileSize]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@30:31 - no applicable action for [totalSizeCap], current ElementPath is [[configuration][appender][rollingPolicy][timeBasedFileNamingAndTriggeringPolicy][totalSizeCap]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@78:85 - no applicable action for [rollingPolicy], current ElementPath is [[configuration][appender][rollingPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@79:30 - no applicable action for [fileNamePattern], current ElementPath is [[configuration][appender][rollingPolicy][fileNamePattern]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@80:23 - no applicable action for [minIndex], current ElementPath is [[configuration][appender][rollingPolicy][minIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@81:23 - no applicable action for [maxIndex], current ElementPath is [[configuration][appender][rollingPolicy][maxIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@84:89 - no applicable action for [triggeringPolicy], current ElementPath is [[configuration][appender][triggeringPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@85:26 - no applicable action for [maxFileSize], current ElementPath is [[configuration][appender][triggeringPolicy][maxFileSize]] (BusinessConsoleApplication.java:58)

Need urgent fix.

17

How to download it please? I usually prefer to do clean installs rather than upgrades. Is there a link to download it from?

18

Download link: https://www.avast.com/download-thank-you.php?product=BMS-DOWNLOAD&locale=en-ww

19

Didn’t you sometimes earlier change log settings in your config?

20

Check the permisions on the file logbak.xml on C:\Program Files\AVAST Software\Management Console\console\config