VMware

VMware Recertification Policy Update | February 5, 2019

VMware just announced Changes to VMware Recertification Policy – Removal of 2 Year Requirement

As of February 5, 2019, VMware Certification will no longer have a mandatory recertification requirement. Now, you have the choice of when to recertify, rather than be required to do so every two years.

Certifications will still retire, so recertification is important to:
• Validate your expertise in the latest VMware products
• Show relevancy in the market by holding up-to-date certifications
• Receive the full benefits of VMware certification

Details and FAQ’s located here

Video on this topic: https://www.youtube.com/watch?v=T1mTUXhqhSw

Here is a sample of some of the Q&A:

Q. What is changing about the VMware recertification policy?

A. VMware is removing the requirement to recertify their VCP certifications within a two year period. Industry research confirms the importance of keeping your skills and certifications current, but VMware will no longer mandate when to recertify. We will leave that decision up to each individual candidate.

Q. Why is VMware removing the two-year recertification requirement?

A. The most compelling reason is that we want VMware certifications to match the needs of each candidate. Many candidates recertify every two years and upgrade their environments to the latest versions. Others maintain older products and do not yet need experience with the new versions. While holding the most current certification is the best way to keep your skills relevant, the recertification policy will no longer mandate when an individual must update their certification(s). We want to allow each person the flexibility to do what best supports their individual and organizational needs.

Q. If my certification becomes active again, will I get access to its logo and certificate?

A. Yes. You will have access to use the certification logo and print the certificate.

Q. Are there changes to any other certifications other than the VMware Certified Professional (VCP)?

A. VCP certifications were the only VMware certifications that had a mandatory two-year recertification requirement. This change does not affect the other certification levels.

Q. Where can I learn more?

A. Visit www.vmware.com/certification to view your VMware Certification options.

Veeam, vSphere 6.5, Restore job failed Error: A specified parameter was not correct: spec.vmProfile

Just a tech short on how to get past the following error: Restore job failed Error: A specified parameter was not correct: spec.vmProfile. This was encountered when testing backups via the Veeam console

This error could also be seen in vCenter

 

After some digging around I was able to get a better understanding of why it was occurring. Each time this failure would occur I would see a message “Failed to set story profile VM Encryption Policy …

But I am not using encryption policies!

This is new in vSphere 6.5 and allows for the encryption of storage where the VM would reside.
To work around this I needed to browse my datastore tree for the intended datastore rather than searching by name; What I had been previously doing.

You may see this as ‘Default policy’ container.  Select the datastore and continue as normal and you should have a successful restore.

Best of luck to you.

 

Removing a Orphaned Virtual Machine from vRealize Automation

**** ATTENTION !!! ****
**** Please be sure to BACKUP any related databases

 

The following steps provide information on removing virtual machines from VMWare vRealize Automation (vRA).

These steps are to be used when the following conditions exist:

  • A virtual machine that is being managed without being deleted from the endpoint.
  • You want to manually remove the machine from the endpoint.

 

vRA Application Steps:

Log into vRA – https://vcac.yourdomain.tld using your-domain\*your-user-id*

  1. Click the Infrastructure Tab
  2. Click Machines > Reserved Machines
  3. Search for Service Name (e.g. VRA-FAQ360)
  4. Delete the associated service

SQL Database Steps:

  1. Connect to SQL Database Server: VRA-SQL
  2. In “Object Explorer” window, Locate database vCAC
  3. Backup the vCAC database
  4. Expand the vCAC database
  5. Under Programmability > Stored Procedures, locate ‘dbo.usp_RemoveVMFromVCAC’
  6. Execute Procedure and apply ID of the Multi-Machine Service (e.g. VRA-FAQ360)
  7. Repeat this step for each instance

Notes:

The store procedure may look like the following:

USE [vCAC]
GO

DECLARE @return_value int

EXEC @return_value = [dbo].[usp_RemoveVMFromVCAC]
@MachineName = N’VRA-FAQ360′

SELECT ‘Return Value’ = @return_value

GO

Set up the Default Domain for vCenter Single Sign-On | Tech-Short

vCenter Single Sign by default requires the user to specify the domain during authentication with vCenter.
Example: JERMSMIT\admin or admin@JERMSMIT.LAB.

You can eliminate the need to insert the domain in the username by following the following steps.

 

  1. Log in to the vSphere Web Client as administrator@vsphere.local or as another user with vCenter Single Sign-On administrator privileges.

  2. Browse to Administration > Single Sign-On > Configuration.
  3. Under the Administration, configuration locate the Identity Sources tab
  4. On the Identity Sources tab, select an identity source and click the Set as Default Domain icon.
  5. In the domain display, the default domain shows (default) in the Domain column. Set the domain of choice as your new default.

The next time when you attempt to login into vCenter, you can omit the DOMAIN from your username.

Full ref located here
Full Link: https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.psc.doc/GUID-11E651EF-4503-43BC-91F1-15502D586DE2.html

 

vSphere Integrated Containers

vSphere Integrated Containers provides critical enterprise container infrastructure to help IT Operating teams run both traditional and containerized applications providing a number of benefits:

  • security
  • isolation
  • management
  • speed
  • agility

I am looking forward to getting my hands on this and expanding my knowledge on how vSphere Integrated Containers (VIC) works in the real world. vSphere Integrated Containers includes the following three major components:

  • vSphere Integrated Container EngineDocker Remote API-compatible engine deeply integrated into vSphere for instantiating container images that are run as VMs
  • Container Management PortalPortal for apps teams to manage the container repositories, images, hosts, and running container instances
  • Container RegistrySecurely stores container images with built-in RBAC and image replication.

For now its research time; later I get to have some hands-on fun. Here are some interesting links: