Skip to content

BCU 3.4.6

Choose a tag to compare

View all tags
@jawheelr jawheelr released this 10 Oct 04:28
· 6 commits to main since this release
3.4.6
0049825
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Blueprint Conversion Utility 3.4.6

Blueprint Conversion Utility 3.4.6 focuses on improving the Jamf Blueprint migration workflow, takeover analysis, deployment validation, administrative safeguards, and in-app guidance.

What's New

Improved Configuration Profile Analysis

  • Automatically analyzes the selected Configuration Profile using jamf-cli.
  • Provides a recommended migration approach based on the profile and takeover analysis.
  • Separates profile compatibility analysis from deployment scope requirements.
  • Unscoped profiles can complete analysis before a deployment group is selected.
  • Selecting another Configuration Profile starts a fresh, profile-specific analysis.
  • Improved handling of incomplete or inconclusive jamf-cli analysis results.

Unlimited Discovered Groups

  • Polls groups in 100 per page. Keep scrolling to load more in the list!

Improved jamf-cli Integration

  • Uses the public Jamf jamf-cli workflow for Configuration Profile analysis and takeover operations.
  • Displays jamf-cli activity in the Advanced interface for troubleshooting and validation.
  • Improved parsing of mixed jamf-cli output and Blueprint results.
  • Improved handling of Blueprint IDs, deployment information, and dropped-key warnings.

Create and Deploy

The guided workflow supports:

  • Create Only

    • Creates the Blueprint without deploying it.
    • Leaves the existing Configuration Profile scoped.

  • Create and Deploy

    • Creates and deploys the Blueprint.
    • Leaves the existing Configuration Profile scoped.
    • Uses Jamf Platform API read-back to validate deployment.

  • Create, Deploy, and Unscope

    • Creates the Blueprint.
    • Deploys the Blueprint.
    • Waits for Jamf Platform to confirm the Blueprint is DEPLOYED.
    • Unscopes the existing Configuration Profile only after successful deployment validation and explicit administrator acknowledgement.

Deployment Validation

Blueprint deployment is asynchronous.

BCU no longer treats the initial NOT_DEPLOYED state returned immediately after creation as a final deployment failure.

For deployment operations, BCU:

  1. Creates the Blueprint.
  2. Retains the Blueprint ID.
  3. Requests deployment.
  4. Queries the Jamf Platform API.
  5. Polls the Blueprint deployment state.
  6. Completes successfully when Jamf Platform reports DEPLOYED.

If deployment cannot be confirmed within the validation period, BCU reports a partial-completion state rather than incorrectly reporting that Blueprint creation failed.

Deployment validation can be retried against the existing Blueprint without recreating it.

Safer Configuration Profile Takeover

The existing Configuration Profile is protected throughout the takeover process.

BCU will not unscope the source Configuration Profile unless:

  • Blueprint creation succeeds.
  • Deployment was requested.
  • Jamf Platform reports the Blueprint as DEPLOYED.
  • The administrator explicitly selected the unscope workflow.
  • The administrator acknowledged the unscope action.

If creation, deployment, validation, or unscoping fails, BCU preserves the safest available state and reports the result.

Scope and Group Improvements

  • Better handling of currently unscoped Configuration Profiles.
  • Compatible target-group selection is available when deployment requires a group.
  • Mobile Configuration Profiles use compatible mobile-device groups.
  • Computer Configuration Profiles use compatible computer groups.
  • Analysis can complete independently of target-group selection.

Blueprint Editing

Expanded Blueprint review and editing capabilities include:

  • Blueprint name and description
  • Editable Blueprint properties
  • Payload/component review
  • Activation Conditions
  • Advanced Blueprint JSON
  • jamf-cli Activity

Activation Conditions can be reviewed and adjusted before creation.

Completion Reporting

Operation results provide clearer information about what actually occurred, including:

  • Configuration Profile
  • Profile ID
  • Blueprint ID
  • Requested deployment action
  • Deployment state
  • Deployment validation source
  • Takeover support
  • Existing Configuration Profile state
  • Dropped-key warnings

The workflow distinguishes between successful completion, partial completion, and failure rather than treating every non-final deployment response as a complete failure.

Updated Interface Guidance

The in-app Knowledge Base has been updated for the current BCU interface and workflow.

A new Administrator Quick Start walks through:

  1. Configuring the Jamf Platform API
  2. Selecting a Configuration Profile
  3. Waiting for automatic analysis
  4. Reviewing the recommended approach
  5. Selecting deployment scope when required
  6. Running Dry Run
  7. Choosing Create Only, Create and Deploy, or Create, Deploy, and Unscope
  8. Reviewing operation results and logs

Additional documentation covers:

  • Profile Takeover
  • jamf-cli
  • Platform API
  • Deployment and Unscoping
  • Device Groups
  • Payload Compatibility
  • Blueprint GUI and JSON editing
  • Troubleshooting
  • Application Updates

Administrative Visibility

  • The application indicates when the API is configured.
  • Detailed application logs remain available from the header.
  • Long-running workflows expose operation status and activity.
  • Advanced mode provides access to jamf-cli Activity and Blueprint JSON.

Upgrade Notes

Version 3.4.6 is intended as a direct replacement for previous 3.4.x builds.

Existing Jamf Platform API credentials stored by the application can continue to be used.

For production migrations, the recommended workflow remains:

Analyze → Review → Dry Run → Create/Deploy → Validate → Unscope only when explicitly required

Always review the Dry Run results and reported dropped keys before allowing a Blueprint to take ownership of an existing Configuration Profile.

Assets 4
Loading