Hi Emilio, I want learn more about VMware in practical and I don't have hardware much compatible to install workstation because I know basic things.....please suggest me can I do

Thanks Richard for your kind words and comment. Appreciate it.

Thanks jaures art, appreciate the comment and sub.

Glad it was helpful! Thanks for the nice comment Tanja Tesic!

Thank you so much!

Awesome, thank you!

Thansk for the nice comment.

Great to hear!

Glad it was helpful! Thanks

You're very welcome!

Glad it helped. Thanks for the comment.

Glad it helped Brian. Feel free to checkout some of my other VMware vids for more info.

Glad you liked it!

glad it helped! thanks for the comment.

please i want to ask, is the VCenter on a single server that has esxi installed , or on all the servers with esxi that is managed by Vcenter

glad it helped

Perfect. Thank you

Glad it was helpful, thanks for the comment!

6 minutes in, and it’s 99% hardware talk… this whole comparison should only be 6 min.

Thank you

Thats worker🔥

Thanks, I put it on x1.5

i was already listening at 1.5, i listen to everything at 1.5

Glad to hear it!

My pleasure!

You're welcome!

nice, enjoy to company!

Glad it was helpful!

Sure, no probs

Glad it was helpful, thanks for the comment!

No problem 👍

I think you can click on data center, the root of all of the vm's, and then there was an export button.

No problem

Great 👍

Awesome! Thank you!

You're welcome!

glad you liked it!

Thanks for the comment. Glad it helped.

No problem

I'm not an expert at Zones, but I read a bit about them just now and they seem to be very similar to Jails in FreeBSD or stuff you can do with cgroups in Linux. So, unless I'm very mistaken: It's not a hypervisor. There's only one Solaris kernel running. Each zone has what looks like its own install of Solaris (which often is just a filesystem trick that overlays an OS on top of the existing Solaris filesystems) and boots sort of like a VM, but without a lot of the hardware setup. The Solaris kernel partitions off different processes by zone, separating everything including things like IPC. The amount of partitioning is configurable, so you can have as much security and separation as you like. So there's no virtualization happening with Zones at all. It's a lot more like multiple versions of Solaris running on the same kernel. One nifty thing is that there's an emulation layer you can use in a Zone to translate Linux syscalls into Solaris syscalls. This allows you to run a Linux environment inside a Zone without actually running a Linux kernel. If you'd like to play with them without forking out a ton of money to Oracle, Illuminos (the open source fork of Solaris) supports them.

You download the VCSA iso to your workstation/laptop and use the ui installer to deploy the vcenter appliance into the host. This will create a vCenter Server VM on the host. But mind you it needs min 2 cores and 12 gb to be assigned to this vcenter appliance vm.

vSphere includes vCenter and ESXi. vSphere is also the web client that is used to login to vCenter and ESXi hosts. Hope that helps

gracias

Any company that has more than a handful of servers can benefit from virtualization. One advantage you get is that you separate your hardware from your servers. Whenever you upgrade or change your hardware, you set up the new hardware, migrate the VMs over, and you're done. You can also get redundancy, depending on your setup. If you're running a NAS, you can have several hypervisors running and move the VMs between them at will. If one hypervisor dies, another can automatically spin up that VM. That takes some extra coordination, but there's software (Microsoft's infamous Failover Cluster) and hardware (see Stratus for an example) solutions that can do this sort of thing. Another advantage is that a lot of servers don't need much in the way of resources. A domain controller today doesn't do a whole lost more than domain controllers did 20 years ago on Windows 2000. Unless you have a relatively large network, putting it by itself on modern hardware with tons of RAM is a waste. Better to virtualize it so it shares the same hardware as other lightweight servers. You can keep old server images around for reference. Copy the old VM off a site before installing a new one. If something on the new one doesn't work, you can spin up the old one and see how it used to work. I do this all the time, upgrading clients from FactoryLink (which went EOL back in 2007) to Wonderware. They're also useful for software that won't run on modern operating systems. I deal a lot with 20+ year old industrial hardware, and it's not uncommon to have software that won't run on anything newer than Windows XP. A VM of Windows XP is a lot more reliable than a crusty old laptop with 14 years of technicians' sandwich crumbs in the keyboard. My company develops and maintains industrial control systems that use multiple servers on each site. Once installed, these are usually firewalled off from the world so they're inaccessible from our end. We keep a virtual copy of our clients' systems on a server. If a tech at one of those sites calls us, we can spin up our copy of their site and investigate problems on our end. As a plus, if a client requests a change, we can change our copy, test everything, and then install it at their site with minimal downtime on their part. So yeah, VMs are nice. I was late to the game and skeptical at first, but I'm a convert today. I suspect I'd be less likely to use them on UNIX/Linux since there are better options there (Docker, Kubernates, Jails, etc.), but on Windows they're great.

hey N N, thanks for the comment. Here is a discount code that you or anyone here can use. It's valid for 4 days. www.udemy.com/course/learnvmware/?couponCode=31629BC8D8830CA52885

This is just a basic overview, redudancy comes later when setting up HA and FT across multiple hosts.

Great job!

You are welcome!