kryt

Cheers

Hi, This coming week I need to change the IP of our primary site server due to a networking restructure (adding vlans, spanning subnets etc). As a result I need to change the IP of our SCCM 2012 server. Short of the obvious (server IP, distribution point IP, AD structure, boundaries), is there anything I need to be aware of? Brief description of layout: Twin buildings, one with the SCCM 2012 server we need to re-address. The other is an SCCM distribution point, wsus update point etc. Both on separate physical boxes, on the same domain. One of the purposes of the new setup is so we can use them properly and have each box serve each building for updates, software, DHCP etc so we no longer saturate our inter-building link. Hope that's enough information; I've seen some threads between here and technet that say it really is as simple as changing the IP but I want to absolutely make sure bases are covered.

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!