Microsoft System Center Suite is a family of IT management software for network monitoring, updating and patching, endpoint protection with anti-malware, data protection and backup, ITIL- structured IT service management, remote administration and more.
It is available in two editions: standard and datacenter. Datacenter provides unlimited virtualization for high density private clouds, while standard is for lightly or non-virtualized private cloud workloads.
$1,323
per month
ServiceNow IT Service Management
Score 8.4 out of 10
N/A
ServiceNow is a fast-growing service management provider that went public in 2012. Built on the ServiceNow Now Platform, the IT Service Management bundle provides an agent workspace with knowledge management, and modules supporting issue tracking and problem resolution, change, release and configuration management, and (on the higher tier ITSM Professional plan) ITAM and software asset management.
$10,000
per year
Pricing
Microsoft System Center
ServiceNow IT Service Management
Editions & Modules
Standard Edition
$1323
Datacenter Edition
$3607
Starting Price
$10,000.00
per year
Offerings
Pricing Offerings
Microsoft System Center
ServiceNow IT Service Management
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Microsoft System Center
ServiceNow IT Service Management
Considered Both Products
Microsoft System Center
Verified User
Contributor
Chose Microsoft System Center
I have not had any experience with another system that you would image computers other than manually imaging them locally with an image.
We used SmarterTrak before and it was almost impossible to use. The flow of ServiceNow is so much better. SmarterTrak was hard to follow the ticket. Unless you were part of multiple groups in the system you couldn't view certain tickets.
When we reviewed BMC offerings and compared with ServiceNow in late 2012, ServiceNow had the most flexibility and I believe still has the most flexibility if you're comfortable with the underlying platform and have a strong guiding service philosophy. You can make the tool do …
Microsoft System Center, SharePoint, Serena. Of those that I have used, ServiceNow was the most competent in all areas. But it was also the most expensive.
We used a product before that was designed to prevent users making changes and saving files to the desktop computer. This required a renewal of the license. By using SCCM in our environment we were able to discontinue using that product because SCCM allows us to completely restore a machine back to the original configuration. We have taught our users to save their individual work on either a network drive or a cloud drive. By doing this, if we do a re-image of their machine they have lost no data, and it makes for a faster resolution. In some instances having a computer in our SCCM environment it can become cumbersome when creating new users for very specific purposes. It can be done by creating new organizational units and applying new policies but when in a pinch it can be frustrating. For the most part we have tried to make "new" purpose images and groups to at least accommodate a quick install.
In our organization, we are using ServiceNow extensively. Change Management, Incident Management, Problem Management, Time tracking are few modules which we use extensively. This sort of model will work for any product or service based companies as the product is built on ITIL framework. So this product will be suited for small or large scale companies to better organize and add controls and track SLA's for technology or business process.
Provides our users the ability to deploy and manage our own datacenter based on defined software with understandable solutions for storage, compute, networking and security.
We are able to update at once all the computers from all departments without having to install the OS on every computer.
It allows us to have everything in one place for database management and datacenter inspection as well.
When I have a number of requests to make, for example a request to add a dozen or so user accounts to more than one group account in Active Directory , I can put all the needed information into the initial form, add it to my "shopping cart" and all of that information remains on the screen for the next item for which I only need to edit a few items (like the AD group name in this example), and keep adding them to the shopping cart until I have them all. When I "Check Out" each of those items is generated as a separate task under the one request. It simplifies and expedites the creation and tracking of these kinds of requests.
I can easily and quickly see what tickets are currently assigned to me in order to prioritize them and remain aware of my workload.
Numerous fields for CIs can be used when trying to find the entry for a particular item. For example, IP Address, server name, raw text, classification, and so on.
To help with making sense out of related tasks, when a task is assigned to me and I need to open another task for a different team to work in order to complete my task, I can open a sub-task from my ticket so that the relationship between the two can be pulled up later into reports. For example, I may have a task to build a new vm, and need to open tasks for networking, security accounts, software installation and so on. By opening sub-tasks from my assignment, the time spent by all parties concerned is tied together for more meaningful cost accounting.
Needs web based storefront for requesting new software
Needs ability to manage the packaging work flow better
Sometimes is slow to download and there is no indication the entire catalog is being loaded, resulting in confused users not being able to find common software in the available list.
It is hard to find areas for improvement, the tool is very powerful. That said, building the CMDB still involves some manual interaction which was not how it was presented in demos.
The CMDB data is almost too deep and detailed. When you build the relationship map it can be so large that it is overwhelming. You can limit this, but the default maps are massive if you are discovering lots of device classes.
The product is expensive. Since they are the leader in the industry and the product has tons of features, they definitely charge for it!
To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.
It is not user-friendly for the most part. With IT infrastructure, sometimes it cannot handle excess requests. Every few months, you will need an upgrade in terms of server resources to keep up with incoming alerts and requests. This does not happen all of the time, but it does happen when there are too many requests.
The dashboard is so confusing, [there are] many clicks to open a task and search by a ticket. The Enterprise customisation [we did] has finished to kill the software and creates a really bad experience on a daily basis. [It is] So slow, and so many clicks to process a ticket. Works only on IE so, that [should] make you realize that [it] is a bad idea.
If I had to dislike something about the system it would be how much it changes once you upgrade. This could be more of a problem of mine since I get used to one way and don't like it when it changes so much. I am enjoying the newest update, but it is a mess when you are actually going through the upgrades.
I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.
To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.
Without exception, every client I have worked with has been very happy with their resulting product. While this is partly due to my work, I must point out that the platform is the winning decision, not the implementer.
We previously used a mix of FOG and Clonezilla to image machines. The biggest issues with these products is that changing one piece of the image required you to rebuild the entire image itself. These pieces of software also did not allow you to manage applications and Windows Updates, causing IT to have to constantly touch machines after they were imaged and update or manage them with a much more hands on approach.
We used to use Jira to handle service tickets but it's way too robust for something this straightforward. Due to the nature of Jira, you needed to already have a lot of documentation and knowledge about who should be assigned the ticket, so the lift of creating a ticket was time consuming.
We have been able to automate our patch management, firmware and other security concerns.
We have a standardized "image" ensuring our setup is consistent across the enterprise. This alone has saved us in time to support and time to understand how to use our desktops.
Overall ServiceNow has a positive impact on getting the SLA of tickets down in supporting our customers.
One negative impact has been the amount of time to get the product to produce an ROI, it's almost too big to fail and too big to replace. You almost become committed to the product. Good or bad.
Another negative impact would be if you track metrics of employees and time tracking, there is a lot of scenarios where engineers will track time on tickets but not get credit for closing them as the assignee function of tickets can only be tied to one user and credits only the engineer who closes the ticket.
Another positive impact would be the level of security for permissions and scaling the workloads is robust and you will get out of the system what your team is willing to put in.