Author Topic: Beta version 2.30 of the new on-premise Avast Business Management Console  (Read 6368 times)

0 Members and 1 Guest are viewing this topic.

Offline Martin Svoboda

  • Avast team
  • Jr. Member
  • *
  • Posts: 89
Hello everyone,
 
it's been a while since last beta version so today are releasing the 2.30 beta version of the new on-premise console.
 
What's new?
  • The SMTP configuration has been moved from the console installer directly into the Console under the "General settings"
  • AV installer creation - ability to specify into which group will be device added after activation and which policy settings will be applied to it.
  • Antivirus now contains all componets which are available for each tier.

 
Known bugs / limitation
  • Only “Start Trial” billing functionality works, any other features (e.g. Buy now, Renew license) are not yet available
    • At the moment no way to renew license
  • Mirror feature still unavailable for Mac AV - The new Mac AV version which will support this feature will be released soon. Once it will be released (we will let you know here), even Mac device will be updated via the Mirror server.

What has been fixed
  • “Agent” is digitally signed by AVG
  • Update of the previous beta to this one doesn't work, you have to make clear installation of the console and then reinstall even clients.
  • “License expired” header shown immediately after application of a licence
  • 3 restarts are needed for newly added device in order to works properly
  • SecureLine and Avast Passwords not available yet
  • Client still shows “Fix all” button
  • Upload licence file widget is obsolete and will be removed
  • After installation of AV you will see a dialog informing that UI failed to load. You can ignore this dialog as UI works as expected.

 
Where to get installer?
Please note: This is not an antivirus installer. You are about to install a solution for management of your devices,
a management console through which you will be able to download and install the antivirus.

 
Step1. Choose a console type
  • Docker image - available via Docker hub
    • This type is multi-platform and requires more advanced IT admin skills
    • Follow the instructions on how to run the console
  • Windows installer - available to download here
    • Open the .exe file and go through all the installation steps
    • We are highly recommend install into Virtual Machine or test environment

Step2. Get your trial license
  • Generate your trial license (choose one the the product, the rest of them can be started directly from the console later on)
  • This license has an expiration period of 60 days.
  • You can insert this code once inside the console (both Docker and Windows).

Step3. Sign-up to the console and upload the trial license
  • Sign-up and create your company account
  • Once on the dashboard you can insert your generated license code
  • Click the “add devices” button to download the installer of agent

 
We would appreciate any feedback from your side, not only obvious bugs but also any comments regarding things that doesn't make sense from your point of view, or any suggestion for improvements.
 
One last thing we want to share a little secret with you - this version of the Management Console will be available also as a Cloud version.
 
Thank you and looking forward to your feedback.
« Last Edit: July 25, 2017, 02:58:02 PM by Martin Svoboda »
Senior Product manager | Avast Business

Again in avast

Offline PAID

  • Jr. Member
  • **
  • Posts: 41
When do you Avast on-premise public release?

Offline Martin Svoboda

  • Avast team
  • Jr. Member
  • *
  • Posts: 89
When do you Avast on-premise public release?

Our plan is to release it after the education holiday (in europe). That is the closest which I can tell.
Senior Product manager | Avast Business

Again in avast

Offline jjsets

  • Newbie
  • *
  • Posts: 19
Short note on getting the trial license > we found out that it worked here only after first flushing all caches (we use Google Chrome) in the browser - well at that point we too updated to the new Google Chrome version (60.0.3112.78 (Offizieller Build) (64-Bit))

Offline Jan Suchan

  • Avast team
  • Newbie
  • *
  • Posts: 15
Short note on getting the trial license > we found out that it worked here only after first flushing all caches (we use Google Chrome) in the browser - well at that point we too updated to the new Google Chrome version (60.0.3112.78 (Offizieller Build) (64-Bit))

Hi jjsets, we had an issue with the mentioned page. It should be fixed now and it should work in all browsers. Thanks for reporting it.
Jan Suchan
Avast Business Lead Developer

Offline PAID

  • Jr. Member
  • **
  • Posts: 41
If Linux client will be supported, Avast can be best in enterprise market!

Offline jjsets

  • Newbie
  • *
  • Posts: 19
First TThX for solving the beta license prob.
Second > i support PAID remarks on supporting the AVAST Linux solution via this on-Premises Business central Administration solution.

Offline jjsets

  • Newbie
  • *
  • Posts: 19
Hi,

just tried to pull the docker Image >
https://hub.docker.com/r/avastsoftware/management-console/
>> got
PS C:\programme> docker pull avastsoftware/management-console
Using default tag: latest
Error response from daemon: repository avastsoftware/management-console not found: does not exist or no pull access

Btw. > docker pull microsoft/nanoserver  works

Any idea what is going wrong?
---
Update: Found that this does find an image > adding (Version)  :2.30.130.273
« Last Edit: August 02, 2017, 09:35:51 AM by jjsets »

Offline Nevik

  • Avast team
  • Newbie
  • *
  • Posts: 4
The reason why you were not able to pull the docker image using "docker pull avastsoftware/management-console" is that we don't have the "latest" tag for the image. We just have tags with specific versions. The management-console docker image is meant to run in a docker-compose application. The image is not usable on its own, it requires an image with database and some additional configuration. We provide the sample configuration in the GitHub repository - https://github.com/avast/management-conle-config (docker-compose.yml, .env).

Currently, the "latest" tag is missing on purpose, as we want to prevent people just pulling and running the single image without reading the documentation about proper use of the docker-compose application. It also helps with troubleshooting of issues, when we ask somebody for output of "docker ps -a" (list of running docker containers), we can clearly see which version is being used. We might re-consider adding the "latest" tag in the future, but for now, we are preferring being explicit about the versions.

Offline misak

  • Avast team
  • Sr. Member
  • *
  • Posts: 234
    • Personal page (CZE)
Possible availability issue with the on-premise beta version in upcoming week.

There will be network & system infrastructure redesign in ATL DC between Aug 8 and Aug 16. We are expecting short connectivity outage on August 8. Antivirus deployment from on-premise console might be affected. Avast for Business production enviroment will be not affected.

Offline studio_two

  • Full Member
  • ***
  • Posts: 114
    • Practical SBS
The image is not usable on its own, it requires an image with database and some additional configuration. We provide the sample configuration in the GitHub repository - https://github.com/avast/management-conle-config (docker-compose.yml, .env).

So, we will therefore need at least two containers to run the Console? One for the Web Console itself, and one for the Database? Also, some addition configuration is needed to link the pieces together?

I would love to test this out, but at the moment, this is above my skill level. Will there eventually be a single "pull" command to install the entire thing?

Kind Regards, Stephen

Offline Nevik

  • Avast team
  • Newbie
  • *
  • Posts: 4
Yes, there are two containers, but is not difficult at all. We provide the configuration that is putting the pieces together and we describe the necessary steps in description of the docker image: https://hub.docker.com/r/avastsoftware/management-console/

In a nutshell, it is just:

git clone https://github.com/avast/management-console-config.git
cd management-console-config
# edit .env file, change value AFB_HOSTNAME=my-server.example.org to AFB_HOSTNAME=hostname of your machine
docker-compose up

If you omit the the step of modifying the .env file, management console will start anyway, but the AV downloaded from the console will not be able to connect with your console (it will not know correct hostname of your server).

Offline jjsets

  • Newbie
  • *
  • Posts: 19
We run into an issue with certificates. I can only add a SSL certificate during installation. I fail to find a place to replace the certificate if necessary. For example, free let's-encrypt-certificates would need to be updated every three months. This should be a feature for the final release.

Offline studio_two

  • Full Member
  • ***
  • Posts: 114
    • Practical SBS
Re: Beta version 2.30 of the new on-premise Avast Business Management Console
« Reply #13 on: September 01, 2017, 11:23:34 AM »
Thank you Nevik.

I will look into this further.

Kind Regards, Stephen