I have a license for 50 computers. For simplicity sake lets say 40 are here in our corporate office and 10 are remote locations. The computers here in corporate are behind the firewall, have addional security so don't need all the features. The other 10 do. I want to be able to make two different settings files so that the one group has one set of settings and the other group has another.
Previously I had this done, but our server with the ADMIN console crashed and I had to reinstall the admin console. Now I can't seem to figure out how to accomplish this. I've been told you can't have different settings for different groups any more. I've also been told that adding 'remote' locations where they will be coming in through an external IP to update settings and everything will slow down the corporate office. This both seems a little strange to me.
Can someone help me out and tell me if I can have seperate settings files and if, infact putting external loctions updating via the server is going to slow everyone down. I can't montior them if they aren't linked in which is the whole point of a central console.
Apologies that no one has replied to your post yet. It is possible to create different settings for different groups in the Admin Console. The way the AVG Remote Administration works is 'Shared Settings for Stations' have a higher priority than 'Shared Group Settings', so anything mandatory in 'Shared Settings for Stations' cannot be configured in Group Settings.
To set up different groups:
- On the left handside of the Admin Console > Right click 'New Stations' > New Group
- Give the group a name and tick the 'do not inherit shared settings for stations in this group' if you don't want shared settings taking priority over the group settings
- Once the group has been created you can manually configure the shared group settings or import a configuration file from a workstation that will belong to the group
- Drag and drop stations into the group to add them (or right click 'Add to group')
It really is network dependant whether any slowdown will occur. If there are no issues then there is nothing to worry about. One thing you may want to consider is installing an Admin Server to distribute updates on the second site but still be managed via the one Admin Console.