I’ve always had a problem with the support statement MS put out stating “supernets” are not supported. I don’t feel like that terminology is technically correct. First of all it’s only for subnet boundaries, ranges ALWAYS work. Secondly you can have a supernet defined as a DHCP scope and have the correct subnet mask and that is supported by ConfigMgr. It’s only when the client subnet mask doesn’t match the subnet mask of the supernet that matters.
In other words if you have two scopes in DHCP that are class C scopes 192.169.0.1/24 and 192.168.1.2/24 you cannot define 192.168.0.1 255.255.255.254 as a boundary in ConfigMgr. This is nothing to do with CM, this is basic subnetting. Your clients network ID in this case would be either 192.168.0.0 or 192.168.1.0 depending upon which scope it’s IP came from. The CM client would try to match it’s network ID to the network ID of the boundary which in my example would be 192.168.0.0 so half the clients would work and the other half would not. From: [email protected] [mailto:[email protected]] On Behalf Of Art Flores Sent: Wednesday, July 13, 2016 5:03 PM To: [email protected] Subject: RE: [mssms] Site Assignment Issues I can confirm what Jason said, SCCM does support a supernet, when I had to figure this out, I had to use the IP calculator at: http://jodies.de/ipcalc As an example, add 10.1.0.0/23 to the link above, and you will see that it can handle 510 hosts. To add to SCCM, add 10.1.0.0/23 to the AD Sites and Services utility, then force SCCM to do an AD Forest Discovery with the “Automatically create IP address range boundaries for IP subnets when they are discovered” box checked, you will see the boundary IP address range has all 510 hosts. [cid:[email protected]] From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of James Massardo Sent: Wednesday, July 13, 2016 4:00 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Site Assignment Issues We do use ranges for some areas but most of our boundaries are subnets. Are you trying to “supernet” some subnets together within SCCM? I.e. putting in 10.1.0.0 as a boundary to cover both the 10.1.2.0/24 and 10.1.3.0/24 subnets? If so, SCCM doesn’t support this technique. Thanks, James Massardo From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Wednesday, July 13, 2016 3:37 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Site Assignment Issues We’ve always used IP ranges, maybe this was why. I don’t recall. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Adam Juelich Sent: Wednesday, July 13, 2016 1:21 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Site Assignment Issues I thought 'IP Range' was the recommended implementation because Subnet and Site Only posed issues. Maybe I'm remembering wrong... On Wed, Jul 13, 2016 at 2:50 PM, Chris Barnes <[email protected]<mailto:[email protected]>> wrote: Hey guys – Have an interesting one for you. I am doing an SCCM Migration at a client. They have 4 existing SCCM sites (1 2007 Central, 2 2007 Child Primary’s, 1 2012 Primary), plus the new 1602 site I just built. I am seeing some issues with site assignment as it relates to client push. I am needing to use an IP Address Range to get the client to be assigned, using a subnet as a boundary isn’t working. There was some existing boundary overlap, I believe I have cleaned all of that up. All sites are publishing correctly. I have made sure that before I add a boundary to the new site, I have removed it from any of the existing sites. Is there anything else that I am missing? Chris Barnes Coretek Services | Enterprise Consultant • 248.767.4415<tel:248.767.4415> cell • [email protected]<mailto:[email protected]> • http://www.coretekservices.com<http://www.coretekservices.com/> NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.
