All my collections are based on OUs in active directory. I have a few workstations with the client that are acting odd after after the OU has been moved. I have it scheduled to run AD system discovery once a day, and it is successful, no errors etc. I have also manually updated it. The machine appears in the proper collection based on OU, although it shows no client installed. Here is what is odd, the machine itself when shows the advertisements that it had from its previous collection A, not the advertisements from collection B that it was moved into through the OU in AD. This was moved 3 days ago now. The machine policy updates give no errors, and the advertisements do not change. The execmgr.log does not show any new programs since it was in the old collection. I checked and their are no duplicate entries for that machine so that is not the issue. I have also done the usual "update collection membership" step as usual. I ran a gpresult, and the computer knows it is in the new OU. I have also repushed the client using client push. Questions: 1) Why does the configmgr console not think the client is installed although it is? 2) How is it still showing the old advertisements from its previous collection even though it is in a new collection now even after a policy refresh? Another issue I have seen is that after a computer is renamed, the console can see the new name\entry pulled from AD, but again it can take up to a week for it to know the client is installed and be functional that is attached to the new name\entry.

Hi1) If the client has been renamed then a heartbeat discovery will reflect the name change in the ConfigMgr console. If a client has been deleted from the console, then a ad sys discovery will make it reappear in the configmgr. console but not as a fully functional client. The client will still work and will appear correctly in the console after running a inventory reseync. 2) have you check the policyagent.log to see if it has successfully refreshed policies.Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products

As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as Answered as the previous steps should be helpful for many similar scenarios. If the issue still persists and you want to return to this question, please reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish. In addition, wed love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks!