We seem to be having communication issues associated with AD. Our KC clients are not reporting correctly, showing up as No Client although the client is in fact installed without error. Along with other troubleshooting I suspected I might see a change if I assigned the KC subnet from it's current site in AD (WAL) to another AD site (CHI) under Sites and Services. I made the change and all the KC clients started reporting correctly over the next few days. The CHI DC is also where the SCCM server resides. Recommendation of what I should be looking for? DNS? Port blocking?

Are you using non-default subnets (super nets etc) in Site and Services?Kind regards Tim Nilimaa IT Consultant at Mindgrape (Sweden) Please remember to mark this answer as helpful if it helped you.

As Tim eluded to, what MS calls supernets (I don't agree with their terminology in this case) is not supported for use as boundaries. The main thing is the client has to have the correct subnet mask that matches it to the network ID used in the AD site. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

No. But could you tell me the relevence if that was the case? Other ideas? Thanks!

Let me get this right. You have two sites. A and B. All SCCM servers are in Site B. Clients are in Site A and B. If clients are assigned Site A they report that they do not have an agent installed. If clients are assigned Site B, they do report that they have an agentinstalled. All clients have agents installed. If you change a subnet assignment in Active Directory Sites and Services from Site A to Site B. Clients on that subnet start reporting that they do have an agent installed. You do not have any subnets of the type /23 or like wise. Correct? To clarify the issue with supernets, please refer to: http://blogs.technet.com/b/configmgrteam/archive/2009/12/21/known-issue-supernets-in-active-directory-sites-used-as-site-boundaries.aspxKind regards Tim Nilimaa IT Consultant at Mindgrape (Sweden) Please remember to mark this answer as helpful if it helped you.

We have many sites. The primary SCCM server is in CHI. The location in question (KC) is /24 as well as the AD site it was pointing to (WAL). We do have issues at other sites as well. I was just pointing out a situation with the KC site that I switched the subnet to point to a different AD (CHI) site with success. Across the other sites we do have /16, 22, 24, and one /23. Sorry, my TCP\IP exam was in 1999 so I'm a bit foggy here to be honest... :( Example from one of our sites in AD Sites and Services: WAL Properties Subnets 10.x.x.0/24, 10.x.x.0/23, 10.x.x.0/16 Tim, from the link you provided, this is one thing that has driven me nuts "Some clients that use supernets can behave as expected, while others do not.". This seems to sum up a lot of the inconsistent problems I have seen. So to clarify, if I have an AD site including multiple subnet types, /16,22,23,24, this could/will cause problems for SCCM clients? Thanks!

Read this, (again I stress that I disagree with the terminology used) http://blogs.technet.com/b/configmgrteam/archive/2009/12/21/known-issue-supernets-in-active-directory-sites-used-as-site-boundaries.aspx John Marcum | http://myitforum.com/cs2/blogs/jmarcum |