Can the same ip range exist in two boundaries?
I'm troubleshooting some CAS issues with a computer that is not in our AD forest. The computer is on a subnet that is part of a AD site that's defined in our SCCM boundaries. After having issues downloading updates and seeing issues in the CAS.log, I added the subnet explicitly to our boundaries as a subnet. Will this cause any issues in SCCM since the ip range is part of our AD Site boundary?Orange County District Attorney
September 20th, 2010 9:18pm

Are both boundaries in the same site? It's definately not a best practice but it MAY work if you have them both at the same site. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
Free Windows Admin Tool Kit Click here and download it now
September 20th, 2010 9:38pm

it will work, as long as the two boundaries are not defined in two different sites.Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
September 20th, 2010 9:45pm

Yes they are. One of our AD sites, called DA-401 has several IP ranges defined in AD: 172.23.4.0-172.23.7.254 172.23.10.0-172.23.10.254 172.23.11.0-172.23.11.254 My other-domain computer is on the range 172.23.4.0-172.23.7.254 I thought that my CAS.log problems were because the machine didn't see a boundary for itself as it wasn't part of the AD site DA-401. So I created a subnet boundary of 172.23.4.0-172.23.7.254 Once done, the other-domain computer started downloading content. It feels good but will it cause issues down the line?Orange County District Attorney
Free Windows Admin Tool Kit Click here and download it now
September 20th, 2010 9:47pm

It should not cause issue if those boundaries belong to the same ConfigMgr site.
September 20th, 2010 10:47pm

The reason the machines aren't getting conent is because of the way the IP's are assigned to the AD Site. What Microsoft calls "supernets" (I say it like that because I disagree with the terminology they use) is not supported as boundaries in AD sites. You will have to break those out into IP subnet boundaries. Plus you can't have them in two sites. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
Free Windows Admin Tool Kit Click here and download it now
September 21st, 2010 4:25am

Fortunately I'm only dealing with a singe SCCM site in this case. Once I added the separate IP Range subnet as a boundary, by itself, the client starting pulling updates down within 2-3 minutes.Orange County District Attorney
September 21st, 2010 5:14pm

Fortunately I'm only dealing with a singe SCCM site in this case. Once I added the separate IP Range subnet as a boundary, by itself, the client starting pulling updates down within 2-3 minutes. Orange County District Attorney Just get rid of the AD site and list them out as ranges. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
Free Windows Admin Tool Kit Click here and download it now
September 22nd, 2010 2:17am

Thanks for the tip - I'll take a look at doing this.Orange County District Attorney
September 22nd, 2010 5:09pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics