You need boundaries or the clients will not find the nearest Distribution Point when they make a Client Location Request. The boundaries help them find the content at the nearest Distribution Point.

Startup the SCCM Configmgr console to check the site boundaries and verify the the SCCM server site name is configured for active directory instead of the IP address (as it is by default). Configuration Manager 2007 clients are assigned to Configuration Manager 2007 sites based on the boundaries defined for the site. Boundaries are defined by IP subnets, Active Directory site names, IPv6 prefixes, IP ranges or a combination of these. We need to configure the Site Boundaries in order for auto-site assignment to succeed (the clients network location must fall within one of the configured boundaries for site assignment to succeed.

Configuration Manager 2007 boundaries are used to identify a roaming client’s position in the Configuration Manager 2007 hierarchy, which in turn facilitates locating the nearest distribution points that host the content requested by clients. When a change in network location results in a client being outside its assigned site’s boundaries, it relies on roaming behavior to locate content.

For more information about planning Configuration Manager 2007 site boundaries, see Planning Configuration Manager Boundaries, and for more information about content location, see Configuration Manager and Content Location (Package Source Files).

The boundaries node of the Configuration Manager console displays all boundaries defined for every site in the Configuration Manager 2007 hierarchy beneath the current site. Boundaries defined for SMS 2003 child sites before joining a Configuration Manager 2007 site hierarchy are not editable. To change the boundaries of an SMS 2003 child site, the pre-defined SMS 2003 boundary must be deleted and a new one created from within the Configuration Manager console.

Startup the SCCM Configmgr console and click on the + beside Site Management to expand that section.

Underneath that you’ll have your SCCM Site Server name (in my case WIN), and underneath that we have the Sites settings.

Attached Image: monthly_08_2008/post-1-1219742708.jpg


You’ll need to know your AD site name. The AD site name is by default called Default-First-Site-Name and you can change that in Active Directory sites and services just as long as the site name is the SAME in both AD and SCCM site boundries

Before change:-

Attached Image: monthly_08_2008/post-1-1219742352.jpg

below we have renamed the Default-First-Site-Name to windows-noob in Active directory sites and services

Attached Image: monthly_08_2008/post-1-1219742361.jpg

Open SCCM Configmgr and expand Site settings, click on the Boundaries node, right click the node and select New Boundary from the context menu.

Attached Image: monthly_08_2008/post-1-1219743103.jpg

Attached Image: monthly_08_2008/post-1-1219743581.jpg

Click on Type and change it to Active Directory Site

Attached Image: monthly_08_2008/post-1-1219743710.jpg

click on Browse and select the AD site name we configured earlier in AD sites and services.

Attached Image: monthly_08_2008/post-1-1219743820.jpg

click on ok to complete

Attached Image: monthly_08_2008/post-1-1219743872.jpg

click ok again and we can now see our SCCM Site boundary is setup in ConfigMgr.

Attached Image: monthly_08_2008/post-1-1219744133.jpg