Hello, I’ve just purchased Avast Endpoint protection, I’ve managed to get the Avast client on all the computers after various firewall issues etc. But each client still won’t grab the license file from the server, and I’m afraid it has something to do with the Mirror on the server failing each time.
It seems to have to do with Setup.exe being locked open each time the mirror update runs. Setup.exe is actually executed each time the mirror update is run. I don’t know if that’s proper or not. I don’t want the avast client on the server, and I do remember seeing an error message after deploying the console saying something to the effect that avast couldn’t be installed to this version of windows. I’m wondering if the program is attempting to batch reinstall the client on the server each time the mirror is updated. We’re running Server 2003 by the way.
To add a bit of insight to this, sometimes during the mirror update procedure, I see setup.exe in the actual task manager as if it’s attempting to run.
Then the mirror.log tails this!:
It seems as if the Mirror update is trying to execute the client setup on the server, and of course it’s bombing with the “I can’t install on Windows 2003 speil” and failing.
06-19 14:23:43,534 [SchedulerWorker3] ERROR Scheduler - Error during server side job execution.
Avast.Sbc.Scheduler.Iface.TaskException: Unexpected unresolvable error in definitions update job! —> System.Data.UpdateException: The setup process failed to exit within the specified timeout!
at Avast.Sbc.UpdateEngine.Iface.UpdateEngine.BuildIniFile(String sbcServerName, Int32 sbcServerPort)
at Avast.Sbc.UpdateEngine.Iface.DefinitionsUpdateJob.BuildIniFile(Int32 lowerBound, Int32 upperBound)
at Avast.Sbc.UpdateEngine.Iface.DefinitionsUpdateJob.Execute(Job job, IPluginContext context)
— End of inner exception stack trace —
To add insult to injury, it appears that the support ticketing system is down. I’ve submitted three seperate trouble tickets, and the submit process blinks then returns me to the view a tickets page, where the submitted ticket roster is blank.
I told the customer at the very worst I could run around to each client with a thumb drive and insert the license that way.
I’ve found if I manually install these clients with the client installer from the website and point them at the server, I’m able to pull the license, but not through the deployment process.
Funny thing was, I was able to deploy the clients from the console just fine. (Barring a few firewall issues)
How was it you were able to “point” the client to the server? When I look at the clients they are in trial mode, and say they are streaming updates and such.
Every client that I deployed did not register on the console. I can see the computer name, but no connection has been made. The 4 machines that I manually downloaded the avast endpoint stand-alone client and installed (machines were off etc) during install it asks if you want Enterprise, SB or Standalone and asks for the corresponding server name. Added that and those 4 show up on the server as active. Now I guess I can’t say for certain they pulled the license as I was in trial mode at the time (wasn’t sure how many licenses were needed) but added it after the fact. Since they are showing communication, I just assumed they pulled the license whereas none of the pushed clients have shown a connection, even though avast is installed and running on the machines.
Ugh after deploying the product from the console none of the clients show as managed. I was hoping after the mirror update from the console it would bing the clients on the head and give them their marching orders.
Just kinda sucks I spent 860 some odd dollars, and we’re relegated to figuring this out on our own. I’m getting the serious heebie jeebies about Awill products.
Sounds like you are having the same issue with the client install not getting customized. Before you went back to the BP console were you unable to download the avast_managed.exe from the admin console (admin - settings - setup - download link at the bottom of the page) as described in this thread:
Funny, I found a reference to one of my threads in this one… I’m batting a thousand! :-\
Yeah, the job labeled “Update Server Deffinitions” is failing on me. I think it’s due to this that I cannot download “avast_managed.exe” from my server. This is now causing issues where I cannot deploy to my remote laptop users.
Running mirror.exe at a command prompt doesn’t yield much info as to if or why it’s failing
U:\>"C:\Program Files\AVAST Software\Administration Console\x64\mirror.exe"
mirror begin...
Mirroring...
Using server: http://download989.avast.com/iavs5x
Using server: http://download118.avast.com/iavs5x
Setting product 'abp' files (901 of 906 set)
Resetting existing files (reset 901 files, leaving 0 files).
Using server: http://download323.avast.com/iavs5x
mirroring 'abp' - nothing to do.
Setting product 'ais' files (4 of 906 set)
Resetting existing files (reset 4 files, leaving 0 files).
Using server: http://download352.avast.com/iavs5x
mirroring 'ais' - nothing to do.
Mirroring done.
Building distributions...
Building distribution 'distrib0'
Setting product 'abp' files (901 of 906 set)
Resetting existing files (reset 901 files, leaving 0 files).
Setting product 'ais' files (4 of 906 set)
Resetting existing files (reset 4 files, leaving 0 files).
Building distribution 'distrib0' done.
Building distributions done.
Uploading distribution 'distrib0'
Sumarizing...
Setting product 'abp' files (901 of 906 set)
Setting product 'ais' files (902 of 906 set)