I'm having many issues, and I bet they are all related. The first issue I noticed was when I went to add a PC to a collection, direct membership, it wouldn't show up in the collection. I refreshed and updated the collection, and nothing. I pulled the PC from the all systems collection that it was in. It's not obsolete and approved. I figured it was just that PC, and it was hosed, needed redone to begin with so I took a Boot disc and did it that way. When it got redone, it still didn't connect back up to SCCM, it's fine in AD. SO I ran a repair on the CCM client, and not it's all installed, but nothing is enabled and there are only 2 actions. The automatic site code discovery is sucessful on the PC. Trying to redo another PC and running into the same thing. Not sure what to do, can't find anything in log files thats helpful. Running SCCM R2 SP2.

See if the Management Point is working: http://technet.microsoft.com/en-us/library/bb932118.aspxTorsten Meringer | http://www.mssccmfaq.de

I get this, not sure if this is what it's suppose to look like. - <MPList> - <MP Name="server" FQDN="server.domain"> <Version>6487</Version> <Capabilities SchemaVersion="1.0" /> </MP> </MPList>

The Management Point looks fine. If an object exist in the database (All Systems), then it should also show up in any other collection that matches the correct criteria. Rebuilding the machine should not be needed. At this point do you have the computer in the database? If yes, create a direct membership rule. Select System Resource and name. Instead of typing a name, just type % and click next until you get to list of all names found in the database.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

I reimaged it to put it on Windows 7. Right now it's in AD, but not the all systems collection. I tried a repair of the CCM client, it looked like it was fine, but the components are listed as installed and there are only 2 actions. Site Code discovery is fine as well. I did have a very strange issue when I got done imaging it. The computer was on the domain, you could log onto it, but it wasn't in AD. I didn't delete the old machine out of AD before I did it, so I'm not sure if it got confused with that. I deleted the old name, removed and readded it and it picked up the PC with the new name. I have another PC I can set up a direc membership the way you said to and nothing gets added. Started a new collection and can't add any PC to it as well. I uninstalled the client, then rebooted. The server must have found the pc without the client and pushed it down and it installed, but still all the components are installed and only 2 item come under actions.

I reimaged it to put it on Windows 7. Right now it's in AD, but not the all systems collection. I tried a repair of the CCM client, it looked like it was fine, but the components are listed as installed and there are only 2 actions. Site Code discovery is fine as well. I did have a very strange issue when I got done imaging it. The computer was on the domain, you could log onto it, but it wasn't in AD. I didn't delete the old machine out of AD before I did it, so I'm not sure if it got confused with that. I deleted the old name, removed and readded it and it picked up the PC with the new name. I have another PC I can set up a direc membership the way you said to and nothing gets added. Started a new collection and can't add any PC to it as well.

Hello - What about the discovery methods and schedules? Did you check the disc overy log files Adsysdis.log (the systems are discovered)? How is the SCCM client installed on the system?Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

adsysdis.log looks like it finds some of the PC's, but not all. I do get a few of these errors on PC's it can't find: WARN: Could not get property (domain) for system (0x80005010)~ $$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Wed May 04 00:00:04.832 2011 Eastern Daylight Time><thread=3376 (0xD30)> The PC i'm looking for isn't listed in the log. In the ccm log on the server, I get an eror about the server's clock not synced with the PDC clock. It worked fine a few days ago, so I'm looking for something yesterday or day before.

double check the LDAP path you have specified in the AD system discovery properties.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

It looks like its ok. If finds most of the machines, I know some it won't since they aren't on the network right now. Found this in my compmom.log an not check availability for component SMS_SOFTWARE_INVENTORY_PROCESSOR since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.253 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_REPLICATION_MANAGER since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.254 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_MP_CONTROL_MANAGER since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.254 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_INBOX_MONITOR since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.254 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_OFFER_STATUS_SUMMARIZER since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.255 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_INBOX_MANAGER since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.255 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_DISCOVERY_DATA_MANAGER since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.256 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_WSUS_CONFIGURATION_MANAGER since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.256 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_POLICY_PROVIDER since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.257 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_OUTBOX_MONITOR since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.257 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_WSUS_CONTROL_MANAGER since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.257 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_STATE_SYSTEM since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.258 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_LAN_SENDER since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.258 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_INVENTORY_DATA_LOADER since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.258 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_WSUS_SYNC_MANAGER since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.259 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_MP_FILE_DISPATCH_MANAGER since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.259 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_WINNT_SERVER_DISCOVERY_AGENT since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.259 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_SOFTWARE_METERING_PROCESSOR since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.260 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_SITE_CONTROL_MANAGER since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.260 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_FALLBACK_STATUS_POINT since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.260 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_SCHEDULER since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.261 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_OBJECT_REPLICATION_MANAGER since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.261 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_HIERARCHY_MANAGER since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.262 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_SITE_SYSTEM_STATUS_SUMMARIZER since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.262 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_INVENTORY_PROCESSOR since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.262 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_DISTRIBUTION_MANAGER since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.263 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_STATUS_MANAGER since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.263 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_STATE_MIGRATION_POINT since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.263 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_PXE_SERVICE_POINT since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.264 2011 Eastern Daylight Time><thread=2960 (0xB90)> Can not check availability for component SMS_OFFER_MANAGER since its execution state is unknown.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.264 2011 Eastern Daylight Time><thread=2960 (0xB90)> Waiting until the next polling cycle in 300 seconds from now.~ $$<SMS_COMPONENT_MONITOR><Thu May 05 14:22:58.264 2011 Eastern Daylight Time><thread=2960 (0xB90)> Doesn't look good :(

I got it working, restart the services. Apparently it has to do with the backup and there's a KB patch for it. I closed the browser before I could get the patch, so will need to go and find it again, but seems to have fixed the issues.