Search the Community
Showing results for tags 'sccm project desing'.
Found 1 result
Hello Windows-noob, I've been tasked to build, configure, and implement SCCM in our environment. I've been watching (and reading) LOTS of tutorials on SCCM installation and dependencies. However, I can't find much resources on the different design/architectures for SCCM. I hear Windows-noob is the go-to place for SCCM. So here goes.. Here's an overview of our organization: Our organization is 300 Employees large and we have two data centers (different geographical location), with a 100MB connection that links both data centers. Location 1: Head Quarters, houses Data center Apha, 411 windows/linux servers (2DCs, 1WSUS) and Employees (275 laptops, unknown # of cellphones) Location 2: Data center Beta, 667 windows/linux servers (2DCs, 1WSUS) Here're my questions: What flavors of SCCM 2016 does MS offer? How's pricing calculated for each flavor? (I've visited the MS page, editions and pricing are not 100% clear to me) SCCM seems to come with lots of configurable features, what are most commonly used by most organization? (updates, os deployments,..etc) Based on the information provided above, what SCCM topology works best? Stand-alone Primary Site (Location A) with a Secondary site (Location B) or CAS with two Primary Sites? What route should we go for SCCM database (primary site & secondary site)? embedded (same server) vs shared (shared sql server) vs dedicated (it's own SQL server)? What type of impact from a networking stand point should we expect after SCCM has been successfully implemented? I really appreciate your input (including criticism) on any of the above.