Install VMware ESXi on a Hyper-V

It is possible to use nested virtualization to run VMware ESXi as a Virtual Machine in Hyper-V. To some, this may be a viable option if you are unable to acquire any new hardware, or if you simply want to test new VMware products on your Windows 10 desktop.

Although this process is not officially supported by VMware or Microsoft, it is possible to get an ESXi environment stood up using Hyper-V. There are a number of prerequisites to adhere to as well as an understanding that following this process may not give a smooth end-to-end user experience.

Before we start we MUST prep the ISO and inject Hyper-V compatible Network drivers. If you do not do this the process will fail and you will be unable to connect to your ESXi server. (more…)

How to configure virtual machines auto start on VMware ESXi

If you are a VMware system administrator, you may find useful to configure a group of virtual machines to auto start at the ESXi host boot.

There may be different reasons to do that, but the most common is to recover from a blackout. ESXi hosts can power on automatically when the power comes back and the virtual machines will be powered on with them.

How to add a new user to a customized vCenter Role

The privileges and Roles allow the administrator of a VMware virtual environment to configure a granular security policy defining individual user rights.

For a VMware system administrator it’s good practice to define the user access rights from the vCenter servers. There are several technologies to secure a virtual environment, this time we are going to see how to assign a customized role to an individual user.

In our previous article we talked about how to create a customized Role to which we gave only the privileges to configure the Virtual Machines.

It’s considered a best pratice not to modify the default roles because they can be useful for future reference.

In this article we’ll explan how to create a new user which we’ll assign to a customized Role named VM Configuration Manager.

How to create custom vCenter Server Roles

The VMware vCenter comes with several privileges grouped in Roles by default. The privileges and Roles allow the administrator to configure a granular security policy defining individual user rights.
On the vCenter there are three system roles as follows:

  • No Access
  • Read-Only
  • Administrator

The system roles are permanent. there is no way to modify them. The No Access and Read-Only roles are very useful for restricting user access quickly.

The six default role samples are as follows:

  • Virtual Machine Power User
  • Virtual Machine User
  • Resource Pool Administrator
  • VMware Consolidated Backup User
  • Datastore Consumer
  • Network Administrator

While it is possible use the default sample roles as they are, it’s also possible to use them as a starting point to create custom roles. It’s considered a best pratice not to modify the default roles because they can be useful for future reference.

How to enable Lockdown Mode on VMware ESXi

The Lockdown Mode is a nice feature of VMware ESXi. When an ESXi host is in Lockdown Mode, it will only perform operations coming from the vSphere Server that is controlling it. vSphere Clients and other sources won’t “work”.

The ESXi Shell, the DCUI (Direct Console User Interface) and SSH won’t be affected.

Lockdown Mode has been created to offer improved security in complex virtual environment. It’s really easy to enable the Lockdown Mode from the DCUI.

How to create a vApp on VMware vSphere

VMware vSphere is a very flexible platform, making you able to manage a group of virtual machines and resource pools in a single entity named vApp.

Let’s think about a web application running on a VM. The application also needs a database and other resources running on differente virtual machines. From a service point of view, all the virtual machines are part of the same entity and that’s why vApp exists.

How to create a Template from a VM on VMware vSphere

Cloning virtual machines is a common task in virtualized environments, so common VMware created a different type of virtual machine to be used as a Template (and named Template). The difference between a VM and a Template is simple: you can’t power on a Template so you can’t modify it without converting it back to a virtual machine.

When a VM is converted to a template its .vmx file become a .vmtx file.

It’s pretty easy and quick to convert a VM to a template with VMWare vSphere Web Client, just follows these steps.