AVG Setup

[protocolpcs]

My service company is starting to promote AVG products. I just purchased the new network version of AVG for a client and the setup process is not totally clear. I have read all the manuals, and although they do well in explaining the features and many modules involved, I can't find a very easy step by step setup instruction. I believe that keeping it simple is a great policy.
I bought a 50 user license and am trying to configure it on a Windows 2003 server. I must centrally manage all clients from the server and want all clients to update from the local server. I also want to install the clients from the server, and use some sort of template so that every client is setup the same way and that the user cannot disable or change any critical settings in the AVG program.
My biggest hang ups are what modules to install first, how to create the templates for remote installation of clients, what paths to install to, how to enter the correct paths in the TCP Server configuration, and where and how to store the updates on the server so the clients can get them automatically.
With your help, we can create a valuable resource for people using this software.

 

[franklin97355]

How far have you gotten? after you install the remote administration you will be able to set up the template and send it out to computers. If you have specific questions ask them here.

 

[protocolpcs]

The version should be the newest and is AVG Anti Virus 7.0.308 and AVGAdmin 7.1.308

The manuals from AVG give the process of installation and what the components do, but don't specifically tell you what settings to use or give real world examples of settings.
If I install the server components to E:\Grisoft, what should my settings be for the TCP Server program and the AVGInet Lite program? How and where do I setup the location for the update files? These type of questions are not covered in the AVG manuals, instead the manual just says to enter in this information. I don't know what the settings should be or the correct syntax for the paths.
I have installed all the components and have tried to configure them but still not sure of the correct specific settings to use for the TCP Server and AVGInet Lite programs.

 

[franklin97355]

For the TCP server you need to give it your license number and database path if it is not in the same directory as the server .exe file. I don't use AVGInet.

 

[protocolpcs]

The concern is with what could be entered into those fields, specifically, Local HTTP server root and HTTP server root and the actual directory on the hard drive. There is some issue with this being case sensitive. I am getting closer and the manual titled "Remote Administration Quick Guide" is the closest set of instructions that make practical sense that I have found. That manual showed me how to get the program up and working. I need to do more testing to learn how to manage the program now.

 

[LloydSev]

hrmm... i wonder why they don't have clear instructions on this setup...

Computer/Network Technician
CCNA

 

[protocolpcs]

I have been emailing the AVG tech support. All I can say is that they are not from the USA. Which means that they rush their answers and don't answer all your questions. If any one reading this thread is thinking about using AVG tech support, just ask one question at a time and choose your wording carefully. One tech said put a "tick" next to the server path. It took me awhile to figure out he meant a "check mark".
If any one has first hand knowledge of this program, please respond to this thread. I am still needing answers to installing on clients using AVGADMIN and the S-Tool.
Thank you.

 

[LloydSev]

I have the trials that I have not had time to monkey with.. maybe I'll install those and see what I come up with.

Computer/Network Technician
CCNA

 

[franklin97355]

We are running AVG here but your questions have been so general they are beyond answering. If you have SPECIFIC questions please ask them.

 

[protocolpcs]

I will try to be very specific. Right now I am trying to remotely install to a Windows XP Pro station from the Windows 2003 server using AVGADMIN and the S-Tool. I should have no problems but when I try a username and password box pops up and I can't get past it. I am putting in the correct username and password. All local users of the station have administrator right to the workstation. I have been logged on to the workstation as Administrator and as the only other profile. There are no firewalls on.
I am going crazy trying to figure this out. Grisoft tech support has not helped.
I need help.........Please HELP!

 

[franklin97355]

We ran into the same thing and I think the fix was to make sure file and printer sharing is on and if you have sp2 to put an exception in the firewall for AVG. I'll check Monday to see if I can find more info.

 

[protocolpcs]

I have AVGADMIN and all Grisoft products installed on E:\Grisoft. This is just a shared drive on the 2003 server. On my XP Pro stations I have made sure they are sharing something, that should mean that sharing is turned on, right? I have also made sure that XP firewall is turned off on the station.
The server is only a "file server". There is not a domain controller on our network. It's all a very simple setup. All users are setup on the server and given rights to the shared folders. The usernames and passwords match those of the station, of course. The user on the station has admin rights.
The AVG instructions say that on XP pro stations the AVGagent can be installed from the S-Tool as long as the user has administrator rights and you enter in the username and password from the S-Tool during remote installation. This is what I can't get past! So I manually installed AVGagent on the XP Pro station just as you would on a XP Home or 9x station. Then I went back to the server and the S-Tool and clicked install to that Pro station and it went on just fine, no password required. This is going to be bad if I have to install AVGagent on all my XP pro stations, I have a 50 users licence.
HELP!!

I also ran a test between two XP Pro stations isolated into a simple peer-to-peer network. Using one as the AVGDataCenter and the other as the station. I was able to remotelly install everything to the station after putting the stations username and password into the S-Tool. No problems and I didn't have to go to the station.

Does anyone have any clues? The reason I am trying to figure this out and not give up is because I would like to use this product on many networks. I hope Grisoft appriciates it. I don't want to go through this hassle anymore.

 

[s21825]

Well I have recently experienced similar problems with trying to perform a remote installation. I even managed to get avgagent installed and running on all the machines in our network (manually) but still could not get avg to install remotely. The avgadmin client was not able to detect avgagent running on the network computers. I believe you have to change some firewall settings on the client pc's in order for the avgagent to be able to communicate with the avgadmin. There is very little info on how avgagent works (what ports, etc) so I have tried added avgagent as an exemption to the windows firewall and that seems to be working. I don't know how you would do this remotely without administrator access though.

 

[wvedu]

I believe that Grisoft hails from Czech.
The college I work for has decided to go 100% AVG, (not a bad idea, make SysAdmin easier).

I recently experienced the same client remote install issues with no luck figuring it out. I probably wind up making an install CD / script with all the defaut setting I want, then handing it out for manual intalls.

The installation of the DataCenter and AvgAdmin went pretty smoothly. Grisoft has installation documentation that is not to bad (the english is rough at times and punctuation is bad but it works).

http://www.grisoft.com/doc/74/lng/us/tpl/tpl01

Look under the section: AVG 7.0 for Computer Networks

Hope this helps. And if someone figures out the remote install (without physically installing AvgAgent on every client) please post it.

Systems Administrator

 

[MrMayhem]

1. Use "DOMAIN\USER" for the user name.

2. Shut off all present anti virus and firewalls. I still havent resolved how to add excemptions in WinXP firewall.

Hope this helps...

/Bo

 

[MrMayhem]

Update: I managed to get the WinXP firewall to work with remote updates by adding all three avg-programs as excemptions PLUS adding manually C:\Windows\avgagent.exe

In total 4 excemptions.

/Bo

 

[SeeThru]

I never got remote install wotking properly....

I came in on a saturday and manually installed the lot from a network share.

Once installed, they all synchronise continiously from a folder on the server - I have the folder under ClientApps.

Works on a mix on 98, ME, 2000 and XP!

 

[cdallen]

Greetings,

I had a similar issue to the one described by protocolpcs. Although its probably been solved by now, the following appears to be something you may want to try. I found it in a FAQ on Grisoft's site:

--------------
The problem could be caused by insufficient access rights on target PC. For the remote installation it is required that target PC's local administrator's account is used to install AVG remotely, in domain networks it is recommended to use domain administrator account.

If the operating system of target PC is Windows XP, check following (and modify if it does not correspond):

Start->Settings->Control Panel-> Administrative tools->Local Security Policy-> Security settings -> Local Policies -> Security Options -> Network Access: sharing and security model Policy-> for local accounts

default value : local users authenticate as guests
new value : local users authenticate as themselves
--------------