kryt Posted April 11, 2012 Report post Posted April 11, 2012 Hi folks, wonder if you can help Firstly, many thanks for these cracking guides We're looking to implement 2012 in our educational establishment this coming Summer. However there's a single question I'd like to pose. We work over 2 sites roughly a mile apart, connected via gigabit fibre. Everything currently runs on W2003 via 3 DCs (2 on one site, 1 on the other). About 550 stations, 250 on Site A and 200 on Site B. It's an entirely flat network on a single subnet which is ideally how it needs to stay. Our plan is simple: 2 servers, the primary site server/DC/SCCM 2012 box on Site A, and Site B will pretty much just be a DC and distribution point. However naturally, to avoid saturation of the fibre link we'd like clients on Site B to only get their updates (including wsus) and software from the Site B server. I've gotten this far on my own misconception that we could achieve this simply by splitting the OU's in AD and setting a boundary per site, and a boundary group containing both. But that's clearly not possible, the two ways I can see of doing it are to set up a separate AD site for each site which requires splitting the IP range/subnet, or you can do the same thing within SCCM itself (setting boundaries per IP range or subnet). I *really, really* want to avoid splitting the IP range between site as we have a lot of unmanaged kit like printers which will need their IP's changing. Is there any simple solution I'm missing? We could do it manually each time we throw software/images out but it would mess up WSUS and would add a chunk of time to each new deployment. Pretty much gearing up to having to split the IP range if we have to, but wouldn't hurt to throw this question out here first Many thanks! Quote Share this post Link to post Share on other sites More sharing options...
