CloudBolt vs. VMware Cloud Director

Creates dynamic groups and flexible Active Directory configurations. Improves our automation capabilities. Helps us to automate a part of our Active Directory administration process. Helps us to automate the process of registration and cleaning the computer accounts with Active Directory. Helps us to improve the reliability of registration to mitigate failures like retry logic and post validation checks.

Incentivized

For a CSP it's the best choice. For internal uses, even in presence of different business units, it's not so easy and flexible to manage. It assures a high level of multitenancy, often not needed for internal purposes. But it could be used in this case, just not created for these purposes. Network management is great.

Incentivized

• Create configuration with Microsoft endpoints.
• Support complex globally distributed multi-domains.
• Create and remove dynamic OU.
• Allows for static text in combination with dynamic content.

Incentivized

• Manages multi-tenancy very well. You can setup resource pools of compute, network, and storage that are independent of each other.
• Easy to create and manage multiple environments.
• Has lease management technology and can easily set leases and expire them based on pre-configured time frames.

Incentivized

• Support could be improved on a >tier 1 level
• Logging could be more descriptive/specific
• Stability of the actual server

Incentivized

• Logging, there is a lot of logging but is not always clear where to look for the right logging.
• The syncing of policy, you can't see if or what he did/didn't sync and the status of it.
• More integrations with VMware product (click like Availability)

Incentivized

We honestly haven't looked into much. We've been using CloudBolt [Software] for a long, long time. I think we briefly looked into Morpheus but figured it was too much effort to lift everything, communicate it, etc. We selected CloudBolt [Software] because, at the time (and still do), they served our very specific case. We also liked the ability to customize certain aspects of the deployments - that enabled our "power users" to really tweak things just right for their departmental tasks.

Incentivized

Another option was own scripting or maintaining the end users in the backend (vcenter). This costs to much time to maintain (scripting) and has a big change of a Security breach. It was not an option for us either way.

Incentivized

• We have invested countless man hours to troubleshooting and being support's QA.
• Most of our teams have saved an invaluable amount of time by being able to automate their deployments.
• After the initial time you spend [understanding] all the nuances, the configuring of groups, permissions, etc., does make administering it easier.

Incentivized

• vCloud Director requires less IT administration. For example, there isn't a need to maintain esx host. or storage administration like creating luns.
• A negative impact is cost. vCloud Director has a monthly cost for storage, processor core, memory, and licensing.

Incentivized