Soft lime

May 30, 2017 I remember how stable System 7.6.1 felt, the new UI overhaul in Mac OS 8 which felt so modern, the rocky initial transition to Mac OS X (I ran 10.0 on an iBook and found it to be so unusable I switched back to Mac OS 9 and then went to Mac OS X again with 10.1) that was then resolved and became a solid and fantastic OS. Nov 29, 2017 If you succeed in downloading the OS installation, your next step is to create a bootable USB or DVD and then reinstall the OS on your computer. How to download older Mac OS X versions via the App Store. If you once had purchased an old version of Mac OS X from the App Store, open it and go to the Purchased tab.

• Jump Push Match Mac Os Catalina
• Jump Push Match Mac Os X
• Jump Push Match Mac Os Pro

Summary

JumpCloud lets you run commands across any number of systems (Windows, Mac OS X or Linux) or tags in parallel. Once you have a good understanding as an Administrator of Using the Commands Tab, you may determine further ways that you can orchestrate your IT activities using JumpCloud.

Checking the Entitlements of an OS X app Submission to the Mac App Store. Alternatively to Xcode's entitlements preview, you can check the entitlements of a OS X app store submission by first creating and inspecting an.ipa file. The following steps outline the process to do this. Making an Inspectable.app bundle.

This article will help to provide you requirements, examples as well as configuration information for installing third-party applications to your JumpCloud managed systems using the Commands Tab.

Prerequisites

Before getting started with installing any applications on Windows or Mac OS X using the Commands tab, there are several considerations that will need to be evaluated. You will need to refer to your software vendor’s documentation or support resources to ensure that the package will be supported with JumpCloud per the prerequisites listed:

OS 8.6 - 9.2.2 might need the last of whichever versions of the USB extensions that each of these System versions supports (for OS 9.1 through 9.2.2, USB 1.5.6 is the preferred version; OS 9.1 and later don't need the extension 'USB Mass Storage Support', especially since it sometimes freezes Macs running OS 9.1 - 9.2.2 that are trying to boot. In Mac OS X, Quartz 2D can work with all other graphics and imaging technologies—Core Image, Core Video, OpenGL, and QuickTime. It’s possible to create an image in Quartz from a QuickTime graphics importer, using the QuickTime function GraphicsImportCreateCGImage. See QuickTime Framework Reference for details.

Command-line Installation Support

While this requirement may seem like an unspoken one, in order to successfully install the application to a JumpCloud-managed system it will need to support execution from the command-line. This is important being that not all packages support non-UI installations.

Windows

In many cases EXE as well as MSI installation packages (Refer to Windows Installer wikipedia article for more information) will be supported. MSI packages in particular are provided for system administrators who would need to deploy the software to several terminals over a network connection. There shouldn’t be any major differences when comparing an MSI and EXE from a functionality standpoint, however there may be additional options available for MSI packages such as performing “silent” installs or having additional pre-configuration options. Because of this, MSI packages may in some cases be more compatible with the JumpCloud Commands tab. Please refer to your software vendor’s documentation and support for further information on the best options and supported methods.

Mac OS X

As with Windows, application vendors will distribute different application package types when working with a Mac OS X application. This may include DMG files, PKG files, compressed archives (.zip, .tgz, etc.) or even flat application files. A DMG file is a disk image, which will require the image to be mounted to the system in order to view it’s contents. Because of this, you may find that application deployment will be more preferred using either PKG files, compressed archives or application files but your vendor documentation and support can provide you direct advisement.

Unattended or Silent Installation

The Commands tab works in such a way that commands are sent to the system for execution and a pass/fail results along with any command result details are displayed within JumpCloud. Because the Commands tab does not present the administrator with an interactive session when performing execution, it is required that all application installations have “silent” or “unattended” installation options. The functionality and terminology can differ from software vendor to software vendor so this may require discretion on your part. By definition a “silent” install should be one that does not display any indication of progress, while an unattended installation is once which does not require user interaction. Explicitly, JumpCloud requires an “unattended” installation which does not require user interaction, but note that some vendors will in fact refer to this as “silent”.

As an example, our very own (Windows) Command Line Installation KB article is a great example that outlines command-line install to a Windows system where a unattended/silent option is available. There are three flags available for our EXE to aid in unattended installations in the form of /SILENT,/VERYSILENT and/SUPPRESSMSGBOXES:

JumpCloudInstaller.exe -k CONNECT_KEY /VERYSILENT /NORESTART

Setup & Execution

Using Upload File with the Commands Tab

You can upload one or more files to be pushed to the server prior to executing the command, including an installation package. The file push occurs immediately before the command is executed, so you can update the files anytime, and know that the next time your command runs, it will have the latest update. You can include any data you like, such as a tarball, that your script can untar and utilize for any purpose.

Note that the Upload File functionality within JumpCloud only supports files of 1MB or smaller size. If your installation package is larger than this, you may want to refer to the next section for downloading a file from a web-hosted source or placing in a centralized network destination external to JumpCloud.

1. From the JumpCloud Administrative Console, click on the Commands tab on the left-hand navigation
2. Click the + button at the top-left to create a new command
3. At the top of the Execute Command window choose either Linux, Windows orMac depending on your target system(s)
4. Before populating your installation command into the main pane, click Upload File under the Files section to attach the installation package
5. Once selected, take note of the File Destination field and it’s default value. Feel free to specify a different local directory on the target machine as needed
6. Populate your installation command, and take note that you will need to specify the full package path was was specified in Step 5
7. Choose the target Systems and or Tags that you would like to execute to from the right-hand side
8. Choose to either Save & Run Now, or click Save for later usage

Downloading Installation Packages

While planning your deployment strategy, you may find that you want to look at other alternatives than the native Upload File functionality provided. This could be due to considerations ranging from the 1MB file limitation that is discussed above, to trying to have a more streamlined method of package acquisition that allows for management external to JumpCloud.

One option that is available to you is to use Windows PowerShell or Bash Shell (Mac OS X) to download a file from a web server for subsequent install.

Windows PowerShell

The following PowerShell command will download a file from a web server to the local machine, and allow you to specify the directory it lives:

(New-Object System.Net.WebClient).DownloadFile('<FILE_DOWNLOAD_WEB_PATH>', '<LOCAL_FILE_DOWNLOAD_PATH>')


Below is an example of the command which is downloading the Windows JumpCloud Agent, and placing the file into the C:WindowsTemp directory. This is purely an example being that the JumpCloud agent must be installed prior to the ability to send commands to the system:

(New-Object System.Net.WebClient).DownloadFile(“https://s3.amazonaws.com/jumpcloud-windows-agent/production/JumpCloudInstaller.exe”, “$env:TEMP/JumpCloudInstaller.exe”)

Mac OS X

The following Bash Shell command will download a file from a web server to the local machine, and allow you to specify the directory it lives:

curl -o <LOCAL_FILE_DOWNLOAD_PATH '<FILE_DOWNLOAD_WEB_PATH>'


Below is an example of the command which is downloading the Mac OS X JumpCloud Agent, and placing the file into the /tmp/ directory. This is purely an example being that the JumpCloud agent must be installed prior to the ability to send commands to the system:

curl -o /tmp/jumpcloud-agent.pkg 'https://s3.amazonaws.com/jumpcloud-windows-agent/production/jumpcloud-agent.pkg'

Executing the Command

At this point you should now have a good understanding on what is required prior to command execution for an application installation. Once you have confirmed that your package supports command-line installation, allows for unattended options and have determined how you will upload/download the installation to the target system you are ready for install.

For more information on the options available with Commands, please refer to Using the Commands Tab.

If you require have any questions or concerns, please contact support@jumpcloud.comfor further assistance.

Q: How can I verify that my submission to the App Store was code signed and entitled correctly?

A: During the app distribution process through the Xcode Organizer > Archives tab, entitlements are set onto the app by way of the provisioning profile used for code signing. It is important to be aware that the re-application of entitlements at this phase creates the opportunity for unintended entitlement differences between any prior development builds you may have tested. The primary purpose of this document is to verify that your entitlements are correct for your distribution builds for beta testing and App Store submission.

Note: Using TestFlight to beta test your app eliminates the opportunity for entitlement differences between the builds you beta test through TestFlight and the build submitted through TestFlight. This document is useful in preventing entitlement differences between development and distribution builds, and also for developers who rely solely on Ad Hoc for beta testing.

Jump Push Match Mac Os Catalina

Note: For Push Notification entitlement troubleshooting, refer to the TN2265 - Troubleshooting Push Notifications document instead.

Inspecting distribution build entitlements while submitting an app in Xcode

Xcode shows the distribution build's entitlements in the Summary pane during the submission workflow. This is the last opportunity you have to visually ensure that your app contains the expected entitlements before submitting your app for review.

Creating an .ipa file to check the entitlements of an iOS app store submission

Alternatively to Xcode's entitlements preview, you can check the entitlements of an iOS app store submission by first creating and inspecting an .ipa file. The following steps outline the process to do this.

Making an Inspectable .ipa file

1. In the Xcode Organizer, instead of Submit to the iOS App Store, do Save for Enterprise or Ad-Hoc Deployment. This will create a local copy of the .ipa file that would be submitted to the App Store.

2. When asked to choose the provisioning profile to sign with, select the same distribution profile you use when submitting to the App Store. Take a screenshot of your choice (command-shift-3) so you can verify this step later. During submission, this screenshot will be the only record you have identifying which profile was used to sign the app.

3. When asked to save the package, uncheck Save for Enterprise Distribution, then save the .ipa file.

Checking the Entitlements of an .ipa file

1. Find the .ipa file and change its the extension to .zip.

2. Expand the .zip file. This will produce a Payload folder containing your .app bundle.

3. Use the codesign tool to check the entitlements on the .app bundle like this:

   where YourApp.app is the actual name of your .app bundle.

4. Use the security tool to check the entitlements of the app's embedded provisioning profile:

   where YourApp.app is the actual name of your .app bundle.

Checking the Entitlements of an OS X app Submission to the Mac App Store

Alternatively to Xcode's entitlements preview, you can check the entitlements of a OS X app store submission by first creating and inspecting an .ipa file. The following steps outline the process to do this.

Making an Inspectable .app bundle

1. In the Xcode Organizer, instead of Submit to the Mac App Store, do Export as Mac Installer Package. That will create a local copy of the .pkg file that would be submitted to the Mac App Store.

2. When asked to choose a provisioning profile to sign with, select the same distribution profile you use when submitting to the Mac App Store. Take a screenshot of your choice (command-shift-3) so you can verify this step later. During submission, this screenshot is the only record you'll have that identifies which profile was used to sign the app.

3. Save the .pkg file when prompted.

4. Use the pkgutil tool to expand the package into its components:

   where YourApp.pkg is the actual name of the package you created in the previous step.

5. Expand the compressed payload inside the package using the opentool or by double-clicking it:

   where com.yourcompany.yourapp is the actual bundle ID of your app.

Checking the Entitlements of an .app bundle

Jump Push Match Mac Os X

Use the codesigntool to check the entitlements on the .app bundle like this:

where YourApp.app is the actual name of your .app bundle.

Use the security tool to check the entitlements of the app's embedded provisioning profile:

where YourApp.app is the actual name of your .app bundle.

Troubleshooting Entitlement Mismatches

Follow these steps if an entitlement is not set as expected.

1. Log into Certificates, Identifiers & Profiles > (iOS or OS X) > Provisioning Profiles > Distribution.

• Click the distribution profile and ensure the desired entitlements are listed under 'Enabled services.' If the desired services are not enabled, navigate to the App ID section of the site and enable the necessary services on the App ID associated to the distribution profile.

• Ensure the status of the distribution profile is 'Valid.' If the status is 'Invalid,' it means that the profile needs to be regenerated. A profile's status becomes invalid if there were changes made to its associated certificates or to the enabled services of its App ID. To regenerate the profile, select it from the list and click 'Edit.' Associate the profile to any new certificates (if necessary) and then click 'Generate.'

2. Follow the steps in Refreshing Provisioning Profiles in Xcode to ensure that Xcode's provisioning profile library is up to date.

3. Click 'Distribute...' on the Xcode > Organizer > Archives tab and choose the distribution profile within the Provisioning Profile selection menu. Take a screenshot of your choice (command-shift-3) so you can verify this step later. During submission, this screenshot will be the only record you have that identifies which profile was used to sign the app.

Note: If the live version of your App Store app is affected by missing entitlements, you can not simply re-sign the existing app archive. Once your profile's entitlements are corrected through the above steps, increase the bundle version, re-archive and then follow Step 3. to submit the app to the app store. You may be able to request an expedited review using this form.

Related Material

For troubleshooting general entitlement problems, see TN2415 - Entitlements Troubleshooting.

Document Revision History

Jump Push Match Mac Os Pro

Copyright © 2015 Apple Inc. All Rights Reserved. Terms of Use Privacy Policy Updated: 2015-10-08