Checking Prerequisites and System Requirements

Note: Version 6.0.0 of Good Mobile Messaging Client has been tested with and is supported by the two previous versions of Good Mobile Messaging Server (5.0 SR1 and SR2). Version 6.0.0 of Good Mobile Messaging Server has been tested with and supports the two previous versions of Good Mobile Messaging Client (5.0 SR2 and SR3). Client version 4.9 is not supported in the 6.0 release. (http://www.good.com/corp/int_support.php?id=502&pid=497)

Ensure that the Good Messaging Server and Good Administration Center Server host machines, and your Exchange server, conform to the following prerequisites. Good Messaging Server and Good Administration Center Server can run on the same host machine, but cannot run on the same host machine as Microsoft Exchange Server. For environments serving more than 1,000 handhelds, we recommend installing the Good Administration Center Server on a separate host machine. The Good Messaging Server should be close to the Exchange Servers it communicates with (low latency, good bandwidth); the Good Administration Center Server should be close to its SQL database (the database can exist prior to installation and be local or remote, or will be installed along with Good Administration Center).

Good Messaging Server host system requirements:

• Pentium 4 with minimum speed of 2GHz
• 512MB RAM
• 8GB hard drive space free for the Good Messaging Servers

These requirements for RAM and hard drive free space are based on 200 users. For each additional user, add 1.5MB memory and 40MB free disk space.

• If a virtual machine session is used for Good Messaging, the free drive space and RAM requirements also apply. Good Messaging is an I/O intensive application; consider this fact when deciding which other applications are to run on the same host machine.

The Good Messaging Server supports VMware ESX Server 3.0.1 and higher (performance may vary, based on VMware performance). The Good Administration Center Server supports only version 3.5. Good Mobile Connection supports versions 3.0 and 3.5. Use version VMware ESX 3.5 when Good Administration Center, Good Messaging Server, and Good Mobile Connection are all present on the same host machine.

• Required minimum LAN speed for the Good Messaging Servers: 10 MB/s. Note: When configuring Good Messaging Servers to connect with an Exchange server, the speed of the network connection must be a sustained minimum rate of at least 10MB/s. Slower network connections between Exchange and Good Messaging Servers will cause increased message latency.
• Microsoft Outlook^® must not be installed on the Good Messaging Server or Good Administration Center Server host machines. Uninstall Outlook if it is present. Installing Good Messaging Server on a Microsoft Exchange server machine is not supported. Installing Good Messaging Server on a domain controller is not supported.

Good Administration Center Server host requirements:

• For 500 users: Intel® Pentium® IV or dual-core Intel® Xeon® processor (2GHz or greater), 1.5 GB RAM; for 1,000 users: Intel Pentium IV dual processor (2GHz or greater), 2GB RAM
• Minimum 40 GB hard disk space

Good Messaging Server and Good Administration Center Server requirements:

• Good Messaging Server can service up to 1,500 handhelds.
• Good Administration Center Server requires Windows 2000 Service Pack 4 or Windows 2003 with Service Pack 2.
• Good Messaging Servers must have access to the Microsoft Exchange Server that will manage user mailboxes (Microsoft Exchange 2000/2003/2007).
• Both the Good Messaging Server and Good Administration Center Server host machines must have Internet access. They should be able to connect to http port 443 (secure https). To check this, use a browser with proxy settings disabled on the host machine to connect to a secure remote location. If you'll be using a proxy server, you'll enter the necessary information for that server during the installation process.

If you limit outbound HTTP and HTTPS on your firewall, you should open outbound ports 80 and 443 for IP ranges 216.136.156.64/27 and 198.76.161.0/24 for Good Messaging to work properly. Do not put the Good Messaging Server and Good Administration Center Server in the DMZ zone or block any LAN ports. The Good Messaging server and operating system calls have many port dependencies for interfacing with Domino mail servers and AD, especially TCP 1433 (Database) and 1352 (NRPC).

The Windows firewall is not supported for use with Good Administration Center. Note that in Windows 2008, the Windows firewall is turned on by default. If currently on, turn off the firewall in Windows 2003 or 2008.

• The host machine should not have an MSDE or SQL server installed on it, unless you choose to create a database on an existing Microsoft SQL 2005 server for use with Good Mobile Messaging. To uninstall SQL if present, refer to "Uninstalling SQL Server"
• Port 135 must be open for TCP connections from the Good Mobile Messaging Server to all Exchange Servers for enabled Good Messaging users. The Good Messaging Server will test connectivity to an Exchange Server by opening a TCP socket to port 135 before starting up users. If the Good Mobile Messaging Server fails to connect it will not allow users on that Exchange Server to start sending messages to their mobile device. This check is used as a health check in the event an Exchange Server is down and not able to handle requests.
• Before installing Good Messaging Servers and Good Administration Center Servers, ensure that the host machines' time and date are set to your network's correct time and date. Otherwise, errors such as a Security Alert regarding a problem with the site's security certificate may occur.
• If you are also installing a Good Mobile Intranet or Good Mobile Connection Server, refer to the installation and administration guide for that product.
• To activate the S/MIME secure-email feature in the Good Administration Center Console, all installed Servers must be version 5.0 or higher.
• For native Microsoft Exchange 2000 and 2003 environments or mixed Microsoft Exchange 2000/2003/2007 environments, Exchange System Manager 2003 with Service Pack 2 is required on all Good Messaging Server machines; if necessary, install Exchange System Manager from the Exchange 2003 CD. Installation of Exchange System Manager 2000 on Good Messaging Server is not recommended.

Important: For Microsoft Exchange 2007-only environments, the MAPI/CDO download from Microsoft is required on all Good Messaging Server machines. If mapicdo is present and its version is earlier than Exchange MAPICDO 6.5.8039.0, no changes are necessary.

If Exchange MAPICDO is not present or is version 6.5.8039.0 or later, do the following:

1. If necessary, download the latest version of ExchangeMAPICDO from Microsoft.
2. Set two environment variables to bypass the MAPI version check within the Good Messaging Server installer:
1. Open Control Manager ->System.
2. Click on the Advanced tab.
3. Click on Environment Variables.
4. Under System Variables:
1. Click New.
2. Type in "SKIPMAPICHECK" for the variable name.
3. Type in "1 for the variable value.
4. Click OK.
5. Click New again.
6. Type in "REQUIREANYCDO" for the variable name.
7. Type in "1" for the variable value.
8. Click OK.
9. Click OK again to exit.
3. Verify that the mapi32.dll is 1.0.xxxx (if not, run fixmapi.exe from the system32 directory).
4. Run the Good Messaging Server installer.

Note: If the installer complains that Exchange System Manager is not found, manually re-register the CDO.dll and retry the installation. To manually register CDO.dll, use Regsrv32 (regsrv32.exe full path and file name of CDO.DLL).

Good Administration Center SQL, .NET Framework, and Console requirements (links subject to change) (note these requirements if you plan to use an SQL server of your own; otherwise, Good Administration Center will install SQL Express for you):

• Microsoft .NET Framework 2.0 Service Pack 1 (x86):

http://www.microsoft.com/downloads/details.aspx?familyid=79BC3B77-E02C-4AD3-AACF-A7633F706BA5&displaylang=en#Requirements

• Good Administration Center:

Microsoft Internet Explorer 7.0 or Firefox 2.0. Internet Explorer 6.0 is not supported.

• Microsoft SQL Server 2005 Express Edition Service Pack 2:

http://www.microsoft.com/downloads/details.aspx?familyid=D07219B2-1E23-49C8-8F0C-63FA18F26D3A&displaylang=en#Requirements

http://www.microsoft.com/sql/editions/express/sysreqs.mspx

• Microsoft SQL Server Management Studio Express Service Pack 2:

http://www.microsoft.com/downloads/details.aspx?FamilyID=6053c6f8-82c8-479c-b25b-9aca13141c9e&DisplayLang=en#Requirements

Preparing for SQL Server Use

Good Administration Center requires access to an SQL server. You can use an existing Enterprise SQL Server 2005 or SQL server instance available within the organization. Good Administration Center Server can connect to a remote SQL server/instance without problems. If you don't have an SQL server that you want to use, a server will be installed along with the Good Administration Center.

Multiple GAC Servers can share an SQL instance but must use separate databases within that instance. If two GAC servers attach to the same database, data loss may occur.

Some knowledge of SQL installation, configuration, and maintenance will be useful if you plan to use an existing database.

You'll need the name of the service account you will use to run the Good Administration Center Service.

SQL Servers enforce their own authentication and authorization. If you encounter an SQL error during the installation process, you'll need to confirm that your SQL configuration information was entered correctly. If you will be using your own previously installed SQL Server instance, gather the following information in advance. You'll be required to provide it during Good Administration Server installation.

• The fully qualified machine name of your SQL Server instance
• Method of connection to your existing SQL Server instance (static port, named instance (dynamic port), or connected to it as the default instance)
• If static port, the port number
• If named instance, the instance name
• Authentication mode used to connect to your SQL Server instance (Windows authentication/SQL Server authentication)
• If Windows authentication, the service account name entered above must already have a login to SQL Server, or, if not, add a login for the service account name to your SQL Server instance, granting it at least the Server-Level Role of "dbcreator."
• If SQL Server authentication, the SQL Server login name you use to connect to SQL Server with, and the password for this SQL Server login. You will be prompted for the login and password during the Good Administration Center installation. The SQL Server login must be a member of the "dbcreator" security role. If not, add the login to the dbcreator security role so that the Good Administration Center install can create its own database and table within the SQL Server instance.
• If your existing database is remote, ensure that TCP/IP is enabled for "Local and Remote connections" on your SQL Server instance.

Remote SQL

To use remote access, the IT administrator should configure the remote SQL server to accept the necessary connections from Good Administration Center Server. This includes but is not limited to:

• Allowing connections via TCP/IP
• Allowing connections via a preconfigured port
• Opening any necessary port in any firewall between Good Administration Center Server and the SQL server
• Creating or obtaining a valid SQL Server user name and password to connect to the remote SQL server during installation or the ability to log in as admin "sa."

We recommend testing remote database SQL server connectivity before beginning an installation.

Related articles from Microsoft:

• To Configure using TCP/IP - http://support.microsoft.com/kb/914277
• To configure using static Port - http://support.microsoft.com/kb/823938
• Installing SQL Server 2005 (complete process) - http://technet.microsoft.com/en-us/library/ms143516(SQL.90).aspx

Microsoft Exchange configuration requirements

Microsoft Exchange configuration requirements:

• Every Good Messaging user account must be set up with an SMTP address (the standard Microsoft Exchange configuration).

The domain containing the Good Messaging account (GoodAdmin) must be trusted by the following domains: every domain containing one or more Exchange servers with mailboxes for Good Messaging handheld users; the domain containing the Exchange server where the GoodAdmin mailbox itself is located. Subject to this restriction, all Windows architectures are supported. To test, you can use the manageprofile command-line tool, installed with Good Messaging, on the Good Messaging Server host machines to open user mailboxes in each domain in question. The tool is explained in "manageprofile"

• MAPI Access is required for all Good Messaging users. Exchange 2003 SP2 introduced a way to turn MAPI Access off that will stop all synchronization for Good Messaging users. To verify MAPI access is on by default, do the following:
1. From Windows Support tools, go to ADSI Edit and connect to the appropriate domain.
2. Right-click on a Good Messaging user and select Properties.
3. Select the "ProtocolSettings" attribute from the list and verify that its value does not have a "MAPI" entry listed. If such an entry is present, verify that MAPI is not disabled:

Acceptable:

[No value]

MAPI§1§0§§§§§§ = MAPI is Enabled

If there is no MAPI string in ProtocolSettings, all MAPI clients are allowed; this is the recommended configuration

Not acceptable:

MAPI§0§0§§§§§§ = MAPI is Disabled

MAPI§1§1§§§§§§ = MAPI is Enabled only for clients running in cached mode

(Good Messaging Server does not run in cached mode.)

• The Public Folder store must be mounted on all Exchange server machines and configured to replicate data to each other in order for the Good Messaging Calendar's free/busy scheduling feature to function correctly. Public Folder referrals to a dedicated Public Folder server are not supported.

The following tables show the operating-system and Exchange software required on the Server and Console host machines. Windows 2008 is supported on the Good Mobile Messaging Server host machine but not on the Good Administration host machine in this version

Operating System

Good Mobile Messaging Server and Good Administration Center Server

Windows 2008 Server® (English (US))(GMM only)*, Windows 2003 Server® (English (US))* with SP2, or Windows 2000 Server® (English (US)) with Service Pack 4 All supported Windows operating systems can run under VMware ESX Server 3.0 or higher for Good Messaging Server. Good Administration Center requires version 3.5. When Good Administration Center, Mobile Messaging, and Mobile Connection are on the same host, 3.5 is required.

* Windows 2008 requires Exchange 2007 MAPI/CDO. Windows 2003 Server requires Exchange 2003 System Manager. Exchange 2000 System Manager is not supported on Windows 2003 Server.

Exchange Software

Good Mobile Messaging Server and Good Administration Center Server

Exchange Server 2007® Exchange Server 2003 System Manager® with Service Pack 2 (recommended), Exchange Server 2000 System Manager® with August 2004 Exchange 2000 Server Post-Service Pack 3 Update Rollup

The following Exchange servers are compatible with this version of Good Messaging. Go to http://customerportal.good.com/ for any compatibility updates and for compatibility with older Good Messaging and GoodLink versions.

Exchange Server

Exchange Server 2007®

Exchange Server 2003® with Service Pack 2

Exchange Server 2000® with August 2004 Exchange 2000 Server Post-Service Pack 3 Update Rollup