Online VMware Training

With vSphere Virtual Machine Encryption, you can create encrypted virtual machines and encrypt existing virtual machines. Because all virtual machine files with sensitive information are encrypted, the virtual machine is protected. Only administrators with encryption privileges can perform encryption and decryption tasks.

An external KMS, the vCenter Server system, and your ESXi hosts are contributing to the vSphere Virtual Machine Encryption solution.

After vCenter Server is connected to the KMS, users with the required privileges can create encrypted virtual machines and disks. Those users can also perform other encryption tasks such as encrypting existing virtual machines and decrypting encrypted virtual machines.

When you create an encrypted virtual machine from the vSphere Web Client, all virtual disks are encrypted. You can later add disks and set their encryption policies. You cannot add an encrypted disk to a virtual machine that is not encrypted, and you cannot encrypt a disk if the virtual machine is not encrypted.

The resxtop and esxtop command-line utilities provide a detailed look at how ESXi uses resources in real time. Also, esxtop displays information about the state of the physical server running an ESXi Server.

It lists CPU utilization for each physical processor, memory utilization, and disk and network bandwidth for each network and disk device available to the ESX Server machine. Furthermore, esxtop lists CPU and memory utilization for each individual VMkernel world.

Memory utilization is characterized by the type of memory (for example, shared, private, or swapped) that is being consumed. These CPU and memory statistics let you monitor the resource utilization for each of your virtual machines.

You can use the Projects feature in vRealize Operations Manager to plan for capacity allocations and upgrades in your virtual environment, or to optimize your existing resources. To plan your upcoming capacity needs, you create a project that anticipates forthcoming changes that affect the capacity of your objects.

In addition to creating projects to plan for hardware changes or virtual infrastructure changes, you can create custom profiles and custom data centers to help forecast your capacity needs.

With custom profiles, you can determine how many instances of an object can fit in your environment depending on the available capacity and configuration. With custom data centers, you can see capacity analytics and badge computations based on the objects contained in the custom data center.

Each object is composed of a set of components, determined by capabilities that are in use in the VM Storage Policy. For example, with Primary level of failures to tolerate set to 1, vSAN ensures that the protection components, such as replicas and witnesses, are placed on separate hosts in the vSAN cluster, where each replica is an object component. In addition, in the same policy, if the Number of disk stripes per object configured to two or more, vSAN also stripes the object across multiple capacity devices and each stripe is considered a component of the specified object.

The NSX Manager contains many tools to help customers in conjunction with Global Support Services to resolve operational issues. The NSX for vSphere 6.x product features a customized command line interface that covers most of the basics that the user interface does and a little bit more.

On occasion, it may become necessary to use a regular unix command line interpreter (shell) to be able to deal with unanticipated configuration issues. In these cases it is required that customers use this shell in conjunction with tech support to avoid inadvertently changing the virtual appliance in such a way that we can no longer support it properly.

VMware strongly recommends that you configure SSL certificates for authentication of View Connection Server instances, security servers, and View Composer service instances.

A default SSL server certificate is generated when you install View Connection Server instances, security servers, or View Composer instances. You can use the default certificate for testing purposes.

Replace the default certificate as soon as possible. The default certificate is not signed by a Certificate Authority (CA). Use of certificates that are not signed by a CA can allow untrusted parties to intercept traffic by masquerading as your server.

With the Cloud Pod Architecture feature, you can link together multiple View pods to provide a single large desktop and application brokering and management environment.

A View pod consists of a set of View Connection Server instances, shared storage, a database server, and the vSphere and network infrastructures required to host desktop virtual machines and application pools. In a traditional View implementation, you manage each pod independently. With the Cloud Pod Architecture feature, you can join together multiple pods to form a single View implementation called a pod federation.

A pod federation can span multiple sites and datacenters and simultaneously simplify the administration effort required to manage a large-scale View deployment.

In this video, two previously standalone View pods in different datacenters are joined together to form a single pod federation. An end user in this environment can connect to a View Connection Server instance in the Student-Desktop datacenter and receive a desktop or application in the SA data center.

You can set up vRealize Automation to use an external vRealize Orchestrator server. System administrators can configure the default vRealize Orchestrator server globally for all tenants. Tenant administrators can configure the vRealize Orchestrator server only for their tenants

For many years, I was a big fan of Asymetrix Toolbook and Visual Basic. I won’s say I’m an experienced programmer but I knew my way around (remember the vmClient).

Since Visual Basic doesn’t run on a Mac, I did some research and have found a good cross platform alternative called Xojo, it’s a a development tool for creating powerful, native applications for desktop, web, iOS, and Raspberry Pi. 

The only problem I had is how to I talk to vSphere? Version 6.5 has a REST API and Xojo is equipped with a rest socket. Just connect those two together and let the fun begin.

In this video, I’ll explain how to create your own cross platform applications in Xojo and access the vSphere 6.5 REST API through the Xojo rest socket. This allows you to list, create, and power-on virtual machines and all the other stuff from your own user interface. Xojo and vSphere we got a lift off.

This video explains how to enable the RabbitMQ management interface on the vRealize Automation Appliance and shows how to subscribe to a que from Orchestrator.