Hi, We have a single secondary site that is acting up. I had a test machine installed and client push went through successfully. After checking over ccmsetup.log everything looked great. The client was installed and had detected its site code properly through AD. 3 days and 10+ update collection memberships later and the client is still showing up as the wrong site code, NO client installed and N/A on the approval. It only knows of this machine because of AD discovery. This is happening on almost all the machines at this site. They all have their clients installed, are updating their site codes just fine, but are showing up as not being a client in ConfigMgr. Any ideas what could cause this? There is nothing unusual being noted in this sites status logs.

This secondary site is not an MP, just a distribution point. Still, no clients in its boundary are checking in with the primary site, even days/weeks after a successful client install which queries and receives the correct site code.

HiCheck the approval configuration.(Auto/Manual)

Are the boundaries configured for the location the client resides in?What does your client's locationservices.log file look like?nick

Boundaries are verified correct. Locationservices.log shows the client finding the correct MP and everything looks fine.

I just did a secure key exchange again (did it just after installing the secondary site to play safe) but it had no affect, the problem persists. DDR.BOX was empty before and after the manual key exchange. Thanks for your help Nick, this is being extremely difficult to track down. /edited for clarity

Any errors in sender.log on the secondary or despool.log / dataldr.log on the primary?

@Minh: the only error found in either log is below, otherwise they both look as they should (same as machines at other sites that are working: Failed in WinHttpReceiveResponse API, ErrorCode = 0x2f78 @Nick: the failing secondary site in this case is actually located in Houston. It must be something with that city! :P In this case there are no overlapping boundaries, I have checked that multiple times. E07 has been odd from the start. When first installed, for about 2 weeks it showed 4 clients installed, then one day we came into the office and it showed over 100 reporting to the server. Since then no new ones have checked in. All these clients have the same problem as my test client - the sccm client is installed and looks PERFECT from the client side, but at head office in Calgary they show up as a non-client. When I say the client is showing up as hte wrong site code, I mean on the client end it is resolving to E01 properly, as ALL clients should as it has been setup. But on the server side, it shows up as a non-client in E07. Nothing should show up as E07 as I have set things up so all client installs should resolve to E01. The secondary site actually has 7 boundaries tied to it...the houston office + all the satellite offices in the area. This problem is affecting all machines within this boundary, but this problem isn't happening on any other secondary site in the infrastructure.

BTW, if this site is not a proxy management point, then why have the secondary? nick Ideally I want all my secondary sites to be MP's ASAP, it was the next step. I have given this sites boundary to head office for now and things are flowing out of there properly, I will re investigate this when I have more time to deal with it down the road. Thanks everyone for your help.