...but you can do that just by typing mirror.exe in cmd prompt when you are in the Avast directory
Yes, I know. But if you are manage several customer AMS servers and you have an avast! Console you don’t have access to the cmd prompt in the servers or access to any directory, you only have access to the AMS Server and his options, even, you have no access to the AMS Maintenance Tools. :-\
Damn, I just thought of a good request, but I got caught answering some other topics while looking for this one, and forgot what it was!
Grr. Oh well, this will bring this post back up on top and hopefully I can remember what it was soon, so that I don’t have to search for this thread again!
I think I remember, but it's hard to word. Anyway, I just had my 27th birthday a few days ago, so I don't think it's that... possibly related to the alcohol intake. ;D
Anyway, I don’t know if this has been said yet, but I think it needs to be said again if it has.
If a computer doesn’t have avast installed, nor even a part of a domain, it shouldn’t be counted in the license totals!
I understand that you can use active directory to pull computer names into the ADNM console, but if they’re disabled, they shouldn’t be added. Discovered computers that are just on the network, shouldn’t be added either.
Basically, the ADNM console should query computers after they are discovered to find out if they have:
Avast installed
A managed product
Check to see if the machine is active in the domain, or disabled.
I really don’t see a point in having the ADNM console count a disabled computer as a licensed machine. If ADNM finds a disabled computer, it should remove it from the database automatically, and re-assign the license to another machine if one becomes available.
I get so sick of managing “two active directories”. I have to find the computer name, remove it from active directory, then remove it from ADNM.
Hey, it might not be possible, but it sure is a wish.
@scythe… 27th??? man u are way past expiration date i should know im turning 30 next month
what you actually mean is:
all discovered computers should be placed in a quarantined container inside ADNM. Inside this container they will NOT get a license appointed yet.
If the detected AD computer is present and active (turn on) on the network there should be a check to see if any Avast software is already installed. If the software is not installed or the installed software is not a managed client then the computer object should reside in the quarantined container to be approved by an administrator to get a license. If the software is a managed client then after approval the license should be given to the computer and the latest client software updates should be applied.
If the detected computer, during the scan for new computers, is found by IP scan (so therefor not yet found in AD) it should be checked in AD and if it is found in AD it should be checked on the status in AD (disabled or not) if it is disabled then there should not be a possibility to give a license to that station AT ALL.
This check should be done after it is found but BEFORE the check for software (no need to check installed software if the computer is not enabled in AD), maybe even put in a different container which is a default container that cant be deleted, a container called AD-DISABLED (something like that)
this about right??
next to that: standard created containers (ADBNM system containers?) should NOT be able to be deleted!