System Center Configuration Manager TechCenter >
System Center Configuration Manager Forums
>
Configuration Manager Admin Console
>
Clients that were set to "approved" are now set to NA.....
Clients that were set to "approved" are now set to NA.....
- Hi, We have numerous clients that we installed the SCCM client to and we set them to "approved". Now, a few weeks later, some of those clients now have a "NA" under the approved column, and, under the Client column, it says "No", even though they defiantely have the client. Any idea what might cause this?
FWIW, these machines have not been on the network for a couple of weeks, but I can't imagine that has anything to do with it. ??
Thanks in advance.
Answers
- If a resource is not a client, it cannot be listed as Approved. Approval is only for clients (Client = Yes). So if the resource was no longer listed as a client, then the approval state is accurate.
So what you'd need to do is to figure out why the clients are no longer listed as clients. I'd check to see if you have the Clear Install Flag task enabled (I'm guessing you do) as that task will change Client = Yes to Client = No for systems that have not sent in a Heartbeat DDR within the configured timeframe.
Wally Mead- Marked As Answer byWallyMSFT, OwnerSaturday, October 24, 2009 5:24 PM
All Replies
- Can you go to one of the machines in question and open up the control panel - then open up the configuration manager client and click on the 'advanced' tab and click discover and it return successful?
Zach Smith - If a resource is not a client, it cannot be listed as Approved. Approval is only for clients (Client = Yes). So if the resource was no longer listed as a client, then the approval state is accurate.
So what you'd need to do is to figure out why the clients are no longer listed as clients. I'd check to see if you have the Clear Install Flag task enabled (I'm guessing you do) as that task will change Client = Yes to Client = No for systems that have not sent in a Heartbeat DDR within the configured timeframe.
Wally Mead- Marked As Answer byWallyMSFT, OwnerSaturday, October 24, 2009 5:24 PM
- Hi ZachSmith,
Thank you so much for responding to my question. If I go to one of the computers in question, it does return successful. However upon further digging, it appears as though we also have duplicate machine names listed in our collections. This particular machine shows twice, once with a client and approved and once without a client (and not approved). it also appears as though our DNS was never set to scavenge old records. DNS as since been set to scavenge old records, so time will tell but could this be causing these kinds of problems? Also, will these duplicate machines go away in SCCM once DNS scavenges them or will we have to manually delete them? - Hi Wally Mead,
Thank you very much for that info!! Actually the "Clear Install Flag" is not enabled. Also, I think there's more to this than what I posted before - see reponse to Zach. DNS issue or more? - You have duplicates - was it possible that one of the duplicates was a machine that had windows reinstalled on it? Duplicates would be caused by that. Same machine name - different SID - so 2 of the same in the SCCM admin console. It will go away on it's own depending upon a few things. How do you have your discovery set? What I would do is if you have one of the duplicate machines - just delete any instance of it out of SCCM and remove and reinstall the client on the machine. Does it show up in the admin console now? can you do a site discovery on the machine now? If not, check your boundaries and make sure that machine falls within your boundaries.
Zach Smith - PS - wally you set an answer to this question that was not agreed upon by the asker - interesting.
Zach Smith - Hi ZachSmith,
None of the machines in question have had the OS reinstalled or were reimaged (we use images here). But it's interesting you ask that question. We recently updated all of our images and one of the things we did was to install the SCCM client onto each image. As part of the sysprep process, the machines get a randomly generated name, then we rename the computer as part of setting it up for a user and the old computer gets deleted (automatically) out of AD. Perhaps SCCM is not deleting the randomly named computer when we rename that computer, even though it comes out of AD?
Our discovery is set to the following:
Heartbeat discovery – enabled every 1 week
AD system discovery – enabled daily via LDAP to AD containers
AD system Group discovery – enabled daily via LDAP to AD
But our settings for deleting aged records is pretty much set to 90 days across the board. Is that what most others set it to? We're wondering if changing that setting to something like 7 or 14 days will help with the situation.
We'll try deleting all instances of the machine out of SCCM and uninstall and reinstall the client and see where that brings us. Thanks! - Changing your time to 7-14 days would help remove duplicates sooner. We have a 30-day removal time. So, if I take a machine out of the domain it will stay in the SCCM database for 30 days unless I manually remove it. If I take a machine out of the domain and re-add the same machine after a re-image of the OS - then I will have a duplicate for 30 days.
I'd be interested to know if deleting the machine from SCCM and then uninstalling/reinstalling the client on the machine was able to get a successful site discovery from the client.
Zach Smith - Yes I did, because what I said is correct. Non-client systems cannot be marked as approved. Only clients can. So the 'answer' to the original post is what I said. Now there may still need to be investigation into why systems got changed from clients to non-clients, but the reason they were marked as N/A is that they are not clients.
If O_S_C wants to mark it an unanswered, he's welcome to do so.
Wally Mead - If a system is in the database, and then renamed, we may update the console to reflect that, just depends on the discovery process. If AD System Discovery, not likely, as there may not be anything for us to match against. If it is a Heartbeat DDR from the client, then it would get renamed in the All Systems collection.
Wally Mead - Hi everyone,
We uninstalled the client off of one of these computers. It wasn't a clean uninstall though, as we had to remove it using the "removing SCCM client by GUID". Kind of screams a bad client install??? Anyway, after deleting both computer names in SCCM console, SCCM discovered the machine and it's only there once. So looks like we have some massive cleaning to do. :( :( :( But not sure we were able to figure out why this is happening? - There is a query you can run in SQL against your SCCM database to return all duplicate client machines. It is in this forum - you should be able to find it easily. The issue is probably caused by the way you imaged your machines. I would look here to make sure you are doing it correctly. http://technet.microsoft.com/en-us/library/bb632552.aspx
Zach Smith - Hi Zach Smith,
Thanks for your reply! Will certainly look for the SQL query here. Thanks for that info. As for imaging, we are not yet imaging with SCCM. We are still using ghost to image our computers. So when we updated our images a few weeks ago, we installed the SCCM client onto the image, so as we roll out computers to new employees, the computers already had the client. We are now in the process of removing the SCCM client from our image to see if this helps with the duplicate machines problems. Thanks so much!
