| Title | Rating | Mindshare | Recommending | |
|---|---|---|---|---|
| ServiceNow | 4.3 | 22.9% | 92% | 221 interviewsAdd to research |
| JIRA Service Management | 4.1 | 9.5% | 93% | 86 interviewsAdd to research |
SCSM was previously known as System Center Service Manager.
I use this solution for managing client devices, system deployment, application deployment, and customization for their client devices. I work in a consultancy company providing services based on client devices.
I find many features valuable: OS deployment, application installation, packages, programs, compliance settings, reporting services, and so on. I've used SCSM a lot, and its features are valuable.
It would be good if Microsoft added custom attributes or tagging like in Jamf.
I have used the solution for 20 years.
The product is stable.
SCSM is scalable. Even moving into the cloud, adding management by introducing Intune into the ecosystem, or adding additional distribution points, SCSM is pretty scalable in all those aspects.
A small company just needs one server. As SCSM can work for multiple roles for bigger companies, you can eliminate a certain server as a specific role, so you can scale quite easily.
I did not need much Microsoft support, but whenever I have had to contact them, I can open a support ticket and have an engineer assigned to it, so there are no issues with them.
Positive
I have previously used SMS by Microsoft, which is System Management Software. I have also used a similar solution in the Mac ecosystem called Jamf.
Several things could be done in Jamf that could not be done in SCSM, such as custom attributes or tagging. In Jamf, I could build several reports based on custom attributes that were straightforward to define for dynamic group memberships. And SCSM is different. If you have a specific need in Jamf, you can cover it easily. But in SCSM, you have to tweak something, and that's quite complex. The two ecosystems target different client and customer needs. I cannot compare them because both of them, in their specific cases, are covering specific needs. SCSM or Intune for Windows devices is pretty good, and Jamf for Mac devices are both good. But as Mac and Windows are completely different stories, the tools used for managing one or the other are also decent. If Microsoft has to learn something from Jamf, it would be custom attributes or tagging.
The complexity of the initial setup depends on the hierarchy. If you define a quite complex hierarchy, then the deployment is complex. I find the initial setup straightforward. If you know what to do, the initial setup is straightforward.
It takes three days to implement the infrastructure. After that, it's a matter of operating the service.
You'll need a team of four or five people because there are several components, such as database, storage, and networking, and all have to be aligned. But their roles depend on what you want to do. If you want a single administrator and separate and define several roles depending on if you want a system administrator on one side, active directory on another side, or packages on another side, then their roles depend.
The pricing is reasonable.
I recommend the solution for any company that needs to manage client devices, operating system deployment, applications, and application portals for users to install some apps or the IT department that needs the portal for several applications or drivers or any other customization required by the business. It's a good product.
If you want to use SCSM, you should read, learn, and keep testing the product. Building a lab on your premises would be good to test and learn the software. If you don't feel confident in setting or experimenting, just try it outside the customer's ecosystem.
I rate the solution a nine out of ten.
