Hello. I have a query with regards to SCCM and boundaries. We have a single domain and single site SCCM setup. The current boundary is defined via the AD site and everything works fine. However I have some PCs that cannot be added to the domain, yet must be patched centrally. I was going to create new subnet boundaries to cover these PCs, and then install the client with teh relevant switches. I have tested this using an IP boundary in a lab and it works fine. However I am concerned that the subnet option will overlap the existing subnets defined via AD Sites and Services and picked up by using the AD Site Boundary. Will this be a problem for SCCM? My understanding of the Boundary in SCCM is that it is there to instruct the client what site it is assigned to. Is there more to it?

SCCM does not like overlapping boundaries as a main rule, but as you only have a single site chances are that you will not run into trouble because of this. On the other hand it is no big job to check AD sites and services to see if a subnet is defined in the AD site before adding it as a subnet boundary. A client that is already assigned to a site will still be serviced even if it falls out of boundary, but it will be treated as if it is on a slow connection.

Please do note that SCCM does not support super nets. (ref: http://blogs.technet.com/b/configmgrteam/archive/2009/12/21/known-issue-supernets-in-active-directory-sites-used-as-site-boundaries.aspx) A good source for information about boundaries: http://technet.microsoft.com/en-us/library/bb633084.aspxKind regards Tim Nilimaa IT Consultant at Mindgrape (Sweden) Please remember to mark this answer as helpful if it helped you.

Ooh, so if the subnet is already defined under Sites and Services (which it is), all I need to do is manually install the client on a workgroup (non-domain PC) with the relevant switches. I don't need to specifically add this subnet into SCCM as a boundary as it already exist in AD Sites and Services and still applies to a PC even if it not on the domain. That makes sense!

that's correct.Kent Agerlund | http://scug.dk/ | The Danish community for System Center products

Hi Rashmika, Tim is right, it's not recommended to use supernets in SCCM, for installing clients on workgroup computers, the followings are some basic suggestion: workgroup clients do need to access the server locator point for successful site assignment. See the documentation Determine If You Need a Server Locator Point for Configuration Manager Clients (http://technet.microsoft.com/en-us/library/bb693467.aspx). You can find more information about requirements and limitations for managing workgroup clients in the Configuration Manager 2007 General Supported Configurations documentation (http://technet.microsoft.com/en-us/library/dd547071.aspx), in the section "Computers in Workgroups". Workgroup clients in mixed mode can find their default management point using DNS or SLP or WINS - this data flow shows how each is tried in turn: http://technet.microsoft.com/en-us/library/bb932196.aspx DNS is the recommended way for workgroup clients to find their management point (more reliable and scalable), but your site systems must be configured to use FQDNs and have host records in DNS. If you're interested in using this method, you can find more information here: Determine If You Need to Publish to DNS: http://technet.microsoft.com/en-us/library/bb633035.aspx How to Configure Configuration Manager Clients to Find their Management Point using DNS Publishing: http://technet.microsoft.com/en-us/library/bb633030.aspxPlease 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.

Thank you for the replies on the Supernet Issue. I don't believe our site has this, but I will double check with our Network Team. That aside, we only have one SCCM site, plus I am using the following command line: CCMSetup.exe /mp:XXX.ac.uk SMSSITECODE=XXX SMSSLP=XXX.ac.uk SMSMP=XXX.ac.uk This has worked in a lab using an IP boundary, however in light of the above I'll try it again on a fresh PC without any additonal boundaries defined in SCCM.