You can export/import settings if you're migrating from the SOA/AEA Consoles to the cloud/on-premise console.
I did that when I migrated from the old console in this office to the new console.
Half our stuff broke because the settings don't work the same in both applications and so what previously worked for stopping our devs complaining about the AV software now no longer worked.
I've now put about 3 months work into making sure our devs are happy and things work. Copying those settings manually from one console to the other (which I've now had to do) took me about 2 hours to complete.
This is wasted time for me. All the data is on one system. There is NO good reason why I should not be able to simply copy said data from one system to the other.
However, for exporting/importing settings from/to the cloud/on-premise console, someone had opened an internal ticket asking for this feature request a while back, but due to lack of interest from other customers/partners/resellers, it was put on the backburner.
And it's this exact attitude that I find so problematic with this. This is not a game or a piece of software being developed by some indie company or a bunch of spirited enthusiasts. It is a piece of software being developed by a multi-million dollar company with 1800 employees.
Not to mention this is something that had I known this was not possible at the time of purchasing the license. I, naively its seems, assumed it would be in a piece of enterprise software. We would have switched to a different product at that time.
Which considering the multiple egregious issues we've had with Avast are now looking to do.
There are so many reasons why this is wanted/needed in a business environment that it's astounding to me that this hasn't just been done as a de rigueur feature.
I reopened the ticket and copied the link of this forum post into the ticket, but if no one else expresses interest in this feature request, it will be placed on the backburner again in favor other features requested by more customers/partners/resellers.
How are people supposed to know they have to ask for this? Until you need it, it's not something you go looking for and when you need it, you need it right the hell now, not in some nebulous future time frame.
You've clearly had people ask for the feature, and it's a feature that makes a lot of sense to have so why is that simply not enough to go "Ok lets implement this feature".
You even have it in the end user client ffs! So why is it not a thing in the console? (
https://support.avast.com/en-us/article/15)
The ticket number is CBC-3435 and you may inquire about its status from our Avast Business technical support at any time.
Great, so every time I want to check on whether or not it's been implemented I have to find the ticket number and email the helpdesk and wait a nebulous period of time for a response?
As other people have mentioned in this thread, and elsewhere on this forum. Why does the feature page not list all feature requests and allows us to vote up/down on them?
If you're going to go this route, then go the whole hog and actually let your users decide on what gets implemented, instead of having the requests filtered by some internal person/team and then giving us the small selection of things you have.
There's at least three things I've mentioned in this forum that should be on there as feature requests (and I'd very surprised if someone else hasn't requested the multiple times)... but there's only one of those three listed on the feature request page.
Our developers and production team prioritizes feature requests by how many customers/partners/resellers are requesting the feature. The more requests for a feature, the higher it's prioritized.
Yes but that only works if people KNOW they need to request said feature, as I've already said if you don't need it you don't go looking for it, and when you do need it... It's because you need it now, not in some nebulous future time frame.
I am not suggesting that you need to support every feature that is requested, but something as basic and low level as being table to import/export configurations should be something that in my humble opinion should have been included from day 1.