Citrix Endpoint Management (formerly XenMobile), is a UEM and enterprise mobility management application for securing mobile applications and devices.
N/A
ServiceNow IT Service Management
Score 8.4 out of 10
N/A
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.
N/A
Pricing
Citrix Endpoint Management
ServiceNow IT Service Management
Editions & Modules
No answers on this topic
ITSM Standard
Custom Quote
ITSM Pro
Custom Quote
ITSM Enterprise
Custom Quote
Offerings
Pricing Offerings
Citrix Endpoint Management
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
—
ITSM Pro and ITSM Enterprise also are available with optional "Plus" add-ons. These include AI Agents, an AI Agent Studio, and other features that augment the capabilities of the platform using AI Virtual Agents to automate tasks.
This product is well suited for any healthcare organization, especially one privately owned by the providers. Many of our providers were displeased with our efforts to use a product that forced sandboxing of Exchange information. Therefore, we needed something that was flexible enough that sandboxing could be used where desired but still allowed native OS integration where necessary.
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.
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.
issues with non apple, non samsung devices: if it is not setup with an apple or samsung phone, then the Certificate onboarding is a struggle/unable to be done.
user-pin setup: for a user to be onboarded, requiring a PIN; there is a self service way but it is clunky and users prefer to call in instead of trying to follow the 15 step process via PDF
if the certificate is ever lost, due to an upgrade via IOS or android, then the entire process [uninstall, reinstall] has to be done, which means downtime for the end user, and higher call volume when a service provider pushes an iOS update.
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.
The software's usability is what we expected. We knew what our organization needed and Citrix was able to meet our needs. The ability to have the apps on a mobile device has been a great plus and Citrix seems to have really developed a software based on the every day needs of the user.
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.
Overall the support from the customer service team has been good. They are very timely and expert in resolving the tickets. They have appropriate knowledge to resolve issues in all stages to development. They were up to the point during the implementation stage of the XenMobile, all queries were answered in time to help finish the deployment. The support for last three years has been extraordinary in helping us use XenMobile effectively and efficiently.
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.
With a zero trust solution for the entire digital workspace, you can continually monitor and assess session activities before, during, and after login. Reduce risk, gain more control over every session, and get deeper insights across your entire application landscape. To achieve this strong security posture across all environments, you need an application delivery solution that shares a common code base. This lets you implement consistent security policies across all your applications for comprehensive protection.
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.
Specific ROI was on us avoiding purchasing company managed cell phones - one of the most important drivers
Makes on boarding, and especially offboarding remote users a heck of a lot easier w/the ability to wipe the container, even if not connected (via time setting)
Easy access to internal resources - no need for separate vpn, etc...
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.
