What is our primary use case?
SysTrack is used to check device performance to have complete insight into what is happening on end user devices such as laptops or desktops within our firm. We have Windows 10 devices and do not use other operating systems. SysTrack is not being used in our firm on any mobile devices.
We mainly use the solution to investigate what has happened on a particular device. The intention was to use SysTrack to check what trends are occurring within the firm so that we can discover problems before we are actually alerted about them by the users. We have 50 technology team members who use the solution.
What is most valuable?
SysTrack gathers a lot of different metrics on every single device including performance metrics and application-related metrics such as application usage and resource utilization by applications. It collects a wide range of different metrics, and from that perspective, it's a really good tool.
We are able to check what is happening on end user devices at a given time. So, for example, when a user has reported having some issues during a remote call or presentation, we are able to track what applications were started at that time, what resources were utilized by those applications, and check the WiFi network conditions.
What needs improvement?
When I started working with it, it appeared to be a good tool, but after all these years, I have concluded that it does not have the best design. It does collect a lot of metrics, but those metrics are not genuine or precise. When you compare the metrics collected by another software to those collected by SysTrack, the latter do not reflect the actual state of the devices. That is, what SysTrack is providing you is false data. This is one of the reasons why we will be decommissioning SysTrack. We're piloting a new solution right now.
SysTrack is a reactive tool. There's very little in terms of the proactive area of investigations. You can tell afterwards the reason why an issue occurred, but there isn't anything you can do to prevent that issue from happening again.
The interface needs to be improved because it looks ancient. If you have been working in IT for a long time, over 20 years, you might remember products from the start of your career that look almost identical to the way SysTrack looks now.
The user interface is not user-friendly. When you first see the solution, it overwhelms you with everything. It's not easy to use, and it's not that intuitive.
In terms of data collection, all the metrics are combined into packages or groups, which you can disable or enable, but you can't do it on an individual basis. For instance, if you want to collect just the space usage on a hard drive, you have to collect every single metric that is related to the hard drive including all the IOPS or all the conditions of the hard drive. It's not very flexible in that aspect, even though at first glance it appears as though it has huge capabilities to do so. There is one aspect that allows you to create your own data sets and start collecting them, but those are totally independent of the built-in data sets. So, if you want to enhance some metrics, then you actually have to double the data that you collect because you essentially want to have some metric collected in a different way or have it in a different dataset. It forces you to double the data collection. However, I've been told that this may be withdrawn from the solution as it develops the ability to create custom data sets.
You can create your own custom dashboards, but they're static. In comparison, other solutions, including simple ones, allow you to play with the dashboard and apply filters. SysTrack dashboards are very static and not easy to customize. You have to be an advanced user to customize your dashboard, but you can't apply all the filters and focuses on the fly. You have to redevelop the dashboard every single time. There are some filtering capabilities and search capabilities, but they're very basic. I've been told they're going to abandon this in future releases as well.
Documentation-wise, this product is not good. There is some documentation, but you don't have the documentation release dates, and the screenshots may even come from an earlier version. Some documents such those on scalability are missing. The few documents that are available are chaotic and not up to date, even to the point where some, especially in the requirements sections, contradict each other.
For how long have I used the solution?
I've been using SysTrack ever since I joined the firm five years ago.
What do I think about the stability of the solution?
The server is rather stable, apart from one version in which the master server crashed. In our experience, the agents are stable most of the time. From time to time, however, you can't tell whether the data you're collecting comes from all of the devices or some of them. We've had situations when a device was providing some of the statistics but not all of them or some of the data were transferred to the master database with a delay. When you would like to assess whether you have a problem in your environment, the more current data you have, the more reliable is the data. With SysTrack, it's actually not that easy to tell because the situation may shift as the data comes along.
What do I think about the scalability of the solution?
We have a single master server and a single SQL server installation, and that covers over 7500 agents with some custom data collection and custom data sets. We could probably go up to 10,000 with the same setup, but we haven't tested it.
How are customer service and support?
My experience with technical support is that it's very uneven. Some support staff are very good in terms of their knowledge and the solutions they provide. With others, it seems like you're talking to a wall and get no help to solve the problem.
Currently, for example, I have four support cases opened. At least two of them were opened a really long time ago. One, for example, is over four months old, and the problem has not been solved yet. All of them are with engineering or development. If it is a bigger problem, it seems that they don't necessarily know how to solve it. However, there were cases that were solved really quickly and with the level of support that you would expect from a company that has been in the market for a long time.
How would you rate customer service and support?
How was the initial setup?
Deployment is an easy process. I didn't deploy it in the firm initially because SysTrack was already deployed when I started, but I have been involved in a number of migrations. We have a central master server and a Microsoft SQL database attached to it. Then, you have agents that are deployed on end user devices, and those agents can be deployed either through the internal capabilities of the tool, or you can distribute them as we do, which is a CCM, for example.
One experienced person can handle the deployment, but if you do not have a basic understanding of databases or if you don't know how to create software packages, then those tasks can be split across different teams or different people. However, it is not rocket science, and you can actually do it on your own. A couple of important steps during the installation require you to contact the vendor and acquire a license key that needs to be applied.
The same applies to the migration. Even if you have purchased the license, you will have to contact the vendor for the link, and then you'll be able to download the installation files.
Basic deployment with configurations set to default takes two days, providing that you have your Windows servers, SQL databases, and all the security requirements for network connectivity in place.
In terms of maintenance, SysTrack does not have a publicly published roadmap of the product. They don't publish the new releases or new release notes. If you get in touch with someone from the customer success department, then you are provided with that information. You can then plan an upgrade or update. When they release a major version, they will contact you.
What was our ROI?
We have not seen an ROI. In our case, it has been a complete waste of time and money. SysTrack has a brilliant marketing department, which encourages you to buy the solution because it can solve your problems brilliantly. Then, you buy it, and the horror starts.
Once a company invests a huge amount of money in a product, it will be a bit hesitant to decommission the solution. In our case, it took a couple of years, but the decision has now been made to decommission SysTrack and to switch to a different product.
What's my experience with pricing, setup cost, and licensing?
If you compare cloud solutions to SysTrack, which is on-premises, then SysTrack is cheaper. If you compare the cost of SysTrack with that of other similar solutions, the cost is similar.
For each master server, there's a license. In terms of end user devices, the licenses are sold in multiplications of 10. That's one upfront cost. Once you procure the license, you can use the software for as long as you like. The maintenance is sold on an annual basis. Additional costs are related to hosting and include a SQL server license and Windows server licenses.
What other advice do I have?
If you're considering SysTrack, I would advise you to talk with the vendor and to try to use SysTrack for a longer period of time, like a month or two months, before investing in it. Every single software on the market has the option to try a limited edition or a full edition of the solution for a specific timeframe prior to purchasing the solution. However, I'm not sure if SysTrack offers an option to test it and compare it with other solutions.
On a scale from one to ten with one being the worst and ten being the best, I would rate SysTrack at four.
Which deployment model are you using for this solution?
On-premises