Avast WEBforum
Business Products => Archive (Legacy) => Avast Business => Avast Endpoint Protection => Topic started by: HomeNet on June 21, 2012, 04:44:03 PM
-
I just recently installed SOA on a Win2k8 R2 server. SOA detected all the clients and I was able to make successful deployments to a handful of Win7 Pro test machines. However, all of the clients are grey and showing no connectivity. The SOA server and all the clients are on the same subnet and domain. The clients are controlled by a GPO that allows UDP/TCP 25322 through the Windows firewall. Windows firewall has been turned off on the server. The clients can ping the SOA server and the server can ping the clients. What am I missing?
Zip file generated by the SOA's troubleshooting section: https://docs.google.com/open?id=0B1V7Mr9BYAxVQjFMNE9QdjBtWmM
-
check the administration service is run or not, after install please restart the client.
you can upload the troubleshooting file to sharing server (mediafire, uploader, etc..) and post the link here.
-
check the administration service is run or not, after install please restart the client.
you can upload the troubleshooting file to sharing server (mediafire, uploader, etc..) and post the link here.
I've edited my first post with a link to the zip file.
What is the name of the service I'm looking for? On the clients, I have avast! Antivirus and I also have avast! Net Client Service. On the server, I have avast! Administration Console, avast! Administration Console Monitor and avast! Administration Console Website Host. All are running. The server & all the clients have been rebooted.
-
On one of the clients go to settings in the upper right corner of the avast gui, then go to troubleshooting, then avast! administration console and check what happens if you change from the fqdn to the ip address of the server.
Also, I think you just need port 25322 TCP (not udp)... I think.
-
On one of the clients go to settings in the upper right corner of the avast gui, then go to troubleshooting, then avast! administration console and check what happens if you change from the fqdn to the ip address of the server.
Also, I think you just need port 25322 TCP (not udp)... I think.
Oddly enough, there was NOTHING listed in that box! I dropped the FQDN in there and restarted the avast! Antivirus service. After that, I had connectivity and I was able to see the PC turn green in SOA. So, now that we know what the issue is, how do I fix it on a grand scale? I deployed the clients from SOA so that setting should've been pushed out with the deployment.
-
I deployed the clients from SOA so that setting should've been pushed out with the deployment.
One would think. :)
I actually hate the push fucitonality - it assumes too much about the availability of the machines and doesn't have an easy way to make sure the old AV was removed first, so I just built a custom install package and launched a script with elevated privladges using other tools (paid tools) that takes care of everything the way I need it to during the user login script... In the console, under admin -> settings -> setup there is a link to download the .exe installer which I saved to a network location and used with success to deploy wtih all settings needed to connect to the console... If you have a method of running as admin in your environment, you can just use that.
-
I deployed the clients from SOA so that setting should've been pushed out with the deployment.
One would think. :)
I actually hate the push fucitonality - it assumes too much about the availability of the machines and doesn't have an easy way to make sure the old AV was removed first, so I just built a custom install package and launched a script with elevated privladges using other tools (paid tools) that takes care of everything the way I need it to during the user login script... In the console, under admin -> settings -> setup there is a link to download the .exe installer which I saved to a network location and used with success to deploy wtih all settings needed to connect to the console... If you have a method of running as admin in your environment, you can just use that.
Ahhh, weak! I was hoping I could just tweak an INI or something and redeploy. I'll look into what you speak of but if anyone knows how to fix the bug, let me know.
-
In the console, under admin -> settings -> setup there is a link to download the .exe installer...
My download doesn't work. In fact, I think the directory in which is resides doesn't even have the file to download. It's as if it was never generated.
-
Also, I think you just need port 25322 TCP (not udp)... I think.
The only reason I added both to my GPO is because when I deployed the client package, the installer made both changes to my Windows firewall config. I merely mimicked what the installer did.
-
HomeNet - how did you installed (deployed) the clients to your network? Did you use the "Unattended Deployment" job or the avast_managed.exe for email deployment?
-
HomeNet - how did you installed (deployed) the clients to your network? Did you use the "Unattended Deployment" job or the avast_managed.exe for email deployment?
I did the unattended install.
-
It would be a lot easier if we can see the avastNet.log located in:
"C:\ProgramData\AVAST Software\Avast\log" or "C:\Documents and Settings\All Users\Application Data\AVAST Software\Avast\log"
-
It would be a lot easier if we can see the avastNet.log located in:
"C:\ProgramData\AVAST Software\Avast\log" or "C:\Documents and Settings\All Users\Application Data\AVAST Software\Avast\log"
That path doesn't exist on my server. The best I have is C:\ProgramData\AVAST Software\Administration Console\Logs and it has the following logs:
- aswRInst.log
- avast.sbc.manager_120622065224.log
- avast.sbc.service.installer_120622065235.log
- Avast.Sbc.Service_120622065328.log
- avast.sbc.websitehost.installer_120622065322.log
- avast.sbc.websitehost_120622065324.log
- mirror.log
- status.txt
-
It would be a lot easier if we can see the avastNet.log located in:
"C:\ProgramData\AVAST Software\Avast\log" or "C:\Documents and Settings\All Users\Application Data\AVAST Software\Avast\log"
That path doesn't exist on my server. The best I have is C:\ProgramData\AVAST Software\Administration Console\Logs and it has the following logs:
- aswRInst.log
- avast.sbc.manager_120622065224.log
- avast.sbc.service.installer_120622065235.log
- Avast.Sbc.Service_120622065328.log
- avast.sbc.websitehost.installer_120622065322.log
- avast.sbc.websitehost_120622065324.log
- mirror.log
- status.txt
Sorry I needed to clarify: you should look for this file on the client machines.
-
It would be a lot easier if we can see the avastNet.log located in:
"C:\ProgramData\AVAST Software\Avast\log" or "C:\Documents and Settings\All Users\Application Data\AVAST Software\Avast\log"
06/21/2012, 15:33:57 avast! NetService identified as prom-6
06/21/2012, 15:33:57 LoginRequest in Reconnected callback
06/21/2012, 15:33:58 LoginResponse arrived (result = TRUE)! {F9017821-35C1-4B9E-8130-ABABA47C67FE}
06/21/2012, 15:33:58 ScheduleBootTimeScan failed with error code = 1168
06/21/2012, 15:35:00 ScheduleBootTimeScan failed with error code = 1168
06/21/2012, 15:38:48 LoginRequest in Reconnected callback
06/21/2012, 15:38:49 LoginResponse arrived (result = TRUE)! {F9017821-35C1-4B9E-8130-ABABA47C67FE}
06/21/2012, 15:38:49 ScheduleBootTimeScan failed with error code = 1168
06/21/2012, 15:39:06 LoginRequest in Reconnected callback
06/21/2012, 15:39:06 LoginResponse arrived (result = TRUE)! {F9017821-35C1-4B9E-8130-ABABA47C67FE}
06/21/2012, 15:39:07 ScheduleBootTimeScan failed with error code = 1168
06/22/2012, 04:02:09 ScheduleBootTimeScan failed with error code = 1168
06/22/2012, 05:34:25 ScheduleBootTimeScan failed with error code = 1168
06/22/2012, 06:16:21 ScheduleBootTimeScan failed with error code = 1168
06/22/2012, 06:39:20 LoginRequest in Reconnected callback
-
I have exactly the same problem as mentioned. My avastNet.log also looks the same.
I also used the 'unattended deployment' and tested it on Windows 7 and Windows Vista.
Both are encountering the same problem.
-
Do you see any entries in the avast! Administration Console > ADMIN > Computer login audit trail?
-
Some of my clients were not connecting to the console - nannunannu comment to change the "fqdn to the ip address of the server" worked. However, some machines connected fine using the FQDN and some needed IP. Is this bug or suggesting that my DNS has gone wrong somewhere?
-
Here's something....
"%programdata%\AVAST Software\Avast\avast5.ini"
After doing my little aforementioned trick, where I deploy the client software, change the settings in the GUI so it actually points to the server and then restart the service, I noticed my avast5.ini is different than others across the network. My file has the server's FQDN whereas the other PC's file does not. There has to be an issue with the deployment package...
My file:
[Common]
PropertyCommunity=1
SBCServerName=h1p-asoac1.homenet.local
SBCServerPort=25322
The other file:
[Common]
PropertyCommunity=0
SBCServerName=
SBCServerPort=25322
-
Do you see any entries in the avast! Administration Console > ADMIN > Computer login audit trail?
I only see entries from the few PCs that I've done my little setting change in the GUI for. Other than that, nothing else seems to be checking in.
-
Some of my clients were not connecting to the console - nannunannu comment to change the "fqdn to the ip address of the server" worked. However, some machines connected fine using the FQDN and some needed IP. Is this bug or suggesting that my DNS has gone wrong somewhere?
From those that could not resolve the FQDN, try to ping that server name and see if you get replies or not. If you don't, there's a good chance that DNS isn't working correctly on that client.
-
Is this bug or suggesting that my DNS has gone wrong somewhere?
I'm in no way an authoritative source for answering the question if it is a bug - but my instinct is that it isn't a bug, but rather a binding issue for your name services on the client (wins, netbios, dns)...
I suggested changing that to the address just to conduct basic troubleshoting to eliminate layers involved with network communication from client to server, that is all.
-
So far, the only bug I'm seeing is the fact that the SOA server's address doesn't get included with the deployment and I have to manually enter it in.
-
Here's something....
"%programdata%\AVAST Software\Avast\avast5.ini"
After doing my little aforementioned trick, where I deploy the client software, change the settings in the GUI so it actually points to the server and then restart the service, I noticed my avast5.ini is different than others across the network. My file has the server's FQDN whereas the other PC's file does not. There has to be an issue with the deployment package...
My file:
[Common]
PropertyCommunity=1
SBCServerName=h1p-asoac1.homenet.local
SBCServerPort=25322
The other file:
[Common]
PropertyCommunity=0
SBCServerName=
SBCServerPort=25322
Sounds like your server is pushing the standard package, and not creating the customized one for your envinronment. As a temporary workaround (until someone from avast can fix your server instance), you could try writing an autoit script write the new value for SBCServerName. Compile it and launch it as part of the users login scripts with an "if exist "%programdata%\AVAST Software\Avast\avast5.ini" \\server\netlogon\compliedfixitscript.exe" line...
-
On my old setup (ADNM), I used to have to create the package. Is there no way to fire off that job on this new setup?
-
On my old setup (ADNM), I used to have to create the package. Is there no way to fire off that job on this new setup?
I think it builds it on the fly when you try to download it from the https://server:8732/Install.aspx?prod=EPS link... Again, not the authoritative source, but when I tried it "just worked"...
-
On my old setup (ADNM), I used to have to create the package. Is there no way to fire off that job on this new setup?
I think it builds it on the fly when you try to download it from the https://server:8732/Install.aspx?prod=EPS link... Again, not the authoritative source, but when I tried it "just worked"...
Well, if that's the case, it's not working for me. When I click on my link under Admin > Settings > Setup, it takes me to a download button but it goes no further once I choose to download.
-
This is just getting worse and worse... I've already chimed in on another thread about the lacking mirror-update job. Now, the few servers that I had all green are now showing as disconnected. This happened about the time I started troubleshooting the mirror-update job. The only thing I've done in the way of troubleshooting that is running it from the GUI and running mirror.exe from a command line. I thought it was something wrong with the clients so I restarted the two Avast services that are installed on the client-side. After doing that, I got a red box on the client's screen, saying it would no longer receive any updates 'cause the license was out of date. I just got the 2-year license from Avast 2012-06-20!
4.8 was old and busted but 7 is full of holes. I'm not sure which I was better
-
I'm having the same problems. We just purchased a new license on the 3rd.
I installed Small Office Admin on a Win Svr 2008 R2 server and went through the setup wizard. I deployed to one Windows 7 pc and one Windows XP pc. Both showed the status as unknown. Neither client had the server name in the settings, so I entered it manually on one pc. It then showed as connected and looked well, but then showed as disconnected sometime after that and still shows disconnected.
Also, the Update server definitions job always fails and the link to download the client install does not work.
If I don't find a solution quick, my boss is going to want me to look into another solution.
-
Yeah, there was supposed to have been an update to the install file while I was on vaca last week. I'm not sure if that ever happened, as both the installers seem to install the same version (1.2.2.8).
Our parent company is also setting up meetings for talks about moving to Symantec...
-
For those with connectivity problems after unattended deployment, please let me know what is inside your [Common.ini] section in "%ProgramData%\AVAST Software\Administration Console\mirror\Packages\admin.ini", usually there should be something like:
[Common.ini]
SBCServerName=your_server_fully_qualified_domain_name
SBCServerPort=25322
Thx. Jan.
-
Are you using SOA, or are you using AEA for the management console?
Can you please forward me your license file?
Their are too many posts for me to understand exactly what is your real issue. Could you please give me outline of what was done, exact versions of console and client, is client managed, is console updated, is client updated, so I can see if I can help you.
J.R. Guthrie
-
For those with connectivity problems after unattended deployment, please let me know what is inside your [Common.ini] section in "%ProgramData%\AVAST Software\Administration Console\mirror\Packages\admin.ini", usually there should be something like:
[Common.ini]
SBCServerName=your_server_fully_qualified_domain_name
SBCServerPort=25322
Thx. Jan.
On my server, where I have SOA installed, there is no %ProgramData%\AVAST Software\Administration Console\mirror\Packages\admin.ini.
-
For those with connectivity problems after unattended deployment, please let me know what is inside your [Common.ini] section in "%ProgramData%\AVAST Software\Administration Console\mirror\Packages\admin.ini", usually there should be something like:
[Common.ini]
SBCServerName=your_server_fully_qualified_domain_name
SBCServerPort=25322
Thx. Jan.
On my server, where I have SOA installed, there is no %ProgramData%\AVAST Software\Administration Console\mirror\Packages\admin.ini.
Hi,
try to locate it under
C:\Documents and Settings\All Users\application data\AVAST Software\Administration Console\mirror\Packages\admin.ini
or
try to search admin.ini with windows search using "search for hidden system files and folders" ;)
-
Are you using SOA, or are you using AEA for the management console?
Can you please forward me your license file?
Their are too many posts for me to understand exactly what is your real issue. Could you please give me outline of what was done, exact versions of console and client, is client managed, is console updated, is client updated, so I can see if I can help you.
J.R. Guthrie
I guess I can email you my license file. How would you like me to do that? I can give you a private link to where I keep it.
- Set up, loaded and updated a new Server 2008 R2 SP1 server
- Installed setup_console_ep_full.exe [1.2.2.8] - without any errors
- SOA pulled in all the clients
- Using JOBS > UNATTENDED DEPLOYMENT, I deployed the client to several Windows 7 Pro PCs - without any errors
- PCs DID NOT show up GREEN in the web-GUI and only showed up as disconnected
- Checked Windows Firewall settings to make sure communication wasn't faling there
- Realized the clients didn't have the correct setting so they could communicate with the server so I had to put that in manually via client-side-GUI > SETTINGS > TROUBLESHOOTING > SERVER NAME/IP
- Tried downloading avast_managed.exe from the web-GUI: SETTINGS > SETUP but it gives me a 404 error
- Realized the mirror job was failing and figured it wasn't building avast_managed.exe for me since the directory on the server is also empty
I hope I got everything....
-
Hi,
try to locate it under
C:\Documents and Settings\All Users\application data\AVAST Software\Administration Console\mirror\Packages\admin.ini
or
try to search admin.ini with windows search using "search for hidden system files and folders" ;)
Just to clarify, you want me to do this on the server (SOA) side or on one of the clients?
-
Are you using SOA, or are you using AEA for the management console?
Can you please forward me your license file?
Their are too many posts for me to understand exactly what is your real issue. Could you please give me outline of what was done, exact versions of console and client, is client managed, is console updated, is client updated, so I can see if I can help you.
J.R. Guthrie
I guess I can email you my license file. How would you like me to do that? I can give you a private link to where I keep it.
- Set up, loaded and updated a new Server 2008 R2 SP1 server
- Installed setup_console_ep_full.exe [1.2.2.8] - without any errors
- SOA pulled in all the clients
- Using JOBS > UNATTENDED DEPLOYMENT, I deployed the client to several Windows 7 Pro PCs - without any errors
- PCs DID NOT show up GREEN in the web-GUI and only showed up as disconnected
- Checked Windows Firewall settings to make sure communication wasn't faling there
- Realized the clients didn't have the correct setting so they could communicate with the server so I had to put that in manually via client-side-GUI > SETTINGS > TROUBLESHOOTING > SERVER NAME/IP
- Tried downloading avast_managed.exe from the web-GUI: SETTINGS > SETUP but it gives me a 404 error
- Realized the mirror job was failing and figured it wasn't building avast_managed.exe for me since the directory on the server is also empty
I hope I got everything....
Hi,
Try to download again the package,
becouse there's a new release of the ASOA console (now is 1.2.2.28) here
http://www.avast.com/download-software
Maybe there're some improvements and then can help you. ;)
-
I tried hitting the download page 2 hours ago but it was giving me 404 errors. I was hoping they were about to give us new files. Downloading it now. We'll see how this goes.
-
Hi,
try to locate it under
C:\Documents and Settings\All Users\application data\AVAST Software\Administration Console\mirror\Packages\admin.ini
or
try to search admin.ini with windows search using "search for hidden system files and folders" ;)
Just to clarify, you want me to do this on the server (SOA) side or on one of the clients?
Under the Server (where you've installed the console).
I tried hitting the download page 2 hours ago but it was giving me 404 errors. I was hoping they were about to give us new files. Downloading it now. We'll see how this goes.
I've received this update one hour ago.. ;)
edit:
with this update you must re-deploy the client protection (if you've set manual program update in the console)
New client endpoint protection version is 7.0.1455 (old one is 7.0.1438)
-
admin.ini now exists:
[Admin]
Product=abp
SilentInstallation=1
Connector=sbc
Path=%PRGFILES%\AVAST Software\Avast Business
ScheduleBoottimeScan=0
Reboot=Ask
[Common]
Edition=6
[Common.setupini]
NetAcc=1
NetIP=
NetPort=8080
NetUser=
NetPwd=
UseNTLM=0
[Common.ini]
SBCServerName=h1p-avast1.homenet.local
SBCServerPort=25322
[ExcludeGroups]
Mirror job now succeeds! Will need to redeploy the clients like I did before but, hopefully, it'll work. I'll keep ya'all posted.
-
Client says I'm on a trial license. Must I reinsert the license file I got a couple weeks ago?
-
Your admin.ini seems good,
Client says I'm on a trial license. Must I reinsert the license file I got a couple weeks ago?
Have you tryed to reboot the clients after deployment (suggested)?
-
Client says I'm on a trial license. Must I reinsert the license file I got a couple weeks ago?
Hold that thought..... It took a hot minute but this seems to have cleared up too.
-
Your admin.ini seems good,
Client says I'm on a trial license. Must I reinsert the license file I got a couple weeks ago?
Have you tryed to reboot the clients after deployment (suggested)?
Oh, they rebooted when I redeployed the client. They just took a few minutes to get caught up with the server (SOA).
-
They just took a few minutes to get caught up with the server (SOA).
Yes it's normal :)
-
If the license file is not working, email it to me at avast@advantage77.com
-
http://forum.avast.com/index.php?topic=101245.new#new
All new versions of SOA and AEA
-
Everything seems to be working as it should now. If I have any new issues, I'll be back or start a new thread.