Installing the TE Client on iOS

The Terminal Emulation Client for iOS is available for iOS version 6.1 or newer. It is supported on the following devices:

• iPad, 3rd & 4th generation

• iPad Mini

• iPhone 4, 4S, 5

• iPod, Touch 4th & 5th generation

Before you install the TE Client for iOS, you must rebuild the IPA file using a distribution profile and certificate associated with an Apple developer account. If you want to distribute the TE Client to more than 100 devices, you must have an iOS Developer Enterprise account.

The instructions below include information about creating a distribution certificate, app ID, and provisioning profile using the Apple Developer website, and then how to use the script provided by Wavelink to rebuild the IPA.

The tasks for creating the distribution certificate, app ID, and provisioning profile only need to be done once. After these tasks are complete, newer versions of the TE Client IPA files can be signed using the same certificate, ID, and profile.

You must build the IPA file on a computer running OS X. Your account on the machine must have administrative rights, and you must have Xcode installed, including the Command Line Tools. If you are replacing the icons for the app, the icons should be stored on the same computer, and should be 114 x 114 pixels and 57 x 57 pixels in PNG format.

• Rebuilding the IPA File with an iOS Developer Enterprise Account (recommended)

• Rebuilding the IPA File with an iOS Developer Account

Rebuilding the IPA File with an iOS Developer Enterprise Account

To create a distribution certificate:

1 Log in to your Apple Developer account and navigate to the Member Center.

2 In the Developer Program Resources section, click Certificates, Identifiers & Profiles.

3 Click on Certificates.

4 Create a new distribution certificate by clicking on the [+] button.

5 Select the In-House and Ad Hoc type.

6 Follow the onscreen instructions for creating and uploading a CSR.

7 Generate the distribution certificate and download it.

8 Open the Keychain Access application on the computer.

9 Import the distribution certificate by clicking File > Import Items and selecting the certificate. The name of the file should be ios_distribution.cer. When the certificate has been imported, it shows up in Keychain Access as "iPhone Distribution: [Company Name]".

To create a new App ID:

1 From the Member Center, create a new App ID.

2 Create a description that helps you identify the app. For the type of ID:

• If you choose Explicit App ID, use com.landesk.te

• If you choose a Wildcard App ID, use com.landesk.*

To create a new provisioning profile:

1 From the Member Center, click Certificates, Identifiers & Profiles.

2 Click on Provisioning Profiles.

3 Select In House as the profile type.

4 Select the App ID that you created.

5 Choose the distribution certificate you created and generate the provisioning profile, then download it.

To create the signed IPA file:

1 Open a terminal window and navigate to the location of the TE_iOS_unsigned.ipa file.

2 (Optional) If you are replacing the icons for the app, ensure they are saved locally.

3 Run the shell script ldresign_te.sh with the following command:

./ldresign_te.sh -a <path to unsigned IPA> -m <path to provisioning profile> -c <name of the certificate> -114 <path to 114x114 icon> -57 <path to 57x57 icon>

For example:

./ldresign_te.sh -a "TE_iOS_unsigned.ipa" -m "My_TE_Provisioning_Profile.mobileprovision" -c "iPhone Distribution: Company Name Here" -114 "My_Replacement_Icon_114.png" -57 "My_Replacement_Icon_57.png"

Or, if you are not replacing the icons:

./ldresign_te.sh -a "TE_iOS_unsigned.ipa" -m "My_TE_Provisioning_Profile.mobileprovision" -c "iPhone Distribution: Company Name Here"

The shell script creates TE_iOS.resigned.ipa.

Once you have the rebuilt IPA, you can distribute it using Wavelink Avalanche or another distribution method.

Rebuilding the IPA File with an iOS Developer Account

If you plan to manage fewer than 100 devices, you have the option to rebuild the IPA using an iOS developer account. If you will be managing more than 100 devices, this method is not recommended.