Installation Guide to SOA + Endpoint Protection Suite

[Che Johnson]

Installation Guide to SOA + Endpoint Protection Suite

Hello and thank you for your participating in our avast! Free for EDU program.  We have made most of our avast! antivirus products and solutions free for use by schools and libraries in the US. This is just the first step and if it is successful, we will extend it worldwide. We are doing this for a couple of reasons. First, even though schools need security products, in these tough budget times, they need the ability to focus their spending on teaching. We know that schools spend a lot on security—money that could be better spent on teaching.  Please feel free to discuss your opinions and/or possible issues with other users in this forum/thread.

NOTE: The SOA console does NOT have to be installed on the server, and does not use conventional SQL (it uses an embedded SQL lite). Ours is running on a XP SP3 box (very light).  You may push a deployment from the console for a domain. Workgroups will not deploy, so installs either occur from users or Administrators. SOA is limited to 200 users (300 users if you use go ahead and use SQL Express 2008 R2, but this is not usually recommended)


For user guides and FAQs please refer to:

1. avast! Endpoint Protection

SOA Installation Guide - http://www.avast.com/FAQ/AVKB76

SOA User Manual - http://files.avast.com/files/documentation/small-office-administration-console-user-guide.pdf

SOA with Mirror Console + Client Download -http://files.avast.com/iavs5x/setup_console_eps_full.exe

SOA Administrator Manual - http://files.avast.com/files/documentation/soa-administrators-guide.pdf

Endpoint Protection Suite Stand Alone Client - http://files.avast.com/iavs5x/setup_av_eps.exe

Endpoint Protection User Guides - http://www.avast.com/download-documentation#business-products

Endpoint Protection FAQ - hhttp://www.avast.com/FAQ/AVKB79


For user guides and FAQs please refer to:

1. avast! Endpoint Protection

SOA Installation Guide - http://support.avast.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=1290

SOA User Manual - http://files.avast.com/files/documentation/small-office-administration-console-user-guide.pdf

SOA with Mirror Console + Client Download - http://files.avast.com/iavs5x/setup_console_eps_full.exe

SOA Administrator Manual - http://files.avast.com/files/documentation/soa-administrators-guide.pdf

Endpoint Protection Suite Stand Alone Client - http://files.avast.com/iavs5x/setup_av_eps.exe

Endpoint Protection User Guides - http://www.avast.com/download-documentation#business-products

Endpoint Protection FAQ - https://support.avast.com/index.php?languageid=1&group=eng&_m=knowledgebase&_a=viewarticle&kbarticleid=1291


Helpful Information

NOTE: The SOA console does NOT have to be installed on the server, and does not use conventional SQL (it uses an embedded SQL lite).  You may push a deployment from the console for a domain. Workgroups will not deploy, so installs either occur from users or administrators. SOA is limited to 200 users (Possibly 300 users if you use go ahead and use SQL Express 2008 R2, but this is not usually recommended)

Service Port Numbers

1. Please make sure the ports listed below are opened in the network on both the client and server side (you can use the GPO to dispatch on all machines, and make sure to reboot the machines for the changes to be applied).  avast! Small Office Administration uses the following ports:

Port for Console: 8731

Secure Port for Console: 8732

Port for Client: 25322

2. Do a discovery task to find all the machines

3. Modify the deployment package for each type of system deployment: Desktop, server, or SharePoint server. NOTE: There is only a single deployment package in SOA

Create a deployment package for each type of OS (Desktop, server)

File Servers

For servers, I will recommend to modify the components of the deployment package (create a light installation package for servers OS’s) which consists of the File System Shield only. This is usually the only real protection required for file servers and this is an industry standard best practice. This assumes that the File Server not being used as a workstation. NOTE: DO NOT use the Network Shield on servers.   SharePoint servers should add the SharePoint shield in addition to the File System Shield.  If servers are to be managed (see below), then each server type will require its own group, separate from the managed client group. If servers are NOT to be managed, then use the custom install feature to select the correct shield/shields for that server type.

Workstations

For desktop installation, I recommend to remove all the server protection modules from the deployment components, so they are not installed on the client. Note: When creating an installation package please be sure to select the server name / address in the installation package for the clients to communicate with the console after deployment.

Workstations

For desktop installation, I recommend to remove all the server protection modules from the deployment components, so they are not installed on the client. Note: When creating an installation package please be sure to select the server name / address in the installation package for the clients to communicate with the console after deployment. It is best to have the system hosting the SOA console to use a fixed IP vs. DNS name.  This will eliminate DNS issues during deployment.

 4. Start to deploy by group of 10-20 machines at once, make sure to enable the “Reboot the machine” option in the deployment task settings (this is necessary to finalize the installation process). **Important** – Before sending out an installation please be sure the mirror is up to date which you can check by going to view tab in the console and check mirror status. Once it’s up to date then you can send out the installation. (NOTE: SOA can be installed with or without mirror)

 5. After you send out an installation you may received an error code 0×00000005 which usually means access denied. This is also due when you don’t reboot the client after the initial installation so please do so and then refresh the Console. Also be sure to use the network administrative passwords or a password with full administrative rights to push the client through the network (Domain/Administrator) NOTE: All systems MUST be rebooted after deployment, so plan accordingly.

6. If you find that when you deploy some of your clients license change or remain in the trial mode please check to be sure you’re not over your license count in which case you will have a “KEY” icon over the PC. Please note the total sum of your license count is Computers with Agent + Computers without Agent = License Count. So if you have old clients in the Active Directory that will not receive the installation package, please delete them from your lists and this should resolve your issue.

7. If you find that you will be over your estimated license count or current license please contact us for remedy.

NOTE: When you are deploying, Enable the Admin Shares. Windows XP systems should have File/Printer sharing DISABLED. Windows 7/Vista systems should have File/Printer sharing ENABLED

WORKGROUP VS ACTIVE DIRECTORY

You may push a deployment from the console for a domain. Workgroups will not deploy, so installs either occur from users or Administrators.

ACTIVE DIRECTORY

If using Active Directory you can easily create an installation package to push the client remotely through the network with Network Administrator password and in the Deploying Group. The Endpoint client will remove existing installation of avast! 4 only.  Any other avast! version or other anti-virus should be un-installed prior to Endpoint deployment.

WORKGROUP

If using a Workgroup you can only DEPLOY remotely (no push deployments from your console)  We recommend to create the installation package manually and send it via email to each client or install it separately via USB Flash disk to manually install it on each client. Once the client has been installed only then will it be detected in the Console.  The Endpoint client will remove existing installation of avast! 4 only.  Any other avast! version or other anti-virus should be un-installed prior to Endpoint deployment.

NOTE: Windows File and Printer Sharing must be enabled so avast! can create the necessary directories!  ALSO, all systems need to be rebooted after installation, so plan accordingly!

Note: Please note the EDU program does not include ticketed support and all matters should try to be resolved using the free Forum and Knowledgebase. There will be some NEW EDU support packages available so if interested, please let us know and we will provide you with further details.

You can contact edu support at edu-support@avast.com

Kind Regards
Che' Johnson
avast! EDU Moderator

[SecTech]

Hello, setting up three servers here.  I would like to know if I need a SQL db per server, or if I could have a deticated SQL server and use it for all three EAS servers.
Thanks

[Che Johnson]

Hello SecTech,

We do recommend using a full SQL db 2008 R2 per EAS Server.   But this should only be done using the EA Console in which case the SOA is not recommended to use as there are no EAS Servers for the SOA.

[sandip13]

Hello, setting up three servers here.  I would like to know if I need a SQL db per server, or if I could have a deticated SQL server and use it for all three EAS servers.
Thanks

[Che Johnson]

Hello, we recommend a full SQL per EAS Server and not 1 for all 3.