i got a test computer to install avg administrator, the test machine is on the domain but i install it on the local machine is that the problem
I think so, if I'm understanding your setup correctly.
For the remote installer wizard ("C:\%Program Files%\AVG\AVG9 Admin\Console\AVG9NetworkInstaller.exe") to work properly in a workgroup environment, you have to run it with an account that is a member of the local administrators group on the end users machine. But in that case, you still somehow need to create firewall exceptions for remote management, and/or turn the firewall off.
Is this a freshly installed windows machine that hasn't been joined to a domain? In that case, I think by default now, microsoft block remote management, pretty much anything over tcp/udp for RPC DCOM. (which is good policy, but means a bit of extra setup by an admin before it can be administered).
Have a look at this avg KB article: http://www.avg.com/ww-en/kb.num-2099.pnuid-1255095004
. The first answer 1990 lists the ports required by the remote installer to work:
1. Ping (ICMP type 0 - Incoming echo request) - required to find a remote station in the network.
2. Microsoft Files and Printers Sharing (TCP ports 139, 445 and UDP ports 137,138) - required to copy AvgAgent tool on the remote computer using Admin$ sharing.
3. RPC: Remote Procedure Call (TCP and UDP port 135) - required to launch AvgAgent service on the target PC.
4. Communication on TCP port number 6150 for AVG Network Installer Wizard and AvgAgent common communication. Using this port AVG Network Installer Wizard controls the AvgAgent tool and uploads the installation files of AVG onto the target station.
You'd need to create exceptions for each of these in the firewall. May be easier to get them to temporarily disable the firewall.
If you've got a version of avg that includes a firewall it can replace the windows one as part of the installation, so you may not even have to worry about them not reenabling the windows firewall after you install?