I’m very happy to announce that I passed the VCAP6-NV Deploy exam and unlocked the VCIX-NV accreditation!
About the VMware VCIX-NV:
The VCIX-NV exam consists of approximately 23 live lab activities and the passing score for this exam is 300 (scale is from 100 to 500). The total time for this exam is 210 minutes, but candidates who take the VCIX-NV Exam and have a home address in a country where English is not a primary language will have an additional 30 minutes added to the exam time.
For my study I used the following list of website’s, HOL Labs and Blogs. This helped me to pass the exam:
My best advice is: Build a Home Lab and deploy VMware NSX-V. After the deployment you start using all the features that NSX-V has to offer (yeah, I know that is a lot). Get familiar and deploy and design like you would in a production environment. This will help you to get the best understanding possible for the exam.
Last Friday VMware announced the vExperts for 2018. I’m pleased to announce that I have been rewarded with a vExpert 2018 award. This means I have been selected for double in a row! I would like to congratulate everyone that has been awarded by VMware and VMware for supporting the community.
I’m also please to tell that my employer ITQhas fifteen vExperts for 2018. Congrats guys! For those interested ITQ is a VMware Premier Partner (the highest level in the VMware Partner Professional Services Program) and we are an independent VMware knowledge partner.
The VMware vExpert award?
The VMware vExpert program is VMware’s global evangelism and advocacy program. The program is designed to put VMware’s marketing resources towards your advocacy efforts. Promotion of your articles, exposure at our global events, co-op advertising, traffic analysis, and early access to beta programs and VMware’s roadmap.
Each year, we bring together in the vExpert Program the people who have made some of the most important contributions to the VMware community. These are the bloggers, book authors, VMUG leaders, speakers, tool builders, community leaders and general enthusiasts. They work as IT admins and architects for VMware customers, they act as trusted advisors and implementors for VMware partners or as independent consultants, and some work for VMware itself. All of them have the passion and enthusiasm for technology and applying technology to solve problems. They have contributed to the success of us all by sharing their knowledge and expertise over their days, nights, and weekends.
Lately I discovered an annoying feature in combination with VMware vCenter and VMware Workstation. When installing VMware Workstation on your management computer it becomes the default Remote Console viewer. To be honest, I like the VMware Remote Console (VMRC) very much. The application has all the features and is quick and light. This compared to starting VMware Workstation to open a Remote Console.
What is VMware Remote Console: “The VMware Remote Console (VMRC) is a standalone console application for Windows. VMware Remote Console provides console access and client device connection to VMs on a remote host. You will need to download this installer before you can launch the external VMRC application directly from a VMware vSphere or vRealize Automation web client.”
In October 2017, I already fixed my problem on my management computer… but after a recent VMware Workstation update it changed the Remote Console back to VMware Workstation. Currently there is no option in the GUI to change the default Remote Console. Ok, but how do we get VMRC back?
When I was comparing the Windows Registry, I found out that the following registry keys were different between machines. To speed up to process I created some PowerShell one-liners to fix the problem.
When you change the registry key, no Operating System or browser restart is required. The change is instant. I hope the blog post helps some vSphere Administrators that also prefer VMRC above VMware Workstation for viewing Remote Consoles.
@VMware: I would like to have an option to control the behaviour without changing registry keys by hand… 🙂 Thanks!
The issues occurred with the following combination of software:
VMware vCenter Server 6.5 (Update 1e)
VMware VMRC (10.0.2-7096020)
VMware Workstation (12.5.9 build-7535481)
Management Workstation: Windows 10 X64
Some screenshots that display the changes when opening the Remote Console of a Virtual Machine in VMware vCenter.
This was not my first attempt. In VMworld 2017 Barcelona, I already tried but failed with just under 300 points.
The VMware VCP7-CMA exam consists out of 85 multiple-choice questions and you need to score at least 300 points. The maximum score is 500 points and you have 110 minutes to complete the exam. In the exam guide made available by VMware are all topics.
VCP7-CMA Study Tips:
For passing the exam, I have used the following websites:
Today I was facing a VMware Content Library issue. I was removing a newly created Content Library in the vSphere Web Client but that resulted in a Java Runtime error.
The conclusion was that there was no way to remove the Content Library item.
Yesterday I attended “ITQ Transform” an event organized by my employer (ITQ). The event was all about IT Transformation and helping to customer. At the event there were about 150 people who were mostly customers of ITQ. The keynote speaker was Brian Gammage (Chief Marketing Technologist at VMware), who explained to everyone in the room how imported IT Transformation is.
At the event there were twelve sessions of 30 minutes with all kinds of topics about:
End User Computing
(Cloud Native) Development
Software Defined Data Center
IT Transformation Services
The sessions were given by ITQ Consultants and Partners VMware, IBM and Pivotal. After the sessions there was room to talk and socialize.
Last week I was deploying a VMware vRealize Operations Manager (vROPS) environment at a customer and that was causing problems because of no TCP/IP connectivity to the virtual machines. At first it seemed like an administrator configuration error or typo, but it appeared to be a VMware bug. This blog post is about my findings and the solution for this problem.
To find the source of the TCP/IP communication problems, I did some basic testing:
Is the vROPS web interface available on port 80 or 443?
Does the virtual machine respond to a ping (ICMP) request?
Is the vNIC enable on the virtual machine?
Is the vNIC connected to the right Port Group of (NSX) Logical Switch?
Are there no NSX Distributed Firewall (DFW) or physical firewall blocking the traffic?
After these tests I could confirm the problem is inside the appliance/virtual machine.
When I was looking at the network card configuration files it appeared that there was a problem with the configured subnet mask. The ‘NETMASK’ field has a prefix notation filled in… not a subnet mask notation. Here is a quick write-up to fix your problem.
Open the Virtual Machine console with the vSphere Web Client or vSphere Client.
Press ALT + F1 to get into the console (Hint: ALT + F2 to get back to the main screen).
Login with the root account and root password.
Open the network card configuration file with the vi editor (vi /etc/sysconfig/network/ifcfg-eth0).
Search for the line that starts with ‘NETMASK’.
Replace the current prefix 28 to a subnet mask 255.255.255.240 (Hint: The values listed here are an example).
Restart the vROPS appliance.
After a reboot of the appliance the IP connectivity should be working.
The screenshots below are taken from the Virtual Machine console and gives you basic directions.
As a result of inserting a prefix in the OVF deployment screen the network card configuration failed. A test with a subnet mask notation did not result in these problems. The problem is caused by a network configuration script that sets the network card configuration in the Operating System. VMware please fix this problem… it’s possibly a small code change or the prefix/subnet mask detection is not working correctly.
Update 04-11-2017: Today I received a notification from an ITQ college that the vRealize Log Insight (vRLI) deployment also is suffering from the same problem (Link).
Recently I was deploying a new vRealize Automation (vRA) 7.3.0 environment at a customer and I ran into some problems. In the “vRealize Automation Installation Wizard” the “Prerequisite Checker” stopped working after applying fixes. This caused a major problem because no buttons in the GUI were working. In this article I’m explaining what might be the cause and how to get around the problem.
This week I travelled with my colleagues to VMworld 2017 in Barcelona Spain. This was my first VMworld but luckily my colleagues helped me out with putting a schedule together. The days were absolutely great and well-organized thanks to my employer ITQ (special thanks to Francisco Perez van der Oord and Paul Geerlings).
This blog post is about my first VMworld with my personal highlights.
At VMworld I attended a lot of sessions but my personal top three were the following:
Delivering Hybrid Cloud Architectures for Your Customer with VMware Cloud on AWS – Adam Osterholt
Replicating VMware VVols: A technical deep dive into VVol array based replication in vSphere 6.5 – Claudio Calisto, Nick Dyer
vCenter Performance Deep Dive – Ravi Soundararajan
I also attended a non disclosure agreement (nda) session with Tom Corn the Vice President of Security Products at VMware about AppDefense.
Server and Storage Hardware (Dell EMC / HPE)
On Tuesday I visited multiple hardware vendors about their new products.
At the HPE stand they showed the new HPE ProLiant gen 10 servers and their current storage portfolio 3PAR, Nimble. A beta version of the HPE ProLiant DL360 G10 was displayed and there was a iLO5 demo.
The Dell EMC stand was one of the largest on VMworld. They displayed all their main products and were displaying demo’s.
I could blog all day about the announcements and sessions but luckily all information is available for everyone. You can find the sessions at the vendor websites or on YouTube. The company I work for has created a dedicated page to display all the VMworld news items.
Today I was planning a NSX manager deployment in my Home Lab… But that turn out to be a problem, because I could not upload an OVF file in the vSphere Client and HTML5 Web Client. When looking in my Home Lab notes I realized the last time I deployed an OVF was when the VCSA was running 6.5 without update 1. I think something went wrong with updating to VCSA 6.5 update 1.
Both webpages display the problem in a different way.
With the vSphere Client the following pop-up appears when trying to deploy an OVF file: “This version of vCenter Server does not support Deploy OVF Template using this version of vSphere Web Client. To Deploy OVF Template, login with version 18.104.22.168 of vSphere Web Client”
HTML5 Web Client:
The HTML5 Web Client does not display any error at all. It just disables the option to deploy an OVF file.
After some googling I found the following VMware KB article 2151085 (link). This turned out to be the solution.
1. Connect to the vCenter Server Appliance with an SSH session and root credentials.
2. Run this command to enable access the Bash shell:
shell.set –enabled true
3. Type shell and press Enter.
4. Navigate to /etc/vmware-content-library/config/ with this command:
5. Create a backup of the ts-config.properties and ts-config.properties.rpmnew file with these commands:
cp ts-config.properties ts-config.properties.orig
cp ts-config.properties.rpmnew ts-config.properties.rpmnew.orig
6. Rename ts-config.properties.rpmnew to ts-config.properties.
mv ts-config.properties.rpmnew ts-config.properties
7. Restart the Content Library service:
service-control –stop vmware-content-library
service-control –start vmware-content-library
8. Refresh or close your browser and connect with one of the web interfaces.