Clients Approved N/A
Hello All,
We have SCCM clients reporting Client: NO Approved: N/A and the site code is correct. The client property value is NULL. We've noticed that the property of machines with client value null….discovery data window has a grey background. Clients where the client property value is 0 have a white discovery data background.Not sure if that matters.
Clients with N/A and client property value null can use remote tools just fine but are not updating their inventory data. I’ve check the few entries on this issue listed on this forum but I am not having any luck. The machines I’ve check are aware of their MP and are registered. Any help will be greatly appreciated.
Thanks
All Replies
- Pick one of those records, and right-click it and go to Properties. Within there will be listed Discovery Agents which were used to discover that particular record, and the date (lower down, with the number corresponding to the agent in [ ] ) . Based on seeing that data, you'll be able to tell which discovery agent "discovered" that record, and placed it into your database. So, for example, if it was AD System Discovery, you'll know that record was placed there by your site server discovering that computer object in AD--but not that it had a client installed. Whether or not a client is installed normally comes from Heartbeat Discovery.
Once you have all of the facts of where those client n/a are coming from, you can come up with an approach to deal with them. it might be simply the approach of "ignore", or you might want to change discovery agents, frequencies, tasks, or a myriad other routines so that your console 'looks' the way you think you want it to look.
fyi...these types of questions are so hard to answer... because it is based on about 10 different settings. and combinations of them.
Standardize. Simplify. Automate. - I checked a few records, and it seems those machines not working properly have not Heartbeat Discovery / MP_ClientRegistration listed.
All the machines I checked also seem to have this error lin the System Log:
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{24FF4FDC-1D9F-4195-8C79-0DA39248FF48}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18). This security permission can be modified using the Component Services administrative tool.
Thanks
-Awens May not be the same thing, but I had a few clients which were failing to submit heartbeat. Check inventoryagent.log on that computer, and see if you are getting errors for the Heartbeat (it's the one ending in 000001} ). I ended up using Roger Zanders' Client Center to WMIRepair those few boxes before they would do heartbeat correctly. Never did figure out root cause, because those particular boxes had been imaged 4+ years ago--who knows what might have been done to them in all that time to make WMI be wonky.
Standardize. Simplify. Automate.Thanks for the help Sherry.
I tried the wmi fix on one of my clients and it's still not working. Sometime last week we for some reason we lost all of our clients and they started reappearing without any data. Once I triggered a "Discover Data collection Cycle', some clients stated to come back as: Client NO Approved N/A Agent Name[0] SMS_AD_SYSTEM_GROUP_DISCOVERY / Name[1] SMS_AD_SYSTEM_DISCOVERY_AGENT / Name[2] Heartbeat Discovery. When it was working I was sure there was a fourth with MP_***.
We aren’t sure what happened and no changes were made at that moment. We did move form native to mixed mode a few weeks ago and it seemed like machines were making the switch just fine.
