Active directory schema is extended. All the boundaries are AD boundaries except one where the entire AD Site can’t be specified and IP Range have been used to limit the scope of management. IP Range is bound to a secondary site with PMP. Auto site assignment is not working for that site. In the location services, I see that the client detect itself as being in the AD Site TPRA and tries to locate the Site based on the AD site and keeps looping through the same messages. Current AD site of machine is TPRA LocationServices 4/8/2011 12:04:58 AM 2144 (0x0860) Attempting to retrieve SLPs from AD LocationServices 4/8/2011 12:04:58 AM 2144 (0x0860) Failed to resolve 'SMS_SLP' to IP address from WINS LocationServices 4/8/2011 12:05:07 AM 2144 (0x0860) LSGetSLP : Failed to resolve SLP from WINS, is it published LocationServices 4/8/2011 12:05:07 AM 2144 (0x0860) LSGetAssignedSiteFromSLP : Unable to get the list of SLPs LocationServices 4/8/2011 12:05:07 AM 2144 (0x0860) Won't send a client assignment fallback status point message because the last assignment error matches this one. LocationServices 4/8/2011 12:05:07 AM 2144 (0x0860) Clientlocation log shows the following message loop Autodiscover Site ClientLocation 4/6/2011 9:01:27 AM 12632 (0x3158) Getting Assigned Site ClientLocation 4/6/2011 9:04:50 AM 17388 (0x43EC) Getting Assigned Site ClientLocation 4/6/2011 11:16:54 AM 5688 (0x1638) Getting Assigned Site ClientLocation 4/7/2011 8:55:00 AM 19576 (0x4C78) Autodiscover Site ClientLocation 4/7/2011 8:55:01 AM 19576 (0x4C78) Autodiscover Site ClientLocation 4/7/2011 8:55:03 AM 19576 (0x4C78) Getting Assigned Site ClientLocation 4/7/2011 9:02:14 AM 21864 (0x5568) Autodiscover Site ClientLocation 4/7/2011 9:02:39 AM 21864 (0x5568) The AD site TPRA consists of a big class B subnet 157.47.0.0/16 The IP range specified to be managed from the subnet is 157.47.1.0 – 157.47.72.255 I am using AD based site boundaries everywhere else on my network so I am pretty sure if I can get the AD site broken down properly it would fix the issue. Unfortunately, in this environment it would take long time and I am on a time crunch to fix this quick I wasn’t sure what the behavior should be for site assignment based on IP Range boundary? Would an SLP help in this situation? Should I specify subnets instead of IP Ranges? Can I specify the site via script or group policy, if yes will the client go through secondary site if assignment was forced? Any other suggestions?Sarosh

Clients are using /24 Shouldn’t the IP range be affective in this scenario? 157.47.x.0/24 should fall in the IP range I specified 157.47.1.0 – 157.47.72.255 Sarosh

Range IP Starting IP 157.47.1.0 Ending IP 157.47.72.255Sarosh

That’s what I suspected originally but I did verify that 157.47.x.0/24 only belongs to TPRA in AD and I do not have TPRA AD site added as a boundary in SCCM. The IP range (157.47.1.0 to 157.47.72.255) is explicitly specifiedSarosh

I don't believe so. Clicking on Discover throws error "Automatic Site Code was unsuccessfull" Available Actions are "Machine Policy Retrieval & Evaluation Cycle" and "User Policy Retrieval & Evaluation Cycle" Clients accept the site code when I manually enter the primary site's site code so It seems like I can force the site assignment but my fear is that it may cause clients to hit the primary site directly and skipping the secondary site entirelySarosh

What I mean to say is if i assign the site code manually how do I make sure client use the PMP and the secondary site(In this case both on the same server) When I assign the Site Code of primary site manually it shows primary site management point in the Configuration Manage ClientSarosh