Failed Commands

[JamfAdmin2]

Hello Everyone,

Not sure why these config profiles I am using with Jamf connect are failing. Does anyone have a way to remove the failed commands? How can I run JAMF Connect and have no failed commands as the outcome 

[Nicholaus]

Were you testing different profiles and scoping/removing devices? Those commands are saying that it failed to remove the profiles because they weren't found.

How are you configuring Jamf Connect? Are you creating the profiles through the Jamf Pro interface or with the configuration utility? If with the config utility, are you saving as .mobileconfig or .plist? Have you tried installing the profile locally to see if there are any issues before deploying via Jamf?

You can clear those failed commands by hitting cancel on the right side in that screenshot.

[JamfAdmin2]

Yes I am only testing on 1 mac computer which is my test mac I have removed it and wiped the mac a couple of times and re added the computer to the config profiles. 

I am creating profiles through the Jamf Pro interface. 

[Nicholaus]

Sorry for the confusion, I'm wondering if you've tried installing the profiles on the Mac by dropping the files onto the desktop/documents/etc.. and double clicking the profiles on the test Mac to install them. I'm just curious if it throws an error when trying to install it that way.

Maybe try using the Jamf Connect Configuration app that comes with the Jamf Connect download? I configured it using that app and saved Login/Connect as separate .plist files. Then in Jamf Pro, you create a new configuration profile and upload the .plist in the "Application and Custom Settings" > "Upload" tab. If you do it this way, the Preference Domain for Connect is "com.jamf.connect" and for Login it's "com.jamf.connect.login" without the quotes.

If you're still getting failures, I would suggest reaching out to your Customer Success team at Jamf and asking for assistance via https://jamf.service-now.com/csm

[SCCM]

They should be visible on the management tab at the top of your screen of the device and you can cancel all from there. 
if your doing it on a larger scale you can prob send a management command to clear them. However if these are reoccurring, you probable have some scoping set wrong