Article ID: 18680
Product: GMC
Date: 15 August 2010

Title: Understanding OTAPing to Good Server version 6.0.x

Fact: Acronyms used:

GMMS = Good Mobile Messaging Server
GMC = Good Mobile Control Server
NOC = Network Operations Center
OTA = Over the Air


1. The customers’ Good Administrator adds user to the GMC. The GMC communicates this action to Good Secure NOC by way of the GMC. The user added to the GMC is reflected in our NOC. This user lschine@good.com is authorized to provision against GMMS server xyz.

2. GMC Updates the Good Secure NOC with the OTA PIN number. Only one pin number can exist for one user at any given time.

3. GMC tests whether the device will be able to connect (this is done behind the scenes).

4. "Authenticating"
The user has now downloaded the OTA installer stub and entered the email address and PIN. This is the file you get from get.good.com. When user enters the email address and Pin. The OTA installer on the device sends the user's email address and pin to NOC for verification.

5. "Securing Channel"
The OTA installer on the device sends the first provisioning request to the user’s corresponding sync server (GMMS – Exchange or Domino).

6. "Securing Channel"
The sync server (GMMS) sends the first provisioning response back.

7. "Securing Channel"
The OTA installer successfully retrieved the first provisioning response from NOC.

8. "Securing Channel"
The OTA installer on the device sends the second provisioning request to the sync server (GMMS).

9. "Securing Channel"
The sync server (GMMS) sends the second provisioning response back.

10. "Securing Channel"
The OTA installer successfully retrieves the second provisioning response from NOC.

11. "Downloading"
The OTA installer downloads the Good client application onto the device.

12. "Installing"
The client Good installer installs the Good client application on the device and then launches the Good application.

13. "Downloading Services"
The Good application on the device has now connected to the server and is requesting a connection map so that it can establish connection for various services (Email, Calendar, etc) with GMMS.

14. "Downloading Services"
The device sends establish connection requests for each connection in the map that it received in the previous step. GMMS will respond with connection responses for each request.

15. Device begins to sync data. At this point the device is provisioned and will begin to sync email, download calendar and contact information, etc.