Title Here - Good Technology

Good Mobile Messaging Server Version 8.3.0 (SQL Version)
Good Mobile Control Server 2.6.0
for Microsoft Windows Exchange
Upgrading Good Mobile Control and Good Messaging (from BDB
Version)
Updated: 12/16/14
1
Introduction ............................................................................................................................... 1
2
Best Practices .......................................................................................................................... 1
3
Performing the GMC Upgrade.................................................................................................. 2
4
Performing the GMM Upgrade ............................................................................................... 11
1
4.1
Installation ....................................................................................................................... 11
4.2
Error Conditions .............................................................................................................. 27
Introduction
This document describes how to upgrade to Good Mobile Control server 2.6.0 from earlier
versions and how to upgrade to Good Mobile Messaging server 8.3.0 (SQL version) from
v8.0 (BDB version). Upgrading is tested and supported from the two earlier versions of Good
Mobile Control server; upgrading from earlier versions of Good Mobile Control will require
additional steps to complete. There is no option to upgrade to Good Mobile Messaging server
v8.3.0 from versions earlier than v8.0 in this release.
Note: There is no downgrade path from GMM v8.3 (SQL version) to v8.0.
Upgrades and migrations should be performed in the order given in this document.
Note: ws.good.com HTTPS 443 216.136.156.64/27 has been added to the outbound network
hostnames for Good Operations Center.
Note: If you are upgrading a GMM server from version 8.0 (EWS/BDB) to version 8.3, and the
GMM server is currently installed in a cluster, it can continue to function in that cluster. However,
upgraded servers not currently in a cluster cannot be added to one. Clustering is not supported
for these upgraded servers. Instead, the new High Availability options supported in version 8.3,
such as AlwaysOn, should be used.
2
Best Practices
As with all mission-critical software, you will want to test and upgrade your Good Messaging
servers, Good Mobile Control servers, Good Mobile Control consoles, and Good Client Software
according to the best practices implemented in your IT organization.
1
Always upgrade (or for GMM, migrate) GMC and GMM in tandem to the latest release. The latest
GMM requires the latest GMC.
For example:
1. Although Good Messaging software is thoroughly tested, some organizations will choose
to run Good Messaging server, Good Mobile Control server, and Good Messaging Client
in a test environment before installation. Such testing can vary in length from a day up to
a week.
2. Next, organizations with multiple Good servers may choose to at first upgrade the Good
Messaging server, Good Mobile Control server, and associated Good Messaging
consoles for a single GoodAdmin account with limited IT users/handhelds. In such a
case, they may let the upgraded components run for up to a week.
Note: Always upgrade the Good Messaging server, Good Mobile Control server,
and Good Mobile Control consoles for a given GoodAdmin account at the same
time.
3. After the server has been configured and operates correctly for a period of time, these
organizations upgrade a larger number of handhelds as a pilot program.
4. Finally, the rest of the handhelds on the server are upgraded.
5. Using this conservative approach, the rest of the servers are upgraded to the new
version. Each server runs for a day before the remaining handhelds are upgraded.
Always upgrade the servers before the handhelds.
3
Performing the GMC Upgrade
To upgrade Good Mobile Control server and Good Mobile Control console, follow this procedure.
If your GMC is already at v2.6.0, skip this section.
1. Launch the Good Mobile Control installer. To do so, run setup.exe from the root of the
installation media.
An upgrade screen is displayed.
2
2. Click Next and a license agreement is displayed. Accept the license agreement by
clicking Next.
3
A Host Selection screen is displayed for the SQL database that the GMC will use.
3. Choose Local SQL server Host and click Next.
4
4. Choose the same named instance as used before this upgrade and click Next.
5. Enter the same database name as used before this upgrade and click Next.
5
6. Do not change any of the values present by default in the fields on this screen (set during
the previous installation of Good Mobile Control). Click Next.
7. Select your Active Directory source. This is where the user directory resides:
•
•
On-Premise Only, O365 Dedicated, O365 Hybrid – Choose Active Directory (on
premise).
O365 Pure – Choose Active Directory on Cloud.
Notes:
•
•
Choosing Active Directory on Cloud to switch from on-premise is irreversible for
upgrades and repairs. Self Service will not be supported. Switching from cloud to onpremise is not supported.
Regardless of which deployment model is employed, a GoodAdmin AD service
account is required to install and run the Good Mobile Control and Good Mobile
Messaging Servers, so that an on-premise AD will be required in all cases.
•
For an overview of Good For Enterprise (Good For Enterprise) deployment in the
Exchange Online environment, refer to “On-Premise and Exchange Online
Environments” in Chapter 2 of the Good For Enterprise Administrator’s Guide.
•
Do not change this setting to cloud unless you have prepared your environment to
do so. Refer to the Preinstallation chapter in the Good For Enterprise Administrator’s
Guide for cloud account, permission, and Mobile Messaging Server dependencies.
Click Next.
8. If you’re switching to a pure Office 365 environment ment, a warning is displayed.
6
Click OK, assuming that your environment has been configured for pure Office 365.
9. Click on Next to show the existing “Administrator Domain\Username” screen. This refers
to the administrator for the Good Mobile Control service account.
7
10. (Cloud) Click Next to provide new Good Mobile Control service account credential
selections.
11. (Cloud) Click Next to provide SMTP address information.
8
12. (Cloud) Click Next to perform autodiscover validation. If this passes, a screen for backup
information is displayed.
9
13. On the Automatic Backup screen, disable automatic backup using the checkbox, or
enable it by providing the destination drive. Click Next.
14. Click Next and the upgrade begins. The Good Mobile Control console files are installed.
10
15. Installation completes and the GMC service is automatically started if “Start Good Mobile
Control server service” option is checked. Click Finish.
4
Performing the GMM Upgrade
Use the following procedure to upgrade a Good Mobile Messaging v8.0 Server (BDB version) to
v8.3 (SQL version). Repeat the procedure for additional Servers as needed. Each Server can
manage hundreds of handhelds on multiple Exchange servers. No special preparations are
necessary. You assign handhelds to Good Mobile Messaging Servers according to the
organizational scheme most convenient to you.
If you are upgrading from v8.0, you will need an SQL server available. Refer to the Good
for Enterprise Administrator’s Guide for preparation and setup details.
4.1 Installation
The Good Mobile Messaging Server host machine must be configured as for the previous
v8.host. Use a secure host (the machine should be located in a secure location and the proper
permissions should be set to control access to the machine).
1. Login with a Good Admin service account and run the GMM installer. The Installation
Manager screen is displayed.
2. Select Add/Remove for the Good Mobile Messaging Server. The current GMM 8.0
version is detected. The Upgrade Good Messaging screen is displayed.
11
3. Click Next and a license agreement screen is displayed.
4. Accept the terms of the license.
12
A Server Database Type is displayed.
5. Choose SQL and click next.
13
6. Click Yes to the following warning prompt.
7. Click Next.
14
An Office 365 Credential Selection screen is displayed.
8. Select the appropriate credentials for autodiscover and impersonation validation.
If you select Default Credentials, the Login and Password fields are not displayed.
If you are using an On-premise Microsoft Exchange server or an Office 365
dedicated server configured for integrated Windows authentication, select the Default
Credentials.
Otherwise, if using an Office 365 hybrid server, select New Credentials. Enter the
login username and password of the Office 365 service account that you have
created. The login username is normally entered in the following format:
user@domain
Click Next.
15
An SMTP address screen is displayed.
9. This screen is used to verify the default SMTP address. If correct, click Next. The
installer authenticates the SMTP address against the Exchange Server.
Otherwise, enter the GoodAdmin SMTP address for an Autodiscover operation. This
may or may not be the same at the Login for New Credentials which is typically the
service account.
Enter the SMTP address of the account you want to impersonate.
If you want to enable SCP lookup for Autodiscover, check Enable SCP Lookup. To
bypass SCP lookup, uncheck Enable SCP Lookup.
Click Next.
16
The credentials are checked.
10. If not correct, update the address and select Next and the installer will authenticate the
new SMTP address against the Exchange Server.
17
A screen is displayed to define the Exchange login username and password.
11. Enter the login and password for the Microsoft Exchange account that you used to install
the GMM server.
Click Next.
18
A Primary Database Information screen will be displayed.
If you are upgrading from v8.0, you will need an SQL server available. Refer to the
Good for Enterprise Administrator’s Guide for details. In this example screen, the
database is local, but need not be.
12. Enter the primary database information.
Click Next.
19
A Failover Database Information screen is displayed.
13. If using a failover database, check Failover Database Server and enter the failover
database information.
Click Next.
20
A screen for creating a new database schema is displayed.
14. This screen allows you to create database tables and monitor the progress of the
procedure.
Click Start and wait for the database tables to be created. The progress bar will show the
status of the table creation. When complete, a message will be displayed at the top of the
window, such as “Database tables created successfully.”
If the procedure was not successful, a failure popup will instruct you to send specified log
files to your authorized service representative. Cancel the upgrade.
21
The progress bar indicates completion of schema creation.
22
With the database creation complete, a screen is displayed for Good Mobile Control
Server registration.
15. Register the GMM with Good Mobile Control. (Use the Advanced button to specify a
specific console user account for registration.)
16. Click Next.
23
A screen will be shown to display the migration of the BDB database to the SQL server
database.
17. Click Start to migrate the BDB data to SQL server. If the migration is successful, the
window will inform you of the fact.
The former cache directory, found in install_path\cache, will be renamed with a “.old”
extension.
If the procedure was not successful, a failure popup will instruct you to send specified log
files to your authorized service representative. Cancel the upgrade.
Time required for BDB to SQL migration depends upon the cache size. For a cache
directory upgrade from 8.0 to 8.2, for a cache size of 8.3GB, with 1,036 users with
7,207,884 records in different tables, refer to the following table.
Database Migration Statistics
BDB
Resulting SQL DB
Cache Size: 8,915,947KB
DB Size: 6,912,256 KB
Log Size: 8,912 KB
DB Size Reported by SQL: 6757.00 MB
Total Records: 7,207,884
24
Total Migration Time: 84.68 mins. 4.90 secs/user. 1036/1036 users migrated.
18. Click Next.
If this screen is displayed, the SQL database may contain data due to a failed BDB
migration previously. Upgrading to an existing SQL database will automatically delete any
existing data.
19. Click Start to migrate the BDB data to SQL server. Wait for the migration to complete.
Migration success will be confirmed by a message onscreen.
Click Next.
25
This screen shows the current settings.
20. Click Next to copy the files and proceed.
A screen shows the status of the file copies.
26
If this is a PRIMARY GMMS, this screen will be displayed when installation is
complete.
21. Check “Start Good Message Server service” to if you want to start the service.
Click Finish to start the service and exit the installer.
22. Click Finish to exit installer.
4.2 Error Conditions
Note: In extremely rare circumstances, upgrading the Good Messaging server or Good Mobile
Control server may fail if for some reason the previous server installation parameters have been
altered in the registry. If you encounter upgrade problems, use the following procedure:
1. Gather the log files in the Log directory, such as migrated.diagnostic, SchemaMigrator.out,
and, in the Temp directory, GoodLinkInstall.log, and contact your authorized service
representative.
2. Install the earlier Good Messaging server using the same cache directory, license key, and
serial number as for your previous installation. If the the upgrade was not successful, this
former cache directory will not have been renamed with .old appended. If the .old is present,
remove it.
3. Upgrade handhelds to the latest version. Note: Good Messaging server is compatible with
two earlier Client versions. You can choose to upgrade the handhelds later.
©Good Technology, Inc., 2001-2014. All rights reserved. Good, Good Technology, the Good
logo, Good Mobile Messaging, Good Mobile Intranet, Good Mobile Defense, Good Mobile
Application Services, GoodAccess, GoodInfo, GoodLink, and Powered by Good are trademarks
27
of Good Technology, Inc. All other trademarks and service marks contained herein are the
property of their respective owners. Good Technology, Inc., and its products are not related to,
sponsored by, or affiliated with Research In Motion Limited. For information concerning other
intellectual property rights of Good and others, go to www.good.com/legaldocs.
28

Download Report