We configured the JSS Plugin to tie into our DEV SCCM Enviornment a few months ago. Everything worked fine until SCCM started aging out old clients (It's a dev lab and I hadn't turned on the Mac laptop in over 30 days so SCCM aged out the record) Now the JSS_SCCM_Proxy.log file shows that the plugin sees the machine in JSS and is sending to our MP, but no data shows up. Verified the JSS password is correct, the account is functional, and it still has a valid cert.
I went ahead and endabled debug logging and looking through the logs I see a few lines that I find odd... can anyone shed any light on these?
I see that it successfully polled.. 2015-02-23 13:19:21,303 DEBUG JAMF.JSS.ProxyService.Utilities - The JSS server 'https://<JSSSERVER>' was last successfully polled at '2/23/2015 6:07:37 PM' UTC.
but I get this error even though I see machines inside of JSS just fine.
2015-02-23 13:19:27,025 WARN JAMF.JSS.ProxyService.JssProxyService - No computers were found in the JSS that have been updated since '1424713766974'.
This process did work, just recently it stopped working for us. any help or assistance is as always appreciated.
JSS or just the plugin?
digging further, inside of ConfigMgr, we see some errors in MP_Hinv.log with an error of "Hinv Sax: Skipping unexpected token at Machine" The only thing i could find online about this error is talking about simulated clients, but I could not find any more than this.
Hi Josh -
Do you have any devices which are currently enrolled and currently updating their inventory in you dev lab?
Based on the snippet from your log, it is not finding any devices to send to SCCM.
The JSS SCCM Proxy service is designed to bring over only the devices that have updated inventory since the last time the proxy service last checked for devices in your JSS. With the default polling interval of 30 minutes, the next time it runs it will check only for devices with updated inventory within the last 30 minutes.
To reset it, and get it to pull over all the devices again follow these steps:
If that does not work for you, please reach out to support and one of the integration specialists will be able to help you out.