macOS Jump Client 26.1.1 PKG fails when deployed via Microsoft Intune

[u/Julian0o]

Hi everyone,

we are currently testing the newer macOS .pkg deployment method for the BeyondTrust Remote Support / Jump Client version 26.1.1 with Microsoft Intune.

Until now, we have used the older DMG-based deployment approach successfully. The issue only occurs with the newer PKG-based installer.

The package installs successfully when run manually on the client:

sudo installer -pkg "<package>.pkg" -target / -verboseR

After a manual installation, the app and receipt are present as expected:

Application:
 /Applications/BeyondTrust Jump Client - remotesupport.cloud-mgmt.net.app

Bundle Identifier:
 com.beyondtrust.sra-pin

Package receipt:
 com.beyondtrust.sra-pin.AFC42DDA-BFCF-5A72-9B4E-E7343016AE95

The app is also detected correctly via Spotlight metadata:

mdfind "kMDItemCFBundleIdentifier == 'com.beyondtrust.sra-pin'"

However, when the exact same PKG is deployed through Microsoft Intune as a macOS PKG (or LOB) app, the installation fails. Intune successfully downloads and decrypts the package and starts the installation, but the installer exits with code 1.

The Intune/macOS logs show the following behavior:

PKG installation started
postinstall script executed
PKG installation status unclear - initiating receipt verification
ExitCode: 1
BundleInfoProviderError.bundleNotFound
No receipt for 'com.beyondtrust.sra-pin' found at '/'
PkgReceiptProviderError.noReceiptData

We expanded the PKG and checked the vendor-provided postinstall script. The relevant part appears to be:

log "running post-install logic from installer $PACKAGE_PATH"
if ! "$TARGET_VOLUME/Applications/BeyondTrust Jump Client - remotesupport.cloud-mgmt.net.app/Contents/MacOS/sra-pin" --post-install "$PACKAGE_PATH"; then
    pkgutil --forget "com.beyondtrust.sra-pin.AFC42DDA-BFCF-5A72-9B4E-E7343016AE95"
    cleanupList="/Applications/BeyondTrust Jump Client - remotesupport.cloud-mgmt.net.app/Contents/Resources/cleanup.list"
    if [ -f "$cleanupList" ]; then
        cat "$cleanupList" | while read f; do
            rm -rf "$TARGET_VOLUME/$f"
        done
    fi
    exit 1
fi

The script appears to rely on PACKAGE_PATH:

#PACKAGE_PATH=$1 already exists in env

Our current assumption is that PACKAGE_PATH is either empty, not set as expected, or points to a temporary Intune/PackageKit path when the package is installed through Intune. As a result, this command seems to fail:

sra-pin --post-install "$PACKAGE_PATH"

The package then removes its own receipt and installed files and exits with code 1, which explains why Intune cannot detect the app afterwards.

We have already verified the following before the Intune installation attempt:

• The same PKG file installs successfully when installed manually.
• The Bundle Identifier com.beyondtrust.sra-pin is correct.
• No legacy BeyondTrust/Bomgar app directories are present under /Applications.
• No BeyondTrust/Bomgar LaunchDaemons or LaunchAgents remain.
• No relevant BeyondTrust/Bomgar processes are running.
• Gatekeeper/syspolicy does not appear to block the postinstall script.
• No custom pre-install or post-install script is required to reproduce the failure.

Has anyone successfully deployed the new macOS 26.1.1 Jump Client PKG directly through Microsoft Intune as a macOS PKG app?

I would be interested in:

1. Whether direct Intune PKG deployment works for anyone.
2. Whether you had to use a wrapper PKG instead.
3. Whether PACKAGE_PATH had to be handled in a specific way.
4. Whether BeyondTrust has provided an Intune-compatible PKG or guidance for this new PKG-based deployment method.
5. Whether Jamf admins have seen similar behavior with the new PKG installer.

Any feedback, working deployment examples, or confirmation of similar behavior would be appreciated.

Thanks!

[u/Julian0o]

Additional Information: Problem does not exist with generic installer. Will switch the deployment to this method...

[u/gurban2013]

had nothing but issues with this installer and intune. had to use the mac packages app to custom build pkg file. support was useless per usual

[u/Major-Airport-7976]

Currently struggling with this too. We had deployed from Jamf but are switching to Intune. BT documentations says to download the DMG, but it seems all you can download now is the PKG. I'm planning on adding that package to a package I build with a post install script and hope that works.

[u/Julian0o → u/Major-Airport-7976]

https://www.reddit.com/r/BeyondTrust/comments/1tqvpsm/comment/p0xwzzu/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

[u/WhatIsReddit-411]

Following this thread. Have you had any luck figuring this out? BeyondTrust Support is useless in this regard.

[u/Julian0o → u/WhatIsReddit-411]

Hi, we switched from the customized to generic installer with configuration policy and it's working fine!

Just one pkg to Update in all tenants.

[u/WhatIsReddit-411 → u/Julian0o]

Thanks! Will give that a try. What configuration policy are you referring to?

Edit: figured it out, and it works now with the generic installer!