Search the Community

I created a collection based on OU and the collection showed up correctly in SCCM. Now when I install the SCCM client on the PC that is a member of that OU (and is part of the collection) the PC is removed from the collection and is placed in the All desktop and server clients collection. Why is that happening? shouldn't the PC still belong in the collection that is based off the OU? I did the update membership and refreshed the collection but the PC still doesn't want to be part of the collection anymore. *I recreated the collection but now when selecting the OU it seems to have created a new structure (which is odd to me). I tried the *new* structure name and sure enough there is my missing computer... structure "a,b computers" OU new structure as seen from SCCM a\ computers ** I ended up going into the system discovery and instead of discovering the computers from the root I selected the OUs that had computers and did a full system discovery. now the collections are pulling the information correctly.

Hi Experts, Looking for some help to understand a rather tricky topic. This has been my understanding so far: Core-based licensing System Center 2016 Standard and Datacenter Server MLs are Core-based licenses. A Server ML Core license must be assigned to each physical core in the server, with a minimum of 8 Core licenses per processor, and a minimum of 16 Core licenses per server. Used Case 1: a single processor server with 4 cores requires 16 Server ML Core licenses, and a 4 processor server with 8 cores on each processor requires 32 Server ML Core licenses. Server ML Core licenses are purchased in 2-packs from resellers and always include Software Assurance. Licensing Rules Software Assurance is included with all Client MLs .When purchased outside of the CAL Suites, Client MLs are available on a Per OSE or Per User basis When purchased via the CAL Suites, Client MLs are available on a Per Device or Per User basis Client MLs include the right to run the Management Server software and SQL Server. Virtualization Rights System Center 2016 Datacenter • The server must be fully licensed with Server ML Core licenses • An unlimited number of virtual machines may be managed on the server System Center 2016 Standard • The server must be fully licensed with Server ML Core licenses • 2 virtual machines may be managed on the server The server must be licensed again to manage a further 2 virtual machines. Used Case 2: A single processor server with 8 cores requires 16 Server ML Core licenses to manage 2 VMs. A further 16 Server ML Core licenses must be assigned to the server to manage another 2 VMs. Another statement in the whitepapers say A customer is eligible for License Mobility through Software Assurance that allows • System Center Standard 2016: rights to manage 2 VMs per licensed server • System Center Datacenter 2016 rights to manage 10 VMs per licensed server Could someone help understand, how would the license calculation work for an ESX on which 200+ VMs are hosted. Would we be licensing only the cores on the ESX box or the VMs hosted as per the matrix given above? Sorry, if this being repeated but I wasn't able to get a clear explanation which will help us calculate the ML licenses.We will get in touch withour licensing partner but need to project an approximate count with at least 10% growth to get a budget forecast.

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.

I am hoping someone may be able to help clarify something for me with SCCM and the versioning. I see System Center 2016 was released, but it looks as if its more server side tools. Is current branch for SCCM the long term versions method, meaning there is no SCCM 2016? Thanks!