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?
In the next release, we are moving to the cloud, which also fits the strategy of Microsoft. We would like that the features on the cloud side are very similar to what we have on the on-premise side. We are looking to move to the cloud with Intune, but Intune is not like SCCM in terms of the features. We prefer that they develop all the features on the cloud. I would recommend others to go for it if they are using any other solution to manage their Windows or Microsoft environment. It will make life easier. I would also recommend others to check the cloud solution before implementing the on-premise solution. They can see what can be done on the cloud. Cloud is not fully ready to replace the on-premise solution, but they can do some of the parts on the cloud and some of the parts on-premises. I would rate it a nine out of 10.
Microsoft Endpoint Configuration Manager is suitable for small businesses. If you have fewer offices and fewer users, then the efficacy of this product is very high. If the company doesn't have a system for a long time or doesn't have many employees or environmental issues, they can open Intune and have a cloud-based solution and get all the features together there. You can stage your content, and you can share where you have no connectivity. You can go ahead and do the whole deployment and a lot of things. Intune is still improving, but SCCM has a feature of all this deployment and all other things. So I would say that SCCM has a stronghold and is still relevant. It's an excellent product, but Intune will take it over in a few years. But not entirely because they will coexist. They are working in an environment simultaneously, hand in hand, but I think the market will move more toward Intune (if it's not moving already). I would advise potential users to take a structural approach. They should know the customer's requirements, the number of users, and the locations. They need to have the setup, create a cache, and then binary and secondary options for these deployments. But if you're using a cloud-based solution, you don't have too much worry about it because everything will come from the internet. On a scale from one to ten, I would give Microsoft Endpoint Configuration Manager an eight.
I would recommend this solution to others. I rate Microsoft Endpoint Configuration Manager a nine out of ten.
I would recommend this solution to others who are interested in using it. I would rate SCCM a seven out of ten.
If you are implementing from new, go with Intune directly, don't use the on-premises version. With the transitioning state to the cloud versions, I would rate SCCM a seven out of ten. They have handled desktops very well but they haven't transitioned servers very well.
I would not recommend using this solution. I didn't really like anything about it. In general, I am not a fan of Microsoft. I would rate SCCM a four out of ten.
Since I cannot think of anything in need of improvement concerning SCCM, I would rate it as a ten out of ten.
We are currently looking for another solution to work in parallel to cover some of the gaps in functionality. I rate SCCM an eight out of ten.
We are Microsoft partners. I'm a consultant. This solution is being used by my client's companies. We are using the latest version of the solution, which is 2010. I would recommend SCCM based on the requirement of the customers. However, if they are looking for Unix and Linux support, which is no longer in SCCM, I'd recommend BigFix. That solution is better for Unix and Linux. Anybody who wants to implement SCCM should do some research online, depending upon what features they want. Once they see that SCCM will be able to manage, will be able to resolve their issues, they should choose it. However, they need to look for a partner, a Microsoft partner, that can take help from them for deployment purposes. I would rate the solution eight out of ten. If the product used less resources, I would rate it higher
I would recommend having someone to help with the deployment because the success of its deployment depends on the experience of the people who are deploying it. If you don't have enough experienced people in the internal IT department, it would be helpful to have a consultant from outside the organization to assist you. I would rate SCCM an eight out of ten.
We're just a customer and an end-user. We don't have a business relationship with SCCM. Overall, I would rate the solution at a seven out of ten. We've been mostly satisfied with it as a product.
We are still exploring this solution, and we haven't yet explored all the features. I would rate SCCM an eight out of ten. It just needs a better user interface and some kind of customizations because currently, they are very limited.
Compared to other tools I would recommend SCCM as a good solution for Windows systems only for managing your systems because it provides support for server operating system as well, rather than only for the client's operating systems. I would rate SCCM a nine out of ten but since their support for other operating systems other than Windows is limited, I rate them overall, a six out of ten.
We're just a customer. In the past, we used System Center version 2012, and after one year we upgraded to System Center 2016. Out of all the products in the market, the best solution is System Center, especially for Microsoft virtual machines and all services that are related to Microsoft Technologies. If you are evolving in the Microsoft environment, I prefer to use the System Center due to the fact that it includes different solutions like System Center Configuration Manager, System Center Operation Manager, System Center Virtual Backup. It's a full solution and provides different services. It has great integration with other Microsoft products. I would recommend the solution to an engineer or administrator. And first, a new user will have to study different best practices and have a good overview of the architect of System Center and the functionality of the different components. After that, they would have to go in through the details about the Linux machines. The biggest problems we had at the time of implementation was related to Linux virtual machines, not Microsoft virtual machines. With the licensing and the price, it's a tricky point that the engineers should consider when they need to set up a license Overall, I would rate the solution eight out of ten.
My advice for anybody looking into implementing SCCM is that it has to be on a larger scale, and you have to be committed to Microsoft. I would rate this solution an eight out of ten.
We are at an endpoint site. The servers that are in our data center. I don't know which exact service-side version we are using at our data center. I would recommend SCCM to others. I've used it from scratch and with the new features, especially Intune. I do recommend the SCCM, especially in the Microsoft environment. VMware Workspace One is also good, from what I understand. The issue is they give very limited trial features. If they would give I full fledged trial base version of the VMware Workspace One, it would be easier for someone to completely evaluate the two. Microsoft gives you a six month evaluation period, for example. That's a lot of time to get to know the system. SCCM, therefore, is the best that I can tell, as I've been able to evaluate it fully. Overall, I would rate it eight out of ten.
It's important to be aware of the capabilities of the software and all that it says it's designed to do, and to make sure that you educate yourself on the use of the software. I would rate this solution an eight out of 10.
In summary, this product works well and I recommend it. I would rate this solution an eight out of ten.
On a scale from one to ten where one is the worst and ten is the best, I would rate System Center as an eight-out-of-ten.
We're a Microsoft customer. It's a very good product. The basic question is the size of the company itself that may want to implement the solution. the point is if you're big enough to afford an enterprise agreement, with Microsoft, then I would highly recommend it. It's a suite of products. If you're a small to medium business, which does not have an enterprise agreement with Microsoft, I would recommend that you look around for third party products. Simply from a cost perspective, you might be better off, but if you have the money and the size and the revenue, then definitely, Microsoft is the way to go, because it includes everything. I'd rate the solution ten out of ten.
We are a Microsoft gold partner. We're noticing many users in our country moving away from Microsoft and towards AWS. We tend to use the latest solution, or something close to that. We always are trying to keep it up to date in all the customer database and systems. Whenever there is the latest update available, we update everything immediately for our customers. The latest version may be 19.06. While all the customers we have are currently on-prem, we are looking for cloud-based solutions going forward, due to the fact that our customers tend to gravitate towards the cloud. They are like looking for something they can easily manage. That's all clients, irrespective of whether they are in the office or are our mobile users. I'd rate the solution eight out of ten. I really like the product, however, there's always room for improvement.
My advice for this product is that it's a team tool that can be helpful. At the same time, it can be harmful if you are not using it properly - it can ruin your company. That's because if someone messes up, they can send a package to one client instead of sending it to another. Once you start the initial installation, it is difficult to stop it. So you should be careful. On a scale of one to ten, I would rate SCCM an eight.
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.
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.
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.
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.
Which is better and why?
Let the community know what you think. Share your opinions now!