If customers are leveraging a certain vendor product, I can usually get a virtualized version of that product, and I spin it up in my lab. Then I can do some testing, I can run through run books on how to do certain backups, how certain configurations will affect workflows, and things like that. That's probably my highest use case.

We use VMware products to support our IT infrastructure and application deployment processes.

The product offers a cost-effective solution.

Virtualization is awesome when you're running particular applications and you need to cookie-cutter them, which is what I'm doing. I've got the mining rig pre-built, and I just clone it, set the number of CPUs, and let it run. It can't get easier than that.

I would prefer running off of virtualization for everybody's computer. I would just load the images in them if I could, but that would be asking too much of the consumers, so I don't do stuff like that.

It made various enhancements to the system once the deployment was completed.

The solution benefits us because it allows us to identify whether we need to spend money on a solution that would involve having to buy a bunch of licenses for software, and running an application or a system for whatever our requirements might be. It allows us to test out that scenario to see if it would be more beneficial for our environment as opposed to buying everything, setting it up and determining whether it is going to work or not. It gives us insight into some of the issues we might run into, and how to better facilitate fixing them.

VMware Workstation is something that I have used on my laptop, while at times I have used the solution for testing process purposes, with Linux, Windows, and servers. I have used VMware Workstation for testing purposes in the production environment.

We are using Workstation to run multiple operating systems.

Since I work with so many different customers, I deal with many operating systems and workstation configurations. When performing upgrades to servers, applications, windows, etc., I need to know the ramifications before we go live with production.  

Creating labs has been useful for my employees when working on certifications.

I am also not a big fan of adding and removing software over and over on my laptop, so I use my VM's when I need a temporary application installed. It also keeps the clutter down, keeping my main tools fast and efficient.  

They also come in handy when cleaning infected thumb drives.

I'm using it for my personal use, for testing. If I want to know how things are working, then I will test it using Workstation.

The ability to run Virtual machines in different networks and with different security levels. I can sandbox my windows machine when I need to use a non domain admin account for daily tasks but have another sandboxed machine to handle system admin tasks. I also have a wireless sand boxed Ubuntu machine that is in no way connected to our internal network for testing our websites, outside email etc. This has saved me a great deal of time and effort.

The performance is good and depends on your PC.

As a systems admin, I use it to run multiple instances of systems on my host machine to get better usability and for testing new builds for our users as well as for server updates. 

It has given us the flexibility to recreate live server scenarios including the supporting networks and AD domain controllers; these are then used to test upgrades or migrations with no impact on the live servers or network. These actions can then be repeated on the live servers, or the upgraded test VM can simply replace the original server (depending on the service requirements and server role). This can be completed by transferring the test VM directly from Workstation to the ESXI host or vSphere environment. If the transfer is the preferred method, the original VM remains available as a failback.