The use cases are based on transformation projects. For example, if clients are trying to implement some new deployments in SCCM, they use this solution and we help them with the migration. We are currently helping with a Windows 10 migration. Clients use it for application and system crashes in order to maintain the compliance status for their business applications.
On individual machines, we can see the performance and what is going wrong as well as what can be improved in order to enhance the performance of the machine. This is very useful when we get any queries from a VIP user or someone from our project's top management. So if they get into any trouble, then we are able to fix it as soon as possible. Because if an agent is unable to work for two hours or even for two days, that won't make much big of an impact. Whereas, if someone from higher management is unable to work on the system for about two hours, then they would lose a lot.
Initially, we were just looking at it in order to maintain compliances, and we were using it only for that. The guy managing this tool before me was more or less concentrated on device compliances. Later on, we started getting into the application and system crashes (when I started).
In our environment, we need to put a proxy server in place. Currently, devices are connected via the corporate network or the VPN. We don't have machines reporting from the open network. This is something that we are working on. Once that is in place, we will get all the machines reporting in our environment.