The package

The Ad-Aware Enterprise installer package consists of two parts: 

1. The main installer to be installed on the server/monitoring computer 
2. A client installer in msi-format to be rolled out to client computers. The client installer is embedded in the Ad-Aware enterprise installer.

1. Installing the server

Start by installing the main package on the server/monitoring computer. During the installation it copies the client installer to the installation directory. It will also be visible in the start menu as “Client Installer Package".

2 Installing the client

This can be done in several ways

A. Using a central login script of some sort

Copy Norman_AAW_Ent_Client_1.9.4.1.msi to a shared resource that is available for all users.

Add the following line in the login script (written as a one line command):

msiexec /i "Norman_AAW_Ent_Client_1.9.4.1.msi" /quiet /qn /norestart
   SERVER_PORT=10020 SERVER_HOST=<nameofSERVER>

For more installation parameters, type msiexec in a command line window.

You can modify default values using any of these command line switches.

Parameter	Description	Default Value
INSTALLDIR	Path where Ad-Aware SE Enterprise Client part is installed	C:Program FilesNormanAd-Aware SE Enterprise Client
SERVER_PORT	TCP port for Server Service to get information from Client Service	10020
CLIENT_PORT	TCP port the Client Service listens to for invokes from Server Service	10010
SERVER_HOST	Hostname or IP address of the Server Computer on which the Server Service is installed	‘null’ * compulsory when installing remotely

Special measures have to be taken if the user logging on is not a local administrator.

B. Using the Microsoft built-in distribution method in Active Directory

Add Norman_AAW_Ent_Client_1.9.4.1.msi to the domain’s Local Computer Policy.
Local Computer Policy ensures one installation per computer rather than one installation per user. Remember, the package needs to be applied, not just announced.

Copy the Norman Ad-Aware Enterprise MSI package (download from this page, requiers username and password received when purchasing the product) to a network share e.g. msi_soft. Be sure to grant read access to the Everyone group and not user groups, because computer accounts have to access the share too. Likewise - grant read & execute permissions on the specific .msi-file - if you do not, the assignment will not work.

On your domain controller open “Active Directory Users and Computers".

Create a new Organizational Unit for your computer accounts, e.g. SoftDeploy by right clicking on your domain and selecting New, then Organizational Unit.

Move the computer accounts to which you want to deploy Norman Ad-Aware into this Organizational Unit.

Right click the created Organizational Unit SoftDeploy and select Properties.

In the Properties of SoftDeploy window switch to the Group Policy tab.

Click on New, name it e.g. naa_install.

Double-click naa_install, expand the tree under Computer Configuration, expand Software settings, right-click Software installation and select New, then Package....

Browse to the network share msi_soft and select the msi file (Norman_AAW_Ent_Client_1.9.4.1.msi) and click open. Check Assigned and click OK.

Close the Active Directory Users and Computers window. Restart the client machine to which you to install Norman Ad-Aware.

The settings need to be applied in a transform file (.mst) or using the login script to distribute the registry settings.

This is what such registry modification file could look like:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Lavasoft\Ad-Aware Enterprise Client]
"PortNo"="10010"
"ServerPortNo"="10020"
"ServerHost"=\\<SERVERNAME>

This file should be saved as a .reg file and placed in the login script or distributed in other ways to ensure all computers have these settings and not others. Command line: regedit /s <name>.reg

Special measures have to be taken if the user logging on is not a local administrator.

Managing Norman Ad-Aware installations from the console

Start Ad-Aware Management Console on the monitor computer. Make sure the Ad-Aware Enterprise Client service is started. You can see whether or not the service is started from the Server Control section. If you select Client Control, all clients reporting to your server should appear in the list. Click the client you want to check status for or start a scan on.

The client informs its specified server of its existence using TCP. This is done to ensure flexibility and platform independence. Port numbers in use are 10020(server) and 10010(client). If you have a firewall enabled (typically windows firewall) these ports must not be blocked. If they are, the remote control will not work.

Please refer to the manual and our FAQ for further details on administration and configuration.