- Jamf Nation Community
- Products
- Jamf Pro
- Re: Jamf SCC Plug-in 3.70 - Invalid registration s...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2022 07:57 AM - edited 03-18-2022 08:00 AM
While trying to send data from Jamf to SCCM, I am getting the following errors:
- [ 5] ERROR Jamf.ProxyService.Plugins.SCCM.SccmReports - There was an unexpected error sending the device to SCCM.
- System.InvalidOperationException: Invalid registration state: Error. Cannot continue.
We are using version 3.70 of the plug-in and SCCM version is 2111
I have look through quite a few of the support articles and I am seeing various information, but none of them ever offer a solution and they just end.
When I use the Jamf SCCM Proxy Service Helper and try to just send one machine manually I get different error.
- [ 67] ERROR Jamf.ProxyService.Plugins.SCCM.Utilities.Certificates - There was an unexpected error sending the device to SCCM.
- System.InvalidOperationException: Invalid registration state: Error. Cannot continue.
Solved! Go to Solution.
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 11-16-2022 10:01 AM
Sorry for not returning to this sooner. We resolved this by putting the plug-in on a separate server, originally it was hosted on the SCCM server. For what ever reason as soon as it was on its own box it started working right away.
6 REPLIES 6
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 04-11-2022 07:34 AM
We've just configured the SCCM plug-in and we're seeing the same errors. Did you find a fix for this problem?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 11-16-2022 10:02 AM
If you are still having issues try running the plug-in on its own box, that's what resolved it for us.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 04-15-2022 07:48 AM
We have not yet. I have been working with support for while and it is slow going. I will update once we figure something out.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 11-16-2022 09:56 AM
Was this issue resolved? If not please reply and i'll see if the fix that worked for us might help.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 11-16-2022 10:01 AM
Sorry for not returning to this sooner. We resolved this by putting the plug-in on a separate server, originally it was hosted on the SCCM server. For what ever reason as soon as it was on its own box it started working right away.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 11-16-2022 11:13 AM
Appreciate you getting back to me so quickly! Happy to hear it worked out.
The issue in my environment was due to the isv proxy certs. When we would renew our certs some of the devices would still be associated with the previous cert thumbprint. It was a challenging to figure out we had to first make sure the old cert was fully removed from the database. The we had to query another table to find the devices associated with the incorrect thumbprint and blow them away. After all of that the devices would successfully synch :)
