Setting up Turbonomic is pretty straightforward if you take it slowly. If you assume you know the answer and click "next" automatically, you will run into an issue here or there. You must properly set up your permissions in the vCenter and Nutanix before you install. I always make a Turbonomic-specific local ID so it can't be used anywhere else.

It's a nice security practice using a local account for Nutanix and one for vCenter to connect proper permissions. After the prerequisites are in place, it is relatively straightforward. It used to be pretty cumbersome for the licensing. I haven't done a fresh installation since 8.1. It wasn't as simple before 8.1, and it seems like they've streamlined it even more in 8.5. I don't think you'll face any challenges if you follow the instructions and set up the accounts it needs to connect to from the appliance ahead of time.

It took about 15 minutes to configure Turbonomic for Nutanix because I connected through Prism Central. That includes verification and making sure the data is coming in. For VMware, it took no more than 10 minutes per vCenter that I added. I spent probably half an hour reading instructions to ensure everything was right before I started.

If you can't set this thing up then you shouldn't be in IT. We're only using it from the infrastructure side. You log into it, you set your passwords, import your vCenter into it, put in the credentials, and tell it what vCenters you want it to monitor. And it just starts gathering data.

We did our setup many years ago and, back then, we had a guy there walking us through it because they were a brand-new company. They really gave us the white-glove treatment. I think we may have spent two hours on it, but most of that was talking. If you buckle down and just shut up and do it, it would probably take 15 or 20 minutes. It only takes one person to implement it.

We have six guys who use Turbonomic now. Some are higher-level guys and we have our entry-level guys, but everybody has access to it and looks at it if they need to.

Turbonomic is fairly easy to deploy. The product is highly intuitive from a deployment standpoint. We worked with a consultant from the vendor. The deployment team consisted of five or six people.

Turbonomic has gone through several versions, and the latest is the most complicated because the first wasn't Kubernetes. It's a deployed OVF, so it's not that hard to do. Understanding the UI and configuration options isn't easy, but I'm an old guy who has been around since '87. I think all the new interfaces are unbelievably complicated and incomprehensible. It's like any product. Turbonomic is easy once you understand it. 

I didn't find the deployment to be complex or challenging. After you've deployed it, you need to configure it, do some placement, and tweak its recommendations. For example, I would never implement an odd number of CPUs, so I will specify that it only makes recommendations in units of two.

The deployment process is relatively lengthy because they've done all this Kubernetes stuff. You deploy it, and it spawns all these Kubernetes things. You need to wait until it finishes. It isn't instantaneous. 

Turbonomic requires no more maintenance than the average application. We keep it updated but don't immediately upgrade to the latest version. We stay one version behind. That's the sweet spot because we don't want to deal with problems in a brand-new release. We also review it annually. I can think of at least two occasions where they scheduled a technician to help us get it to the spot we agreed was the best. 

The initial setup was very straightforward. This is one of the very few tools which we were able to stand up and get it running within weeks. 

It is a very simple product to install, then there are just a couple of configurations to tweak. Then, you are up and running. They literally tell you what you need. It's like, "Here are the requirements: You need X number of virtual images - this level." It has very simple instructions. We probably had it installed in one day, then we had everything reporting within a couple of days. After that, we did the tuning, mapping, and everything else. Within 30 days, we were probably getting useful data out of this tool.

The setup is straightforward. It involves bringing down all the services from vCenter. There's nothing complicated about it. Deployment takes half a day once you have all the prerequisites, like the IP hosts, record ports, firewall configurations, etc. The virtual operations team handles deployment and maintenance. It's about ten people. 

The initial setup was relatively straightforward. It was a pretty easy setup. I wouldn't say it was any more difficult than any other tool that we set up or have used in our environment. It is pretty easy to deploy, then probably just as easy to configure once it was deployed.

We did not go with the SaaS offering. We most probably implemented it on-prem. I was not involved in its deployment in this company, but I was involved in my previous company.

I would rate it a seven out of ten in terms of the setup. It is not as straightforward as they say during the sales calls, but most of the complications that we faced were from our side.

The initial setup was straightforward. I worked with some engineers and they were really helpful and really kind. They guided me along the path. 

We actually deployed a proof of concept first, over a couple of days. Then we took the proof of concept and applied for a license and then just put it in an environment. The deployment process took a couple of days.

It's incredibly easy to set up. It took a couple of days. You spend more time building servers and getting ready for it.

It gathers its own data from vCenter. It doesn't touch the actual servers at all. Same thing with the different cloud vendors. It looks at your account information. It doesn't actually have to touch the servers themselves.

As far as the product goes, it's not an agent based. It can gather information, and start making recommendations within two or three days, then better recommendations within a week. After that, you're good. It doesn't get much easier.

The deployment process is a little tricky. It wasn't hard for me because I have pretty in-depth knowledge of Kubernetes, and their software runs on Kubernetes. To deploy it or upgrade it, you have to be able to follow steps and use the Kubernetes command line, or you'll need someone to come in and do it for you. We're deploying it to use with our OVA in our VMware environment on-premise, which is a little rough. It's not terrible, and I've had way worse software vendors, but I would say there's probably a little bit of room for improvement as far as upgrades go. We have to schedule a window and then make sure everything's working. With other on-prem services, you just run one command, and everything updates for you. Turbonomic upgrades are a little more involved.

When the guy on our side was going through the install process and setting all of this up, he had to get into the virtual machine environment and do a bunch of stuff, download some things, and then start running scripts. On top of that, he was trying to run these Kubernetes controls, and this other guy was helping install them. So it felt a little more clunky. I don't know how you would improve that unless it was a complete software solution service or a simple installer that you download and run.

The total deployment time depends on some different factors. We've deployed Turbonomic a couple of times. When they come out with a new version, we have to do a complete redeployment. I wasn't involved in the initial setup, so it's hard for me to say. But it took a couple of days to deploy the new version, plus a couple of hour-long sessions. It was around 15 hours total. I remember we tried to download a file, and it took two hours. I think that was because of the internet connection on our side. It's hard for me to quantify it. 

We have it set up in the cloud and on-premises. I wasn't involved in the initial deployment as it was already on-prem. We just expanded it to the cloud. That operation was very easy. We just opened the access to the cloud. That was it.

We have a test environment, so we apply things on the test environment and make sure our policies are having the proper effects and are working perfectly. We can work on an environment-by-environment basis.

There is not much maintenance involved, other than applying patches.

The initial setup was fairly straightforward.

There were some complexities added from our side in trying to make sure that this platform was most successful with the standardizations that we have in our environment. When Turbonomic would perform actions, in most situations, we're actually calling on it to run in-house developed scripts to perform the additional configurations required from that action. Since that has been taken care of, it's been great.

To clarify, the initial setup is simple but we brought some complexity on ourselves. To deploy it to the level that we're using now, it took between six and eight months. This was really taking our time going through non-production environments first, then production, turning on one thing at a time.

There were also scheduling concerns, such as having our maintenance windows every other month. This didn't give us much opportunity throughout the year to deploy, which is why it took several months for us to get fully implemented. Even today, we're still not using it to its fullest potential.

I went to the training when they first rolled it out, but I wasn't involved in the setup.

They did the setup in sections. So, they started off with the lower environments and some of the clusters out there that really needed a lot of attention, mostly blade servers and such. So, it was a gradual rollout. I think the entire rollout was somewhere in the area of a year to a year and a half. However, to get it fully running, where we could use this solution to our benefit, that was at least six months.

We use scheduling in real-time for implementing the solution’s actions as well as manual execution, which is when we schedule for a later date to change activities. We have had to enable or disable certain things. It seems to do that just fine.

The initial deployment proved complex due to our extensive environment, encompassing over 23,000 VMs. This necessitated a year-long rollout, overseen by a dedicated team comprising a salesperson and a senior technical expert.

The initial setup was very straightforward, and it was done within a couple of days.

The initial deployment is very straightforward. The Kubernetes stuff was a little beyond me because I'm not a Kubernetes person. But once we got somebody who knew Kubernetes involved, it was pretty straightforward. It takes less than a few hours and that's for an enterprise. It can be done very quickly.

We started with the solution on-prem, but I quickly moved it to the SaaS model because with on-prem there's a lot to manage. It's a Kubernetes cluster and you need a Kubernetes administrator. You have to have rights to it. There are a lot of other moving parts when you manage it yourself. Once you move to a SaaS-based solution, the burden of keeping the product upgraded and up to date is on Turbonomic. I don't want to manage updates and patches.

With the SaaS solution, there is no maintenance on our side.

The initial setup was straightforward. It's point and click. You install the VM and point it to your environment and it starts working.

The initial deployment took a couple of hours. 

I was working for the company when they implemented Turbonomic but I wasn't part of the project that implemented it. I have since taken over one of the primary roles in utilizing it and we've deployed an updated version of it. I have a co-manager who uses it as well, on the same level as me. We back each other up on it.

That's something where there is room for improvement: upgrades. We have deployed the newer version, version 8 of Turbonomic. The problem is that there is no way to upgrade between major Turbonomic versions. You can upgrade minor versions without a problem, but when you go from version 6 to version 7, or version 7 to version 8, you basically have to deploy it new and let it start gathering data again. That is a problem because all of the data, all of the savings calculations that had been done on the old version, are gone. There's no way to keep track of your lifetime savings across versions.

Maybe there's a way that they can go and retrieve those specific bits of data, but so far I haven't seen how that happens. I would like to see them make major version upgrades work, first of all, because you can't currently upgrade to a major version. You have to deploy it to a new server. But at the very least, if we have to deploy it to a new server, give us a way to pull in that lifetime savings information, and track the information they've built up. We've had the same one for almost two years and it would be nice to keep all that tracking information for future reference.

Our admins who deployed the technology said it was fairly straightforward. Because Turbonomic in OpenShift runs as a pod, it is fairly straightforward from a deployment model.

It is a relatively easy product to implement. If you're familiar with OpenShift, my OpenShift admins had no problems deploying it and working with the Turbonomic team. Their support has been great.

Phase one in deployment is to understand what actions would be from Turbonomic regarding resizing, then take actions based on those recommendations. After we are satisfied with what Turbonomic is doing, we will let Turbonomic take automated actions, which is phase two. We will be building a better trust relationship between our app and operations teams, when we allow Turbonomic to automatically deploy and take actions.

We like that Turbonomic provides a proactive approach to avoiding performance degradation. In phase one, we will do a manual evaluation of the recommendations. Then, in phase two, we plan to have Turbo fully automated and take actions based on what it thinks the best resource allocation model is.

We have two separate OpenShift clusters. We will be deploying one environment with more than 100 nodes and the other one with more than 50 nodes.

We tried it first on-prem, years ago. We used to host it. I installed it and updated it, working with the Turbonomic team. When it was hosted in our environment, I was responsible for everything.

The initial setup was straightforward. Because it was an appliance, the deployment took about an hour to stand it up. We use VMware on-prem so it was done with an OVA file, and it was pretty much a "next-next" process because the OVA is already packaged with how the tool should be deployed. There are certain custom inputs needed, like the name of the appliance, and how much storage. But everything else was already pre-packaged. The configuration definitely took a little bit longer.

The only downside was that Turbonomic came out with many releases. The latest releases had the latest features, but it required continuous upgrades. If we wanted to take advantage of one feature we continued to have to upgrade the appliance on-prem. That is why, when we found out that they do have a SaaS model, we went with that instead. We wanted Turbonomic to worry about things like the licensing, the updates, et cetera. We don't have to worry about that at all now, and that has been a huge relief. That has saved us a lot of time, for sure.

We didn't have to do any type of migration to their SaaS offering. They took care of everything in the back end.

We have five engineers who use the product, including a networking engineer, a storage engineer, and our DevOps team.

Very easy, just deploy the appliance and enjoy. There is very little setup that goes into this.

I am not involved in its deployment. In terms of maintenance, there are general updates, and making sure the platform works and you are getting what you need from it.

The deployment model depends on the requirements, but 90% of the time, it is in the cloud. In certain classes, it is deployed in the cloud, managing multiple hybrid infrastructures between the cloud and on-prem. In certain circumstances, it is separated between different sites across the globe.

I'm the one who deployed the virtual appliance, connected it to our vCenter, and did the add-ons for Pure Storage and Dell storage. The setup, back then, was pretty straightforward. The complexity came in when we started having to use policies and rules. That's where we got a lot of help from Turbonomic.

The full deployment from end to end, with policies, took just over a couple of weeks. We have under 10 users of the product.

Initial setup was performed by a teammate who has moved on, but as I recall, it was a straightforward process.

Setup is very easy. Takes a little extra config to add in storage arrays but well worth the extra time to do for the results that brings

We simply installed their VM and turned it on. Thirty minutes later we made the decision to go live with virtual machine automation and have not looked back.

Download OVF file, then configure the IP, enter your VC credentials, and boom, you are done. Just one virtual appliance.

Very straightforward. It was as simple as loading an OVA, setting the networking, and pointing it at our vCenter. Tweaks have been made over time as needed, but the initial setup was quick and painless.

Setting up Turbonomic was pretty straightforward. You deploy the OVA, answer some questions, and point it at your environment. It's one of the easier infrastructure products to implement. I deployed Turbonomic in one afternoon, so it was a couple of hours max. After deployment, we had to install regular updates, but it was easy to do. Two people are involved in maintaining the product. 

The setup was straightforward. You simply install the OVA, set the IP, and plug it into your Vcenter.

Easy.

Setup was very easy.

The initial setup is pretty straightforward.

Setup is relatively straightforward. There is a template to deploy and configure the initial IP address. After that, the rest of the configuration is performed through the web GUI. This includes adding various environments, setting up reports, configuring actions, etc.

It wasn't too complex.

Straightforward with no issues.

Install is almost to easy and the tool is up and running in no time.

The initial setup is very straightforward. You execute an application or a script, depending on whether you're running it in Linux or Windows, and then you deploy the containers. It's pretty much one command and then everything is automatic. It took us about 20 minutes. 

The initial setup of Turbonomic was straightforward. I worked with somebody from Turbonomic and we got an understanding of the environment and we worked together to get it installed and to get the placement working first. After the placement, we worked on changing and automating the addition of CPUs and RAM.

We pretty much set up the product from the documentation provided. This was originally one of the few products we researched that was a single virtual appliance.

I think my six year old son could deploy it.

Step 1. Deploy OVA.
Step 2. Connect to vCenter.
Step 3. Complete

Pretty Straightforward.

Upgrading the solution is straightforward. It is pretty easy.

When we are notified of an upgrade, feature pack, or patch, it is like a two or three step function to get to the next level. It is very non-intrusive and easy. It takes 35 to 40 minutes to upgrade or apply a patch, and the solution doesn't go down.

It was very straightforward. It was basically just an OVA appliance that I brought up, licensed, and then gave it permission to be able to talk to my vCenter. Boom, everything was out there and running. You could actually write custom reports in it and do things of that nature. Its setup was very easy.

Very straightforward and the technical team walked us through all we needed to configure.

Initial setup was with the "appliance" package but we decided to migrate to a RHEL server. Both the setup and migration were documented well and easy to follow.

Pretty straightforward.

Initial setup is fairly straightforward. We deployed a virtual machine - configured it to our vCenters - and that was pretty much it.

It was originally deployed before my employment, but I did do redeployment and the process was very simple.

Very straightforward, we powered up the trial VMTurbo virtual appliance, gave it an IP address, pointed it at vCenter and the NetApp clusters and started using the product straight away.

Initial setup was straightforward.

Very simple. If you can run "yum" and follow a one-page document you can install this product.

Simple setup that was easy enough for a sales person to do.

Initial setup was very straightforward. OVF download and deployment to live application in less than 30 minutes.

Very straightforward. The only downside was we lost history of prior performance.

Very straightforward, we were up and running in less than half an hour.

Really straightforward, just deploy an OVF template to your VMware environment. Configure a service account and setup permissions within VMware so the account can access what you want it to and stop it from accessing hosts you don't want to monitor.

Initial spinup is simple from an image, with some configuration help from support at the time of implementation.

The initial install was very straightforward. We downloaded the package and uploaded to our Virtual Environment. After following a few guided steps, it was completed.

The initial setup was very straightforward.

Initial setup is as easy as you would want. Simply deploy the OVA and point it to vCenter.

Very simple.

Setup was simple and fast.

Very straightforward, we were able to easily import the VMWare appliance to our environment.

The install was very straightforward. I don't think it took more than an hour to implement.

We had no problems and the installation folks were there just in case they were needed.

It was a simple deployment, but was done by a Turbonomic employee when our initial 30 day trial began.

The setup was simple, with the deployment of a virtual appliance. Updates are similarly easy.

Tech support aided in the install, and then provided training. The install and setup is straightforward.

It was a standard OVA deployment with just a few configs to get set up.

Straightforward.

It is pretty straightforward.

Very straightforward.

Straightforward. Upgrades are easy as well.

It was a very straightforward setup, as far as getting the product running. It got a little bit complex defining rules for my specific environment. For instance, "don't auto-resize machines whose name is like "nnnnnnn". Tweaking the rules to fit my odd needs was complex, but the support team breezed right through it for me.

Not at all, deploy it, give it an IP or DHCP then connect to vCenter. 2-3 hours later you will start to see recommendations.

Straightforward. Deploy an OVA.

The initial OVA based setup, including setting up one or two service accounts, took less than 20 minutes. I believe that our vSphere environment was discovered in less than an hour.

Simple OVA deploy and IP setup.

Pretty straightforward.

Initial setup was straightforward: deploy OVA, assign IP address, log in as administrator, configure your targets, done. You can be up and going within 60 minutes.

Painless.

Very simply and fast setup. Customizing can feel daunting at first.

Very straightforward.

Initial setup was very straightforward. At least getting the appliance up and running and connected to vCenter. Fortunately, support was excellent and provided some hand-holding in the initial configuration, and it has been pretty much set-it-and-forget-it since.

The setup was very easy. Deployed the OVA, assigned a static IP and linked it to our hypervisors. Saw recommendations to improve our infrastructure within minutes.

Initial setup was very simple. Deploy a simple OVA, give it an IP and sufficient rights, and voila.

Straightforward. It was just a virtual appliance.

We opted to have trainers come onsite. They first worked with us remotely to set it up.

Complex - highly secured environment. Had to change many of the system configs to make it more secure.

Straightforward and easy to setup.

Was straightforward, we had no issues installing the appliance.

I didn't handle the initial setup of this product. I inherited it. For upgrades they seem fairly straightforward, but we have always had Turbonomic assist in upgrades.

Straightforward, extremely user friendly.

It was fairly straightforward to set up and anything we could not figure out ourselves the team had a solution for us very quickly.

It was very straightforward - deploy the appliance, add my vCenter Servers and wait for data to populate. Doesn't get much easier than that.

Both, you can do a lot with it out of the box, but you can also get quite advanced with managing the environment.

Initial setup was straightforward.

Very easy. Deploy an OVF template, some minor out-of-the-box configuration, and it is up and going.

Ongoing.

NA - I did not participate in the initial setup.

If you are familiar with the VM product you're using, then setup shouldn't be a problem.

Just install and hook into vCenter and then understand what it is saying.

We did initially work with pinning workloads between types of VMs but now let all swim in the same pool with a Turbonomic lifeguard.

Easy and straightforward.

Very simple to deploy the appliance, give it an IP address and then after logging in, attached it to your vCenters....simple!

Very straightforward.

Unit was up and running in 5 minutes. All I needed was basic networking information and admin accounts

The setup is very straightforward. Deploy the VM from their OVA file and within 30 minutes you're up and running and ready to automate workload placement.

Setup is very straightforward and you have data within hours, not days or weeks.

It's a very straightforward setup, anyone can simply deploy.

Easy to deploy.

Initial setup was very straightforward with very simple steps to follow.

Setup of Turbonomic is straightforward and easy to deploy.

Yes, it was a simple setup.

Setup was very straightforward and tons easier than the other products we have used in the past.

Complex to get reports we wanted.

The setup was straightforward and quick.

Initial setup was pretty straightforward.

Very straightforward. Deploy the virtual appliance and set up vCenter connections. Creating the policies takes a little explaining but just for understanding. Once you understand what exactly you are setting up, very easy.

It was very straightforward. The OVA file was simply imported into vSphere and turned. Following that it was just a matter of a few simple networking configurations.

It comes as a virtual appliance which is installed and configured (IP Settings / vCenter connection) quickly. Around half an hour and you are ready to use it. Some hours later the first recommendations come up.

The initial setup is very straightforward. When you get into the actual configuration for your specific environment, it is recommended to have one of the VMTurbo folks on the phone to walk you through some of the intricacies of the software.

Yes.

Very straightforward. Thirty minutes on the phone and the tool was working.

Very simple and straightforward.

It was very simple, deploying a VM template with a few settings is a breeze, and integration to vCenter is seamless.

Very straightforward. It took me longer to identify a free IP address on my network than to get the software running.

The setup was straightforward. Understanding how the application works in our environment and how to set up rules for different clusters, however, took a little longer. Turbonomic has great training materials on their web site and a really good user forum. They have a top-notch support and engineering team.

Simple.

No

Initial was straightforward and followed documentation cleanly.

It was straightforward.

The installation was very straightforward.

Initial set up was very easy. Support helped us with some additional steps to take for the creation of policies.

Straightforward.

It was straightforward.

The initial setup was easy and straight forward.  The company provides you with an OVA template to get you going within an hour.

Very straightforward and simple. Adding monitored components was a bit cumbersome and required some help from support but in the end everything was successfully identified and properly connected.

Our initial setup was complicated due to specific versioning issues that were resolved once Technical Support became involved.

Initial install was extremely simple.

Although VMTurbo assisted with the install, is was very straightforward. The same goes for the upgrade process.

It was very straightforward. It's own ISO made it super simple.

Easy VM deployment - set an IP, set a password, give login credentials to clusters. Boom, done.

Initial setup was very smooth and easy to execute.

The initial setup was straightforward. You deploy an appliance, give it the normal basic configs (IP, Subnet, Name) then wait a few hours and you start having data to act on.

Within two weeks we were collecting metrics and watching how it was working. In a month is enough to do right recommendation for Turbonomic.

The setup was straightforward. We were up and running within five minutes and pulling data.

As previously stated, setup was very straightforward: Deploy VM, configure connections and targets, and Automate!

Straightforward

Very striaghtforward.

We got help from an on-site tech to perform the install.

The initial setup is really easy and just point and click.

Dead simple.

Very, straightforward setup by deploying the OVA template. You can slowly automate tasks once you’re comfortable with what its recommending.

Setup was very straightforward.

Very easy initial setup and support team was always there to address any issues.

Straightforward.

Straightforward.

The install was clean and simple, tailoring it to our environment didn't take much but does take some thought.

Straightforward and easy.

Very easy setup. OVA template, adding vCenters, making some groups, allowing our firewalls to let Turbo access everything and we were set.

Straightforward, took less than an hour to completely install and configure baselines. Within a couple days all tweaks were in place and it ran great.

Install is very simple - used the free version at first.

The setup was simple, with the deployment of a virtual appliance. Updates are similarly easy. The only issue is the time necessary for Turbonomic to observe the environment before it can provide actionable data.

It was simple.

It is very easy to setup, i.e., one VM to deploy with one week to audit your infrastructure, then add the first recommendation.

Straightforward.

The initial setup was straightforward. Download the appliance and deploy it to our vCenter, configure the network settings and that was pretty much it.

It was simple.

It was a straightforward setup.

Very straightforward.

No, the initial setup was very easy and streamlined. I had support from Turbonomic team, but feel very confident I could deploy the software and configure it myself.

Very simple. OVA/OVF file and point right to our vCenter.

Very straightforward.

Initial setup was very smooth and easy to execute.

No.

Setup was straightforward.

Yes, just load the OVA, assign an IP, import your inf.