SCCM2007 - splitting system roles
I am currently managing about 4 minutes of reading TechNet before I suddenly find myself distractedly reading something else, so whilst I try and force myself to read through that, I thought I'd ask here - seems like a few have gone through this before me so if I ask nicely maybe y'all can share some of that hard-earned wisdom ;)
Setting up SCCM2007 on a new 2008R2 server here, really so that I can have SCVMM ready to run some Hyper-V hosts across two other physical servers, but I want SCCM set up properly as well. The server I'm setting up on is the physical DC for the new virtual infrastructure. We run about 400 clients, 1100 users, so not a massive network but still pretty reasonable.
So my point is: I would prefer to have as much running on Hyper-V as possible, for failover and easy backup etc., but with SCCM needing to run on the physical host anyway, is it better having it all on one box for integration? Or does SCCM really prefer being split up a bit for load-balancing? The physical server has a 2Gb connection where the 2 virtual hosts will have 8Gb each (although this will have to cover all the VMs), so software deployment might be better from the virtual hosts, where they will have SAN sized storage and faster links. In that case, does the SUP role (with WSUS) want hosting on the same virtual box as the distribution point?
Also - and this point could render the whole discussion moot - I assume that the SCCM licence allows for the roles to be split like this, or am I meant to buy a full SCCM licence for every instance?
What I'm really asking, I suppose, is how you've all done it, and how you'd do it differently if you would. Is one server fine for a school-sized network, or are there benefits to be gained from splitting even for us? I'm not worried about complicating installation, as I'd rather take my time on this and do it right for once, rather than the usual kludge that happens with school set ups :cool: