Managing ControlUp’s CoreAgent on macOS without a Bundle ID

ControlUp‘s C4Desktop for macOS utilizes the CoreAgent process to collect and transmit inventory data to the ControlUp platform. This agent is responsible for maintaining device registration, managing credentials, and facilitating communication between the device and ControlUp services. Additionally, CoreAgent oversees scheduled tasks such as periodic device reporting, license checks, and configuration updates. It also monitors and manages supporting modules that gather specific data, including CPU usage, Wi-Fi status, process information, crash reports, location data, and collaboration application activity. In the event that any of these supporting modules cease functioning, CoreAgent is designed to restart them to ensure continuous data collection. Furthermore, CoreAgent serves as the central hub for data transmission, securely uploading collected information to ControlUp and facilitating features like remote control and file browsing.

The CoreAgent binary is located at `/usr/local/com.controlup.edgedx.agent/Bin/CoreAgent` on macOS systems. It’s important to note that CoreAgent is a signed binary and not an `.app` bundle, which means it does not have a `CFBundleIdentifier` and, consequently, lacks a bundle ID. This absence can present challenges when integrating with Mobile Device Management (MDM) solutions like Jamf, which typically rely on bundle IDs for application management. ControlUp does not publish a bundle ID for CoreAgent, and there is no documented `CFBundleIdentifier` for it in the Jamf or MDM documentation. Instead, for CU4Desktop on macOS, MDM profiles target other agent components by bundle ID. The main one tied to the core agent stack is:

This approach allows MDM solutions to manage and configure the necessary components of the ControlUp agent effectively, even in the absence of a bundle ID for CoreAgent itself. For detailed instructions on deploying ControlUp for Desktops with Jamf, including the creation of configuration profiles and deployment scripts, refer to the official ControlUp documentation. ([support.controlup.com](https://support.controlup.com/docs/deployment-with-jamf?utm_source=openai))

In summary, while CoreAgent is integral to the functionality of ControlUp’s C4Desktop for macOS, its lack of a bundle ID requires alternative methods for management and deployment, particularly when using MDM solutions like Jamf. By targeting other agent components with known bundle IDs, organizations can effectively deploy and manage the ControlUp agent on macOS devices.

Read the entire ‘Managing ControlUp’s CoreAgent on macOS without a Bundle ID’ thread below:

Hey all,

Quick question about C4Desktop for MacOS – is CoreAgent the process that collects and writes inventory data to ControlUp?

Hi Dustin.
Short answer is yes. You may also see other processes like AgentAssist, AppDXHelper, depending on your deployment

If using Version Control, you may also see Agent Manager, which deals with agent updates

The binary lives at:
`/usr/local/com.controlup.edgedx.agent/Bin/CoreAgent`

What it does
• Keeps the device registered with your ControlUp tenant and manages the credentials the agent uses to talk to the service.
• Stays in contact with ControlUp so the device can send health and experience data, receive configuration, and pick up actions or scripts you send from the console.
• Runs the agent’s scheduled work — periodic device reporting, license checks, configuration updates, and similar background tasks.
• Starts and watches the supporting modules that collect specific data (for example CPU, Wi‑Fi, processes, crashes, location, and collaboration-app activity). If one of those helpers stops, CoreAgent brings it back.
• Acts as the hub for those modules: they send collected data to CoreAgent, and CoreAgent uploads it. Features such as remote control and file browsing also go through CoreAgent so they can reach ControlUp securely.

Thanks Joel and Abel!

Do you happen to have the bundle ID for the CoreAgent?

Our JAMF expert is asking for that information if it’s available.

We have native integration with Jamf https://support.controlup.com/docs/deployment-with-jamf

I’m not at my desk, but we can get you the bundleid

ControlUp does not publish a bundle ID for CoreAgent. It’s a signed binary, not an `.app` bundle, so there’s no documented `CFBundleIdentifier` for it in the JAMF/MDM docs or official configuration profiles.
Instead, For CU4Desktop on macOS, MDM profiles target other agent components by bundle ID. The main one tied to the core agent stack is:

if you find more up-to-date information, please share it

Continue reading and comment on the thread ‘Managing ControlUp's CoreAgent on macOS without a Bundle ID’.  Not a member? Join Here!