System Requirements
Depending on the number of users in your environment, eControl can be installed on a Windows workstation, a shared server or on a dedicated system. eControl is not very CPU intensive and can co-exist quite nicely on an existing server. The most important factor in your choice of hardware will be to ensure eControl is running on a machine that can provide satisfactory up-time.
Server Requirements
A Windows operating system for the eControl proxy host is required because eControl uses the Win32 GroupWise Admin APIs to manage GroupWise information. These APIs are only available for Windows 32-bit platforms. Windows is also required because of Active Directory support. A single instance of eControl can be configured to manage multiple eDirectory trees and Active Directory Forests and Trees. eControl provides support for eDirectory, GroupWise, and NetMail running on NetWare, Open Enterprise Server, Windows or SUSE Linux and Active Directory and Exchange.
- Microsoft Windows 2000 Professional, Windows 2000 Server or Windows XP Professional are supported natively with eControl. To install eControl on Windows 2003 Server, you must add an empty GroupWise Secondary Domain on the server before eControl can be installed.
- If you are running GroupWise exclusively on SUSE Linux or OES Linux, a secondary GroupWise domain (without any users or other objects) is required to be installed on the eControl proxy host
- For Active Directory support, the eControl server can be installed on Windows 2000 or Windows 2003 Server. The destination Active Directory server must be installed on a Windows 2003 server
- To support Microsoft Exchange 2000 or 2003, the destination server must be running Active Directory on Windows 2003. There is no support for Exchange running on Windows NT.
- IIS 5 or IIS 6
- If you want to synchronise eDirectory password changes to GroupWise and Active Directory and Exchange, Universal Password is required
- A Security Certificate for SSL (optional for GroupWise and eDirectory)
- An "Enterprise Certificate Authority" installed on the Windows 2003 Active Directory domain that will be used to connect via LDAP (required for Active Directory and Exchange). Click here for information on how to install this certificate and how to request the certificate from your eControl station.
- TLS for LDAP encryption (optional)
- Microsoft Message Queuing (MSMQ - can be installed and configured at time of installation)
- Microsoft MSDE 2000 or MSSQL (if audit archiving or "Forgot Password" is required)
- Novell Netware Client 4.9 (if eDirectory support is required)
- GroupWise Client (if GroupWise support is required)
- MDAC 2.8 SP1
- ConsoleOne installed locally with required GroupWise and LDAP Snap-ins (for eDirectory and GroupWise systems)
- An internet connection to remotely manage the eControl Server using LogMeIn will be required to facilitate the remote installation process.
- There is no requirement for eDirectory or Active Directory services to be installed on the eControl server.
- eControl is virtualisation enabled.
eControl requires LDAP authentication to eDirectory running on the NetWare, Novell OES, Linux or Windows server or Active Directory that normally hosts directory services for your user environment. eDirectory or Active Directory DO NOT need to be installed on the eControl server.
- eDirectory 8.7+
- LDAP Version 3
- All versions of Active Directory
- GroupWise 5.5 EP, GroupWise 6.x, Groupwise 7.x
- Exchange 2000 and 2003
- NetMail
During the Remote Installation, we will add and configure the following:
- eControl Proxy Server and support software
- LDAP will be mapped to eDirectory or Active Directory values during the installation
- A Virtual IIS Root for eControl. You will need to determine what URL/DNS name will be used to allow users to connect to the eControl login page.
eControl User Account Management Solutions:
