Planning Your eControl 3 Environment


(1) eControl 3 Installation and Setup Guide > Planning Your eControl 3 Environment

eControl 3 integrates into a large number of systems using a wide variety of different programming interface (API) to communicate with each system. Since many of the API's required for eControl to manage and communicate with these systems, the Windows platform is required for the eControl server itself.

Planning the eControl Environment
Typical eControl Scenarios
Standard eControl Installation

Planning the eControl Environment

eControl integrates into a large number of systems using a wide variety of different programming interfaces (APIs) to communicate with each system. Windows is the required operating system for eControl because many of the APIs required to manage and provision user accounts in Novell-only, Microsoft-only and mixed and multiple GroupWise, eDirectory, Active Directory and Exchange environments are only available on the Windows platform.

Typical eControl Scenarios

eControl for Active Directory & Exchange Environments

There are three typical eControl scenarios:

eControl managing Active Directory only:
- "Domain Controller" - must be configured to support SSL LDAP authentication to support creating and changing user account passwords.
- "Active Directory Domain" - must be configured with an eControl master service account.
- "eControl Server" - a Windows 2003 or 2008 server that will host the eControl website:
  - Windows server that meets system requirements
  - Installation of eControl
  - Configure Active Directory Connections
  - License the eControl installation

eControl managing Active Directory with Home Directories - All requirements for "eControl managing Active Directory only" and add:
- "Home Directory Servers" - must be configured to support WMI so that user home directories can be created, managed and deleted.
- "eControl Server" - IIS must be configured to support WMI connections to remote Home Directroy servers. Active Directory connections "WMI" settings must be configured.

eControl managing Active Directory with Exchange - All requirements for "eControl managing Active Directory only" and add:
- "eControl Server" - Exchange connections must be added/configured in Riva. Existing Active Directory connection "Remote Agent" settings must be configured.
- "eControl Connection Agent" - eControl must be installed and then properly configured on the Exchange server that the eControl host server will connect to.
- "Domain Controller" - must have Exchange Management Tools installed.

eControl for eDirectory & GroupWise Environments

There are two typical eControl scenarios:

eControl managing eDirectory only - eControl is installed on:
- "eControl Server" - a Windows system that will host the eControl website
  - Windows 2003 or 2008 server or Windows XP Pro workstation that meets system requirements
  - Novell client installed
- "eDirectory" - must be configured with an eControl service account.
- "Home Directory Servers" - eControl can only manage user home directories hosted on NSS volumes (NetWare or Linux).

eControl managing eDirectory and GroupWise- All requirements for "eControl managing eDirectory only" and add:
- "eControl Server" - a Windows system that will host the eControl website. GroupWise client must be installed, or if GroupWise system is running on another Windows server, or on Linux (non-NSS volumes) then install a secondary domain on this server.

Other eControl Scenarios

eControl managing a mix of Active Directory and eDirectory, and Exchange and GroupWise - combination of the first two scenarios above.

Upgrade of an existing eControl 2.5 environment - upgrade to eControl 3.0 first before upgrading to the latest eControl release. The environment must be built to the same planning requirements as the scenarios above.