Repository navigation
Blueprint Conversion Utility 3.4.7
BCU 3.4.7 focuses on workflow clarity, administrator intent, profile-specific analysis reliability, and safer Blueprint migration decisions.
This release resolves several issues where BCU could display conflicting information between Setup and Review, reevaluate an administrator-selected alternative, or retain analysis from a previously selected Configuration Profile.
Highlights
Administrator selections are now authoritative
BCU now clearly separates three concepts:
- Recommended Approach: BCU and
jamf-cliguidance based on profile analysis. - Selected Approach: The action explicitly selected by the administrator.
- Takeover Capability: Whether the selected profile is technically eligible for takeover.
- Evaluation Incomplete: Provides this "error" when there are no groups assigned. The world is your oyster. Choose an alternative method and go for it!
Once an administrator explicitly selects an Approach, subsequent analysis or reevaluation will not silently replace that selection.
For example, if BCU recommends:
Convert to a New Blueprint
but the administrator selects:
Create Blueprint for Review
BCU may continue to display its recommendation, but the administrator's selected Approach remains authoritative.
Setup and Review consistency
The Review screen now uses Approach instead of the previous Workflow terminology.
The Approach displayed on Review reflects the administrator's actual selection rather than an internal execution mode or takeover capability.
This prevents confusing situations where Setup could show:
Convert to a New Blueprint
while Review incorrectly displayed:
Profile Takeover
BCU now carries the selected Approach consistently through the workflow.
Improved jamf-cli takeover verdict handling
BCU now recognizes additional valid jamf-cli responses indicating that profile takeover is unavailable, including variations such as:
takeover not supportedtakeover is not supportedtakeover is unsupportedtakeover not possibletakeover is not possiblecannot take overconverting the profile rather than keeping it as installed
When takeover is conclusively unsupported but conversion is available, BCU now recommends:
Convert to a New Blueprint
instead of incorrectly reporting:
Evaluation Incomplete
Genuinely inconclusive jamf-cli results can still produce Evaluation Incomplete so administrators are not given false certainty.
Profile-specific analysis isolation
Analysis in the Advanced view is now tied to the Configuration Profile currently selected in the sidebar.
When selecting a different Configuration Profile, BCU now:
- Cancels the pending analysis task for the previous profile.
- Immediately clears previous
jamf-cli Activity. - Resets profile-specific evaluation state.
- Displays the newly selected profile name and ID while analysis begins.
- Starts a fresh analysis for the new profile.
- Prevents late asynchronous results from a previously selected profile from updating the current profile's interface.
The Advanced activity pane therefore remains synchronized with the profile currently being reviewed.
Improved asynchronous analysis protection
BCU now tracks the Configuration Profile ID and profile-load generation associated with an evaluation.
Before asynchronous analysis results are applied, BCU verifies that the result still belongs to the currently selected profile.
This prevents circumstances such as:
Select Profile A
↓
Profile A analysis starts
↓
Select Profile B
↓
Profile B analysis starts
↓
Profile A finishes late