2.2 Planning Your Aegis Environment

This section provides requirements, details of supported configurations, and other information necessary for planning your Aegis installation environment.

2.2.1 Determining Installation Type

The Aegis setup program does not require a license key for installation. By default, the setup program installs a fully functional installation with a trial license that allows you to evaluate Aegis for 30 days. After 30 days, Aegis provides a 30-day grace period, during which you see a notification of the grace period each time you log on to Aegis. The environment in which you install Aegis determines the installation type.

Trial Environment

You can evaluate Aegis in a “full trial” environment that meets production environment prerequisites or in a “proof of concept” environment that does not meet production standards. For more information about configuring a full trial environment, see Section 2.2.6, Supported Configurations.

Production Environment

When you deploy Aegis in your production environment, you can install the production license key in the Configuration Console immediately after installation or at any time during the 30-day trial period. For more information about obtaining license keys, contact your NetIQ sales representative.

Ensure you plan ahead for your production environment. Aegis supports taking a full trial environment to a production license key. However, Aegis does not support automated migration from a proof of concept environment to a production environment. If you wish to migrate from a proof of concept environment to a production environment, NetIQ recommends you install a new Aegis configuration in your production environment and use the export and import features in Aegis to manually migrate activity libraries and process customizations. For more information about configuring your production environment, see Section 2.2.6, Supported Configurations.

2.2.2 Licensing

Aegis requires a license key that allows you to use the product. The Aegis setup program automatically installs a trial license key that expires 30 days after installation, with an additional 30-day grace period.

After installation, you can add a production license key at any time during the 30-day trial. For more information about taking a trial licensed environment to a production license key, see Section 2.2.1, Determining Installation Type.

Use the Licenses list in the Configuration Console to manage the licenses in your Aegis environment.

Aegis supports the following types of production licenses:

Full License

Aegis allows you to create and run any number of processes in your production environment.

Per Process License

Aegis allows you to create any number of processes, but allows you to run only a specific number of processes in your production environment. The processes can be associated with multiple Aegis adapters.

Signed Process License

Aegis allows you to run signed processes from NetIQ in your production environment. Signed processes address specific needs, and do not affect the number of processes you can run with the Per Process license. You cannot modify signed processes.

For more information about obtaining license keys, contact your NetIQ sales representative.

2.2.3 Understanding Aegis Components

Aegis includes a number of software components that you should plan to install strategically over a number of computers. The following diagram displays a three-tier configuration in a non-cluster environment. For more information about supported configurations, see Section 2.2.6, Supported Configurations.

Aegis includes the following major components:

Operations Console

A Web-based user interface that accesses the Operations Web site on the Web Server computer. The Operations Console allows Process Operators to:

  • Monitor active work items and view their details

  • Investigate information from data sources and appended events

  • Provide remediation input

For more information about Process Operators and their responsibilities, see Section 4.1, Managing Users and Groups.

Configuration Console

A Windows-based user interface delivered to a user’s desktop using Microsoft ClickOnce publishing and deployment technology. The Configuration Console allows users to:

  • Configure Aegis

  • Create processes

  • Define assets

  • Specify user and group permissions

  • Provide email content for notifications

The Configuration Console also includes a built-in Workflow Designer, which Process Authors use to define the steps in a process. For more information about Process Authors and their responsibilities, see Section 4.1, Managing Users and Groups.

Reporting Center Console

A Windows-based reporting tool for Aegis installed locally for each user that runs reports. For more information, see the Reporting Guide for NetIQ Reporting Center.

NetIQ Aegis Business Services Layer (BSL)

A Web service that allows the Operations Console and the Configuration Console to communicate with the Aegis Server computer.

Reporting Center Web Service

A Web service that allows the Reporting Center Console to communicate with the Reporting Center database and retrieve report data from the Aegis and Resource Management databases.

Aegis Services

A set of services on the Aegis Server computer that manage the workflows in production.

  • The NetIQ Aegis Engine (Aegis Engine) receives events from adapters and sends them to the Correlation Engine for evaluation. After the evaluation, the Aegis Engine initiates work items from process workflows and executes workflow activities. This service depends on the NetIQ Aegis Namespace Provider (current or pre-2.2) and the NetIQ Resource Management Namespace Provider.

  • The NetIQ Aegis Correlation Engine (Correlation Engine) receives events from the Aegis Engine and determines whether the events match any triggers.

  • The NetIQ Aegis Activity Broker (Activity Broker) allows the Aegis Engine to execute workflow activities. This service depends on the NetIQ Aegis Namespace Provider (current or pre-2.2).

Providers

A set of components on the Aegis Server computer that facilitate communication with the databases for both the BSL and the Aegis services.

  • The NetIQ Aegis Namespace Provider communicates with the Aegis database and runs adapters. Core adapters implement base Aegis functionality, such as scheduled events and monitoring email accounts. Product adapters extend Aegis functionality by allowing Aegis to communicate with data sources, such as BMC Remedy and NetIQ AppManager. This version of the Aegis Namespace Provider is present in both cluster and non-cluster environments.

  • The NetIQ Aegis Namespace Provider (pre-2.2) communicates with the Aegis database and runs older versions of product adapters released prior to Aegis 2.2. This version of the Aegis Namespace Provider is not present in a cluster environment.

  • The NetIQ Resource Management Namespace Provider communicates with the Resource Management database to provide centralized access to the resource, user, and security data in Aegis.

Adapters

A set of components on the Aegis Server computer that facilitate communication between the Aegis Namespace Provider and data sources. For a complete list of Aegis adapters, see the Aegis support site available at http://support.netiq.com/aegis.

Aegis Database

Microsoft SQL Server database that stores all Aegis information, such as processes, work items, workflows, and supporting analysis.

Resource Management Database

Microsoft SQL Server database (display name: IQRM) that stores information needed to display resource data such as business services, users, and computers. It is typically installed on the Database Server computer with the Aegis and Reporting Center databases. You can install it on a separate Resource Management server computer if your environment has multiple NetIQ products that use the same Resource Management database.

Reporting Center Database

Microsoft SQL Server database that stores information the Reporting Center Console needs to display reports. It is typically installed on the Database Server computer with the Aegis and Resource Management databases. You can install it on a separate Reporting server computer if:

  • Your environment has multiple NetIQ products that use the same Reporting Center database.

  • You plan to use Aegis in a cluster environment. The Reporting Center database does not support clusters.

2.2.4 Restarting Aegis Services

The Aegis services need to start in a certain order. If you need to restart one or more Aegis services, use the following list to determine the order:

  1. NetIQ Resource Management Namespace Provider

  2. NetIQ Aegis Namespace Provider

  3. NetIQ Aegis Namespace Provider (pre-2.2)

  4. NetIQ Aegis Engine

  5. NetIQ Aegis Activity Broker

  6. NetIQ Aegis Correlation Engine

  7. NetIQ Aegis Business Services

2.2.5 Understanding Aegis Application Credentials

During the installation process, the Aegis Administrator specifies the default user account and password for the Aegis application credentials.

NOTE:The user account must be a member of the local Administrators group on the Aegis Server computer.

The Aegis application credentials allow Aegis to operate the following accounts:

Aegis Service Account

The account with which Aegis executes the following services on the Aegis Server computer:

  • Aegis Engine

  • Activity Broker

  • Aegis Namespace Provider

For best results, ensure the service account is a domain account. For more information about service account privileges, see Trusted Domains and Section 4.1.2, Understanding User and Group Synchronization.

Aegis Database Runtime Account

The account with which Aegis connects to the Aegis database at run time. This account can be one of the following:

  • A SQL-only account you specify during the installation process

  • The Aegis service account

During the installation process, the Aegis setup program associates the specified account with the db_owner role on the Aegis database.

Resource Management Account

The account with which Aegis adapters communicate with the Resource Management Namespace Provider.

Resource Management Database Runtime Account

The account with which Aegis connects to the Resource Management database at run time. This account can be one of the following:

  • A SQL-only account you specify during the installation process

  • The Resource Management account

During the installation process, the Aegis setup program associates the specified account with the db_owner role on the Resource Management database.

Default Aegis Administrator Account

The account the Aegis Administrator uses for the first Aegis logon. Aegis associates the account with the following Aegis groups:

  • Aegis Administrators

  • Aegis Users

For more information about the default Aegis groups, see Section 4.1.1, Default Groups.

After installation, you can modify the user account associated with the Aegis application credentials at any time. For more information about modifying the Aegis application credentials, see Section 3.7, Modifying Aegis Application Credentials.

2.2.6 Supported Configurations

NetIQ recommends you install Aegis strategically over multiple computers in one of the following configurations.

NOTE:

  • Installing all required components on one computer is not recommended.

  • Installing Aegis components on domain controllers is not recommended.

Two-Tier Configuration

In a two-tier configuration, you distribute Aegis components across two server computers.

Database Server Computer

Install the Aegis, Resource Management, and Reporting Center databases on one computer.

Combined Aegis Server/Web Server Computer

Install the Aegis services, the Aegis Namespace Provider, the Resource Management Namespace Provider, any Aegis adapters, the Operations Web site, the BSL, and the Reporting Center Web service on one computer.

Three-Tier Configuration

In a three-tier configuration, you distribute Aegis components across three server computers.

Database Server Computer

Install the Aegis, Resource Management, and Reporting Center databases on one computer.

Aegis Server Computer

Install the Aegis services, the Aegis Namespace Provider, the Resource Management Namespace Provider, and any Aegis adapters on one computer.

Web Server Computer

Install the Operations Web site, the BSL, and the Reporting Center Web service on one computer.

Four-Tier Configuration

In a four-tier configuration, you distribute Aegis and Resource Management components across four server computers. If you want to install Aegis in a cluster environment, you must install the Reporting Center database on a separate computer.

Database Server Computer

Install the Aegis and Reporting Center databases on one computer.

Resource Management Server Computer

Install the Resource Management database on one computer.

Aegis Server Computer

Install the Aegis services, the Aegis Namespace Provider, the Resource Management Namespace Provider, and any Aegis adapters on one computer.

Web Server Computer

Install the Operations Web site, the BSL, and the Reporting Center Web service on one computer.

The following diagram displays a four-tier configuration in a cluster environment.

After you determine the configuration you want to use in your environment and install the appropriate components on the server computers, install the Reporting Center Console on each computer where users will run reports.

For more information about installing Aegis components, see Section 2.4, Installing Aegis Components in a Non-Cluster Environment or Section 2.5, Installing Aegis Components in a Cluster Environment.

Firewall

If your environment requires a firewall between the BSL and the consoles, you must open an additional port in the firewall. If you want the BSL to use port 80 (443) to communicate with the consoles through a firewall, install the BSL on a separate computer from the Web Server computer. For more information about configuring the BSL to communicate through a firewall, contact NetIQ Technical Support.

Trusted Domains

You can configure a Windows domain to trust one or more domains. A trust passes account authentication from one domain to another, allowing easier access to computers, resources, and data across domains. Trusts directly influence domain security, because if even one domain in a trust contains a vulnerability, all domains in that trust are open to attack.

Aegis supports one-way and two-way trusts. To ensure Aegis can synchronize and display trusted domain account information in a one-way trust, the Aegis service account must be:

  • A member of the Administrators group on the Aegis Server computer

  • Able to perform Active Directory domain queries across all domains from which users can log on to Aegis

Specify the appropriate Aegis service account during the installation process for the Aegis Server components. For more information about the Aegis service account, see Section 2.2.5, Understanding Aegis Application Credentials. For more information about installing the Aegis Server components, see Section 2.2.12, Planning to Install Aegis Server Components. For more information about synchronization, see Section 4.1.2, Understanding User and Group Synchronization.

2.2.7 Planning to Install Aegis in a Cluster Environment

You can install all Aegis components except Reporting Center in a Microsoft Clustering Services cluster environment. If you want to install Aegis in a cluster environment, you must:

  • Create an Aegis-specific resource group for each cluster. A cluster resource group is not the same as a resource group in Aegis. For more information about resource groups in Aegis, see Section 5.1.1, Understanding Resource Groups.

  • Install the Reporting Center database on a separate computer.

For more information about the requirements for creating the Aegis resource group and installing Aegis components in a cluster environment, see the following sections:

For more information about setting up a Microsoft Clustering Services cluster environment, see the appropriate Microsoft documentation

2.2.8 Default Ports

Open the ports listed in the following table for proper communication between Aegis components.

Port Number

Component Computer

Port Use

2219

Aegis Server computer

Used by the NetIQ Aegis Namespace Provider to run adapters. For more information about how the NetIQ Aegis Namespace Provider interacts with adapters, see Section 2.2.3, Understanding Aegis Components.

2220

Aegis Server computer

Used by the NetIQ Aegis Namespace Provider (pre-2.2) to run adapters that were released prior to Aegis 2.2. For more information about how the NetIQ Aegis Namespace Provider (pre-2.2) interacts with adapters, see Section 2.2.3, Understanding Aegis Components.

9900

Aegis Server computer

Used by the Correlation Engine to communicate with the Aegis Engine and NetIQ Aegis Namespace Provider.

10117

Aegis Server computer

Used by the NetIQ Resource Management Namespace Provider. For more information about the NetIQ Resource Management Namespace Provider, see Section 2.2.3, Understanding Aegis Components.

1433

Database Server computer

Used by the Aegis and Resource Management databases to communicate with the NetIQ Aegis Namespace Provider and NetIQ Resource Management Namespace Provider.

NOTE:If your environment uses separate computers for the Aegis and Resource Management databases, ensure port 1433 is available on both computers.

8091 (TCP)

8092 (HTTP)

Web Server computer

Used by the BSL to communicate with the Operations Console and the Configuration Console.

80 (HTTP)

443 (HTTPS)

Web Server computer

Used by the Web Server computer to allow remote users to log on to the Operations Console. The Web Server computer uses port 80 by default.

2.2.9 Supported Languages and Locales

Aegis supports English language versions of the Microsoft Windows operating system in the following locales:

  • English

  • Spanish

  • German

  • Japanese

2.2.10 Planning to Install the Databases

This section provides requirements, recommendations, and configuration information for the Database Server computer. For the most recent information about third-party software requirements, see the Aegis support site available at http://support.netiq.com/aegis.

Typically, the Database Server computer hosts the following databases:

  • Aegis database

  • Resource Management database

  • Reporting Center Configuration database

If you plan to install in a cluster environment, you must install the Reporting Center Configuration database on a separate reporting server. For more information about installing Reporting Center on a separate server, see Section 2.2.11, Planning to Install Reporting Center in a Cluster.

The following table lists the requirements and recommendations for the Database Server computer:

NOTE:

  • If you plan to install the Resource Management database on a separate Resource Management server computer, use the following requirements for both the Database Server computer and the Resource Management server computer.

  • In a cluster environment, these requirements apply to each node in the cluster.

Category

Requirement

Processor

1.8 GHz Intel Pentium 4 server class with dual processor

Disk Space

Two drive configuration:

  • System drive: 60 GB free disk space

  • Data drive: 200 GB free disk space

Memory

4 GB

Operating System

One of the following:

  • Windows Server 2012

  • Windows Server 2008 R2

  • Windows Server 2008 Service Pack 2 or later (32- or 64-bit)

  • Windows Server 2012 R2

NOTE:If you install the databases remotely, the Aegis setup program does not validate the operating system on the remote computer.

Additional Software

  • One of the following:

    • Microsoft SQL Server 2012 (32- or 64-bit)

    • Microsoft SQL Server 2008 R2 (32- or 64-bit)

    • Microsoft SQL Server 2008 (32- or 64-bit)

    • Microsoft SQL Server 2005 Service Pack 2 or later (32- or 64-bit)

  • Microsoft SQL Server Native Client for the installed version of Microsoft SQL Server

  • Microsoft SQL Server Reporting Services for the installed version of Microsoft SQL Server (non-cluster environment only)

  • Windows PowerShell 2.0 (required only for a cluster environment)

NOTE:

  • Non-U.S. language versions of Microsoft SQL Server are not supported.

  • If you install the databases remotely, the Aegis setup program does not validate the version of Microsoft SQL Server on the remote computer.

Port

1433: Used by the Aegis Server computer and the Web Server computer to connect to the SQL Server databases.

For more information about the ports, see Section 2.2.8, Default Ports.

Resource Group Configuration

If you plan to install in a cluster environment, you must create an Aegis-specific resource group.

2.2.11 Planning to Install Reporting Center in a Cluster

Reporting Center does not support clusters. If you want to install Aegis in a cluster environment, you must install the Reporting Center database on a separate Reporting server computer.

In a cluster environment, the Reporting server computer hosts the following components:

  • Reporting Center Web service

  • Reporting Center Configuration database

For more information about the requirements for the Reporting server computer, see the Reporting Guide for NetIQ Reporting Center. For the most recent information about third-party software requirements, see the Aegis support site available at http://support.netiq.com/aegis.

2.2.12 Planning to Install Aegis Server Components

This section provides requirements, recommendations, and configuration information for the Aegis Server computer. For the most recent information about third-party software requirements, see the Aegis support site available at http://support.netiq.com/aegis.

Typically, the Aegis Server computer hosts the following components:

  • NetIQ Aegis Activity Broker service

  • NetIQ Aegis Correlation Engine service

  • NetIQ Aegis Engine service

  • NetIQ Aegis Namespace Provider

  • NetIQ Resource Management Namespace Provider

  • Aegis adapters

The following table lists the requirements and recommendations for the Aegis Server computer.

NOTE:

  • If you are installing Aegis in a two-tier configuration, ensure the computer where you want to install the combined Aegis Server and Web Server components meets the requirements for both. For more information about Web Server computer requirements, see Section 2.2.13, Planning to Install Web Server Components.

  • In a cluster environment, these requirements apply to each node in the cluster.

Category

Requirement

Processor

1.8 GHz Intel Pentium 4 server class with dual processor

Disk Space

Two drive configuration:

  • System drive: 60 GB free disk space

  • Data drive: 80 GB free disk space

Memory

4 GB

Operating System

One of the following:

  • Windows Server 2012

  • Windows Server 2008 R2

  • Windows Server 2008 Service Pack 2 or later (32- or 64-bit)

  • Windows Server 2012 R2

Additional Software

  • Microsoft Message Queuing 3.0, 4.0, 5.0, 6.0, or 6.3

  • Microsoft .NET Framework 2.0 (required for pre-3.2 activities)

  • Microsoft .NET Framework 4.0 *

  • Microsoft SQL Server Native Client for the version of Microsoft SQL Server installed on the Database Server computer

  • Windows PowerShell 2.0 **

* The Aegis Server components do not use Microsoft .NET Framework 3.x, but .NET Framework 3.x and 4.x can coexist on the Aegis Server computer.

** The Aegis Server components do not use Windows PowerShell 3.0, but PowerShell 2.0 and 3.0 can coexist on the Aegis Server computer.

Ports

2219: Used by the NetIQ Aegis Namespace Provider to communicate with the Aegis database and run Aegis adapters.

2220: Used by the NetIQ Aegis Namespace Provider (pre-2.2) to run older versions of Aegis adapters that do not support clusters.

10117: Used by the NetIQ Resource Management Namespace Provider.

For more information about the ports, see Section 2.2.8, Default Ports.

Resource Group Configuration

If you plan to install in a cluster environment, you must create an Aegis-specific resource group by clustering Microsoft Message Queuing 3.0, 4.0, 5.0, or 6.0. For more information about clustering Microsoft Message Queuing, see Section 2.5.3, Clustering Microsoft Message Queuing on the Aegis Server Computer.

2.2.13 Planning to Install Web Server Components

This section provides requirements, recommendations, and configuration information for the Web Server computer. For the most recent information about third-party software requirements, see the Aegis support site available at http://support.netiq.com/aegis.

Group Policy Settings

Before installing the Web Server components, ensure you configure the Group Policy security settings on the Web Server computer to allow anonymous access.

Web Server Computer Requirements

Typically, the Web Server computer hosts the following components:

  • Operations Web site

  • BSL

  • Reporting Center Web service

If you plan to install in a cluster environment, you must install the Reporting Center Web service on a separate reporting server. For more information about installing Reporting Center on a separate server, see Section 2.2.11, Planning to Install Reporting Center in a Cluster.

The following table lists the requirements and recommendations for the Web Server computer:

NOTE:

  • If you are installing Aegis in a two-tier configuration, ensure the computer where you want to install the combined Aegis Server and Web Server components meets the requirements for both. For more information about Aegis Server computer requirements, see Section 2.2.12, Planning to Install Aegis Server Components.

  • In a cluster environment, these requirements apply to each node in the cluster.

  • Do not configure Network Load Balancing (NLB) on your Web Server cluster.

WARNING:When you configure Microsoft Internet Information Services (IIS) in a cluster environment, do not use the Shared Configuration option.

Category

Requirement

Processor

1.8 GHz Intel Pentium 4 server class with dual processor

Disk Space

60 GB free disk space

Memory

4 GB

Operating System

One of the following:

  • Windows Server 2012

  • Windows Server 2008 R2

  • Windows Server 2008 Service Pack 2 or later (32- or 64-bit)

  • Windows Server 2012 R2

Additional Software

  • Microsoft Internet Information Services 6, 7, 7.5, 8, or 8.5 *

  • One of the following versions of Microsoft ASP.NET:

    • If you are running IIS 6 or 7.x, ASP.NET 2.0, 3.0, or 3.5

    • If you are running IIS 8.x, ASP.NET 4.0 or 4.5

  • Microsoft .NET Framework 2.0 (for Reporting Center Web service only)

  • Microsoft .NET Framework 4.0 (required for all other components)

  • Windows PowerShell 2.0 (required only for a cluster environment)

* If you install IIS 7.x or 8.x, you must enable IIS 6 compatibility mode.

Ports

8091 and 8092: Used by the BSL to communicate with the Operations Console and the Configuration Console.

80 or 443: Used by the Web Server computer to allow remote users to log on to the Operations Console using HTTP or HTTPS.

For more information about the ports, see Section 2.2.8, Default Ports.

Resource Group Configuration

If you plan to install in a cluster environment, you must create an Aegis-specific resource group.

Operations Console Web Browser Computer Requirements

The following table lists the requirements and recommendations for each computer where users launch a Web browser to log on to the Operations Console.

Category

Requirement

Operating System

One of the following operating systems:

  • Windows 8.1 (32- or 64-bit)

  • Windows 8 (32- or 64-bit)

  • Windows 7 (32- or 64-bit)

  • Windows Server 2008 R2

  • Windows Server 2008 Service Pack 2 or later (32- or 64-bit)

  • Windows Vista (32- or 64-bit)

  • Windows XP Service Pack 2 or later (32- or 64-bit)

Additional Software

Any of the following browsers:

  • Microsoft Internet Explorer 8, 9, 10, or 11

  • Google Chrome *

  • Apple Safari *

  • Mozilla Firefox *

  • Opera *

* For best results, ensure you are using the latest version of this browser.

Securing Your Aegis Environment

Aegis encrypts and authenticates all communication between the consoles, the BSL, the Aegis Server computer, and the databases. However, to secure communication between the Operations Console and the Web Server computer, you must use Secure Sockets Layer (SSL) for all Web Server computers in your Aegis environment. Otherwise, any person using a sniffer on your network could access passwords and other privileged information.

NOTE:In a cluster environment, ensure you import a certificate from a .pfx file instead of generating a temporary self-signed certificate. If you generate a temporary self-signed certificate on the node where you install the Web Server components, the certificate is available only on that node. The certificate is not available to the other nodes in the cluster.

For information about configuring SSL in Microsoft Certificate Services and in Microsoft Internet Information Services (IIS), see the Microsoft documentation.

Aegis uses the following technologies to secure your Web Server computer:

  • ASP.NET security provides application-level security for the Web Server computer. You can lock down the server using best practices for ASP.NET security.

  • Security features in IIS control access to the Web Server computer virtual directory.

  • The BSL authenticates connections between the Operations Console and an Aegis Server instance.

2.2.14 Planning to Install the Reporting Center Console

Install the Reporting Center Console on each computer where users will run Aegis reports. For more information about the requirements for the Reporting Center computer, see the Reporting Guide for NetIQ Reporting Center. For the most recent information about third-party software requirements, see the Aegis support site available at http://support.netiq.com/aegis.

2.2.15 Planning to Install the Configuration Console

This section provides requirements, recommendations, and configuration information for each Configuration Console computer. For the most recent information about third-party software requirements, see the Aegis support site available at http://support.netiq.com/aegis.

NOTE:If your environment does not support the default ClickOnce deployment, you can install the Configuration Console locally for all Aegis Administrators and Process Authors. For more information about installing the Configuration Console locally, see Section 2.8, Installing the Configuration Console Locally. For more information about installing the Configuration Console using ClickOnce deployment, see Section 3.10, Starting the Configuration Console the First Time.

The following table lists the requirements and recommendations for each Configuration Console computer.

Category

Requirement

Operating System

One of the following operating systems:

  • Windows 8.1 (32- or 64-bit)

  • Windows 8 (32- or 64-bit)

  • Windows 7 (32- or 64-bit)

  • Windows Server 2008 R2

  • Windows Server 2008 Service Pack 2 (32- or 64-bit)

  • Windows Vista (32- or 64-bit)

  • Windows XP Service Pack 2 or later (32- or 64-bit)

Additional Software

Microsoft .NET Framework 4.0, 4.5, or 4.5.1

2.2.16 Planning to Install the Aegis Event Generator

This section provides requirements for each computer where you want to install the Aegis Event Generator. By default, the Aegis setup program installs the Aegis Event Generator on the Aegis Server computer. You can also install it on a remote computer. The Aegis setup program installs the Aegis Event Generator in the C:\Program Files\NetIQ\Aegis\IQConnect73\bin folder.

For the most recent information about third-party software requirements, see the Aegis support site available at http://support.netiq.com/aegis.

The following table lists the requirements and recommendations for each computer where you install the Aegis Event Generator.

Category

Requirement

Operating System

One of the following operating systems:

  • Windows Server 2012

  • Windows Server 2008 R2

  • Windows Server 2008 Service Pack 2 or later (32- or 64-bit)

Additional Software

Microsoft .NET Framework 3.0 or 3.5

NOTE:The Aegis Event Generator does not use Microsoft .NET Framework 4.0 or 4.5, but .NET Framework 3.x and 4.x can coexist on the same computer.