ServiceNow IT Service Management vs VMware Cloud Director Formerly vCloud Director

• 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.

Read full review

• The advantage to using vCloud Director is it a cloud based application allowing access anywhere. I have the ability to make changes to our virtual environment without being in the office or using a vpn.
• The vCloud Director provides a lot of the same features as vSphere.

Read full review

• 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!

Read full review

• It is not good for end users or customers to use. The UI is geared more towards VMware admins.
• There is somewhat of a learning curve to it, you have to think through and plan out how you want to set your OVDC and PVDCs up. It takes a lot of architecture experience.
• Once you built workloads in vCloud director, it's real difficult to take them out or manage them directly in vSphere. This is a huge pain.

Read full review

• ServiceNow has helped majorly in removing the in-house development effort for the ticketing tool and now we can focus on using the ticketing system and rest is managed by service now
• ServiceNow have had a great impact in Incident reporting and management through its subscription models and a powerful dashboard
• With machine learning feature available within service now, we are able to analyze the incident patterns and root cause and reduce the production outages

Read full review

• Time to market = 0 means profits almost immediate after investment
• Customers trust the VMware brand more than any other
• Elasticity: allowing the company to choose the best HW in the lower layer

Read full review