Hi

We're using SCCM 2012 to send patch to my clients using ADR, but in the monitor for the deployment, shows aroud 35% of equipment in the status unknow: "Client ckeck passed/inactive" and "Client check passed/Active", I took some of the equipments and manually refreshed all the Action, but this continue showin in unknow state.

Any Idea why all these machines appear like unknow? I refreshed the actions in the client machine and continue with the same status.

Thanks

Can you run the summarization manually for the deployment under monitoring node and check the unknown assets?

Thanks

Hi

I ran several times the summarization and only change the others status (progress and compliant), but the status unknow remain.

Hi to all

Any other idea? I'm worried of this, many clients in the ADR are not reporting, and if I check locally, with the windows update, they have all the patches, but are not reporting in the SCCM console, I restarted the clients, run all the actions in the SCCM in the control panel, summarize and nothing... :(

Hi to all

Does anybody knows the difference bettween:

-Client Check Passed /Inactive

VS

-Client Check Passed/Active

Because I revised some of them and are updated, but only appear Active in the unknow status.... so I think this equipments sould be in the complain part, why is this?

Which .log file should I have to dig

Thanks

Hi to all

Any suggestion?

Are there any errors on the Monitoring node, Site Status? Does hardware inventory and heartbeat make it to the site/database? Is everything else working fine?

I have this too.

No further errors only "Client check passed/Active" under Unknown..

Hanna

Hi Hana

Already no one has give me an answer for this issue, I'm not sure if the problem is the Built number, this is 7711, May be this can be a RTM. Do you know about this?

If this is the problem, it can be updated to a new version?

Thanks to all

Hi Torsten

No, in the site status and the component status we don't have any error, just 3 warnings that appear and disappear regurlarly about: "SMS_CLIENT_CONFIG_MANAGER", "SMS_AD_SYSTEM_DISCOVERY_AGENT" and "SMS_AD_USER_DISCOVERY_AGENT", and I think this are not related to the unlnow status of my clients, or this coul be the problem?

Hi DocMX

Yes it is 7711.

Is an update available ?

I have also issues that something is reported "compliant" while it is not compliant at all but I think I stat a new thread about this.

Thanx

Hanna

Hi Hana

Could you send me the link to your new issue about "compliant", I observed the same thing in my environment.

Thanks

Hi DocMX

I did not start the thread yet.

Coming weekend I am going to deploy about 1000 pc's then I see what is going to happen about compliancy :-)

Yes, I know this is an old post but Im trying to clean up old posts.

Did you figure this out?

Not yet ! We have delayed the deployment because of another bug.

I will come back to this thread as soon as I have some more information.

Hi Garth

This threat has not been already solved, does someone have an idea?

Thanks

Hi guys,

I've had a bit of a breakthrough with this.  I had 4 servers that were appearing as active/passed.  The client installed fine but nothing else was happening.  Tried reinstalling the client and deleting the CCM folders but nothing.

On one of the machines Windows Update was also failing and in trying to fix this, I've fixed the SCCM issue and it's received updates and now moved to the In progress tab and one is compliant.

I found this http://support.microsoft.com/kb/971058 and ran the fix it tool on the server.  It found some errors and fixed them.  Had to run it twice on one server as it fixed an error the second time around.  On completion I kicked off the software update scan cycles on the clients and within a few minutes the console appeared.

As I type, I'm two servers down and awaiting the scans on the other two.  Fingers crossed!

• Proposed as answer by Garth JonesMVP, Moderator Saturday, March 02, 2013 3:23 PM
• Marked as answer by Garth JonesMVP, Moderator Saturday, March 09, 2013 4:03 PM

I had this same issue, but the resolution was different... I also had an issue with Windows Updates with the client showing Unknown status, but for me I just had to add the PC to the proper SCCM WSUS GPO (we have two GPO's - one for standard domain WSUS and one for SCCM WSUS). Details posting the resolution here - http://proweb-solutions.net/?p=189

I solved some of the problem by correcting an issue we had with boundaries.  I had a subnet boundary like 10.10.3.0 but the physical subnet had been re-subnetted so some clients had a different subnet mask and were reporting their subnet as 10.10.3.64 and so did not fit the boundary.  They could find the management point but not the DP.  Find the client in the list of devices on the console and double click to reveal the subnet. Check and see if you have a DP associated with that subnet.  This solved some but no all unknowns.  Good luck.