Install & Register Launchpads

IMPORTANT:  The registration configuration profile for macOS mass deployment can only be distributed via MDM to Mac Launchpads. Mass deployment installers for Mac are supported in MAM 7.1 UAT.

1. Click Download to download the Mac registration configuration profile. The MAM_LP_Registration_<token>.mobileconfig profile is downloaded.
   where
   <token> corresponds to the first four digits of its registration token. This makes it easier to identify the correct Mac registration configuration profile and registration token in your environment.
2. Click Download to download the installer for Mac. The GroundControl Launchpad.dmg file is downloaded.
3. Extract the GroundControl Launchpad.pkg file from the GroundControl Launchpad.dmg.
4. Upload the Mac registration configuration profile and the GroundControl Launchpad.pkg file to your MDM and distribute it to your Mac Launchpads.
   On launch, the Launchpads are registered.
   NOTE: Resetting the Launchpad will automatically relaunch and re-register to the same organization, as long as the auto registration profile remains installed on the Mac.

For Windows mass deployment installers, MAM generates a command line string for automatically registering the Launchpads.

Click the copy icon to copy the command line string to your clipboard. Save this information.

The command line string should appear similar to the examples below:

Windows
msiexec /i "MAMMassInstaller-x64-6.6.0 (12410).msi" GCHOST=groundctl.com GCTOKEN=12345abc-cede-4d9d-90b5-9de0ea78591e

where:

• GCHOST is the MAM Server hostname. For most organizations, this is groundctl.com.
• GCPROXY is the optional unauthenticated proxy:port. If missing, no proxy is used.
• GCLPNAME is the optional Launchpad name. If missing, the PC name is used.

Transfer the installer to your Desktop Engineering team, along with the appropriate command line strings (Windows).

Installation Requirements

• The Launchpad can be installed on any Mac running a supported Mac OS release. For additional information, see System Requirements.
• Launchpads requires that the local Mac user be a macOS local admin, or the GroundControl Launchpad.app must be installed in a directory the local user has full file permissions over.

Install the Interactive Mac Launchpad

Download the interactive Launchpad Mac DMG:

1. Log into the MAM admin console and navigate to the Launchpads tab and click Download Launchpad.
   1. In the Download Launchpad dialog, select Interactive Launchpad installer and select Mac from the OS list.
   2. Click Download to download the interactive installer.
   3. The Download Launchpad dialog displays the MAM Server and the MAM Org ID. Click the copy icon to copy the information to clipboard.
      Take note of them for use during interactive registration.
      Org ID is optional. This is only required if the user registering the Launchpad has a role in more than one organization, the server will register the Launchpad to the specific organization.
2. After the DMG is downloaded, distribute it to your Mac Launchpad.
3. Double-click the GroundControl Launchpad disk image to open.
4. Transfer the .app to the /Application directory. Requires macOS Admin.
5. Double-click the GroundControl Launchpad.app.
6. Accept the prompt to open the software.
7. Eject the disk image.

The Mobile Access Management Launchpad can be installed on any PC running a supported Windows operating system. For additional information, see the System Requirements.

Install the Interactive Windows Launchpad

Download the interactive Launchpad Windows EXE:

1. Log into the MAM admin console and navigate to the Launchpads tab and click Download Launchpad.
   1. In the Download Launchpad dialog, select Interactive Launchpad installer and select Windows from the OS list.
   2. Click Download to download the interactive installer.
   3. The Download Launchpad dialog displays the MAM Server and the MAM Org ID. Click the copy icon to copy to clipboard.
      Take note of them for use during interactive registration.
      Org ID is optional. This is only required if the user registering the Launchpad has a role in more than one organization, the server will register the Launchpad to the specific organization.
2. After the installer is downloaded, distribute it to your Windows Launchpads.
3. Double-click the Mobile Access Management Launchpad EXE to install.
4. Choose whether you will install for all users on the machine (recommended) or just for the local user.
5. For iOS-only MAM environments:
   1. Extract and install MobileDevice components bundled with iTunes using these instructions. This is required on Windows.
      NOTE: Android-only MAM environments do not require Apple MobileDevice components.

NOTE: This method of interactive registration does not apply to the Mass deployment installers.

After installation of the interactive installer, you must register the Launchpad using a Mobile Access Management user and password. Below are the instructions for interactive registration.

• Launch the MAM Launchpad app. An unconfigured Launchpad prompts for registration.
  
  • The Launchpad Name is used to identify this Launchpad computer to the MAM server. The Mac or PC computer name is entered by default.
  • The default server hostname “launchpad.groundctl.com” is correct for most organizations. If you are using a dedicated cluster, enter the correct name for your organization here.
  • If your network requires an unauthenticated proxy to access the MAM server, add that information here.
• Click Next.
• Enter your MAM user name and password.
• Enter the password for your account.
• In the Organization ID box, enter the ID for your organization that you saved earlier.
  
  • The Organization ID is only required when the user registering the 7.0 Launchpad has a role in more than one organization. The MAM server will register the Launchpad to the organization specified.
  • Launchpads running earlier than 7.0 do not support the input of an Organization ID.
  • If the user registering the Launchpad only has a role in a single organization, the MAM server registers the Launchpad without needing the Organization ID.
  • If the user registering the Launchpad has a role at more than one organization, and omits the Organization ID, the MAM server fails the registration and sends an error message to the Launchpad.

The app tests connectivity and connects to the MAM server.

DEPRECATED: This method has been deprecated. Imprivata recommends using the Mass Deployment workflow instead.

Use a text file to automatically register a Launchpad.

NOTE: This method of automated registration does not apply to the Mass deployment installers.

First, obtain a Launchpad Registration Token from Imprivata Support. Include the following in your request:

• The email address of the Mobile Access Management user for “Registered By”.
• An expiration date for your token, for example: 1 day or 30 days; 1 year or 2 years.

After you have obtained the token, create a text file named gc-auto-reg.txt with the following:

server: launchpad.groundctl.com

token: ABCD123456789

launchpad: FN-2187

• The server and token keys are required.
• A launchpad key is optional.

If included, that value will be used for the Launchpad name. If included, a value must be specified.

If omitted, Mobile Access Management uses the Mac or Windows system name for the Launchpad name.

NOTE: All Launchpads must have unique names.

Install the file gc-auto-reg.txt in the temporary folder of the Mac or Windows system:

• Mac: /tmp/gc-auto-reg.txt
• Win: %Temp%\gc-auto-reg.txt

Install this file before the Launchpad software is first run.

When this file is present and valid, the Launchpad app will skip the usual interactive registration steps, and automatically register and start up. If registration is successful, Mobile Access Management will delete the file from the temporary folder as it is no longer needed.

If registration fails due to an invalid file or expired token, the Launchpad will show the standard interactive registration screens.