Chapter 2 - Installation

 

Applies to: Microsoft Antigen

This release of the Antigen Enterprise Manager supports local installs on Microsoft Windows 2003 Server.

Note

The AEM cannot be installed on a server that is used as a Domain Controller.

AEM’s setup wizards can be used to install the product to a local Windows 2003 Server. Prior to installation, you will need to know the Administrator Account and Password for the machine on which the AEM is being installed.

System Requirements

Minimum Server Requirements

  • Windows 2003
  • 128 MB of available memory
  • 183 MB of available disk space for pre-requisites listed below
  • 65 MB of available disk space for the AEM

Pre-requisites

  • IIS 5.0 or higher
  • .net Runtime v. 1.1mory
  • ASP.net v. 1.1
  • Microsoft Message Queue and MSMQ Triggers
  • MSDE 2000 or SQL Server 2000
  • Microsoft Internet Explorer 5.5 or higher

If you are going to do an Enterprise Installation (which stores the AEM databases on an existing SQL Server), before starting the installation you must:

  • Create two databases:
    SybariEnterpriseManager
    SybariEnterpriseManagerReports
  • Know the name of the SQL Server to be accessed.
  • Know the domain in which SQL and AEM are located (if you will be using Windows Integrated Security to connect to a remote SQL server).
  • Know a username and password (for SQL or Windows Authentication).

Important

The specified user must have been granted access to both the AntigenEnterpriseManager and AntigenEnterpriseManagerReports databases and have db_owner permission.

Installing

To begin the installation procedure, run SETUP.EXE from the directory containing the AEM installation files. Follow the steps below to complete the installation:

  1. The Install Wizard will first check for the required system components. If the Install Wizard believes any system components are missing, it offers to install them for you. Click Yes to have the Install Wizard install missing components or No if you prefer to install the components manually. If no components are missing, this step is skipped.

    Note

    IIS is an install prerequisite, however, for security reasons it must be installed and patched manually by an administrator.

  2. Select the type of installation:

    • Express Installation – uses the MS SQL Server 2000 Desktop Engine (MSDE) and installs its own instance of SQL Server on the local machine. The installation continues with the steps at Express Installation, below.
    • Enterprise Installation – uses an existing SQL Server. The installation (which has prerequisites, see System Requirements above) continues with the steps at Enterprise Installation, below. Important: If you are running SQL Server 2005, you must choose the Express install mode (MSDE) because the AEM is incompatible with SQL 2005.

Express Installation

The Express Installation process continues as follows:

  1. Modify User Information, if necessary. Click Next.
  2. Modify the install destination folder, if necessary. Click Next.
  3. Click Install to begin the installation. The install status is displayed.
  4. Click Finish when the installation is complete.

Enterprise Installation

The Enterprise Installation process continues as follows:

  1. Indicate the following:
    • Authentication Method—Specify whether to use Windows Integrated Security or SQL Authentication. Your SQL Server Administrator will be able to tell you how the system was set up. If the wrong Authentication type is selected, the install will fail to log on.

      Note

      If you are using Windows Integrated Security with a remote server, the AEM Server requires credentials accessible to both AEM and the remote SQL machine. This is only supported using AEM & SQL in a domain/Active Directory environment.

    • Server—The local or remote SQL server to install to. The list will display all the SQL Servers that could be discovered in the client’s environment. You are not limited to the entries in this list; you may enter a different server name.

    • Domain—This field can be ignored if you are using a local SQL server with integrated security and a local account, or if you are using SQL authentication. If you are using Windows Integrated Security to connect to a remote SQL server, enter the domain in which SQL and AEM are located. Enter the Domain Name, not a fully-qualified domain.

    • User—Enter the name of the user with access to the SQL repository.

      Note

      This user will automatically be added to the AEM database user list, but it will not be included in the list of users displayed in the AEM console to prevent anyone from deleting it.

    • Password—Enter that user’s password.

    • Test Logon—After providing the necessary credentials, you may test the logon using the Test Logon button (provided you have ‘logon as batch’ rights).

  2. Specify the target databases in the SQL Server. These are the databases created by your SQL Administrator prior to the AEM install (see above). The default values for these databases are “SybariEnterpriseManager” and “SybariEnterpriseManagerReports.” You may confirm database access to the remote server by clicking both Check Database buttons (provided you have ‘logon as batch’ rights).
  3. Modify User Information, if necessary.
  4. Modify the Destination Folder for the install, if necessary.
  5. Click Install to begin the installation. The install status is displayed.
  6. Click Finish when the installation is complete.

Uninstalling

To uninstall AEM, you may either use the Windows Add/Remove Programs function or run setup.exe and select the Remove option. Follow the on-screen instructions to complete the removal process.

Regardless of the method you use, you will be asked the following question:

“Would you like to delete the AEM database information and revoke associated login rights?” Select Yes or No.

Microsoft suggests deleting old AEM databases when removing the product. If they are left in place, any new AEM installations will attempt to connect to the old databases. The administrator will be asked to confirm a connection to an old database, because if the old database is corrupted or was created with a different version of AEM, it may not function properly.

Restoring AEM after a System Failure

To restore AEM after a system failure, restore your SQL or MSDE database first and then reinstall AEM by following the appropriate installation procedure for your environment. During the AEM reinstallation you will be prompted to connect to an existing database; select the restored SQL or MSDE database.

For more information on backing up and restoring SQL and MSDE databases, see the following articles.

Disaster Recovery Planning for SQL Server

Disaster Recovery Articles for Microsoft SQL Server

Recovery Planning for Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) Databases