The setup is literraly 10 mins. If you have VLANs or anything it's so easier than VMware.

View full review »

The initial setup was straightforward.

View full review »

The initial setup is easier than anything I've done previously. It's not complex. It's straightforward. 

You can have this solution both on-premises and on the cloud.

It takes about half an hour to deploy. 

I just followed the instructions for the deployment and it was good. 

Only one person is needed to handle deployment. 

View full review »

The solution is simple to set up. There are certain credentials and you simply provide them. 

View full review »

It is very easy to implement. I'd rate it ten out of ten in terms of ease of setup. 

The deployment itself only takes an hour.

View full review »

The initial setup is quite straightforward. It isn't that complex. I’d rate it at a one or a two in terms of complexity, on a scale from one to five.

The deployment depends a bit on how many nodes or servers you have. You want to get into the cluster. This depends on the month's amount of time, however, we have half a day for a server. For me, it takes a little bit of time. You need a half-day per node, per server. Maybe even less.

While maintenance is always necessary, I would say we would invest more or less a day a month just to maintain it and that would entail checking logs and so on. It doesn’t require heavy maintenance.

View full review »

The initial setup is easy. 

View full review »

The initial setup is easy for me, because I'm very familiar with this product. Deployment takes an hour or two. 

View full review »

The question of whether it is easy to set up or not really is more like five questions. They are pretty easy questions.  

We have the source on a thumb drive. You launch the system install from the thumb drive and the first question it wants answered are "What is the time zone," "What is the host hostname," and "What is the IP address?" There are three of the questions. With those three questions, you just started the installation on the target server.  

If you want to get running, there are two more important questions. You answer these questions the installer does its job and installs everything you need on your end and you are done. The two questions are "What is your username?" and "What is your password?" You answer those questions and you are done with the installation. You can see it has a high-level of difficulty.  

From the time the setup starts, the total time it takes to deploy everything is about 20 minutes. You do not need an integrator, reseller, or consultant to help you out with the installation. You can set up everything yourself.  

View full review »

The initial setup of Proxmox VE was straightforward.

View full review »

The initial setup takes 15-20 minutes on Google Cloud with Persistent SSDs, but on a home server, it can take up to 30 minutes.

I rate the initial setup a nine-point five out of ten, where one is difficult and ten is easy.

View full review »

The initial setup was straightforward and pretty easy. It took us an hour to deploy the first VM. It was pretty fast.

View full review »

The tool’s setup is easy. The setup took two weeks to complete.

View full review »

The initial setup is straightforward.

View full review »

It's easy, but the management is not really that efficient for us, so I'd rate it a seven out of ten.

It usually takes two days to conclude. There is also migration. Migrating less than twenty VM to a newly configured Proxmox would approximately take two to three working days.

View full review »

I rate the ease of setup a four or five out of ten. The initial setup is not exactly difficult, but it is not easy either.

View full review »

It's straightforward to get started with Proxmox VE, but if you want to do something more advanced, it can become complex. The installation process is simple as long as you set up the cluster correctly. Setting up the cluster is straightforward, but when you try to do something more advanced, the complexity increases significantly.

View full review »

The first test was a little complex, in the time of the 1.4 version, but since the 2.0 version it is extremely simple, takes less then an hour to deploy a node and connect it to an existing cluster.

The 6.x release made things even easier, most maintenance tasks are now in the web interface

View full review »

The tools' deployment is easy and I rate it a seven out of ten. It took two hours to complete. Install Proxmox VE on the server, then proceed to install the hard disk. After that, configure it for the work system and install the desired system. Finally, install all the necessary programs on the server. You need one resource to handle the deployment. View full review »

The initial setup of Proxmox VE is complex. The full deployment took many weeks and I am still configuring it.

I rate the initial setup of Proxmox VE a seven out of ten.

View full review »

Proxmox VE is very simple to use.

The deployment took a long time, but it was not because of Proxmox. It was some other issues for other projects. Installing the Proxmox software is very easy. It just takes a day or two.

View full review »

The initial setup of Proxmox VE was very easy. With Proxmox VE, the installation, clustering, and configuration parts are easy.

The solution is deployed on an on-premises model. My company plans to deploy the solution on the cloud in the future.

For the deployment process of Proxmox VE, since my company migrated from VMware to Proxmox VE, we rely on our own hardware. The deployment process didn't require much effort. In our company, we were able to handle the workload related to the deployment process easily.

The migration process from VMware to Proxmox VE was completed in a period of 15 to 20 days. In my company, we had very little workload on VMware. To work on the VDI part in Proxmox VE, my company had to do a fresh setup, meaning we had to start from scratch since we weren't using it with VMware. After looking at the solutions available in the market, my company decided to go ahead with Proxmox VE.

View full review »

Proxmox VE's initial setup of easy. I started the implementation process by selecting a location, installing the hardware and Proxmox VE, and then I made the cluster without the Proxmox VE. The last step was to implement my virtual machine. The full process did not take more than two hours.

I rate the initial setup of Proxmox VE a nine out of ten.

View full review »

Does a three and a half minute setup sound reasonable to you? When I first installed it, I thought there must be more to it. I downloaded the ISO onto a thumb drive and made it bootable. Then you boot the server, boot off the thumb drive. You have to answer about six questions and that's it. Very simple. 

View full review »

The initial setup is straightforward. It was hard at first, but I went over the forums. After I went over the forums, I did the YouTube tutorials and videos, and after that, I managed my clients well without paying for a bit of support. Surprisingly, I have been running for about five years.

It doesn't take hours because I've deployed on two nodes, and I've deployed on three nodes. Currently, I'm running it on four nodes, and it's doing great. So, with every installation, I tend to get better.

On a scale from one to five, I would give my initial setup experience a four.

View full review »

The initial setup is not overly complex. It's very straightforward and very simple. 

I had a server that I needed to expose to the internet and I just decided to use it instead of VMware and it worked.

You only really need one person to handle maintenance, however, we have two people on staff that can handle those types of responsibilities. 

View full review »

The initial setup, after you've done it once, is straightforward, but the first time it isn't. That's because of the way you build the image. When you install on x86 infrastructure, mounting the installation is not straightforward. Unless you have medium to good NAVIS experience, it's actually difficult to install. 

View full review »

Proxmox VE's installation is very simple. 

View full review »

Everything has a learning curve, steps to watch, understand and explore. But with Proxmox there are hardly any challenges. I don't think the deployment took more than an hour.

View full review »

The initial setup was simple. Deployment took us several weeks. 

View full review »

The initial setup was fairly straightforward. The initial deployment probably took two hours.

View full review »

The initial setup was relatively simple. We had a couple of servers and an iSCSI SAN, VLAN, and LACP Bonding with no HA.

View full review »

For me, it was straightforward. There are different user levels for things like this, but it was straightforward for me. It takes about a day or two.

View full review »

The initial setup is easy.

View full review »

The installation takes 30 minutes. It's not that hard, as it is on a GUI. There's an interface to it involving one's country, the email address, password and IP address that one wishes to use. That's it. It will handle everything else.

View full review »

I rate the product's setup an eight out of ten. 

View full review »

The initial setup is easy and straightforward. We set it up locally.

Our team does the configurations.

It takes a couple of days to deploy.

View full review »

The setup is very easy, but the problem is when you have to customize the solution they're talking about more episodes. You have to be more hands-on to have a very good draft, it will be more helpful to have a very good delivery.

View full review »

The initial setup isn't too bad, however, it's a bit complex. There's definitely a learning curve for people implementing it themselves.

View full review »

initial setup was a bit of a learning curve, as with any new product. Some of the configuration required uses the console and options were not available in web interface (like setting MTU on NICs).

View full review »

My impression is that the initial setup process is straightforward.

View full review »

For deployment, we used eight blade servers.

View full review »

The installation is very easy. It's straightforward. It's not complex. This is due to the fact that it's an environment that depends on Linux with the version of the kernel in Linux.

When we install it the environment is so easy, we just have to put the image of the system and we choose the mode of installation. It's quite simple.

When we are in the environment, we just need to create an instance of a VM.

View full review »

The initial setup of this solution is not complex. 

We set up three nodes and fixed storage.

The deployment took us at most four hours.

View full review »

The initial setup is very easy. Once you get the hang of it, setting up the VMs, containers, and deploying them is incredibly quick.

The setup for most of the configurations is similar, once you understand the concepts and the principles, it comes down to basics. You know your hardware and what you're setting up, and what it's capable of doing. You can't set up older generation hardware and then expect to have PCI Express Passthrough or GPU Passthrough, because the hardware doesn't support it.

You can't expect the solution to do what the base hardware is not capable of doing. Work within the constraints of the hardware, understand your hardware, and the OS.

You can download the solution and it is an open-source installation, it is exactly the same as their commercial solution.

The maintenance of the solution depends on how you've set it up. If you've only set it up as a functional hypervisor, you have your VMs running, and that's the last thing you did, then you're going to have to come back every two weeks or every month to check on your OS updates, upgrades, and security patches, et cetera. However, you can automate a lot of that with Cron jobs. It's about learning the system which is based on Debian. If you understand Linux and Debian, you will understand how powerful the system is and what you can actually do with it. When you start running things, such as Monits or syslogs, you can automate any error messaging or any problems and it can be sent to your system administrator in an email.

Whether it's a case of regular backups that are happening, if everything is working well, then great, but if one fails, an I/O error or other errors pop up and you get notified of it quickly, then you can fix it easily. If you're only coming in every four weeks to have a look at it and see what's going on, things could have gone horribly wrong.

I would suggest to anybody who's running a hypervisor, is schedule regular backups. Back up your VMs regularly. Schedule it. Automate it, and make sure it happens on a separate machine, onto a separate machine, onto a separate host- because you don't want to lose your VM with all its backups.

If you've taken the time to set it up well with all your Cron jobs and automation, there will be almost zero maintenance.

I rate the implementation of Proxmox VE a five out of five.

View full review »

It is complicated to set up. It took us one week.

View full review »

The initial setup of this solution is straightforward, and it is relatively easy to set up.

View full review »

The initial setup was straightforward.

View full review »

It's straightforward. We have developed a tried and tested method to set up servers and it works well once you know how you want your servers to work.

View full review »

The solution is very easy to set up and implement. It's not complex. We can put a single host or even a Cluster only line in less than one hour! 

View full review »

Very straightforward.

View full review »

The initial setup was straightforward. It was very simple.

View full review »

The initial setup was complex. We took about a month to fully deploy the solution.

View full review »

The initial setup was really straightforward and easy.

View full review »