Can't add clients to device collections after accidentally deleting them from database

In our testing, one of the desktop admins deleted a collection and accidentally told it to delete the computers in the collection, which was about 4 PCs.
After reinstalling the client on them, I can see them in SCCM, and I can see that the client is "Active" but they can't be added to any collections.  I can still use the same direct method to add other PCs that aren't having problems.
 
This same thing happened on clients that WEREN'T deleted, but the client was installed manually rather than via push.  Everything seems correct in the client on the PCs, but I cannot add them to collections.  I add them via direct rule and they never appear.
 
Any ideas?  Any log files that would help you help me?

If you have heartbeat discovery enabled, each client will just show up again on their own.  If you don't, you can go to the CM control panel on each and force a discovery to run.  Then they'll show up. 

The problem is that the devices can't be added to collections.  I can get them to show back up, just can't add them to anything.

So, they are back?  In what collection(S) do you see them?  If you right-click properties on one, what discoveries have run, and when?  Do they have hardware inventory results?  software inventory? (if you have it enabled)  under properties, is the record marked as obsolete?
 
If you make a new collection, and limit it to the collection in which you DO see the record, and the collection query is select * from systemresource (i.e., everything); do they show up in the new collection?
 
It sounds like you are doing a manual, by name/lookup individual computer name.  if you use a query... does it work?

Thanks for the reply.
They are back in SCCM.  I can see them in "All Desktop and Server Clients" and "All Systems".  I did what you suggested and created a new group using select * and yes, it appeared in that collection.  I was using a direct rule, but it only fails on those PCs.  I can use direct rules for any of the other 40ish machines I am testing SCCM with no problem!  I just did a spot check on two PCs and yes, I can see their hardware inventory results - whether or not those are new results or old information from the first time the client was installed or not, I'm not sure.  It does have under "New Items Since Last Inventory Collection" as 24 on 7/10/2012, so I guess it is being actively updated.  
 
I also just added them to a query rule using a new security group on the affected device collection and they showed up just fine.  When doing the query rule, you can't even search and find the computer.  It's like it doesn't even exist in SCCM.  When you find it in "All Systems" right click and add it to an existing device collection, it never appears in that collection, though it does appear in the "Membership Rules" tab of the collection.  Also, the software deployment tied to the collection is working.  So, it appears that everything is fine except for using direct rules on these particular PCs.
 
Regarding the part about "obsolete record", I'm not sure where to find that.
 

skissinger


So, they are back?  In what collection(S) do you see them?  If you right-click properties on one, what discoveries have run, and when?  Do they have hardware inventory results?  software inventory? (if you have it enabled)  under properties, is the record marked as obsolete?

If you make a new collection, and limit it to the collection in which you DO see the record, and the collection query is select * from systemresource (i.e., everything); do they show up in the new collection?

It sounds like you are doing a manual, by name/lookup individual computer name.  if you use a query... does it work?

Ok, it's become clear that there is a problem with installing the client manually.  I can still push the client just fine and I have no problem adding it to collections manually or anthing.  Is there anything I can do to recreate the client files I am using?
 
One of the techs said that even after adding it to a group via the query method, it is not getting updates.  It's getting software deployments though.  Not sure if that's worth looking into or not.
 
 
Update: I just pushed the client to 3 servers, 2 of them failed, 1 worked.  The 2 that "failed" actually installed, but all of the components are set to "Installed" rather than "Enabled".  I have corrected one of them by re-pushing the client.

I just deployed the client to 3 servers.  2 of them are not working, 1 is.
 
The first symptom I notice is that all of the components are "Installed" while none are Enabled.  The one that is working properly is getting patches and everything just fine.
The CAS.log file only exists on servers that are working properly. No cas.log exists on the 2 servers I am currently having issues with.
Can somebody help?