SIM 5.4.1 - SCCM Connector on SCCM2016 rejects clients

Portal User asked a question.

September 28, 2017 at 7:00 AM

Hi, I've tried to connect a SCCM 2016 (Version 1702) database to my SIM 5.4.1 - all pre-requisites have been configured. Integrated authentication has to be used, domain user is provided Service account is configured for the External Data Provider service (and can access the DB according to the logs) SCCM best practises according to the respective Snow papers are set in SCCM Preview in SIM works fine, Inventory Provider log is fine However, I end up with the imported computers being logged in <SIM path>\RejectedClients. No .snowpack files are created/transferred. Log files in the RejectedClients folder look like this: 2017-09-28 [5] [SoftwareEntity] Name is or empty. 2017-09-28 [6] [NetworkAdapterEntity] IpAddress is . 2017-09-28 [6] [NetworkAdapterEntity] MacAddress is . In SCCM GUI, it seems that there is one MAC address present for the system. Any hints on how to further troubleshoot this issue? I'm aware that the SCCM version in place is pretty new and not yet on the current support matrix, only a previous version (1606) is. As we are accessing the database here, and the structure there has not changed in 1702, I *assume* that this is not causing the issue above. Thanks, best regards Stefan

Anthony Yip (Flexera Software)
9 years ago
Simply using a SQL account with access to the SCCM database has resolved this for me in the past.
Expand Post
- Portal User
  9 years ago
  Hi Anthony, I assume that this would solve the issue, but unfortunately this is not an option for my customer, due to his internal rules. Best regards Stefan
  Expand Post
matt.white
9 years ago
HI, We had this issue, but with SCCM 2012r2 For us It was authentication issue that caused the data not to run through to the folder though we have no idea why the update caused this currently. We had to uninstall, delete the registry keys, etc., then uninstall SIM tool and reinstall the latest version and use a new account, that also had permissions to the share ,to run the software I Hope this helps a bit as I know its all a bit of a woolly answer, but I don't have the details as I only manage the SAM processes so am not allowed to play without the backend/tech side (unfortunately)
Expand Post
- Portal User
  9 years ago
  Hi Matthew, your approach finally solved my issue. It seems that the connector configuration did not work properly. I cannot really explain it, but uninstalling and deleting the connector configuration seemed to do the trick. Thanks! Best regards Stefan
  Expand Post

Related Product Forums