If you were talking to someone whose organization is considering SCCM, what would you say?
How would you rate it and why? Any other tips or advice?
Since this solution is agent-based, computers without the agent cannot be reached on the network. In addition, non-Microsoft products are not supported. So if you have a mix of platforms like Linux and Mac OS, you'd be better off looking for an agentless solution and not SCCM. Security is one of the big problems with Microsoft products, but usability is equally good. I would rate this product a seven out of ten.
If you need only deployment purposes, and no management capability, then use MDT also. And if you want to deploy many devices and manage those devices, then go for SCCM.
They are very aggressive with the feature steps that they're adding right, so every 6 months they come out with a bunch of new features, so I like that.
If an organization is more than 95% Windows, then SCCM is the best choice because Microsoft makes the best software to manage their own software.
There is no advice anybody can give on SCCM. Everybody has to go through their journey. It's like giving birth. There's no advice. It works. But you have to deliver yourself.
Do your homework. Understand the basics of it, how it works between services. When you go to install it's going to ask you specific questions, and you might not know what the question is unless you did your homework ahead of time. Microsoft offers architectural sessions. Right before we installed it, we went to Microsoft and they sat down with us and did a session with us to understand how to architect it, how do design it. I would definitely advise doing that. I don't know who they offer it to, but that was very helpful. We met with their architects at Microsoft and they helped us understand how to architect it. I give SCCM an eight out of 10. It's powerful. It's not a 10 because it has little bugs here and there. It has little issues that are annoying. For example, you may want to do something on a maintenance window. There's no way to say, "I want this maintenance window to be on the second Tuesday of the month." It's strict. This window is this and that's it. You can't fluctuate. There are little intricacies that are a little annoying. Sometimes we find the flexibility is not there in certain circumstances.
SCCM is a fantastic solution whose use is only limited by your creativity. Since it allows you to use PowerShell or VBScript to configure settings or execute procedures, a technician can make the any system do what they would like, provided they know how to do it programmatically. It can be a bit of a challenge to setup, configure, and maintain, but once you do, it will benefit you greatly. It is a complicated, complex product, so there is a learning curve, but that complexity is intrinsically linked to its ability to be a powerful tool. If setup improperly, SCCM can wipe out entire environments (don’t make an OS a required task sequence to all computers, for instance), but that is difficult to do.