[RFC] multiple changes requested in the EA Console

[HomeNet]

RFC 20: "Find computers" task in AEA to scan a specific OU in AD

I'd like to have the ability to use a task like the default "find computers" task in AEA to scan a specific OU in AD.  Since this is an enterprise solution, the option of scanning workgroups seems a bit out of place.  Evidently, it already has the ability to scan for new computers in a certain domain but what happens when you have all your users in one OU and all your servers in another?  I'd like to be able to create two tasks: one would scan an OU for clients and the other would scan for servers.  Each of these tasks would be able to dump the findings into different groups.

[Infratech Solutions]

RFC 19. Clean/empty the log files.
You can see several log files from the  View option in the menu: Server, remote install... but you cannot clean them or empty from the console.

[wpn]

Unfortunately i cannot add anything to the first post anymore since the character limit per posting has been reached

[wpn]

edj wrote:
RFC 19: Clean/empty the log files.
You can see several log files from the  View option in the menu: Server, remote install... but you cannot clean them or empty from the console.

RFC 20: Test SMTP/database settings during setup and SMTP also inside the console
There is no option to test the settings for SMTP and database connections during setup. This was introduced in the setup for the SBC 6 console. This should return.
When there is no SMTP configuration during setup, then there should be a test option for the configuration in the console itself.

RFC21: semi-integration of the maintenance tool into the console with smart-decisions
Right now there are two tools:  the console and the maintenance tool
When the console doesnt work you need to use the maintenance tool to do troubleshooting.
Re-write the console login procedure to be smarter:  When the console cant login offer to start the maintenance tool or start it automatically when the console is started from the AEA server.
Since the maintenance tool requires administrator rights, a person that dont have those right will not be able to use the tool so its secure to offer the program this way.

[MarKvi]

Thank you for adding your ideas/tips! Some of them are really great and I hope, that we will have the opportunity to implement 
them in one of the next program updates.

[wpn]

Love the response MarKvi, thank you so much for that!
as you see we like to help improve the product


Keep us updated please   love to see our input getting incorporated in the product     THAT is (in my opinion) the best reward for our support to the Avast team

[spi]

+1 to MarKvi

[BPWarrior]

RFC 20: "Find computers" task in AEA to scan a specific OU in AD

+1

[RFC] 22 :  hollow us to have your avast! licences deploy for specific group of de AEA console and not all computer detected

When we run the the "find computers" task with AD detection it find all object and that fine
But we have to delete computers who don't have (and don't need) an avast! agent.
Otherwise we they have a licence count and we can't deploy more computers.
I would love have the "unmanaged group" back!

[wpn]

Regarding RFC 10:  i personally dont need to have it in the Avast installation.  For personal use i use Teamviewer. This program is specially meant for remote control. For business uses i also use teamviewer .  Teamviewer is optimised for remote control and its the core business of the program where as this is not for the avast part.
Teamviewre doesnt need to be installed on the computer, it runs portable. This way you can also support when your behind a computer that doesnt have avast installed (how is that even possible?!) and take over the computer with the problems where avast is installed

Maybe the teamviewer software van be integrated with a deal with teamviewer team?


RFC 20 and 22:  This is basicly the same request, from which the UNMANAGED group is the best option (like the sbc product had). I have several OUs in which also are objects that i dont need avast on but do get licensed, this is not wanted, we need to have more control over which object gets a license or not.

[Battleship]

RFC 20: "Find computers" task in AEA to scan a specific OU in AD

+1

[RFC] 22 :  hollow us to have your avast! licences deploy for specific group of de AEA console and not all computer detected

When we run the the "find computers" task with AD detection it find all object and that fine
But we have to delete computers who don't have (and don't need) an avast! agent.
Otherwise we they have a licence count and we can't deploy more computers.
I would love have the "unmanaged group" back!

ugh... this must be my problem.  I have my find computer run against AD.  it finds my macbooks that will never have avast, old pc's that we don't want it on (they use the free windows one), and servers, etc we don't put it on.  It should be based on that dynamic group of computers with agent.  I have 100 licenses, but only 20 currently running the agent.  Now i'm trying to get avast on a pc that has a yellow key icon on it so i assume it doesn't have a license available.  And its random... I just have to start deleting computers?  I have the discovery task set to run daily.... won't they come back?  I shouldn't have upgraded...

[wpn]

@battleship,   yes you have to delete computers from the console, AND stop the discovery task, if you want to be in control of the license assignment. When the job runs (auto/manual) the deleted objects from the console will come back again, UNTIL RFC 20/22 are implemented!

the key icon actually means there is no license for that machine

[Infratech Solutions]

Regarding RFC 10:  i personally dont need to have it in the Avast installation.  For personal use i use Teamviewer. This program is specially meant for remote control. For business uses i also use teamviewer .  Teamviewer is optimised for remote control and its the core business of the program where as this is not for the avast part.
Teamviewre doesnt need to be installed on the computer, it runs portable. This way you can also support when your behind a computer that doesnt have avast installed (how is that even possible?!) and take over the computer with the problems where avast is installed

Teamviewer is not free for business use, like avast!. So if you are giving support to your customers you have to pay about 499,00 € for a license of a single machine, because this is not a personal use.

I don't understand why to give support to a free user is so easy (a tool included with avast!) and to give support to a business (paid) user is not so easy. Open ports in business customers for a remote connection to de AEA console is not easy in most cases.

[wpn]

You got a point there EDJ.

For businesses that really cant cut out the budget between 500 en 2500 euro for licences for teamviewer (or other remote control software) this remote option in Avast is ideal.  But like i said the remote control sollutions like teamviewer have their core business at programming the software for remote control where as Avast core business is anti-virus.
The specialised programs also give a lot more options to do things with the remote computer then the avast option (so far)

But like i said  its my personal opinion about that point.

[Infratech Solutions]

Are there any of these requests in the AEA 7.0.306 release?

[Infratech Solutions]

RFC 12: MS Windows 8 Support.

Solved!