Filter Ratings and Reviews
Filter 37 vetted System Center Service Manager reviews and ratings
Reviews (1-6 of 6)
February 18, 2020
Service Manager, Solid overall!
We use this tool for tracking IT service requests in our organization. We use this specifically as an internal IT tool that we use between technical staff across the company. We also are leveraging this tool to automate some of the more routine items that we run across on a daily basis.
- This tool is used to track support requests among our IT staff.
- We use this tool to automate some more routine tasks.
- It takes a while to configure everything.
- It lacks some more advanced features of other ticketing tools.
February 13, 2019
Great all inclusive tool, but needs to be babied.
We use Microsoft System Center Service Manager for patching physical machines, as a tool for remoting into end-user machines, getting quick info on devices, and building and deploying packages and software to end users. It's a nice, central solution for much of what needs to be done via our service desk.
- Remote control.
- Quick info on end users.
- Deploying software.
- Kind of clunky.
- Takes a lot a lot a lot of configuration.
- There is a lot of jargon to learn to be able to use it to its full ability.
Used as the main ticketing system on one of the customers. SCSM helps to drive IT processes like incident and change management according to ITIL. Rich reporting capabilities allows us to create informative reports about things going around IT infrastructure, and analyze the trends. It natively integrates into the Microsoft stack-based environment and does not require huge administrative efforts.
- Incident management according to SLAs.
- Change management following internally approved processes.
- Reporting.
- Sometimes clients are working slowly and we are not able to find the reason.
- Hardly customizable.
- Need to spend some time to learn the administration part.
Microsoft System Center is used to push software and security updates throughout the organization. The tool is used for a number of reasons including providing consistent updates, saving manpower and, validation of configuration. We save a significant amount of time, using this tool compared to other tools. The system has configuration into Active Directory which helps to have better control of systems
- Integration with Microsoft Products
- Availability of 3rd party configurations using the tool
- Very large install base promotes administration familiarity
- Reporting in System Center could be more user-friendly. While the data is there, sometimes several reports have to be run to get what you want
- SCCM would be better making updates to SCCM easier. We see risk in updates, so it causes delays, which creates more risk
- Improving the application deployment log files , making them easier to read
We use System Center to image and manage machines. We use it to manage several different images for all the machines in the company. It is also used to deploy individual software as the need arises. It is also a tool used to deploy patches so we can manage them at a higher level and do more thorough testing before we push out to the entire network and find an issue the hard way. It also has some useful tools that you can use to get other information like using the command line and looking into another host to see their user profile.
- Imaging - Can hold all of your images and allow them to be deployed from one central place
- Patching - Able to manage patches from a central database and have reporting on machines out of compliance
- Reporting - ability to utilize several reports to check compliance and other items you may want to review
- When imaging on occasion the system does not seem to accept your deployment. It may require you to put the image in the machine collection several times before it shows as available.
- Patching seems to go well on the admin side but we have been having some issues with them installing on the user side. It seems like the user gets a message and then they get concerned. I have noticed that if you ignore the message the updates will install at some point. It is always a small percentage of users each time we push a patch but not able to tell why this is happening.
- Deploying software seems to be about a 50/50 success rate. Not sure why and it is almost not worth the headache of using SCCM for this type of deployment. It would be nice if it was working consistently because you could push the software and have it installed on the user's machine without any downtime for the user.
February 17, 2018
SCSM is the right choice for an IT environment
SCSM is used mainly for asset management and knowledge management, This allows us to know where and who owns what devices within our company. The knowledge management is mainly used to know how our equipment has been managed throughout the use of. This is mainly an IT organization tool.
- Asset management. Before we used a spreadsheet for serial numbers, equipment location, etc. With having a spread out IT staff managing all this equipment, it came apparent real quick we were losing equipment, knowledge of replaced equipment, etc. SCSM resolved this with a better organization method.
- Compliance Management has become an asset with becoming a PCI compliance shop.
- We just started using the workflow optimizer for team asset tracking. These has helped manage who is working on what issues throughout the companies.
- Customization of the service manage data warehouse. This is the primary function for storing lists within the data warehouse.
- The overwhelming functions thrown at you in the beginning. I recommend a course that steps a new user through all the functionality so it doesn't seem impossible task to implement.
System Center Service Manager Scorecard Summary
Feature Scorecard Summary
About System Center Service Manager
Categories: IT Service Management (ITSM)
System Center Service Manager Technical Details
| Operating Systems: | Unspecified |
|---|---|
| Mobile Application: | No |