rebuilt server can't see any clients running

[Battleship]

I had to rebuild my avast console, wiping the database to successfully get to the new version.  So I am now running Avast enterprise administration 7.0.223
I ran a discovery task and it discovered all computer in my domain but it does not see they are running avast.  all computers have a 7.x managed version that was deployed from the business protection console before I upgraded.  Is there a way to get these computers to sync with this?  The avast server name and IP has NOT changed.
Secondly, we installed avast previously via a login script (bat file) deployed via group policy.
Is there a good login script example to do a silent install of avast for this ?  maybe if i have them push out a new client they will show up?

[wpn]

From my experience so far the older clients from BP dont connect to the new console, you need to redeploy the client ot the machines via the console

when generating an installation package, there is only an EXE file, no MSI file anymore.
The EXE file runs almost completely silent, at start of the exe u see a short flash of a window and then its waiting for installation.

[Battleship]

what's weird is the client version is the same.  and if i look at an old (old just meaning it talked to my prior avast console) client it says the same server and port that it wants to talk to.  Yet the current console completed discovery, found all pc's yet has them showed as nothing installed.  I guess best way would be a login script deployed via group policy that runs the .exe from a network share?
We will see what happens with the current version then on there....

[Avosec-UK]

You say that you had the old Business Protection (Plus) console installed on the server.
Well the problem is that the connectors are different.
You need to redeploy the AEA client over the top of the old one.

[Battleship]

thanks got a login script doing the install...  Is there any key to these icons? I have light gray, dark gray, solid green, dark gray with a green check mark, one that looks like a nuke warning, etc....  I can't find what all these mean...

[wpn]

you dont need to run a login script, configure your deployment job propperly and you can deploy from the console   and please TEST about 5 computers before doing this to ALL computers at the same time

[Battleship]

It always fails.  I've tried setting GPO to open ports in windows firewall and doesn't help.

Code: [Select]

08/08/12 16:53:21:   rinstInstall begin
08/08/12 16:53:21:   Init 50 60 C:\Windows\TEMP\aswEE58.tmp C:\Program Files\AVAST Software\Enterprise Administration\InstPkgs NULL  0
08/08/12 16:53:21:   Store
08/08/12 16:53:21:   Domains: MYDOMAIN,
08/08/12 16:53:21:   Init MYDOMAIN\DELL-E6430
08/08/12 16:53:21:   DELL-E6430: GetAccount
08/08/12 16:53:21:   DELL-E6430: Queueing
08/08/12 16:53:21:   StartThread
08/08/12 16:53:21:   Loop
08/08/12 16:53:21:   SpawnThreads
08/08/12 16:53:21:   DELL-E6430: StartSetup
08/08/12 16:53:21:   DELL-E6430: Connecting
08/08/12 16:54:04:   DELL-E6430: WNetAddConnection2 \\DELL-E6430\C$ MYDOMAIN\Administrator error 53 (The network path was not found)
08/08/12 16:54:04:   DELL-E6430: WNetAddConnection2 \\DELL-E6430\ADMIN$ MYDOMAIN\Administrator error 53 (The network path was not found)
08/08/12 16:54:04:   DELL-E6430: RemoveOnError
08/08/12 16:54:04:   DELL-E6430: Finished with error
08/08/12 16:54:04:   TerminateAll
08/08/12 16:54:04:   rinstInstall end 0


[Battleship]

HMM now it just worked on one.  I think the gpo firewall settings did it.  but i have to wait a day for those to apply company wide. half the computers have gray icon before avast is on them and the other half seem to have a yellow key?  anyone know the difference?

[nannunannu]

HMM now it just worked on one.  I think the gpo firewall settings did it.  but i have to wait a day for those to apply company wide. half the computers have gray icon before avast is on them and the other half seem to have a yellow key?  anyone know the difference?

Grey icon - computer has not communicated.

Yellow key - client has communicated and attention required.   I ran into this with the new version where the sharepoint shield installed but wasn't running because we don't use sharepoint.  by default in the group options it was set to monitor the sharepoint shield, so since it was monitored and not running, I got an attention required status.  Quick solution - disable monitoring in your group settings for sheilds that you don't use.

[Battleship]

so in one of the computers i'm trying out the login script on... its gray with a yellow key on it.  It detects no avast version installed even though I know it ran the script. 
or could it be the yellow key is showing they had that other client on them that tried communicating but because of whatever differences it really can't until i re-push out an install?

edit: this computer says it is running in trial mode though i know its talking to the server as I get prompted for the password i set before i can modify any settings... why would just this one be in trial mode?  I have 100 licenses and install on 5 so far.

[Battleship]

now that i think about it, i bet that is what that yellow key means.  make sense logically... like it needs license or is running in trial mode... now how to figure out why it is like that and not getting license from the server....

[Mariano_Oviedo]

I have the same problem, did you solve it?

[Avosec-UK]

now that i think about it, i bet that is what that yellow key means.  make sense logically... like it needs license or is running in trial mode... now how to figure out why it is like that and not getting license from the server....

Check the number of computers in your company and in the administration console.
Just sum the number of computers in the administration console. If the number of computers is greater than the number of computers in your company, delete the nonexistent computers, remove the schedule for the "Find Computers" discovery task, close the AEA console and restart the AEAS service.

[Mariano_Oviedo]

Thank you!, It was that