release notes for gems - help and manuals · l notificationlocalizationsupportforgoodwork[ios]...

1

Good Enterprise Mobility Server™ (GEMS)Release Notes

Compendium Updated: 29-Sept-16

Contents

Version 2.2 (SR2) Release Notes 2

Version 2.2 (SR1) Release Notes 5

Version 2.2 (GA) Release Notes 9



Version 1.5 (SR 1) Release Notes 27


Version 1.4 (SR 1) Release Notes 40




Version 1.1 (SR) Release Notes 55



2

Good Enterprise Mobility Server™ (GEMS)Version 2.2 (SR2)

Release NotesBuild: 2.2.22.25

Last Updated: 29-Sept-16

This document contains important information pursuant to the release of the software version cited aboveand is specific to this version unless otherwise noted.

Java RequirementThe following Java versions are supported:

l Java 7 Update 79 (7u79) or later for Microsoft Windows (64-bit)

l Java 8 Update 65 (8u65) or later for Microsoft Windows (64-bit)

Supported Upgradesl GEMS 2.2 (2.2.20.20)ð GEMS 2.2 (2.2.22.25)

l GEMS 2.2 (2.2.12.11)ð GEMS 2.2 (2.2.22.25)

l GEMS 2.1 (2.1.5.3)ð GEMS 2.2 (2.2.22.25)

Upgrade NotesUpgrade Pre-checkRun the following queries to ensure that the CORE and Push schema descriptions are “Schema for Kung Fu withNVARCHAR.” If either is not, use upgrade option 2. Otherwise, use option 1.

Run the following query to check the GEMS CORE schema version:

SELECT *

FROM [database_name].[dbo].[JSONSTORE_DB_VERSION_RECORD]

If the query results do not show the following results, use upgrade option 2 (steps 1, 2, 3, 4, 6, 7).

[schemaVersion] = 0.1.6.20160606

[schemaDesc] = Schema for Kung Fu with NVARCHAR

Run the following query to check the Push Notification schema version:

SELECT *

Version 2.2 (SR2) Release Notes

3

FROM [database_name].[dbo].[PUSHNOTIFY_DB_VERSION_RECORD]




Option One

1. Back up the GEMS cluster database before upgrading the GEMS servers.

2. Perform a rolling upgrade using the Installer.

Option Two


2. Download the GoodEnterpriseMobilityServer.2.2.22.25.zip file and extract dbmanager-2.2.25-jar-withdependencies.jar from it. The zip is found in GoodEnterpriseMobilityServer\DBManager. Copy the file toone of the GEMS servers on a machine where Java is installed.

3. Stop all the servers in the cluster before running the tool.

4. Open the command-line tool as an administrator and navigate to the folder where you have copied the JARfile. Run the following command, to upgrade the Core database schema (replacing HOSTNAME,DATABASENAME, USERNAME, and PASSWORD with actual values).

Note: The Core databases schema referenced in this step and the Mail database schema referenced in thefollowing step are the same database schema.

SQL authentication:

java -jar dbmanager-2.2.25-jar-with-dependencies.jar -moduleName jsonstore -dbType sqlserver -action upgrade -dbHost "HOSTNAME" -dbName "DATABASENAME" -dbPort "" -integratedAuth false -userName "USERNAME" -password "PASSWORD"

Windows authentication (need to log in to the Windows machine using credentials that have access to thedatabase):

java -jar dbmanager-2.2.25-jar-with-dependencies.jar -moduleName jsonstore -dbType sqlserver -action upgrade -dbHost "HOSTNAME" -dbName "DATABASENAME" -dbPort "" -integratedAuth true

5. Upgrade the Mail database schema using the following command (replacing HOSTNAME, DATABASENAME,USERNAME, and PASSWORD with actual values).

SQL authentication:

java -jar dbmanager-2.2.25-jar-with-dependencies.jar -moduleName pushnotify -dbType sqlserver -action upgrade -dbHost "HOSTNAME" -dbName "DATABASENAME" -dbPort "" -integratedAuth false -userName "USERNAME" -password "PASSWORD"


4

Windows authentication (log in to the Windows machine using credentials that have access to the database):

java -jar dbmanager-2.2.25-jar-with-dependencies.jar -moduleName pushnotify -dbType sqlserver -action upgrade -dbHost "HOSTNAME" -dbName "DATABASENAME" -dbPort "" -integratedAuth true

6. Restart all the servers in the cluster.


Fixed IssuesDefect TrackingNo.

Description

FIRST-12623 In some cases when you upgraded from Good Enterprise Mobility Server 2.1.5 to 2.2.12,the installation failed after the Pre-Installation Summary dialog box, and the following errormessage appeared: Failed to save GEMS configuration files. See installer log fordetails.

For more information, visit goodpkb.force.com/PublicKnowledgeBase/articles/Answer/ toread article 22828.

FIRST-12567 When you created a Docs repository with Japanese characters, you were unable to save thenew repository information, and the following error appeared: Failed to createRepository. Warning: Path validation failed. Verify path entered and if valid, clickSave again.

For more information, visit goodpkb.force.com/PublicKnowledgeBase/articles/Answer/ toread article 22999.

FIRST-12652 When you installed a new GEMS server 2.2.20 using the GEMS Cisco Jabber Connect andJabber Presence, the Jabber Connect adaptor didn't install.

Known IssuesThere are no known issues for this release of GEMS.


http://goodpkb.force.com/PublicKnowledgeBase/articles/Answer/

http://goodpkb.force.com/PublicKnowledgeBase/articles/Answer/

5

Good Enterprise Mobility Server™ (GEMS)Version 2.2 (SR1)


Last Updated: 02-Sept-16


What's Newl Fix for email notifications not working for users after GEMS 2.2 upgrade under heavy load.

l Optimizing of SQL Queries to speed up notifications during startup of the GEMS Push Notification Service.

l Improved error handling for Exchange EWS subscription errors.

l Ability to recover from Invalid Exchange sync state errors returned by Exchange to GEMS Push Notifications.


l Java 7 Update 79 (7u79) or higher Java 7 update for Microsoft Windows (64-bit)

l Java 8 Update 65 (8u65) or higher update for Microsoft Windows (64-bit)


l GEMS 2.1 (2.1.5.3)ð GEMS 2.2 (2.2.20.20)

l GEMS 1.5 (1.5.35.45)ð GEMS 2.2 (2.2.20.20)

Configuration ChangesServer configuration changes from server version 2.2 MR.

Value ChangesName/PID Config Name Old Value New Valuecom.good.server.core.datasource jdbc.maxActive 100 20

com.good.server.core.datasource jdbc.maxIdle 50 20

Upgrade Notes


http://www.oracle.com/technetwork/java/javase/7u67-relnotes-2251330.html

http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html

6

Upgrade Pre-checkRun the following queries to ensure that the CORE and Push schema descriptions are “Schema for Kung Fu withNVARCHAR.” If either is not, use upgrade option 2. Otherwise, use option 1.

Run the following query to check the GEMS CORE schema version:

SELECT *

FROM [database_name].[dbo].[JSONSTORE_DB_VERSION_RECORD]




Run the following query to check the Push Notification schema version:

SELECT *

FROM [database_name].[dbo].[PUSHNOTIFY_DB_VERSION_RECORD]




Option One



Option Two


2. Download the GoodEnterpriseMobilityServer.2.2.20.20.zip file and extract dbmanager-2.2.20-jar-withdependencies.jar from it. The zip is found in GoodEnterpriseMobilityServer\DBManager. Copy the file toone of the GEMS servers on a machine where Java is installed.


4. Open the command-line tool as an administrator and navigate to the folder where you have copied the JARfile. Run the following command, to upgrade the Core database schema (replacing HOSTNAME,DATABASENAME, USERNAME, and PASSWORD with actual values). Note: The Core databases schemareferenced in this step and the Mail database schema referenced in the following step are the same databaseschema.


7

SQL authentication:





SQL authentication:




6. Restart all the servers in the cluster.


Fixed IssuesDefect Tracking No. DescriptionFIRST-12452 Push notification settings doesn’t get saved with newly provisioned users.

FIRST-12316,G3SERVER-6443,G3SERVER-6445,G3SERVER-6513,G3SERVER-6444,G3SERVER-6511

Fix for email notifications not working for users after GEMS 2.2 upgrade under heavyload.

FIRST-12240 Ability to recover from Invalid Exchange sync state error returned by Exchange to GEMSPush Notifications.

FIRST-11719 Improved error handling for Exchange EWS subscription errors.

FIRST-11852 Handles error cases in Autodiscover with HTTP 302 redirects containing invalid URL.

FIRST-12256 Dashboard contents goes blank for Japanese language .


8

Defect Tracking No. DescriptionG3SERVER-6511 Any servers that were previously upgraded from GEMS 1.3 will fail to upgrade to 2.2.

G3SERVER-6464,G3SERVER-6397

Optimizing of SQL Queries to speed up notifications during startup of the GEMS PushNotification Service.

G3SERVER-6387 Forward Meeting Invitation shows incorrect sender from PNS .

Known IssuesDefect TrackingNo.

Description

G3SERVER-6575 Upgrading to latest GEMS throws a BadPaddingException for directoryservice-api.Restarting the common services fixes this issue.


9

Good Enterprise Mobility Server™ (GEMS)Version 2.2 (GA)Release Notes

Build: 2.2.12.11Last Updated: 23-June-16


What's NewNotifications

l Support for Exchange 2016

o Notifications, Badge Count, VIP Notifications in Good Work

o Conversation history in Good Connect

l Notification localization support for Good Work [iOS]

SMIME

l Support for client certificate authentication for SMIME certificate lookup in Good Work (AD and LDAP)

Good Docs

l Access Microsoft® AD RMS protected files in Good Work

l Support for CMIS enabled repositories in Good Work/Docs. Eg. EMC Documentum, Alfresco, HP RecordsManager

Good Presence

l Support for Jabber Presence

GEMS Infrastructure

l Support for specifying multiple Good Proxy in GEMS for failover

l Improved scalability for push notification service to support 10,000 users

Troubleshooting Page

l Pages adds the ability to automate periodic upload of GEMS statistics to the Good/Blackberry NOC. Theinformation collected includes number of users assigned to the instance, name of instance, name of thecluster, version of GEMS, list of instances, feature set for instance, feature set for cluster, services installed,status of the instance, JVM Version, last restart time, system bugs, operating system, schema version, and

Version 2.2 (GA) Release Notes

10

system health. The mail service must be installed for much of this information to be retrieved. Refer to theAdministrator's Guide for details.





l GEMS 2.1 (2.1.5.3)ð GEMS 2.2 (2.2.12.11)

Configuration ChangesServer configuration changes from server version 2.1 SR1.

Added ConfigurationsClass Name Config Name Description DefaultConfigurationImpl(autodiscover) easAutodiscoverUrlOverride Override URL for ActiveSync

autodiscover

CachedSyncStateStoreImpl flushIntervalSeconds 4 * 60 * 60

CachedSyncStateStoreImpl flushAfterNumNewEmails 50

Value ChangesName/PID Config Name Old Value New Valuekaraf-wrapper (windows) wrapper.java.initmemory 4096 (set for 2.1 hotfixes

only)2048

karaf-wrapper (windows) wrapper.java.maxmemory 2048 4096

karaf-wrapper (windows) wrapper.java.additional.15 -XX:MaxPermSize=128m -XX:PermSize=128m

karaf-wrapper (windows) wrapper.java.additional.16 -XX:MaxPermSize=256m

Upgrade Noteswrapper.java.additional.16Use the latest GC and GP available for download in GDN (as of 04/22/16, GC Server v2.2.511.26 and GP Serverv2.2.511.16):

https://community.good.com/community/gdn/cockpit.jspa





11

Note: In this release, the database schema has been updated to improve push notification scalability. For thisreason, when upgrading in clustered environments, you will be required to halt all GEMS server services forthe upgrade, providing downtime for the servers. Warn the end users as required before performing such anupgrade.

You can use either of the following two options.

Option One: Upgrade steps using the installerYou can use this option or Option Two.


2. Stop all GEMS server services except for the services of the server being upgraded first.

3. After the first server is upgraded, start the GEMS services on all the remaining servers.

4. Upgrade the remaining servers .

Option Two: For environments with three or more serversYou can use this option or Option One.

To reduce server downtime, follow these steps:


2. Download theGoodEnterpriseMobilityServer.2.2.12.11.zip file and extract dbmanager-2.2.12-jar-with-dependencies.jar from it. Copy the file to one of the GEMS servers onto a machine where Java is installed.


4. Open the command-line tool as an administrator and navigate to the folder where you have copied the JARfile. Run the following command, to upgrade the Core database schema (replacing HOSTNAME,DATABASENAME, USERNAME, and PASSWORD with actual values).

Note: The Core databases schema referenced in this step and the Mail database schema referenced in thefollowing step are the same database schema.

SQL authentication:






12

SQL authentication:




6. Restart all the servers in the cluster



Description

FIRST-12398FIRST-11581

GEMS Push Notifications stop working. GEMS Dashboard is inaccessible. After restarting theGEMS nodes, notifications work fine temporarily.

GEMSS-4242 Custom document libraries in SharePoint 2010/2013 are now supported.

G3SERVER-5453 After upgrade, web proxy test fails if the password is not re-entered.

G3SERVER-5885 [Installer] Quit button does not functional properly on last step of installation for releasebuild.

G3SERVER-6144 [Installer] During fresh installation, after pre-install summary, the path returns to the DBinfo screen.

G3SERVER-6220 Fails to get VIP Push while testing Rule with Unicode Sender and Subject.

G3SERVER-6226 Notifications stop working when load balancer loses connection with Exchange server.

G3SERVER-6236 Wrong values returned to K-series client after upgrade with JL data present.

G3SERVER-6240 Streamer connections are not enabled for web-proxy.


Description

G3SERVER-5891 Dashboard -Log upload page: the time-zone text display is not correct for a time zone.

G3SERVER-5932 [NTLM web proxy] Autodiscover fails for remote accounts when using NTLM authenticationfor web proxy in a hybrid exchange environment.

G3SERVER-6170 GEMS update should be coalesced into a single push notification.

G3SERVER-6182 If Good Proxies are running on different ports, then the individual GP should pick the portfor which it is set.

G3SERVER-6381 When GEMS cluster is in a mixed mode, where one node is v2.2 GA and another is v2.1 GA,


13

Defect TrackingNo.

Description

there is a discrepency in the badge count.

G3SERVER-6382 Upgrading from v2.1to v2.2 causse some of the devices to get duplicate pushes.

GEMSS-4275 [LYNC 2010] Due to a limitation with Microsoft, the IT Administrator must change to pollingmode. Once enabling polling mode, there will be a 5 minute delay before users see anupdated presence status from their contacts.

GEMS-4398 Conversation History not saved. In the Connect Configuration / Exchange ServerConfiguration section of the GEMS Dashboard, if Microsoft Exchange Server 2013 isselected from the Exchange Server Type dropdown menu and Enable Conversation Historyis checked, the conversation history may not be saved. The workaround is to instead selectfrom the dashboard Microsoft Exchange 2010 SP1 or Microsoft Exchange 2010 SP2 as theExchange Server Type for the conversation history after the installation.

Related Technical PublicationsThe following related publications and resources are available from the Good Admin Portal:

l GEMS Deployment Planning Guide

l GEMS Installation and Configuration Guide for Administrators

l SSL/TLS Certficate Check for GEMS and Good Work

l Good Work EAS Guidance

l Good Work Product Guide for Administrators


https://community.good.com/community/administrators-home/product-resources#DownloadsDoc

https://media.good.com/documents/gems_deployment.pdf

https://media.good.com/documents/gems_install_and_config.pdf

https://media.good.com/documents/gems_gw_ssl_tls_cert_check.pdf

https://media.good.com/documents/goodwork_eas_guidance.pdf

https://media.good.com/documents/goodwork_product_guide.pdf


Build: 2.1.5.3Issued: 12-Feb-16 | Updated: 12-Feb-16


What's Newl Improved installation software

l Support for GEMS Connect using Cisco Jabber

l Silent installer (unattended installation)

l Discontinue notifications when the Good container or app is removed from GC

l Badge count kept consistent with Outlook unread-email count

l Centralized configuration: saved GEMS Mail configuration in the database syncs to other nodes in the cluster

l Bug Fixes




Supported Upgradesl GEMS 1.5 SR 1 (1.5.35.45)ð GEMS 2.1 (2.1.5.3)

l GEMS 2.0 (2.0.16.23)ð GEMS 2.1 (2.1.5.3)

Upgrade Notesl Use the latest GC and GP available for download in GDN (currently, GC Server v2.2.511.9 and GP Server

v2.2.511.3):


l The installation/upgrade media has changed. Refer to theGEMS Installation and Configuration Guide for adescription of the new installation flow.

Jabber Support for Good Connect

© 2016 Good Technology, Inc. 14

Good Enterprise Mobility Server™ Release Notes




Where “GEMS Connect for Jabber“ is referenced, this document is specifically referring to Cisco’s IM and Presenceserver.

The Good Connect user functionality for Android and iOS devices using Jabber will remain unchanged. Someelements of the user interface have been improved. User login and authentication are described in the GEMSConnect documentation.

Note: The GEMS Launcher and other GEMS client applications do not support Presence in a Jabber GEMSimplementation.

Configuring Jabber support for Good Connect is described in theGEMS Installation and Configuration Guide.

Fixed IssuesDefect Tracking No. DescriptionFIRST-11087 Fix for issues with document downloads from Sharepoint (Etag mismatch).

FIRST-11056 Add retry for GdAuth token mismatch errors.

FIRST-11004 Optimizations of Presence service queries for federated contacts.

FIRST-10894 Enhancement to allow Global Catalog as a user source for Presence service.

FIRST-10746 Optimizations of LDAP queries for Docs service.

FIRST-10510 Fix to use FQDN for ActiveMQ.

FIRST-10404 Enhancement to retain user added configuration changes in Connect on upgrade.

FIRST-10117 Fix for duplicate users found in Docs database.


Description

G3SERVER-5932 Autodiscover fails for remote accounts when using NTLM authorization for web proxy in ahybrid Exchange environment.

G3SERVER-5885 Quit button does not functional properly on last step of installation.

G3SERVER-5790 Push Notifications may not work in installations with more than one version of GEMS untilthe client is launched and negotiation occurs.

G3SERVER-5651 In the installation media, service account boxes are active even if "local system account" isselected.

GEMSS-3833 In Jabber, the Connect client may request multiple new sessions almost at the same time,causing a login issue.










Build: 2.0.16.23Issued: 30-Nov-15 | Updated: 16-Dec-15


In This ReleaseGood is introducing an array of important GEMS services and capabilities, including enhanced Phase 2 S/MIMEsupport for Good Work, Docs Service extensions with support for Box repositories, MS Word editing, and SQL-based auditing tools.

What's NewThe following new/enhanced services and supported features/functionality are being introduced in this release:

l Good Work: Secure/Multipurpose Internet Mail Extensions (S/MIME) Support (Phase 2)

o Ability to configure LDAP lookups directly from GEMS Dashboard

o Ability to lookup certificates for contacts including personal contacts from LDAP

l Push Notifications and Alerts

o Ability to select and assign custom sounds for Push Notifications and VIP Alerts (requires Good Work 2.0)

l Good Docs: Box as a storage provider

o Create, Save, Upload, Download, and Browse Box documents

o OAuth 2.0

o Support for collaborative folders in box

o Online viewing and editing of box documents (via Office Web Apps)

l Good Docs: Support for Microsoft® Word editing (via Office Web Apps)

o Editing option for MS word documents in iPad view

l Good Docs: Microsoft SQL-based auditing tools

o Sample scripts to create auditing reports for document access via MS SQL

l Bug Fixes







l GEMS 1.5 SR 1 (1.5.35.45)ð GEMS 2.0 (2.0.16.23)

Important Upgrade NotesPrior to upgrading from 1.5.x to 2.0.x, review the notes in this section and in the Known Issues section below.The following sections were created to help you review the most relevant information:

GEMS General Upgrade Considerations

1. When upgrading from 1.5.x to 2.0.x, administrators must provide their AD user credentials to login to theGEMS Dashboard.

If, however, you are upgrading from a version prior to 1.5.x, you must enter the System password; i.e., thepassword controlled by theuser.properties file—the GEMS Dashboard password in previous releases ofGEMS. If you did not change it or if this will be a fresh install, the default password is "admin". If you changedthe System password by modifying user.properties, enter this password in the installer screen. See AppendixK in theGEMS Administration Guide for guidance.

2. Internet Explorer 11 (IE 11) users must close the browser before upgrading GEMS.

GEMS Connect Upgrade Considerations

There is a known issue where certain configuration information is not retained after upgrading. Please read thefollowing steps to ensure that you maintain existing functionality by capturing the relevant information andmanually updating the configuration as indicated.

1. If you are presently using the Lync Conversation History feature and configured GEMS Connect to storemessages on an Exchange server, back up the GEMS Connect server configuration file prior to performing theupgrade. The configuration file can be found in <install path>\Good Technology\Good

Server\Good Connect Server\GoodConnectServer.exe.config. After you have upgraded GEMS,you will need to specify the Exchange server (EWS) settings in the Connect component of the configurationdashboard. (Known Issue GEMSS-3382)

2. If you had added or adjusted any of the other documented GEMS Connect properties (refer to "Appendix C –Understanding the GEMS-Connect Configuration File" in the GEMS Administration Guide), back up the GEMSConnect server configuration file, referenced above, prior to performing the upgrade. After you upgradedGEMS, you will need to edit the GEMS Connect configuration file to reintroduce these settings. (Known IssueGEMSS-3407)

GEMS Docs Upgrade Considerations





https://community.good.com/community/administrators-home/product-resources/good-work

1. If upgrading from a version prior to 1.5.x, the upgrade installer will not auto-populate the Docs databasename (even if previously configured). Whether upgrading or installing Docs to use an existing database, youmust manually enter this Docs database name (if it is not present) when prompted. The upgrade installer willsubsequently make any database schema changes necessary.

2. When upgrading from GEMS 1.4 or Good Share, choose the action appropriate for your existing database:

Existing DB is not on same physical database server as GEMS 1.5 DB – Do not enter database valuesfor Docs when requested by the Installer. Instead, run the script(s) in the table below corresponding toyour existing version. You can then return to the GEMS Dashboard to enter the corresponding databasevalues.

Existing DB is on the same physical database server as GEMS 1.5 DB – Do enter the database valuesrequested by the Installer.

3. If you enter DB information for Docs in the Installer, the Installer will look for that existing database.Therefore, you must make sure the database currently exists before running the GEMS Installer.

Database scripts are located in:

GoodEnterpriseMobilityServerSetup.2.0.16.23\GoodEnterpriseMobilityServer\Docs\Sql\serverdocs-dbscripts-0.6.15-sql.zip\serverdocs-dbscripts-0.6.15\sqlserver

Run the following SQL query to determine your existing Docs database version:

select DBSchemaVersion from MiscItems

Existing Docs DB Version Upgrade Script(s) to Run204 205/sqlserver_upgrade_from_204_to_205.sql203 204/sqlserver_upgrade_from_203_to_204.sql

205/sqlserver_upgrade_from_204_to_205.sql202 203/sqlserver_upgrade_from_202_to_203.sql

204/sqlserver_upgrade_from_203_to_204.sql205/sqlserver_upgrade_from_204_to_205.sql

201 202/sqlserver_upgrade_from_201_to_202.sql203/sqlserver_upgrade_from_202_to_203.sql204/sqlserver_upgrade_from_203_to_204.sql205/sqlserver_upgrade_from_204_to_205.sql

200 201/sqlserver_upgrade_from_200_to_201.sql202/sqlserver_upgrade_from_201_to_202.sql203/sqlserver_upgrade_from_202_to_203.sql204/sqlserver_upgrade_from_203_to_204.sql205/sqlserver_upgrade_from_204_to_205.sql




Existing Docs DB Version Upgrade Script(s) to Run204/sqlserver_upgrade_from_203_to_204.sql205/sqlserver_upgrade_from_204_to_205.sql

91 95/sqlserver_upgrade_from_91_to_95.sql200/sqlserver_upgrade_from_95_to_200.sql201/sqlserver_upgrade_from_200_to_201.sql202/sqlserver_upgrade_from_201_to_202.sql203/sqlserver_upgrade_from_202_to_203.sql204/sqlserver_upgrade_from_203_to_204.sql205/sqlserver_upgrade_from_204_to_205.sql

88 91/sqlserver_upgrade_from_88_to_91.sql95/sqlserver_upgrade_from_91_to_95.sql200/sqlserver_upgrade_from_95_to_200.sql201/sqlserver_upgrade_from_200_to_201.sql202/sqlserver_upgrade_from_201_to_202.sql203/sqlserver_upgrade_from_202_to_203.sql204/sqlserver_upgrade_from_203_to_204.sql205/sqlserver_upgrade_from_204_to_205.sql

Installation and Configuration WorkflowUpon verification that all environment and infrastructure prerequisites listed in theGEMS Administration Guidehave been met, the GEMS installation and configuration workflow can be summarized as follows:

Installation and Configuration Steps1. Install GEMS

a. Ensure all prerequisites, including Java, .Net, and enabling IIS are in place and functioning properly on theGEMS host before attempting to install the GEMS software

b. Download the GEMS Installer package

c. Create the Mail, Connect, and Docs databases on the SQL Server host. Be sure to make the collation CI(case-insensitive). See theGEMS Administration Guide for details

d. Run GoodEnterpriseMobilityServerSetup.2.0.16.23.exe

e. Provide the database info and the installer bootstraps the database for the Mail, Follow-Me (JSON storetables are bootstrapped to the Mail database), Connect, and Docs services

f. Click on Configure from the installer to go to launch the Dashboard, then login initially as a member of




https://community.good.com/community/administrators-home/product-resources/gems

the local administrators group. Afterward, underGEMS System Settings, you can configure your ADgroups for admin login using AD credentials.

2. Configure the GEMS Dashboard

a. Mail

l Select Mail >Database

l Provide DB details and test. If successful, save.

l Restart GEMS Common Services

l Return to Dashboard Home and select Mail > Good Dynamics, then provide theGood Proxyconfiguration information and save

l Return to Dashboard Home and select Mail > Exchange, provide the Windows Service Account andsave

l Go to Exchange and test an end-user email address to confirm that Autodiscover is working

l If configuring a Web Proxy between GEMS and the APNS Relay, go to Mail > Web Proxy and add theproxy configuration information

l Go to Mail > Android Push Notification and enter the Sender ID and AuthKey, then save.

Note: If Android devices are to be provisioned, these steps are required.

To retrieve the values for Sender ID and Key from Good Control:

1. In the GC Dashboard, click Licenses and Keys under SETTINGS and open theAPI KEYS tab2. In the listing forGoogle Cloud Messaging API, click Edit3. Write down or copy the respective values shown.

b. Docs

l Return to Dashboard Home and click on Docs, then click on Database and configure the details

l Click Good Dynamics and enter the FQDN of your Good Proxy server

l If a brand new installation of Docs (empty DB), click on Repositories and add File Shares andSharePoint sites as desired, adding users in accordance with the v1.5 (or 1.6 Beta) edition of theGEMSAdministration Guide.

3. Configure Good Control

a. Add your GEMS host(s) to the Entitlement to Good Enterprise Services app:

n In the GC Dashboard underAPPS, click Manage Apps

n Scroll down or search for "Entitlement to Good Enterprise Services", click it, then open theGOOD DYNAMICStab

n Enter the FQDN of each GEMS host and port "8443", then click Submit

This entitles the Presence, Follow-Me, and Directory Lookup services—all three—and needs to becompleted only once.



https://community.good.com/groups/beta-good-dynamics-and-gems


b. Add the Entitlement to Good Enterprise Services app to at least one Application Group like Everyone:

n In the GC Dashboard underAPPS, click App Groups

n Click on Everyone

n Click , search for "Entitlement to Good Enterprise Services", enable its checkbox, then click OK

c. Add your GEMS host(s) to Feature - Docs Service Entitlement:


n Scroll down or search for "Feature - Docs Service Entitlement", click it, then open the SERVERS tab


d. Add the Feature - Docs Service Entitlement app to at least one Application Group like Everyone:


n Click on Everyone

n Click , search for "Feature - Docs", enable its checkbox, then click OK

e. Add your GEMS machines to the Good Work app (if not already configured):


n Search for or scroll down to the appropriate version of Good Work, click it, and open theGOOD DYNAMICS tab

n In the Server section, click EDIT and add the new host, specifying port 8443

n Click Save

4. Configure LDAP in the GEMS Web Console to support Directory Lookup and Certificate Lookup (see"Configuring the Certificate Lookup Service" in theGEMS Administration Guide").

5. Enable Box connector support as follows:

a. Upgrade all GEMS-Docs servers to 2.0 (Build 2.0.16.23)

b. In Good Control, do the following:

4Under POLICIES, select Policy Sets, then open or clone the policy you want to govern Docs4Open theAPPS tab and expand APP SPECIFIC POLICIES4 Click GOOD WORK (the version of Good Work for this beta test)4Open theDocs and Attachments tab and enableBox.4 Click Update.

c. Create a Box Repository In the GEMS Dashboard with the following steps:

4Go to Docs > Repositories and cick New Repository4 EnterDisplay Name, chooseBox as the Storage Type4 For Path, enter the URL of the Box account (e.g., https://company.app.box.com/files/share)4 Select a List (e.g., Box Repository)4 If desired, enable inheriting of access control of this repository list4 Click Save.




Note: The URL you provide is the URL you see in the browser. This is not the Box shared URL that it createswhen you share a folder or file, it's just the browser URL that lead to the rendering of the resources thatyou want your users to access, or you want to access if it you are adding a user defined repository.

Use Lists to assign users to multiple repositories and/or to organize your repositories by commoncharacteristics. This allows you to batch-configure user access permissions. Included repositories can inheritthe configured user access permissions of the list or maintain permissions independent of the list.

d. Restart Good Common Services

6. Enable Microsoft Word editing by completing these steps on all GEMS nodes:

a. Make sure you have the correct Office Web App Server URL configured in the GEMS Dashboard underDocs > Settings

b. Export the GEMS SSL certificate to the OWAS machine as follows:

On the GEMS machine, execute:keytool -export -alias serverkey -file gems.cer -keystore gems.jks

(gems.jks is in etc\keystores folder under C:\Program Files\Good Technology\Good EnterpriseMobility Server\Good Server Distribution\gems-quickstart-2.0.16)

On the OWAS machine:4 Copy the gems.cer file (outputed above) over to the OWAS machine.4 Launch mmc.exe, then select File > Add/Remove Snap-in....4 Select Certificates , then click Add, select Computer account and click Next.4 Select Local computer and click Finish.4 Expand Certificates (Local Computer), then right-click Trusted Root Certification Authorities. file.4 Select All Tasks > Import and complete theCertificate Import Wizard, specifying the gems.cer

c. From the Windows folder on the OWAS machine , copy Microsoft.CobaltCore.dll to C:\ProgramFiles\Good Technology\Good Enterprise Mobility Server\Good Server Distribution\gems-quickstart-2.0.16\lib on the GEMS machine.

d. Restart theGood Common Service.

Complete instructions, guidance, and feature descriptions are available in the v2.0 edition of theGEMSAdministration Guide.





Additional Considerations1. TLSV1.0 is enabled in GEMS, so if there is third-party software in the ecosystem that uses TLSV1.0 for

communication with GEMS, it will work out-of-the-box (for example, officeweb apps).

To disable the TLSv1.0 protocol, add the following line on the Jetty.xml:

<Item>TLSv1</Item> under <Set name="ExcludeProtocols">

1. GEMS Administrators are now added via Active Directory groups. Groups in Active Directory are directoryobjects that reside within a domain and organizational unit container objects. Active Directory gives you theoption of creating new groups. Adding a group of administrators to your GEMS settings gives GEMSDashboard permissions to the entire group.

2. If you have a mixed environment (i.e., some servers on a previous version of GEMS and some upgraded to2.0.x), the feature set enabled will be limited to the features common in both versions.

3. If upgrading from an ealier GEMS version configured with Docs, you will have to enter the Docs databasename manually.

4. When upgrading GEMS-Docs, user defined data sources may disappear from the client. To prevent this fromhappening, upgrade the client first. If there are any offline files, save them to an online resource beforeupgrading the client, otherwise offline files will be removed.

5. If an earlier version of GEMS is configured to disable SSL checking for Microsoft Exchange, after upgradeadmin will need to disable it again in the dashboard by going to Mail > Microsoft Exchange.

6. To ensure proper configuration of GEMS within your Windows Services environment, strict adherence to theconfiguration sequence for the Push Notification Service (PNS) documented in theGEMS AdministrationGuide, is strongly recommended. Please ensure that you configure the PNS Database before you configureEWS Impersonation. Failure to follow the steps in the sequence listed could result in connectivity issues.

If, during GEMS configuration, GEMS is unable to connect to its Push Notification database, this usuallymeans that the configuration steps listed were executed in the incorrect order; that is, typically Mail >Microsoft Exchange configuration information was applied in the GEMS Dashboard before configuring theMail > Database information. If you encounter this problem, use the following procedure to resolve theissue.

From the GEMS Dashboard:

a. Clear out theMail > Exchange Server configuration and click Save.

b. Make sure the information in Mail > Database is correct.

c. Restart theGood Technology Common service.

d. Repopulate theMail > Exchange Server configuration and save your changes.

7. To enable external contact labelling—meaning contacts outside of your organization—you will need to insert<add key="ENABLE_SOURCE_NETWORK" value="true" /> to GoodConnectServer.exe.config in the<appSettings> section.

Example:





{quote}<configuration>

<appSettings>...

<add key="ENABLE_SOURCE_NETWORK" value="true" />...</appSettings>

</configuration>{quote}

Acknowledged LimitationsWhen upgrading GEMS Docs, user-defined data sources may disappear from the client. To prevent this fromhappening, upgrade the client first (to Good Work 1.6). If there are any offline files, save them to an onlineresource before upgrading the client; otherwise, offline files will be removed.

Fixed IssuesDefectTracking No.

Description

G3SERVER-5472

[GCM] Push notification not working for any Android user if GCM Sender ID/ key gets addedafter a single Android client gets provisioned

G3SERVER-5244

Badge number can't increase if email notification is disabled in Good Control.

FIRST-10594 User not receiving APNS to iOS device when using GW 1.5.3 from TF.

FIRST-10556 EWS Subscription Error.

FIRST-10546 KCD-enabled docs not working for security group.

FIRST-10542 "Undefined" error when searching user in GEMS-Docs.

FIRST-10530 The Audit Purge button within the GEMS Docs console does not work when using IE 11.

FIRST-10418 Android Push notification not working .

FIRST-10178 Good Work Docs Unable to Access SP or File Shares.

FIRST-10150 GEMS Docs File Access Error.

FIRST-10054 EWS Connection drop (iOS Devices not receiving APNS for Good Work in Pilot Environment.

FIRST-9931 Presence not working on new infrastructure.


Description

G3SERVER-2639 [GEMS-Mail][EWS-Listener][SCP] Configuring ewslistener bundle with a FQDN for the host,rather than just the hostname, sometimes fails Autodiscover SCP lookup check

G3SERVER-3118 After upgrade, dashboard doesn’t respond for 10 minutes. Workaround: Wait; self-correctsafter 10 minutes; only happens after upgrades

G3SERVER-3606 [GEMS-Mail][DataBase] After changing the Mail database, GEMS cannot connect to the new



Defect TrackingNo.

Description

DB.Workaround: After DB change, enter Exchange service account password via Dashboard. Thisis because the password is encrypted with a key that was present in the previous databaseand can no longer be decypted with the key from the new/changed DB

G3SERVER-4198 When installing GEMS Connect on Windows 2012 R2 for Lync 2013, the installer will showthat PowerShell is not installed. Workaround: If you truly do have PowerShell 4.0 installed,please disregard this error

G3SERVER-4917 If upgrading from an earlier GEMS version configured with Docs, admin has to enter theDocs database name manually; Docs database name is not pre-filled during upgrade

G3SERVER-5118 IE windows left open during upgrade will have inconsistent info post-upgrade.Recommendation is to close and open the browser windows

G3SERVER-5469 [INSTALLER] Java installed but installer shows as missing if JAVA_HOME is not set

GEMSS-3184 [Docs] Occasionally a .docx file will not open when viewed online in Good Work via GoodAccess. This is due to a known OWAS third-party limitation that occurs under certaincircumstances

GEMSS-3382 [Connect] If Exchange Conversation History is enabled before upgrade, the Exchangeversion information will not be retained after upgrade. Specify the correct information inthe configuration dashboard after upgrade.

GEMSS-3398 [Connect] In certain circumstances relating to HA/DR, messages sent to the Connect clientcan be delayed for a brief period of time.

GEMSS-3407 [Connect] If you set the custom settings in GEMS Connect, such as SESSION_TIMEOUT_SECS, back up the settings before upgrading and manually add them after installation.

GEMSS-3417 [Docs] First download will fail for files at the root of Shared With Me, but second attempt todownload will work.

GEMSS-3436 [Connect] When adding a contact from your Lync desktop client, the new contact may notinitially appear on the Connect client. To force a refresh, sign out and sign in again to see thecontact appear in your list.















Good Enterprise Mobility Server™ (GEMS)Version 1.5 (SR 1)


Issued: 30-Sep-15 | Updated: 1-Oct-15


In This Service ReleaseThis service release contains important fixes to the core release (1.5.22.31) issued 3-Aug-15, including:

l Receiving double new mail notifications

l Not getting banner new mail notifications

l Intermittent issues resolved wherein some users were occasionally unable to send messages from GoodConnect

l Docs admin-defined repository fixes:

o Resolved an isolated issue wherein Docs could not access AD to find users

o Administrators can now access users who have hyphenated names within a domain

o Administrators can now access identically named security groups residing in different domains

o Administrators can now search AD security groups in child domains

Supported Upgradesl GEMS 1.5 GA (1.5.22.31)ð GEMS 1.5 SR 1 (1.5.35.45)

l GEMS 1.4 SR 1 (1.4.17.23)ð GEMS 1.5 SR 1 (1.5.35.45)

Browser Compatibilityl IE: 10, 11

l FF : 32, 31, 30

l Chrome: 37.0.2062.120

Upgrading to the Unlimited Java Cryptography Extension (JCE)JCE furnishes a framework and implementation for:

l Encryption, including symmetric, asymmetric, block, and stream ciphers

l Key generation and key agreement

l Message Authentication Code (MAC) algorithms



The extension also supports secure streams and sealed objects. Moreover, JCE allows other qualifiedcryptography libraries to be plugged in as service providers so that new algorithms can be added seamlessly.Qualified providers are digitally signed by a trusted entity.

Note: JCE has been integrated with the Java 2 SDK, Standard Edition, since Version 1.4. Before J2SDK 1.4, JCEwas an optional extension package.

GEMS currently supports both Java 7 and Java 8. Regardless of the Java version currently installed on your GEMShost(s)—7 or 8—you will need to update the Java cipher to allow GEMS 1.5.35.45 to connect to GC/GP 2.0 andsubsequent GD platform servers over HTTPS. Here, it's important to remember that Java 7 and Java 8 requiredistinct cipher packages, available for download from these respective links:

l Java 8 – http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html

l Java 7 – http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html

Consequently, if you have deployed GC/GP 2.0 and are connecting from GEMS using SSL , the following stepsneed to be performed:

1. Download the cipher package listed above corresponding to the Java version running on each GEMS machine.

2. Uncompress and extract the zip files to create a subdirectory called \jce containing the following files:

l README.txt

l local_policy.jar (unlimited strength local policy file)

l US_export_policy.jar (unlimited strength US export policy file)

3. Make a copy of your original JCE policy files—both US_export_policy.jar and local_policy.jar—and renamethem (e.g.,US_export_policy.jar.oob and local_policy.jar.oob). Depending on your OS, these files arefound in:

l UNIX – <java-home>/lib/security

l Windows – <java-home>\lib\security

4. Replace them with the files you downloaded and extracted in Steps 1and 2 (i.e.,US_export_policy.jar andlocal_policy.jar, respectively).

Tip: If you later decide to revert to the original "strong" but limited policy versions, simply replace the unlimitedpolicy files with the backup you made in Step 3 and give them back their original names—i.e.,US_export_policy.jar and local_policy.jar.


Description

G3SERVER-5329 Receiving double new mail notifications

G3SERVER-5328FIRST-10136

Not getting banner new mail notifications

GEMSS-3054 Docs admin repository – Resolved an isolated issue where Docs could not access AD to find



http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html

http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html

Defect TrackingNo.

Description

users

GEMSS-3130 Docs admin repository – Administrators cannot access users in domains that containhyphens in their name

GEMSS-3135FIRST-10186

Docs admin repository – Administrators canot access the same named security groupresiding in multiple domains

GEMSS-3220 Docs admin repository – Administrators cannot add users with GEMS KCD enabled

GEMSS-3222 Docs admin repository – Administrators cannot search AD security groups in child domains

GEMSS-3230FIRST-10040

Connect – intermittent issue for which some users were unable to send messages fromGood Connect

FIRST-10360 GEMS Connect - Application not loading contacts

FIRST-10136 KCD Good Docs 1.5 not working

FIRST-10070 GEMS upgrade to 1.5 is hanging (600+ user Pilot Environment)

FIRST-9617 User cannot access data sources using Docs


Description

GEMSS-2590 [GEMSS-551] Upon server upgrade from GEMS 1.4 to 1.5, user defined data sourcesdisappear from the client. Workaround: To prevent this from happening, upgrade the clientfirst. If there are any offline files, save them to an online resource before upgrading theclient; otherwise, offline files will be removed


GEMSS-2702 When changing the configuration of the Office Web Apps Server you will need to restartwindows common services

G3SERVER-3606 [GEMS-Mail][DataBase] After changing the Mail database, GEMS cannot connect to the newDB.Workaround: After DB change, enter Exchange service account password via Dashboard. Thisis because the password is encrypted with a key that was present in the previous databaseand can no longer be decypted with the key from the new/changed DB



GEMSS-983 Before upgrading from the remote Good Share web console, manually create the directorystructure C:\Program Files(x86)\Good Technology\Good Share Server\ and copy over theconfig.xml file, then run the installer



Defect TrackingNo.

Description

GEMSS-2793 [Docs] When searching for AD users or groups in admin- or user-defined repositories, theFQDN of the domain should be used


GEMSS-2901 Adding a data source with a purely numeric name (e.g., "112233") will produce an emptyfolder message; when attempting to delete, a data source not found error is thrownWorkaround: End-user can login on self-service portal for Docs(https://<localhost>:8443\docsconsole) and change the repository name to supported characters(i.e., not purely numeric)



G3SERVER-4370 [MSM Support] Due to the versioned install path in each GEMS upgrade (..\gems-quickstart-1.5.35\), log file share locations must be manually changed so that MSM can seethem and monitor the server



l GEMS Administration Guide (formerly "GEMS Installation and Configuration Guide")


l SSL/TLS Certificate Check

l Good Work Product Guide

l Good Work Client User Guide for Android Devices

l Good Work Client User Guide for iOS Devices



https://community.good.com/community/administrators-home






https://media.good.com/documents/goodwork_ug_android.pdf

https://media.good.com/documents/goodwork_ug_ios.pdf


Build: 1.5.22.31Issued: 3-Aug-15 | Updated: 19-Aug-15


In This ReleaseGood is introducing an array of important GEMS services and capabilities, including unread and new badge countsupport for Good Work, synchronization for subscribed subfolders, web proxy support for notifications whenconnecting to O365 Exchange, a new bypass SSL checking option for Exchange mail notifications, Office webediting for Good Access, KCD support for GEMS-Docs service, Docs configuration console integration into GEMSDashboard, AD-based GEMS Dashboard login, JRE 8.0 support, the ability to upload logs directly to GoodSupport from the GEMS Dashboard, and more.


l Unread and New Mail badge count for Good Work [iOS only] (see Note 1)

o Badge count for Good Work will be updated by the GEMS Mail Notification service

o Badge count will update on Good Work when the app is in offline or background mode on the end userdevice

l Subfolder Synchronization for Good Work (see Note 1)

o Ability to sync subscribed subfolders

l Web Proxy support for notifications when connecting to O365 Exchange

o Support for NTLM, Basic and Digest authentication modes

l Bypass SSL checking option for Exchange mail notifications

o Useful when using self signed certificates or non-public certificates to connect to Exchange

l Office Web Editing for Good Access 2.4

o Ability to view and edit online office documents through integration with Office Web Apps Server (OWAS)and GEMS Docs service

o Supports documents to be edited and viewed from Good Work 1.5 email attachments, SharePoint2010/2013, and File Shares



l KCD Support for GEMS Docs service

o Ability to enable KCD access for Docs repository access

o Can be enabled/disabled through the GEMS Dashboard

l Docs console integration into GEMS

o Ability to fully configure and install Docs service from the GEMS dashboard

o Replaces the separate installer and IIS console required for GEMS Docs service in v1.4

l AD based GEMS Dashboard login

o Ability to use AD groups to manage administrative access and login to GEMS Dashboard

o Ability to add and remove multiple AD groups from the Dashboard

l JRE 8.0 support

l Upload logs directly to Good Support from GEMS Dashboard

l Bug Fixes

Note 1: Client support for this feature will be available for use with release of Good Work 1.5.

Note 2: Word editing is not supported in this release.

Note 3: Requires Good Access 2.4, scheduled for release in August 2015.

Java RequirementJava Runtime Environment (JRE) 7 Update 67 (7up67) or higher update for Microsoft Windows (64-bit) isavailable for download directly from Oracle.

New: Java 8 is now supported.

Supported Upgradesl GEMS 1.4 GA (1.4.14.19)ð GEMS 1.5 GA (1.5.22.31)

l GEMS 1.4 SR 1 (1.4.17.23)ð GEMS 1.5 GA (1.5.22.31)

l GEMS 1.5 Beta-2 (1.5.17.26)ð GEMS 1.5 GA (1.5.22.31)

Important Upgrade Notes1. You must enter the System password; i.e., the password controlled by theuser.properties file. This was also

the GEMS Dashboard password in previous releases of GEMS. If you did not change it or if this will be a freshinstall, the default password is "admin". If you changed the System password by modifying user.properties,enter this password in the installer screen. See Appendix K in theGEMS Installation and Configuration Guidefor guidance.

2. The upgrade installer will not auto-populate the Docs database name (even if previously configured) duringan upgrade. Whether upgrading or installing Docs , you must enter in the Docs database name (if it is not




http://www.oracle.com/technetwork/java/javase/downloads/java-se-jre-7-download-432155.html


https://community.good.com/community/administrators-home/product-resources/good-work

present) when prompted. The upgrade installer will make any database schema changes as necessary.

3. When upgrading from GEMS 1.4 or Good Share, choose the action appropriate for your existing database:

Existing DB is not on same physical database server as GEMS 1.5 DB – Do not enter database values forDocs when requested by the Installer. Instead, run the script(s) in the table below corresponding to yourexisting version. You can then return to the GEMS Dashboard to enter the corresponding database values.

Existing DB is on the same physical database server as GEMS 1.5 DB – Do enter the database valuesrequested by the Installer.

3. IE 11 users must close the browser before upgrading GEMS to v1.5.

Important: If you enter DB information for Docs in the Installer, the Installer will look for that existingdatabase. Therefore, you must make sure the database currently exists before running the GEMS Installer.

Database scripts are located in:

GoodEnterpriseMobilityServerSetup.1.5.22.31.zip\GoodEnterpriseMobilityServer\Docs\Sql\serverdocs-dbscripts-0.3.23-sql.zip\serverdocs-dbscripts-0.3.23\sqlserver\

Run the following SQL query to determine your existing Docs database version:

select DBSchemaVersion from MiscItems

Existing Docs DB Version Upgrade Script(s) to Run203 204/sqlserver_upgrade_from_203_to_204.sql

202 203/sqlserver_upgrade_from_202_to_203.sql204/sqlserver_upgrade_from_203_to_204.sql

201 202/sqlserver_upgrade_from_201_to_202.sql203/sqlserver_upgrade_from_202_to_203.sql204/sqlserver_upgrade_from_203_to_204.sql



91 95/sqlserver_upgrade_from_91_to_95.sql200/sqlserver_upgrade_from_95_to_200.sql201/sqlserver_upgrade_from_200_to_201.sql202/sqlserver_upgrade_from_201_to_202.sql203/sqlserver_upgrade_from_202_to_203.sql204/sqlserver_upgrade_from_203_to_204.sql




Existing Docs DB Version Upgrade Script(s) to Run203/sqlserver_upgrade_from_202_to_203.sql204/sqlserver_upgrade_from_203_to_204.sql

Installation and Configuration WorkflowUpon verification that all environment and infrastructure prerequisites listed in theGEMS Installation andConfirguration Guide for Administrators have been met, the GEMS installation and configuration workflow can besummarized as follows:

Installation and Configuration Steps1. Install GEMS

a. Ensure all prerequisites, including Java, .Net, and enabling IIS are in place and functioning properly on theGEMS host before attempting to install the GEMS software

b. Download the GEMS Installer package

c. Create the Mail and Connect databases on the SQL Server host. Be sure to make the collation CI (case-insensitive). See theGEMS Installation and Configuration Guide for details

d. Run GoodEnterpriseMobilityServerSetup.1.5.22.31.exe

e. Provide the database info and the installer bootstraps the database for the Mail, Follow-Me (JSON storetables are bootstrapped to the Mail database), Connect, and Docs services

f. Click on Configure from the installer to go to launch the Dashboard, then login initially as a member ofthe local administrators group. Afterward, underGEMS System Settings, you can configure your ADgroups for admin login using AD credentials.

2. Configure the GEMS Dashboard

a. Mail

l Select Mail >Database

l Provide DB details and test. If successful, save.

l Restart GEMS Common Services

l Return to Dashboard Home and select Mail > Good Dynamics, then provide theGood Proxyconfiguration information and save

l Return to Dashboard Home and select Mail > Exchange, provide the Windows Service Account andsave

l Go to Exchange and test an end-user email address to confirm that Autodiscover is working






l If configuring a Web Proxy between GEMS and the APNS Relay, go to Mail > Web Proxy and add theproxy configuration information

l Go to Mail > Android Push Notification and enter the Sender ID and AuthKey, then save.

Note: To retrieve the values for Sender ID and Key from Good Control:

1. In the GC Dashboard, click Licenses and Keys under SETTINGS and open theAPI KEYS tab2. In the listing forGoogle Cloud Messaging API, click Edit3. Write down or copy the respective values shown.

b. Docs

l Return to Dashboard Home and click on Docs, then click on Database and configure the details

l Click Good Dynamics and enter the FQDN of your Good Proxy server

l Click Database and configure your SQL server DB.

l Go to Settingsand configure your AD domains; configure the other settings as desired

l If a brand new installation of Docs (empty DB), click on Repositories and add File Shares andSharePoint sites as desired, adding users in accordance with the v1.5 Beta edition of theGEMSInstallation and Configuration Guide.

3. Configure Good Control

a. Add your GEMS host(s) to the Entitlement to Good Enterprise Services app:


n Scroll down or search for "Entitlement to Good Enterprise Services", click it, then open the SERVERS tab


This entitles the Presence, Follow-Me, and Directory Lookup services—all three—and needs to becompleted only once.

b. Add the Entitlement to Good Enterprise Services app to at least one Application Group like Everyone:


n Click on Everyone

n Click , search for "Entitlement to Good Enterprise Services", enable its checkbox, then click OK

c. Add your GEMS host(s) to Feature - Docs Service Entitlement:


n Scroll down or search for "Feature - Docs Service Entitlement", click it, then open the SERVERS tab


d. Add the Feature - Docs Service Entitlement app to at least one Application Group like Everyone:


n Click on Everyone

n Click , search for "Feature - Docs", enable its checkbox, then click OK.





4. Configure LDAP in the GEMS Web Console to support Directory Lookup and Certificate Lookup (see"Configuring the Certificate Lookup Service" in theGEMS Installation and Configuration Guide").

Complete instructions, guidance, and feature descriptions are available in the 1.5 edition of theGEMS Installationand Configuration Guide for Administrators.

Additional Considerations1. GEMS Administrators are now added via Active Directory groups. Groups in Active Directory are directory

objects that reside within a domain and organizational unit container objects. Active Directory gives you theoption of creating new groups. Adding a group of administrators to your GEMS settings gives GEMSDashboard permissions to the entire group.

2. If you have a mixed environment (i.e., some servers on a previous version of GEMS and some upgraded tov1.5), the feature set enabled will be limited to the features common in both versions.

3. If upgrading from an ealier GEMS version configured with Docs, you will have to enter the Docs databasename manually.

4. When upgrading GEMS-Docs, user defined data sources may disappear from the client. To prevent this fromhappening, upgrade the client first. If there are any offline files, save them to an online resource beforeupgrading the client, otherwise offline files will be removed.

5. If an earlier version of GEMS is configured to disable SSL checking for Microsoft Exchange, after upgradeadmin will need to disable it again in the dashboard by going to Mail > Microsoft Exchange.

6. To ensure proper configuration of GEMS within your Windows Services environment, strict adherence to theconfiguration sequence for the Push Notification Service (PNS) documented in theGEMS Installation andConfiguration Guide, is strongly recommended. Please ensure that you configure the PNS Database beforeyou configure EWS Impersonation. Failure to follow the steps in the sequence listed could result inconnectivity issues.

If, during GEMS configuration, GEMS is unable to connect to its Push Notification database, this usuallymeans that the configuration steps listed were executed in the incorrect order; that is, typically Mail >Microsoft Exchange configuration information was applied in the GEMS Dashboard before configuring theMail > Database information. If you encounter this problem, use the following procedure to resolve theissue.






7. To enable external contact labelling—meaning contacts outside of your organization—you will need to insert<add key="ENABLE_SOURCE_NETWORK" value="true" /> to GoodConnectServer.exe.config in the<appSettings> section.








Example:

{quote}<configuration>

<appSettings>...


</configuration>{quote}

8. A new parameter—DB_PURGE_HOURS—has been added to theGoodConnectServer.exe.config. It sets themaximum age, in hours, of missed messages and invitations before they are automatically deleted (purged).See Appendix C in theGEMS Installation and Configuration Guide.

Acknowledged Limitationsl Web Proxy component for Docs does not support NTLM and Basic Authentication in this release. GEMS-Docs

currently supports web proxy with no-authentication only.

l When upgrading GEMS Docs, user-defined data sources may disappear from the client. To prevent this fromhappening, upgrade the client first (to Good Work 1.5). If there are any offline files, save them to an onlineresource before upgrading the client, otherwise offline files will be removed.

l NTLM and Basic authentication are not supported by the Docs service in GEMS 1.5 release.


Description

FIRST-9348 In certain environments, unable to test and verify Exchange credentials in the GEMSdashboard

FIRST-9321 [Docs] Client times out upon server taking ≈323 seconds to recursively explore largedirectory trees

FIRST-9423 Intermittent outages with PNS to Apple devices

FIRST-9184 [Cloud] Good Control to GEMS certificate trust notification failure

FIRST-9545 [iOS] Inconsistent Presence indication

FIRST-9635 Push notifications not sent due to connection error triggered by a variation in IIS/Exchangeenvironment

FIRST-9125 Unable to upgrade GEMS server to 1.4 due to Java versioning error

FIRST-8479 [Connect] Race condition issue in certain environments when multiple hosts use the sameConnect DB

FIRST-9167 GEMS 1.2.16.32 to 1.4.17.23 upgrade successful, but schema error in Connect logs andLync Test Dashboard Error

FIRST-9752 In a hybrid on-prem/O365 organization, only on-prem users are getting push notificationsG3SERVER-2186 In certain environments, Good Technology Common Services cannot be stopped cleanly




Defect TrackingNo.

Description

G3SERVER-4975 Lookup (via EWS) doesn't always use proxy even when "Use the same web proxy settings toconnect to an externally hosted Exchange" is enabled

G3SERVER-5002 Not all EWS calls go through the web proxy setting to connect to an externally hostedExchange

G3SERVER-5096 ActiveMQ broker should bind to all IP-addresses


Description



GEMSS-2702 When changing the configuration of the Office Web Apps Server you will need to restartwindows common services

G3SERVER-3606 [GEMS-Mail][DataBase] After changing the Mail database, GEMS cannot connect to the newDB.Workaround: After DB change, enter Exchange service account password via Dashboard. Thisis because the password is encrypted with a key that was present in the previous databaseand can no longer be decypted with the key from the new/changed DB



GEMSS-983 Before upgrading from the remote Good Share web console, manually create the directorystructure C:\Program Files(x86)\Good Technology\Good Share Server\ and copy over theconfig.xml file, then run the installer

GEMSS-2793 [Docs] When searching for AD users or groups in admin- or user-defined repositories, theFQDN of the domain should be used


GEMSS-2901 Adding a data source with a purely numeric name (e.g., "112233") will produce an emptyfolder message; when attempting to delete, a data source not found error is thrownWorkaround: End-user can login on self-service portal for Docs(https://<localhost>:8443\docsconsole) and change the repository name to supported characters(i.e., not purely numeric)



40

Good Enterprise Mobility Server™ (GEMS)Version 1.4 (SR 1)


Issued: 21-Apr-15


In This Service ReleaseThis service release contains important fixes to the core release (1.4.14.19) issued 27-Mar-15, as well as a securityupdate governing the cutoff time for displaying notification details.

Added Security Feature for Detailed NotificationsAfter a configurable amount of time (12 hours by default), if Good Work has not been unlocked and actively usedon a device, the GEMS Push Notification Service will remove details about individual email messages fromnotifications displayed on the device. Message details in notifications sent by the GEMS Push Notification Servicewill resume when Good Work is next unlocked and used on the device.

See "Detailed Notifications Cutoff Time" under "Configuring the Push Notification (Mail) Service, Logging andDiagnostics" in theGEMS Installation and Configuration Guide for additional guidance.

Java 7 RequirementJava Runtime Environment (JRE) 7 Update 67 (7up67) or higher Java 7 update for Microsoft Windows (64-bit) isavailable for download directly from Oracle. Only 64-bit Java is supported.

Note: Java 8 is not supported at this time.

Supported UpgradesGEMS 1.4 (1.4.14.19)ð GEMS 1.4 SR 1 (1.4.17.23)

GEMS 1.3 (1.3.10.8)ð GEMS 1.4 (1.4.17.23)

GEMS 1.2 (1.2.16.32)ð GEMS 1.4 (1.4.17.23)

Acknowledged Limitationsl Java 8 is not supported at this time.

Version 1.4 (SR 1) Release Notes




41


Description

GEMSS-2228 [Connect] Unhandled exception on subscriptionsGEMSS-1317 [Docs] Users from child domain are not able to get the data source listGEMSS-1298 [Docs] No file size is shown for files at the root SharedWithMe viewGEMSS-1220 [Docs] Files cannot be uploaded in SharedWithMe viewGEMSS-1219 [Docs] Uploaded file under flat view does not use storage pathGEMSS-1217 [Docs] Return date not modified for files in SharedWithMeG3SERVER-4471 [EWS Listener] Notification processing queue stallsG3SERVER-4368 [PNS] When device is wiped or the app is removed, notifications are still sent for next 72

hours


Description

G3SERVER-3577 [Mail]: admin password is not able to include comma. Workaround: Use Password withouta comma

G3SERVER-3654 [Dashboard] Username is prepopulated as “sa” in Mail > Database page by defaultG3SERVER-3606 If the database GEMS is connecting to is changed, then the exchange service account info

need to be re-saved from the dashboard.

G3SERVER-4198 Lync 2013 installer cannot find PowerShell 3.0 or PowerShell 4.0 on Windows Server 2012R2 system

G3SERVER-4168 Once the DB connection details are entered in the installer for a fresh installation, adminneeds to go to the GEMS dashboard and add it again. Workaround: Add DB connectiondetails in dashboard section too

G3SERVER-4338 In some environments currently using Good Work EA, push notification delay of up to 20minutes after email received is experienced intermittently.

GEMSS-411 [Presence] [Lync Presence Provider] Lync Presence Provider stops receiving presenceupdates for a few contacts after restarting Common Services. Workaround: Restart LPP

GEMSS-835 [Docs] SharePoint URLs are not validated by Docs Configuration ConsoleGEMSS-841 [Docs] Folders/document library is not removed form SharePoint URLs when SP data

sources are added using the Docs Configuration ConsoleWorkaround: User needs to enter each SP data source with a URL to the desired SharePointsite or subsite

GEMSS-890 The first time one or more new Connect servers are started simultaneously in a Connectcluster, a race condition may exist that can cause Active Directory cached information to


42

Defect TrackingNo.

Description

contain duplicate entries. Workaround: Do not start all servers in the cluster at the sametime

GEMSS-1043 [KCD] Docs service does not currently support KCDGEMSS-1051 If Docs web console is not installed, an invalid Docs Service Configuration screen is displayed

in GEMS Dashboard when "Docs" configuration is invokedGEMSS-1056 Installation of Docs Web Console displays an incorrect version number on GEMS

Dashboard. Workaround: Restart your browser to update the version number in theDashboard.

GEMSS-1084 Docs web console allows adding user-defined Data Source to be enabled without either aFile Share or SharePoint type being selected

GEMSS-1095 Good Drive displays error page when invoked from Settings.






l Good Work Client User Guide for Android Devices

l Good Work Client USer Guide for iOS Devices




Build: 1.4.14.19Issued: 27-Mar-15 | Updated: 28-Mar-15


In This ReleaseGood has implemented an array of important GEMS services and capabilities, including a Docs service that allowsmobile users to access, sync, and share their enterprise file server and SharePoint documents, enhanced VIPnotifications, an expanded Android push notifications service, Good MSM integration, a GAL directory lookupservice supporting search and display from Good Launcher, and an improved installer to automate databaseschema creation.

For deployment planning guidance, see theGEMS Deployment Planning Guide. For guidance and instructions oninstalling and configuring GEMS, see theGEMS Installation and Configuration Guide.


l Android Push Notifications Service

o Added support for Google Cloud Messaging to send push notifications to Good Work for Android clients

l Rules-based VIP Notification Service for Email push notifications

o Rules can be set for Sender, Subject, and Priority fields of an email

o Automatic passing of rules from Good Work clients to GEMS

o Rules can be synchronized across devices

o Custom sound files can be associated with the rules

l Directory Lookup Service

o Ability to look up first name, last name, and picture from the GAL to be displayed within Good Launcher

l Automated schema creation via GEMS Installer

o Create database schema for GEMS Mail and GEMS Connect services as part of product installation

l Good Docs Service

o Enable SharePoint and NAS file access for Good Work clients

o Server-based API to do file upload, download, browse, and save from SharePoint and NAS-based storage

l Follow-Me Service

o Supports Launcher service on Good Work clients





l Connect External Contacts

o When enabled in the Good Connect service, Good Connect clients will display federated contacts outsideof your organization with a label next to their name. A federated contact is a member of a company whoseOffice Communications Server is federated (connected) with your company’s Office CommunicationsServer

l Bug Fixes

Java 7 RequirementJava Runtime Environment (JRE) 7 Update 67 (7up67) or higher Java 7 update for Microsoft Windows (64-bit) isavailable for download directly from Oracle. Only 64-bit Java is supported.


Supported UpgradesGEMS 1.3 (1.3.10.8)ð GEMS 1.4 (1.4.14.19)

GEMS 1.2 (1.2.16.32)ð GEMS 1.4 (1.4.14.19)

Tip: During an upgrade, when prompted to enter database information for the Mail/Core and Connect DBs, besure to enter the database details that apply to your current (pre-1.4) GEMS deployment.

Additional Considerations1. To ensure proper configuration of GEMS within your Windows Services environment, strict adherence to the

configuration sequence for the Push Notification Service (PNS) documented in theGEMS Installation andConfiguration Guide, is strongly recommended. Please ensure that you configure the PNS Database beforeyou configure EWS Impersonation. Failure to follow the steps in the sequence listed could result inconnectivity issues.

If, during GEMS configuration, GEMS is unable to connect to its Push Notification database, this usuallymeans that the configuration steps listed were executed in the incorrect order; that is, typically Mail >Microsoft Exchange configuration information was applied in the GEMS Dashboard before configuring theMail > Database information. If you encounter this problem, use the following procedure to resolve theissues:

a. From the GEMS Dashboard, clear out theMail > Exchange Server configuration and click Save.


c. Restart theGood Technology Common service in Windows Service Manager.

d. Repopulate theMail > Exchange Server configuration in the GEMS Dashboard and save yourchanges.







2. To enable external (federated) contact labelling—meaning contacts outside of your organization—you willneed to insert <add key="ENABLE_SOURCE_NETWORK" value="true" /> to GoodConnectServer.exe.config inthe <appSettings> section.

Example:

<configuration><appSettings>...


</configuration>

3. The GEMS Docs Service Configuration Dashboard displays "Version 3.1.369" instead of the correct GEMS1.4.14.19 version number. This is a temporary cache issue. The version number updates once you restart thebrowser.



Description

FIRST-8723GEMSS-1155

Presence issue on Good Work

FIRST-8337

GEMSS-492GEMSS-490

In some environments, Good Technology Connect Service intermittenly crashes


Description


G3SERVER-3654 [Dashboard] Username is prepopulated as “sa” in Mail > Database page by defaultG3SERVER-3606 If the database GEMS is connecting to is changed, then the exchange service account info

need to be re-saved from the dashboard.

G3SERVER-4198 Lync 2013 installer cannot find PowerShell 3.0 or PowerShell 4.0 on Windows Server 2012R2 system

G3SERVER-4168 Once the DB connection details are entered in the installer for a fresh installation, adminneeds to go to the GEMS dashboard and add it again. Workaround: Add DB connectiondetails in dashboard section too

G3SERVER-4338 In some environments currently using Good Work EA, push notification delay of up to 20



Defect TrackingNo.

Description

minutes after email received is experienced intermittently.


GEMSS-835 [Docs] SharePoint URLs are not validated by Docs Configuration ConsoleGEMSS-841 [Docs] Folders/document library is not removed form SharePoint URLs when SP data

sources are added using the Docs Configuration ConsoleWorkaround: User needs to enter each SP data source with a URL to the desired SharePointsite or subsite

GEMSS-890 The first time one or more new Connect servers are started simultaneously in a Connectcluster, a race condition may exist that can cause Active Directory cached information tocontain duplicate entries. Workaround: Do not start all servers in the cluster at the sametime

GEMSS-1043 [KCD] Docs service does not currently support KCDGEMSS-1051 If Docs web console is not installed, an invalid Docs Service Configuration screen is

displayed in GEMS Dashboard when "Docs" configuration is invokedGEMSS-1056 Installation of Docs Web Console displays an incorrect version number on GEMS

Dashboard. Workaround: Restart your browser to update the version number in theDashboard.

GEMSS-1084 Docs web console allows adding user-defined Data Source to be enabled without either aFile Share or SharePoint type being selected

GEMSS-1095 Good Drive displays error page when invoked from Settings.




l Developer’s Preview: Services Configuration for Analytics and Docs







Build: 1.3.10.8Issued: 26-Feb-15 | Last Updated: 3-Mar-15


In This ReleaseGEMS 1.3 introduces a greatly improved end-user experience for new email notifications in the iOS NotificationCenter. Notifications now display reliably when Good Work is suspended in the background or even when it isnot running at all. This results in an end-user experience wherein they can reliably know which messages theyhave received without having to enter the Good Work app.

In prior versions, new email notifications would only display when Good Work was successfully woken up fromthe background by iOS after receiving a wake-up push notification from GEMS. In the new design, GEMS will stillpush a Good Work wake-up notification and will now also push a notification to the iOS Notification Center sothat it does not rely on Good Work being woken up by iOS to provide the end-user notification.

When permitted by iOS, Good Work will wake up and synchronize in the background as a result of thesenotifications. Otherwise, the new messages will quickly synchronize after the end user resumes Good Work as aresult of seeing Notification Center notifications.

The GEMS notification service will now send, per the policy configuration in Good Control, the appropriatecontent (i.e., subject, from, etc.) in the notification messages to Good Work, making notifications more robust.

Refer to theGood Work Product Guide, available from the Good Admin Portal, for details on configuring policy-driven notifications.

What's Newl Policy-driven notifications (server-triggered)

l Bug Fixes

Supported UpgradesGEMS 1.2.16.32ð GEMS 1.3.10.8

Upgrade Steps1. FromGoodEnterpriseMobilityServerSetup.1.3.10.8.zip, extract the file named pushnotify-dbmanager-

<version>.sql, located in the EWS folder.

2. Locate the appropriate SQL script file in the EWS folder in accordance with the following criteria:

a. If you are installing GEMS for the first time, create a new SQL database (e.g., "EWS"), then use sqlserver_create_utf8_0.1.1.sql.

© 2016 Good Technology 47


b. If you are replacing the database, use sqlserver_drop_utf8_0.1.1.sql.

c. If you are upgrading the database from a previous version, use sqlserver_upgrade_from_0.1.1_to_0.1.2.sql.

3. Open the appropriate <filename>.sql file in Microsoft SQL Server Management Studio and execute the scriptagainst the GEMS-PNS database (i.e., EWS).

4. Run the GEMS executable.

The installer will detect previously installed versions of GEMS and offer an upgrade option. Please selectUpgrade, then follow the on-screen instructions in accordance with yourGEMS Administration Guide,available from the Good Admin Portal.

5. Restart the Presence service (i.e., Lync Presence Provider [LPP]).

Note: There is no update to the GEMS Connect database. As such, it can remain "as is."

Java 7 RequirementJava Runtime Environment (JRE) 7 Update 67 (7up67) or higher Java 7 update for Microsoft Windows (64-bit),available for download directly from Oracle.


Additional Considerations1. To improve performance and stability in a GEMS Connect implementation, add <gcServer

enabled="true"/> to GoodConnectServer.exe.configwithin <runtime/>.

Example:

<configuration><runtime> <gcServer enabled="true"/>

…</runtime> </configuration>

The gcServer parameter controls how memory is managed in the .NET framework. Setting thisparameter to true allows for better memory management on a multiprocessor server. For more information,please reference this Microsoft KB article.

2. When upgrading instances of GEMS in a cluster you should first upgrade the database using the upgradescript provided (see Step 2 above under Upgrade Steps), before upgrading any of the instances in the cluster.Once the database has been successfully upgraded, use the GEMS installer to upgrade each GEMS instance inturn.

For upgrade situations in which there are multiple GEMS instances pointing to a shared (common) database,upon upgrading the database, new features will not be available until all GEMS instances have beenupgraded. In a mixed-version environment, each GEMS instance will continue to function with the earlier







https://msdn.microsoft.com/en-us/library/office/hh364754(v=office.14).aspx

version’s features. Running in a mixed-version environment for an extended period of time is notrecommended.

Important: To ensure proper configuration of GEMS within your Windows Services environment, strictadherence to the configuration sequence for the Push Notification Service (PNS) documented in theGEMSInstallation and Configuration Guide, is strongly recommended. Please ensure that you configure the PNSDatabase before you configure EWS Impersonation. Failure to follow the steps in the sequence listed couldresult in connectivity issues.

During GEMS configuration, if GEMS is unable to connect to its Push Notification database, this usuallymeans that the configuration steps listed were executed in the incorrect order; that is, typically Mail >Microsoft Exchange configuration information was applied in the GEMS Dashboard before configuring theMail > Database information. If you encounter this problem, use the following procedure to resolve theissue.







l No corporate proxy support for Cloud O365 from on-prem GEMS deployments. Workaround: Use atransparent proxy instead, or use a GEMS-in-the-Cloud deployment.


Description

GEMSS-889 When the session record is deleted in the database, iOS users can't sign in automatically andAndroid users can't sign in at all.

GEMSS-487 Remove presence\ping from public APIGEMSS-467 HTTP 200 code for presence bundle not listed in karaf log

GEMSS-527 Connect crashes while client connections are in background. See Point 1 above underAdditional Considerations.

G3SERVER-3750 Policy-driven GEMS iOS support for sending Sender/Subject to client




Description

GEMSS-158 Lync 2013 installer cannot find PowerShell 3.0 or PowerShell 4.0 on Windows Server 2012R2 system


GEMSS-433 Presence bundle API calls to honor subscriptions not configured in HTTP codes

GEMSS-439 Presence service requires the user to run the provisioning through the dashboard afterupgrade for the service to start. Workaround: When configuring Presence, click Test, thenclick Save.


G3SERVER-3654 [Dashboard] Username is prepopulated as “sa” in Mail > Database page by defaultGEMSS-937 [Connect] When you move a Lync contact between groups on the desktop, Connect may

show the contact as offline. Workaround: On the Connect client, sign out and sign in toresolve.

GEMSS-955 [Connect] When a server is taken down or crashes, Connect clients may need to sign outand sign in again if they observe connection or chat send/receive issues.

GEMSS-890 GEMS Connect service issue due to race condition










51


Build: 1.2.16.32Issued: 13-Jan-15


In This ReleaseGood Technology continues its rapid delivery of Good Enterprise Mobility Server (GEMS) supporting a growinglist of services. In this release, APIs for the new Docs file sharing service and the new Analytics event collectionsystem and logging service are both exposed to Good’s developer community in preparation for the full rolloutof support of these services in 2015.

What's Newl Admin related Features

o Support for O365 with EWS Notifications

o Support for Hosted Exchange with EWS Notifications

o Support for Web Proxy (NTLM, Basic, Anonymous ) with EWS Notifications

o Expose GEMS versions through Dashboard and log files

o Automatic creation of self-signed certificates through installer

o Advanced Exchange configuration tests from Dashboard for EWS Notifications

l Developer-only Features (not yet integrated with client apps)

o Document sharing service API

n Upload, Download, View, Save of documents

n SharePoint and SharePoint Online

n Local file store support

o Analytics

n API to collect events from applications

Supported Upgradesl GEMS 1.1.29.57ð GEMS 1.2.16.32

l GEMS 1.1.38.70ð GEMS 1.2.16.32


52

Upgrade StepsIf you are upgrading from a previous version of GEMS:

1. Extract the database scripts from the installer zip file (GoodEnterpriseMobilityServerSetup.1.2.16.32.zip) .Scripts are located in:\GoodEnterpriseMobilityServerSetup.1.2.16.32.zip\GoodEnterpriseMobilityServer\EWS\pushnotify-dbmanager-0.2.16-sqlserver.zip\pushnotify-dbmanager-0.2.16\gcsmail-db-sqlserver\

2. Run the SQL script sqlserver_upgrade_from_0.0.1_to_0.1.1.sql against the current database to which GEMSEWS is connected.

3. Run the GEMS executable.

4. Restart the Presence service (i.e., Lync Presence Provider [LPP]).

Note: The installer will detect previously installed versions of GEMS and offer an upgrade option. Please selectUpgrade, then follow the on-screen instructions in accordance with your GEMS Installation and ConfigurationGuide for Administrators.

Additional ConsiderationsWhen upgrading instances of GEMS in a cluster you should first upgrade the database using the upgrade scriptprovided (see Step 2 above under Upgrade Steps), before upgrading any of the instances in the cluster. Once thedatabase has been successfully upgraded, use the GEMS installer to upgrade each GEMS instance in turn.

For upgrade situations in which there are multiple GEMS instances pointing to a shared (common) database,upon upgrading the database, new features will not be available until all GEMS instances have been upgraded. Ina mixed-version environment, each GEMS instance will continue to function with the earlier version’s features.Running in a mixed-version environment for an extended period of time is not recommended.

Important: To ensure proper configuration of GEMS within your Windows Services environment, strictadherence to the configuration sequence for the Push Notification Service (PNS) documented in theGEMSInstallation and Configuration Guide, is strongly recommended. Please ensure that you configure the PNSDatabase before you configure EWS Impersonation. Failure to follow the steps in the sequence listed couldresult in connectivity issues.

During GEMS configuration, if GEMS is unable to connect to its Push Notification database, this usually meansthat the configuration steps listed were executed in the incorrect order; that is, typically Mail > MicrosoftExchange configuration information was applied in the GEMS Dashboard before configuring theMail >Database information. If you encounter this problem, use the following procedure to resolve the issue.







53




54


Description

FIRST-8080 Presence Service does not display indicator for certain users in Good WorkFIRST-7953 Good Work fails to process push notifications from GEMSFIRST-7889 Setting presence in Connect app not working in GEMS (Part II of FIRST-7719)

FIRST-7794 Beta-3 presence indicator not updating in Good Work until restart

Known LimitationsNo corporate proxy support for Cloud O365 from on-prem GEMS deployments.Workaround: Use a transparent proxy instead or use a cloud GEMS deployment.


Description

GEMSS-158 Lync 2013 installer cannot find PowerShell 3.0 or PowerShell 4.0 on Windows Server 2012R2 system


GEMSS-439 Presence service requires the user to run the provisioning through the dashboard afterupgrade for the service to start. Workaround: When configuring Presence, click Test, thenclick Save.


G3SERVER-3654 [Dashboard] Username is prepopulated as “sa” in Mail > Database page by default









55

Good Enterprise Mobility Server™ (GEMS)Version 1.1 (SR)Release Notes

Build: 1.1.38.70Issued: 17-Nov-14 | Updated: 19-Nov-14


In This Releasel Auto-generation of Self-Signed SSL Certificate with Installer; eliminates the manual step to create a self-signed

certificate to access GEMS Dashboard for configuration

l Installer improvement; bundles MSSQL JDBC 4.0 DLL with the product package

l Upgrades from v1.0 and v1.1

l Ability to restrict SSL certificates used for Lync authentication with friendly names

l Push Notification improvement to handle Exchange crashing or failing over

l Addition of GEMS version number in log files

l Auto lockout of Dashboard after 10 consecutive failed attempts

l Bug fixes

Important Installation Note: To ensure proper configuration of GEMS within your Windows Servicesenvironment, strict adherence to the configuration sequence for the Push Notification Service (PNS) documentedin theGEMS Installation and Configuration Guide, is strongly recommended. Please ensure that you configure thePNS Database before you configure EWS Impersonation. Failure to follow the steps in the sequence listed couldresult in connectivity issues.

During GEMS configuration, if GEMS is unable to connect to its Push Notification database, this usually meansthat the configuration steps listed were executed in the incorrect order; that is, typically Mail > MicrosoftExchange configuration information was applied in the GEMS Dashboard before configuring the Mail > Databaseinformation. If you encounter this problem, use the following procedure to resolve the issue.


1. Clear out the Mail > Exchange Server configuration and click Save.

2. Make sure the information in Mail > Database is correct.

3. Restart the Good Technology Common service.

4. Repopulate the Mail > Exchange Server configuration and save your changes.

Fixed Issues

Version 1.1 (SR) Release Notes


56

Defect TrackingNo.

Description

G3SERVER-3190 Push notifications stop due to exception in StreamerImpl.removeUsers handlerG3SERVER-3094 GEMS has no account lockout policy after 10 consecutive failed attemptsFIRST-7664 Lync pool cannot be used with GEMS deploymentFIRST-7794 Beta-3 Presence indicator isn't updating in Good Work without a restartFIRST-7868 Beta-3 Presence service crashes after receiving sub-requestsFIRST-7882 Push Notifications fail when HTTP header size is greater than 3500 bytes


Description

G3SERVER-3118 After upgrade dashboard doesn’t respond for 5-7 minutes. Workaround: Wait; self-correctsafter 5 minutes; only happens after upgrades.

G3SERVER-3336 [Uninstall] No confirmation message pop-up on uninstall completionG3SERVER-1265 Use of a corporate web proxy in digest or NTLM mode with GEMS Push Notifications is

currently not supported. Workaround: Use a basic or anonymous mode of authentication onyour web proxy configured with your GEMS Mail Push Notification Service

G3SERVER-2228 Dashboard is not compatible with IE 9. Workaround: Use IE 10 or laterG3SERVER-3069 If any extra OSGi configuration is set (outside of admin console), the admin will have to

reset those configurations after upgrade. Workaround: After upgrades, manually reset theextra configurations done outside of the admin console

G3SERVER-3030 Dashboard URL is case sensitive. Workaround: Use proper casing or bookmark the URLG3SERVER-2639 For autodiscover to use SCP, the domain name should not be set to fully qualified domain

name. Workaround: Do not use the FQDNG3SERVER-2186 Stopping the "Good Technology Common services" manually sometimes doesn’t stop it

cleanly. Workaround: Try a manual stop againG3SERVER-3105 Connections error when exceeding Exchange set limitations on 2013 service account

connections. Workaround: You can override it in web.config by adding the following nodeunder appSettings XML node in web.config (it sets it to 10) and restartingMSExchangeServicesApppool:

add key="HangingConnectionLimit" value="10" (append xml tags)

web.config for EWS app pool can be found at: C:\Program Files\Microsoft\Exchange

Server\V15\ClientAccess\exchweb\ews. Location may vary depending on Exchange Installationdirectory. Also, please note that this change needs to be made on Mailbox Server(s) wherethe users active database exists.

G3SERVER-3037 Cancelling an upgrade midway through the installer leaves a backup directory behind.


57

Defect TrackingNo.

Description

Workaround: Manually delete the backup directoryG3SERVER-3150 When launched in another tab on the browser and you copy a deep link, GEMS logs out the

admin from all the tabs. Workaround: Copy the URL localhost:8443/dashboard, instead ofany deep link

G3SERVER-2325 Sometimes, upon resuming from background, incorrect presence for contacts shows up.Workaround: Self-corrects with the next automatic subscription triggered by a client action

G3SERVER-3084 LPP (Presence) doesn’t start correctly after upgrades. Workaround: Manual restart, happenswith upgrades only








58


Build: 1.1.29.57Issued: 6-Oct-14


In This ReleaseGood Technology is pleased to introduce the new Good Enterprise Mobility Server (GEMS). Leveraging a services-based approach to integrated enterprise mobility, the service integration offered by GEMS currently comprisesConnect (IM), Presence (LPP), and Push Notifications.

The Push Notifications Service (PNS) accepts push registration requests from hand-held mobile devices—iOS,Android etc.—and then communicates with Microsoft Exchange via its Exchange Web Services (EWS) protocol tomonitor the user's enterprise mailbox for changes.

TheConnect service boosts user communication and collaboration with secure instant messaging, corporatedirectory lookup, and user presence from an easy-to-use interface on IT-provisioned mobile devices.

The Presence service furnishes the Lync Presence Provider (LPP) to third-party Good Dynamics applications—giving them a powerful add-in for mobile collaboration.

Hence, building on the Connect and Presence services launched in v1.0, this GEMS v1.1 release adds thefollowing features:

l Push Notifications for email through EWS

l Multi-tenancy support for EWS Push Notifications

l HA and DR support for Presence and Push Notifications

l GEMS Event Log integration

l Integrated Authentication for Exchange and SQL Server

l Bug Fixes

Installation/UpgradeDeployment of v1.1 requires a fresh installation of the server and database in accordance with the instructions intheGEMS Installation and Configuration Guide. Please do not attempt to upgrade from earlier beta and/or testreleases.

Known Issues



59

Defect TrackingNo.

Description

G3SERVER-3094 Currently GEMS doesn't have account lockout policy. Workaround: Limit the number ofconsecutive failed login attempts to the Dashboard to prevent a brute force attack aimed atunauthorized access to GEMS

G3SERVER-1265 Support for Good Server APNS bundle to use my corporate web proxy (with Digestauthentication) does not work with the default libraries in GEMS. Workaround: UseAnonymous or Basic authentication if Web Proxy needs to be configured for APNS

G3SERVER-820 Aging for push channel registration (in current release the push channel is not deleted if thedevice removes the container or if the user is blacklisted for a longer period) causes recordsnot to be purged for inactive devices. Workaround: None, this is an optimization with no enduser effect

G3SERVER-2228 Dashboard is not compatible with IE 9. Workaround: Use IE 10 or later

G3SERVER-3069 If any extra OSGi configuration is set (outside of admin console), the admin will have toreset those configurations after upgrade. Workaround: After upgrades, manually reset theextra configurations done outside of the admin console

G3SERVER-3030 Dashboard URL is case sensitive. Workaround: Use proper casing or bookmark the URL

G3SERVER-2639 For autodiscover to use SCP, the domain name should not be set to fully qualified domainname. Workaround: Do not use the FQDN

G3SERVER-2186 Stopping the "Good Technology Common services" manually sometimes doesn’t stop itcleanly. Workaround: Try a manual stop again

G3SERVER-3105 Connections error when exceeding Exchange set limitations on 2013 service accountconnections. Workaround: You can override it in web.config by adding the following nodeunder appSettings XML node in web.config (it sets it to 10) and restartingMSExchangeServicesApppool:

add key="HangingConnectionLimit" value="10" (append xml tags)

web.config for EWS app pool can be found at: C:\Program Files\Microsoft\Exchange

Server\V15\ClientAccess\exchweb\ews. Location may vary depending on Exchange Installationdirectory. Also, please note that this change needs to be made on Mailbox Server(s) wherethe users active database exists.

G3SERVER-3039 Cancelling an upgrade midway through the installer leaves a backup directory behind.Workaround: Manually delete the backup directory

G3SERVER-3150 When launched in another tab on the browser and you copy a deep link, GEMS logs out theadmin from all the tabs. Workaround: Copy the URL localhost:8443/dashboard, instead of anydeep link

GEMS Presence Issues

G3SERVER-2325 Sometimes resume from background, incorrect presence for contacts shows up.Workaround: Self-corrects with the next automatic subscription triggered by a client action


60

Defect TrackingNo.

Description

G3SERVER-3118 After upgrade dashboard doesn’t respond for 5 minutes. Workaround: Wait; self-correctsafter 5 minutes; only happens after upgrades

G3SERVER-3084 LPP (Presence) doesn’t start correctly after upgrades. Workaround: Manual restart, happenswith upgrades only


61








62


Build: 1.0.18.49Issued: 5-Aug-14


Good Enterprise Mobility Server (GEMS) is a new server pioneered by Good to provide standardized access tomobile backend systems. Eventually replacing and standardizing a variety of servers currently supported byGood, this v1 release of GEMS supports the Connect and Presence services with more services soon to be added.Built on Good Dynamics—the Secure Mobility Platform for building, deploying, and managing secure mobileapps—GEMS will initially provide reusable mobile backed services around Email, IM, and Presence, along withother third party services. These services are available for consumption by app developers within their ownapplications or directly from Good and Good Partner applications.

In This ReleaseThis release includes the following important components and features:

l Server-based Presence Service, providing real-time presence information for Lync users.

l Good Enterprise Mobility Server (GEMS) with Connect, providing real-time instant message (IM) capability andpresence information for Lync users.

l Single installer for all GEMS components.

l Unified configuration dashboard for setting up and maintaining Presence and IM.

Minimum GD Requirementsl Good Control v1.7.38.19

l Good Proxy v1.7.38.14


Description

G3SERVER-2697 When installing GEMS Connect on Windows 2012 R2 for Lync 2013, the installer will showthat PowerShell is not installed. If you have PowerShell 4.0 installed, please disregard thiserror

G3SERVER-2497 Under certain circumstances, after a GEMS Connect server restart, reconnecting Connect


63

Defect TrackingNo.

Description

clients may not see updated contact list presence information. To resolve, sign out and signback in again

G3SERVER-1897 When accessing the GEMS configuration dashboard, if the user session expires you canrestart the browser to continue to configure the server

G3SERVER-1886 JRE 7 is required. The environment cannot have global settings that refer to other JREversions


64








release notes for gems - help and manuals · l notificationlocalizationsupportforgoodwork[ios]...

Documents