The technician and a colleague from my team handled the deployment. I observed with interest. While the initial rollout seemed less complex and time-consuming than anticipated, the overall undertaking itself remains intricate in terms of its requirements. However, the actual execution was faster than expected.

The technician's tasks might have been intricate, but for us, the process was manageable. We set up the new system in parallel with the existing one, free from time constraints and stress. This allowed us to gradually migrate workloads from the old to the new environment at our own pace. Essentially, the technician guided us up to a certain point, demonstrating how far we could independently handle the transfer, and we took it from there. From our perspective, it was a straightforward approach.

We adopted a methodical approach, constructing the new environment in parallel with the existing one before gradually transitioning workloads. This ensured continuity as some workloads remained in the old environment while others were migrated to the new. The entire process was seamless, causing no disruptions to business operations. For mission-critical systems like the ERP system and file server, we performed the migration outside of business hours, further minimizing any potential impact. The migration itself was uneventful and smooth. Once VxRail was fully operational with multiple nodes and redundant storage, we began provisioning new VMs to accommodate additional workloads.

I was involved in the deployment of VxRail. The whole process was straightforward. 

In terms of deployment, we did the first 600 stores in three months, and we now are doing 1200 stores and we'll be done by October. We worked together with Dell. We had a cross-functional team and we started slow and then built up to peak volume. Our strategy was to make sure we didn't disrupt any location.

About four or five people on our side were involved in the implementation. Dell assisted us and I don't know how many Dell had. Obviously, they needed people to go to every store to implement.

Our job was to act in coordination and communication with the locations where it was being deployed.

The solution does require maintenance, however, it's very easy since there are tools that are provided with the technology. About five people are involved with administration and maintenance. They address any predictive alerts that come out on failures and care and feed any additional firmware or other types of updates that are required.

Its initial setup is very easy as compared to vSAN, traditional models, and VMware vCenter because everything is automated, but you need to prepare your data, for example, your IP address for the cluster and your username and password.

The initial setup was straightforward. 

VxRail is easy to set up. It was very easy.

The complete configuration and powering of VxRail took a couple of days to set up the servers and infrastructure, as well as the cabling. When we power up the servers, VMware and vSAN were already applied to it. We will only need to buy the license to configure the appliances.

For myself, it's fairly straightforward and no longer very complex. However, I've done more than a dozen of them so far. If you don't know what you're doing, it can be pretty complex. You really do need some expertise with the solution to manage everything.

In terms of deployment, it chiefly takes about two days of planning and about two days of implementation.

In terms of maintenance, what makes it so nice is that it automates management and patching of all of an organization's virtual hosts and even their switches if the switches are supported. Therefore, it reduces admin.

The more difficult part of it was the planning. The actual deployment was not as difficult.

The deployment didn't take more than a month from doing the actual planning to having it shipped, brought inside, and then brought online.

VxRail is deployed to data centers and globally as well.

The maintenance is sustained within supportability, so it has to be updated whenever leases come out.

The initial setup is straightforward. As soon as I prepare a JSON file I have no problem.

Usually deployment depends on the number of nodes — it's taken up to two hours.

The initial setup was straightforward. The process took around one day.

Our environment is in one location, and it's not a stretch cluster; it's a single cluster. We run about 190 virtual desktops and 200 virtual servers on it.

The solution does not require a lot of maintenance, and the system engineer takes care of that.

We didn't have any issues with the initial setup. It was very straightforward and not overly complex. 

Our contract partner handles any maintenance tasks. 

The configurations of VxRail can be difficult. However, it has improved in the newer version. From version 6 to 7, there has been a lot of changes.

The initial setup of VxRail was straightforward because they get handled by Dell themselves. There is a one-stop-shop for all your needs. They gather the information on what you require in your environment and how you want to set it up, such as what local IT information networks are required. They do a good job and the whole process took them a couple of hours to half a day.

For the HCI it's quite straightforward; however, in regard to the switches, there is no GUI implemented with the top-rack switches which can make things difficult. Overall, deployment took one week.  

We deployed the solution with Dell. The process was very easy.

The most valuable aspect of VxRail is its ease of implementation. It's not like the ReadyNodes. When you create the adjacent file and manage it with the customer, then the implementation will not take much time. VxRail can manage the whole cluster at the same time, so it's easy to expand. VxRail has more features vSAN ReadyNodes that make it easier to implement from scratch. 

The initial setup was straightforward as it was deployed with the help of product management partners. As for requirements for deployment and maintenance, no additional software is needed. Basic skills and general knowledge are sufficient for deploying and managing this solution.

We had the help of a partner. We had no major issues at the time. It was a recent technology back in 2017. There were not many experts on the market, but we did not encounter any difficulties, and the infrastructure is still running today. It is still the same one as the one from that era.

In terms of the initial setup, compared to any other platform, it pretty simple. I've used Cisco UCS in the past, and have experience with that solution, and compared to that, this implementation is easy.

It's got a very good integration between hardware and software specific configurations. You just need to watch out for technical inputs.

The maintenance we negotiated as a bundle over years of use. Our partner handles the maintenance of the solution.

The tool's setup process for VxRail is easy. If you follow the deployment guidelines and best practices, it typically takes no more than an hour to complete.

The initial setup is very complex. 

The main issue during the initial deployment is if there are any errors, you have to completely re-image the nodes. There is no option to fix the issues and resume from where you stopped. This adds many hours to the process. 

We always follow what Dell recommends and their best practices.

You don't have to be an expert to install VxRail. To install the node, you just follow the steps from Dell EMC, and you can install the solution in one sitting. It only takes one person to install. We have 30 engineers on my team, but only three are responsible for maintaining VxRail. 

The installation is straightforward we have never had a problem. They could improve on the process of adding clusters. For example, when you want to add a four-node cluster to a 12-node cluster, there is a whole lot of resetting we have to do on that cluster and put it back on. We do not understand why you can not add a cluster into the same management interface. This is something they should look into.

In terms of the initial setup, only the network part was a little complex for us. Maybe because we were doing it for the very first time because there is a very strict firewall applied there, being a manufacturing site. We had multiple firewalls there, so we had to open each and everything one by one. That was the only thing.

Once the network part was done, everything was smooth and we had a product life support from Dell. It was Dell who basically deployed it from a remote session with our presence. We only give them some input around the infra set up and they actually did the end to end deployment.

It took one day for rack and stacks and then two days for its set up, installation, and configuration as per our department. Later on we did the migration on our own based on the downtime that we received because we had to update the VMware Tools. We had to configure the backup, et cetera. We did it slowly, one by one, three, four servers a day.

For deployment, we used a consultant. We needed auto recovery because we faced a hardware problem. It was a board problem. That's why we engaged DNC to replace the board, and it was very easy to discover the node and deploy the process.

Tackling the initial deployment single-handedly would have undoubtedly been a difficult task, rife with complexities and pitfalls. Thankfully, the Dell technician's expert guidance shed light on the intricacies of the process, transforming it into a surprisingly straightforward endeavor. Even now, post-deployment, tweaking and adjusting settings remains a breeze. The initial apprehension has given way to a newfound confidence and ease, a testament to the clarity and efficacy of the training provided.

Our phased implementation strategy endeavors to systematically migrate various functions towards automated execution, a process fraught with unforeseen challenges. While the strategic framework was readily established, translating it into tangible action proved significantly more arduous.

The initial setup was a little lengthy but straightforward. To deploy a 12 node plus it took two months.

The initial setup is pretty easy and straightforward.

The initial setup is not too complex. It's pretty straightforward, in fact. 

In terms of deployment, it typically takes less than a week, in some cases. Of course, it depends of the customers, however, in many cases it takes about a week.

It is very straightforward.

As part of a VxRail deployment, you have to get professional services. It's an assisted install. I have experience with all of the components of VxRail. In terms of the VSN, the hyper-converged, some of my coworkers did not. That actually was a learning experience for them. They were able to learn from the documentation and that made it easier, however, it was still a learning curve. That was the only difficult part in terms of implementation -  the learning curve.

The initial setup could have been easier. There were too many cooks with all the Dell departments.

If I had done it without the help of the person from Dell for the first time, it would have been more complex. Because he showed me once, it was very easy. If I want to change something now, it is just easy. There is all the automation behind it. When I have a new server, I slide it into the rack, connect all the wiring, give it an IP address, and click a button to bring up the server.

I would rate the tool's setup an eight out of ten. The tool's deployment got completed in a few hours.

We migrated from our older hardware consists of multiple servers, storage and switches to simple and more powerful HCI - 4 node VxRail device.

Studying current and future Business requirement, validating multiple solution which suits our requirement, which is agile, easily scalable and more power to suite our future plans.  It took almost six plus months to freeze the VxRail solution.  Post finalization, releasing the order and receiving to hardware it took almost 6 months to complete the migration to new setup.  Delay was due to lockdown, travel restrictions otherwise it would have been completed within three months.  Complete migration was very smooth and very minimal downtime without any Business impact.

The initial setup was straightforward. It took about a week initially, plus three weeks to move all my VMs to the new system.

The setup is very simple.

The solution’s initial setup is straightforward. The solution's implementation is straightforward and presents no challenges. However, upgrading the versions of the solution requires some time.

The initial setup was straightforward. The engineers asked for what is required and they came with the same initial set.

VxRail is a hyper-converged system that's automated and consists of nodes. Those nodes are one or two U-servers depending on the requirement. Bringing the VMware automation and lifecycle management platform together is difficult, so we recommend having a certification to do that assemblage. 

It assembles these servers into nodes in an appliance. Once the appliance is set up, it's simple to manage the solution and the box. However, assembly and automation are complex. You want to make sure that the firmware is all the same between the nodes.

We've seen situations where we had a five-node cluster, and one firmware was not mapped to the others. We recommend working with Dell on those challenges, but our architects are also really well versed in those nuances. And if you want to deep dive into a technical requirement, I have several that have done that for a living.

The initial setup was very easy. It took about one and a half days and then another three or four days, maximum, with the tuning and everything else.

We had to energize each node and I did it a week before they went to implement the process. They asked about everything. They asked about IP addresses, everything that was technical. They made some assessments and the day that we implemented VxRail, they had everything set. They just wrote all the addressing and everything of our root and our network. The implementation goes so fast. Almost a day. That was what it took to implement that machine.

The next day, they migrated from virtual machines with the VMware Converter. They used two RecoverPoints for Virtual Machines, I think. It didn't take too much time. Only a few hours, maybe half of the day, and it was okay. We started planning it and we made some tests over a day and a half on the timing and stability of the system and we had the process standard because we needed to have a hybrid solution.

The initial setup was straightforward.

The installation was straightforward and took approximately five days to implement the whole stack.

The initial setup was a bit complex and they didn't manage to bring it up in the first attempt. Really, only the support people can do it and if something happened the support people need to have control of it. The second attempt also took longer than expected. It took almost two days to complete the full installation, which is longer than the claim that it should take around two to three hours for the full setup. 

We had three people involved in the deployment process.

The initial setup is very straightforward. Fill out the spreadsheet and generate the JSON file, then pump it in. 

Customers like it. It's simple to deploy. 

The initial setup of this solution is not complex. Take it out of the package and implement; it's very easy.

The initial setup is straightforward. The time it takes to set up depends on the size of the cluster. For a mid-size cluster of 12 nodes, it usually takes one to two days.

We haven't fully deployed VxRail because we only got our first order for the systems today, and we will go to the setup, but the demo system was easy to use and set up.

The initial setup was simple. The amount of time it takes depends on the number of nodes you have.  

It does require some maintenance over time. For maintenance, you have to request that through your supplier or even through the implementation team. It will be totally different depending on the kind of activity and the issue, but it should not be disruptive for the most part. The only exception is in critical applications. These may be critical but it is simple to restore the network connectivity or storage availability.  

The initial setup was not really any more complex than some other HCI deployments. We completed a spreadsheet, with IP addresses and names, that was imported into a JSON file. This was then used to automate the deployment and creation of the virtual environment.

The initial setup is straightforward. We have close to 1,000 end users who connect directly to the VDI and to the UCC solution. 

As I am not an engineer, I am not in a position to talk about the installation. I do not have familiarity with implementation. 

The initial setup is straightforward for versions 6.5 and 6.7.

When I asked for a quote for a partner that was doing the implementation, they told me that it took two people to complete the implementation. 

The process of the installation is straightforward. The initial implementation took use three to four months. The technician allocated to it did not have much networking experience. Once he mastered networking everything went well. You have to be good at networking to be able to have everything completed in a timely manner.

The initial setup was not that easy, it was a medium difficulty level.

The initial setup was straightforward.

It took less than a week to deploy, without dedicating full days. It was approximately two to three hours a day for this particular job.

It comes with preloaded ESX sites, it's about how you configure it.

The installation is very straightforward. You forward your IP, password, and some other information then you are done.

The initial setup was not complex. 

The implementation of a VxRail, it's straightforward, but the ongoing utilization, and integration, are where it can start to become difficult if you're not used to doing it.

The initial setup is straightforward. Installation took approximately 2 days, but migration from the old UCS to the new infrastructure took time.

Setting up VxRail is straightforward. 

The initial setup was not complex, it was very straightforward. Deployment took us three to four days. 

The maintenance we do on it now is mostly preventative. 

We have two people working on VxRail. 

The initial setup is straightforward and can take up to four days. Deployment requires a technician and an assistant engineer to plan everything and get it ready to host the services. Maintenance is required but we receive documentation regarding updates and framework feature updates. We have five system administrators working on this product.

It is easy to install and implement the VxRail clusters. The initial setup was a piece of cake for us. 

We had Dell EMC Professional Services come in and install it, then do the handover and some training,

The solution hasn't really arrived yet. We're still in the process of the implementation strategy. We're working with our reseller in order to implement everything.

We're not sure how long deployment will take us in the end. That's yet to be seen.

We are going to deploy the solution in perhaps three months, we expect. At this point, we're going to plan the installation, plan the rollout of our actual solution between HPE Blade and the old solution. We're going to install VxRail, deploy Citrix environment, and so on.

The initial setup process is pretty straightforward. Technically speaking, there could be some complications, but Dell's support is very good.

In the course for VxRail, they tell you that it's a single click to deploy. From a technical viewpoint, that isn't true because you have to build the rack system. If the system is projected well, then you have a single click to deploy it with a single panel of glass.

I am not in a position to assess the difficulty or duration of the deployment as this is done with our partner, who sends it to us only after the implementation and deployment are completed. 

Its installation can be a little complex, but it is not bad. If you plan it well and stay in touch with the customer about requirements, it is not difficult. For an implementation project, it is a standard practice for us to work very closely with the customer. It is definitely not as complicated as deploying a three-tier architecture with SAN storage, SAN switches, and those kinds of things.

In terms of maintenance, it usually requires version upgrades. When a VxRail cluster is already in production and in use, these things are discussed very deeply with the customer, and whether to go for an upgrade or skip it is decided based on the consultation with the customer. It depends on a whole lot of things, and the customer is the key in deciding such things. You have to consider the following:

• What is the business cycle at that point in time?
• What is the workload on the virtual machine?
• Is this the right time to carry out the upgrade?
• Is the upgrade really necessary?
• Is the upgrade going to impact any of their applications?

The initial setup was not complex. It was pretty straightforward for us.

The initial setup was pretty straightforward. Once the storage was up, EMC did the actual deployment, configuring, and setting up the initial part of it and then the reseller took over and did the more advanced configuration. 

Deployment took a week to get everything set up with EMC, deployed, powered on and configured. Then the reseller took over and did all the migration and more complex tasks.

The implementation was quick, we used a checklist and it took approximately one hour.

The initial setup was not overly complex. It was very easy. I used a certified partner to do the installation. 

It took less than a week and the system was up and running.

How much of a technical team is needed for deployment depends on the customer. That said if the team is about seven people they can run everything including security and the regulation and whatever we need to run the solution. In our case, there were seven engineers. One of them is the manager, and they all handled everything including networking, the system, and the protection.

As with SimpliVity, the initial setup took two days. 

The solution's implementation is very straightforward. It will take, at a maximum, one hour to deploy all the nodes. It's not complex at all. It's easy.

It's quick and easy to initialize the cluster in VxRail. You can have your cluster up and ready in a few minutes. To deploy and maintain VxRail, we need one person for the solution and another for networking. 

The initial setup was very easy. Part of the process was migrating the virtual machines to the new server.

It should be straightforward. That's what we're trying to do. We are trying to make it straightforward.

The initial setup was quick and involved medium complexity. It requires help from the vendor to scale. 

We received technical support from Dell as part of the deployment implementation plan and contract.

The initial setup of VxRail is straightforward, especially if you know what you are doing. It is quite simple because the solution is pretty intuitive in the way that Dell has set it up, as most of the planning is done upfront before deployment starts.

Deployment was not initially straightforward for us. We had an incompatibility issue that was very difficult for Dell Professional Service to solve. We had people from different countries trying to solve it. We were deploying the regional product but something with the version was inconsistent. It was a special case, but was very difficult to identify and to solve. It took us about two days.

Once we solved that issue, deployment was very easy. It took maybe an hour and was really easy. 

A disadvantage is that the initial first deployment can be complicated.

The initial setup is not easy because you need to have a very clear understanding of the machine and the switches in order to put it all together so that it works properly. We had some problems during the initial setup, but now, we have no problems at all.

Overall, deployment takes roughly two weeks.

The initial setup is quite simple and very easy.

It is very straightforward, but it would be great if it can be done in 10 minutes rather than 40 minutes.

The complexity of the initial setup depends on your infrastructure as you need to integrate some existing components. It's not only about the VxRail components, but integration with the existing network and firewall. It's case-by-case. Sometimes it's very easy, sometimes it's not.

The solution does not have a complex setup. It's very simple and very straightforward.

I did some online training before setup, implementation probably took a few months. 

The initial setup of VxRail is more complicated than Nutanix. If you have prepared the network for implementation you will not have any problems. You need to organize and prepare the network well.

Deployment is simple because everything is already built into the finished product. Implementation will not take as long as other products. The management is also straightforward. It has its own support that integrates directly through the network with the vendor. The vendors can automatically log into the system and support the customer. This and other features make VxRail more accessible to our customers.

I've deployed it so many times, including the mounting, nodes, cabling, visualizing, and configuring everything until it gets into production. The full deployment takes a day at most. The maintenance can either be physical or software maintenance. If there are any issues with the physical part, we do the RME process to get the hardware directly from the vendor. If there is a software issue, it's usually an issue we've seen before, so we can troubleshoot it ourselves. If there are any issues we can't resolve, we create a support ticket for the vendors to log into the system and do the maintenance directly.

Our product vendor did the installation for us.

The initial setup is straightforward.

If you are deploying VxRail from the external vCenter, then it is fine. However, if you're using the version of vCenter which has been supplied through the VxRail, then there are some challenges.

The initial setup is straightforward, as everything is pre-installed.

I think the initial setup is a straightforward process. In the beginning, there may have been issues in terms of sizing and collecting the requirements. But there weren't too many complications.

The initial setup was straightforward for us, because the Dell EMC team did all the work.

VxRail could be easier to set up. It's tricky to configure the network properly and match the requirements.

It is a little complex. We had a lot of technical discussions to set a proper plan and basic architecture.

The initial setup is not straightforward, but it's not that complicated. Deployment is supposed to be complicated, so it does not necessarily need to be easier.

The initial setup was straightforward.

The initial setup was straightforward.