In this video, I will show you how to HOW TO: Update VMware vSphere vCenter Server 7.0 (VCSA 7.0) using the Appliance Management Interface. In this video, I will show you how to Update VMware vCenter Server 7.0 Update 2c (7.0.2.0400) Build 18356314 to VMware vCenter Server 7.0 Update 3e (7.0.3.0600) Build 19717403.
In this video I refer to the word VAMI – vCenter Server Appliance Management Iinterface,. Listening on the TCP port 5480 on the VMware vCenter Server Appliance. It is used to perform basic administration tasks, e.g. backup, updates, networking changes, and status monitoring.
e.g. https://hostname.domain.com:5480
VAMI has been present since vSphere 6.0 and later.
Video Steps
1. Connect to vCenter Server 7.0.
Using a web browser, enter the fully qualified domain name of the vCenter Server 7.0 in the URL.
2. Privacy Notice.
If using the VMware self-signed certificate (the default), click Accept to proceed.
3. Launch vSphere Client (HTML5)
Click the Launch vSphere Client (HTML5) button.
4. Enter SSO credentials
Enter the Administrator@vsphere.local username and password.
5. Select vCenter Server
At the very top, select your Center Server in the GUI.
6. Appliance Management
Select Summary followed by Appliance Management.
7. Login to VAMI
Enter root username and password for Appliance Management.
8. Backup
Select Backup and create a backup.
9. Update
Select Update and install the latest update.
10. Terms
Agree the terms and conditions, and tick you have made a backup.
11. Install Update
Click Stage and Install and wait for the update to be completed.
12. Update Complete
Click Close and check vCenter Server has been updated correctly.
In this video, I will show you how to HOW TO: Add VMware vSphere Hypervisor ESXi 7.0 Host to VMware vSphere vCenter Server 7.0, with some helpful tips along the way. Did I mention DNS and A records ?
Download the VMware-VCSA-all-x.y.z-abcdefg.iso (DVD image) from VMware and before you start allocate a static IP Address for vCenter Server 7.0 and create an A Record in DNS
2. Mount the ISO.
Mount the ISO, and browse to the folder – vcsa-ui-installer\win32 on the DVD, click the installer.exe file to start the installation of VMware vCenter Server 7.0. There is an OVA present in the ISO. vCenter Server is not designed to be deployed from the OVA. Use the vcsa-ui-installer.
3. Follow the wizard.
Ensure to use a hostname, and FQDN, you did create an A Record in DNS before you started the installation?
4. Configuring VMware vCenter Server 7.0..
Click Continue to proceed with Stage 2 of the deployment process.
5. Connecting to vCenter Server 7.0.
Click the FQDN URL, to access vCenter Server using the vSphere Web Client..
In this video, we are going to show you HOW TO: Rollback VMware vSphere Hypervisor 7.0 U2a (ESXi 7.0.2a) using VMware Hypervisor Recovery Mode.
You may need to complete this procedure if you find that a recent update to a later version of ESXi causes you production issues e.g. storage controller or network interface compatibility issues.
Video Steps
1. Power on
Power on or shutdown and restart your ESXi server
2. Wait for the VMware Hypervisor Recovery screen
Quickly press Shift and R together at the same time
3. Rollback
To rollback to the previous version enter Y
4. Wait
Wait for the ESXi server to select the previous bootbank to start the rollback version
This video will show you how to update ESXi 7U1 to ESXi 7.0U2a using VMware vSphere Lifecycle Manager (vLCM) to get your system up to the latest release. In this tutorial, the version of ESXi 7.0 installed is ESXi 7.0U1, but this video can be followed to upgrade any version of ESXi 7.0. If you do not have vCenter Server 7.0, and your ESXi host has access to the internet, there is a method shown in this video – HOW TO: Update VMware ESXi 7.0U2 to ESXi 7.0U2a direct from VMware.
VMware has removed many older legacy processors (CPUs) from ESXi 7.0U2, and also storage and network controllers. Please check the VMware Hardware Compatibility Lists (HCL) here.
It is not recommended to install ESXi 7.0 on USB or SD cards because of higher write I/O, and the SD cards are currently suffering because they are not higher endurance. Problems have been found in the wild.
It is technically still supported; eventually, this may filter down through the server vendors…
Some additional information regarding the use of USB and SD cards with VMware vSphere Hypervisor 7.0 (ESXi 7.0) and installations.
In the world of virtualization, VMware vCenter Server serves as a crucial component for managing your virtual environment. However, encountering an HTTP 500 Internal Server Error can be frustrating. This blog post will guide you through the steps to troubleshoot and resolve this error effectively.
Understanding the HTTP 500 Internal Server Error
The HTTP 500 Internal Server Error is a generic error message indicating that something has gone wrong on the server side. In the context of VMware vCenter Server, this error often points to underlying issues, such as expired certificates or storage problems.
Common Causes of HTTP 500 Errors
When troubleshooting an HTTP 500 error in VMware vCenter, two primary causes often arise:
Certificate Expiration: Certificates can expire, leading to authentication issues.
Storage Issues: If the storage usage exceeds 95%, it can cause service interruptions.
Initial Steps to Troubleshoot
Before diving deeper into the troubleshooting process, it is essential to perform some initial checks to gather information about the environment and understand the scope of the issue.
1. Check Storage Usage
Start by checking the storage usage on your vCenter Server appliance. Use the following command:
df -h
Ensure that the storage is not above 95%, as this could lead to service disruptions.
2. Verify vCenter Server Build Version
It’s helpful to confirm the build version of your vCenter Server. This can provide insights into whether there are updates or patches available. Use the command:
vpxd -v
3. Check Uptime
Knowing the uptime of your vCenter Server can help diagnose if the server has been restarted recently, which might correlate with the error. Use:
uptime
4. Review vCenter Server Services
Check the status of all vCenter services to see if any are down. This can be done using:
service-control --status --all
Identify any services that are not running, as this will point towards the root of the problem.
Examining Certificate Status
Certificates play a crucial role in the security and functionality of your vCenter Server. If they have expired, you will need to renew or replace them.
1. Check Certificate Expiration
To check the status of your certificates, run the following command:
for store in $(/usr/lib/vmware-vmafd/bin/vecs-cli store list | grep -v TRUSTED_ROOT_CRLS); do echo "[*] Store :" $store; /usr/lib/vmware-vmafd/bin/vecs-cli entry list --store $store --text | grep -ie "Alias" -ie "Not After";done;
This command will list all certificate stores and their expiration dates. Look for any certificates that have expired.
Resetting the vCenter Server Environment
If you determine that the issue is related to an expired certificate, you may need to reset your vCenter Server environment. However, if your vCenter is running in High Availability (HA) mode, you must first disable HA before proceeding.
1. Disable High Availability
To disable HA, you can use the following commands:
vcha-reset-primary
vcha-destroy -f
This process will allow you to make the necessary changes without the constraints of HA.
2. Running Certificate Manager
Once HA is disabled, you can run the Certificate Manager to reset the certificates. Use the command:
/usr/lib/vmware-vmca/bin/certificate-manager
Select the option to reset all certificates. You will need to provide the administrator credentials for the operation.
3. Fill in Certificate Details
During the certificate reset process, you will be prompted to enter various details, including:
Organization Name
Location Information
Hostname
IP Address
Ensure that you enter this information accurately to avoid further issues.
Final Checks and Restarting Services
After resetting the certificates, it’s time to verify that all services are operational.
1. Check Service Status Again
Run the following command to check the status of all services:
service-control --status --all
2. Start Any Stopped Services
If any services are still down, you can start them with:
service-control --start --all
Monitor the output to ensure that all services start correctly without errors.
Conclusion
Resolving an HTTP 500 Internal Server Error in VMware vCenter Server can be a complex process, particularly when dealing with expired certificates and HA configurations. By following the steps outlined in this guide, you can effectively troubleshoot and repair your vCenter Server environment. Always ensure to maintain backups and document your procedures for future reference.
If you encounter further issues or have specific questions regarding your setup, consider reaching out to VMware support or consulting the VMware community forums for additional assistance.
Have you ever faced a vSAN disk group issue that left you scratching your head? You’re not alone. In this guide, we’ll walk through the process of vSAN disk group repair, a critical skill for any VMware administrator. We’ll cover everything from troubleshooting to recreating healthy disk groups, ensuring your vSAN environment stays robust and reliable.
Understanding vSAN Disk Group Issues
vSAN disk groups are the building blocks of your VMware vSAN storage. When they become unhealthy, it can lead to data unavailability and performance issues. Common causes include:
Hardware failures
Firmware incompatibilities
Configuration errors
It’s important to note that using non-HCL (Hardware Compatibility List) compatible hardware can increase the likelihood of these issues. While we’ll demonstrate a repair process, always aim to use VMware-approved hardware in production environments.
Troubleshooting vSAN Disk Group Health
Before diving into repairs, it’s crucial to identify the problem. Here’s how to spot unhealthy disk groups:
1. Check the vSphere GUI
Log into your vSphere client and navigate to the vSAN section. Look for any disk groups marked as “Unhealthy” or with warning icons.
2. Run a vSAN Health Check
Use the built-in vSAN Health Check tool to get a comprehensive view of your vSAN environment’s health.
3. Review ESXi Logs
Sometimes, the ESXi logs can provide more detailed information about the cause of disk group issues.
Remember, before attempting any repairs, always back up your data. vSAN issues can potentially lead to data loss, so it’s better to be safe than sorry.
vSAN Disk Group Repair: The SSH Method
While the vSphere GUI often allows you to remove and recreate disk groups, sometimes you’ll need to use ESXi SSH commands for more stubborn issues. Here’s how:
1. Enable SSH on the ESXi Host
First, enable SSH access on the affected ESXi host through the vSphere client or the Direct Console User Interface (DCUI).
2. Connect via SSH
Use an SSH client to connect to your ESXi host. You’ll need administrative credentials.
3. Remove the Problematic Disk Group
Use the following command to remove the disk group:
esxcli vsan storage remove -u <disk_group_uuid>
Replace <disk_group_uuid> with the UUID of the problematic disk group. You can find this UUID in the vSphere client.
4. Verify Removal
After running the command, refresh the vSphere client and verify that the disk group has been removed.
Recreating a Healthy vSAN Disk Group
Once you’ve removed the problematic disk group, it’s time to create a new, healthy one. Here’s how:
1. Identify Available Disks
In the vSphere client, navigate to the storage devices section of your host. Look for unclaimed disks that can be used for your new disk group.
2. Select Cache and Capacity Tiers
Choose an appropriate SSD for your cache tier and HDDs or SSDs for your capacity tier. Remember, the cache tier should be a high-performance SSD.
3. Create the New Disk Group
In the vSphere client:
Go to the vSAN section
Click on “Add Disk Group”
Select your cache and capacity disks
Confirm and create the disk group
4. Monitor the Creation Process
Keep an eye on the tasks pane in vSphere to ensure the disk group creation completes successfully.
Post-Repair vSAN Health Check
After repairing your disk group, it’s important to verify that everything is functioning correctly:
1. Run Skyline Health Check
Use the vSAN Skyline Health tool to perform a comprehensive health check of your vSAN environment.
2. Verify Virtual Object Status
Check that all your virtual machines and other vSAN objects are accessible and performing as expected.
3. Check Hosts in Maintenance Mode
If any hosts were put into maintenance mode during the repair process, ensure they’re brought back online and fully integrated into the vSAN cluster.
Best Practices for vSAN Storage Management
To minimize the chances of future disk group issues, consider these best practices:
Perform regular health checks and monitoring
Use only VMware HCL compatible hardware
Keep ESXi hosts and vSAN up to date with the latest patches
Implement proper capacity planning for your vSAN environment
Set up alerts for disk failures and performance issues
By following these guidelines, you’ll create a more stable and reliable vSAN environment, reducing the need for emergency repairs.
Mastering vSAN disk group repair is an important skill for any VMware administrator. While it can be challenging, especially when dealing with non-HCL hardware, the process we’ve outlined should help you navigate most issues. Remember, prevention is always better than cure, so invest time in proper planning, monitoring, and maintenance of your vSAN environment.
In our next post, we’ll dive deeper into troubleshooting vSAN cluster issues, so stay tuned for more VMware insights!
FAQ (Frequently Asked Questions)
What causes vSAN disk groups to become unhealthy?
vSAN disk groups can become unhealthy due to various reasons, including hardware failures, firmware incompatibilities, configuration errors, or using non-HCL compatible hardware. Regular monitoring and using approved hardware can help prevent these issues.
Can I repair a vSAN disk group without using SSH?
In many cases, you can repair vSAN disk groups using the vSphere GUI. However, for more stubborn issues, SSH access and command-line tools may be necessary.
How often should I run vSAN health checks?
It’s recommended to run vSAN health checks regularly, ideally daily or weekly, depending on your environment’s criticality. Additionally, set up automated alerts to notify you of any issues promptly.
What should I do if I can’t remove a disk group using the vSphere GUI?
If the GUI method fails, you can use the ESXi CLI command “esxcli vsan storage remove” via SSH to forcefully remove the problematic disk group. Always ensure you have backups before attempting this.
Is it safe to use consumer-grade SSDs in a vSAN environment?
While it’s possible to use consumer-grade SSDs, it’s not recommended for production environments. VMware’s Hardware Compatibility List (HCL) provides a list of tested and approved hardware for vSAN, which helps ensure stability and performance.
Troubleshooting VMware vSAN can feel like trying to solve a Rubik’s cube blindfolded. But fear not, fellow IT warriors! We’re about to unravel the mysteries of vSAN troubleshooting and arm you with the knowledge to tackle common issues head-on.
vSAN, or Virtual Storage Area Network, is a software-defined storage solution that pools together storage resources from multiple ESXi hosts. While it’s a powerful tool for modern data centers, it can sometimes throw a wrench in your perfectly oiled IT machine.
Let’s dive into the world of vSAN troubleshooting, focusing on ESXi host issues, configuration pitfalls, and performance optimization. By the end of this post, you’ll be ready to face vSAN challenges with confidence and a toolkit of solutions.
ESXi Host Issues in vSAN Clusters: The Silent Troublemakers
ESXi hosts are the backbone of your vSAN environment. When they act up, your entire virtual infrastructure can come crashing down faster than you can say “blue screen of death.” Here are some common ESXi host issues you might encounter:
Power-Related Problems: The Spark That Ignites Chaos
Power issues are like that one friend who always shows up uninvited to your party and ruins everything. They can cause hosts to unexpectedly shut down or restart, leading to data inconsistencies and VM inaccessibility. Always ensure your hosts have reliable power sources and proper UPS systems in place.
The Uncooperative Host: When Restarting Isn’t Enough
Sometimes, an ESXi host might refuse to play nice with vSAN after a restart. It’s like that one coworker who comes back from vacation and forgets how to do their job. This can lead to all sorts of problems, including:
Virtual machines becoming inaccessible
Data synchronization issues
Cluster health degradation
Virtual Machine Inaccessibility: The Disappearing Act
Picture this: you’re working on an important project, and suddenly your VM vanishes into thin air. Poof! Gone! This heart-stopping moment is often a symptom of underlying host communication issues. Your VMs aren’t really gone, but they’re playing an unwelcome game of hide-and-seek.
Host Communication Blockage: The Silent Treatment
When hosts stop talking to each other, it’s like a dysfunctional family dinner where nobody’s speaking. This communication breakdown can lead to data inconsistencies, performance issues, and a generally unhappy vSAN cluster.
Critical vSAN Configuration Parameters: The Hidden Puppeteers
Behind the scenes of your vSAN environment, there are configuration parameters pulling the strings. Two of these parameters can make or break your vSAN performance:
DOMPauseAllCCPs: The Gatekeeper
This cryptic-sounding parameter is like the bouncer at an exclusive club. When set correctly (to 0), it allows smooth communication between hosts. But if it’s set to 1, it’s like the bouncer decided to block everyone, causing chaos in your vSAN cluster.
Ignore cluster member list updates: The Gossip Suppressor
This parameter, when set to 0, ensures that your hosts are always up to date with the latest cluster information. It’s like making sure everyone in your team has the most recent version of the project plan. If it’s set to 1, your hosts might as well be working with outdated information from last year’s Christmas party.
Checking and Modifying These Values: Your SSH Adventure
To check and modify these values, you’ll need to channel your inner hacker and use SSH. Here’s a quick guide:
SSH into your ESXi host
Run the command: vsish -e get /config/VSAN/intOpts/DOMPauseAllCCPs to check the current value
If it’s not 0, set it using: vsish -e set /config/VSAN/intOpts/DOMPauseAllCCPs 0
Repeat the process for esxcfg-advcfg -g /VSAN/IgnoreClusterMemberListUpdates
Remember, with great power comes great responsibility. Always double-check before making changes!
Troubleshooting vSAN Performance: Detective Work in the Virtual World
When your vSAN cluster starts acting slower than a sloth on a lazy Sunday, it’s time to put on your detective hat and investigate. Here are some tools and techniques to help you crack the case:
VM Creation Test: The Canary in the Coal Mine
This test is like trying to bake a cake in each of your ovens to see which one’s temperature is off. Create a test VM on each host and observe the time it takes. If one host is significantly slower, you’ve found your problem child.
Monitoring Resyncing Objects: Watching Paint Dry, But More Exciting
Resyncing objects in vSAN is normal, but excessive resyncing can indicate underlying issues. Keep an eye on the “Resyncing Components” view in the vSphere Client. If it looks busier than a beehive, you might have a problem.
Observing Virtual Object Data Moves: The Great Migration
Data moves in vSAN are like a never-ending game of musical chairs. Some movement is normal, but excessive shuffling can impact performance. Use the vSAN performance service to monitor these moves and identify any hosts that are overly active.
Regular Cluster Health Checks: The Virtual Doctor’s Appointment
Just like you wouldn’t skip your annual physical (right?), don’t neglect regular vSAN health checks. Use the built-in health check tool to catch potential issues before they become full-blown problems.
Best Practices for vSAN Maintenance: Keeping Your Virtual House in Order
Maintaining a healthy vSAN environment is like keeping a garden. It requires regular care, attention, and sometimes a bit of pruning. Here are some best practices to keep your vSAN cluster happy and healthy:
Proper Shutdown and Startup Procedures: The Virtual Bedtime Routine
When shutting down or starting up your vSAN cluster, follow the proper procedures. It’s like tucking your virtual children into bed – do it right, and they’ll wake up happy and refreshed.
Always shut down VMs before hosts
Power on hosts before powering on VMs
Allow time for synchronization between steps
Regular Monitoring of Host Configurations: Trust, but Verify
Keep a watchful eye on your host configurations. Sometimes, settings can change unexpectedly, like a toddler getting into the cookie jar when you’re not looking. Regularly check and verify your host settings to ensure they haven’t wandered off course.
Addressing Issues Promptly: The Stitch in Time Saves Nine Approach
When you spot an issue, don’t procrastinate. Addressing problems quickly can prevent them from snowballing into larger, more complex issues. It’s like fixing a small leak before it floods your entire basement.
Keeping ESXi Hosts Updated: The Software Fountain of Youth
Regular updates for your ESXi hosts are crucial. They’re not just for new features – they often include important bug fixes and security patches. Think of it as giving your hosts a regular spa day to keep them young and vibrant.
As we wrap up our journey through the labyrinth of vSAN troubleshooting, remember that mastering these skills is an ongoing process. Every challenge you face is an opportunity to learn and improve your virtual infrastructure.
Keep these tips in your back pocket, and you’ll be well-equipped to handle whatever vSAN throws your way. And who knows? You might even start to enjoy the thrill of the troubleshoot!
Stay tuned for our upcoming exploration of vSphere VDT – another exciting chapter in our VMware adventure. Until then, may your clusters be healthy and your VMs be always accessible!
FAQ (Frequently Asked Questions)
What is vSAN and why is it important?
vSAN (Virtual Storage Area Network) is a software-defined storage solution that pools storage resources from multiple ESXi hosts. It’s important because it provides a flexible, scalable, and cost-effective way to manage storage in virtualized environments, eliminating the need for external SAN or NAS arrays.
How can I identify if an ESXi host is causing issues in my vSAN cluster?
You can identify problematic ESXi hosts by running a VM creation test across all hosts, monitoring resyncing objects, observing virtual object data moves, and conducting regular cluster health checks. If one host consistently performs poorly or shows unusual behavior, it may be the source of your vSAN issues.
What are the most critical vSAN configuration parameters to check?
The two most critical parameters to check are “Dom pors all ccps” and “Ignore cluster member list updates”. Both should be set to 0 for optimal vSAN performance. You can check and modify these values using SSH commands on your ESXi hosts.
How often should I perform vSAN health checks?
It’s recommended to perform vSAN health checks regularly, ideally at least once a week. However, in more dynamic environments or during periods of change, you may want to increase the frequency to daily checks.
What should I do if I notice excessive data movement in my vSAN cluster?
If you notice excessive data movement, first check if there have been recent changes to your cluster (like adding or removing hosts). If not, investigate the health of your storage devices, network connectivity, and host configurations. You may also want to review your storage policies to ensure they’re optimized for your workload.
Are you looking to streamline your VMware ESXi upgrade process? vSphere Lifecycle Manager (vLCM) offers a powerful solution for managing ESXi updates efficiently. In this post, we’ll walk through the steps of performing a VMware ESXi upgrade using vLCM, specifically focusing on the ESXi 7.0 U3q update. We’ll also discuss the benefits of VLCM over manual methods and address some common questions about VMware support and licensing.
Preparing for the ESXi 7.0 U3q Update
Before diving into the upgrade process, it’s important to ensure your environment is ready. Here are the key steps to prepare:
Check your current ESXi version and build number
Verify vCenter Server compatibility
Use images instead of baselines for the upgrade
Assign the correct image to the cluster
In our example, we’re upgrading from ESXi build 22348164 to the latest 7.0 U3q build 23794027. It’s worth noting that using images for upgrades is becoming the preferred method, as baselines may be deprecated in the future.
VMware Host Remediation Process
Once you’ve prepared your environment, it’s time to start the remediation process. Here’s what to expect:
Initiate the remediation process through the vSphere client
Review and acknowledge any warnings about removed VIBs
Monitor the upgrade progress
Wait for the host to reboot after successful installation
During the upgrade, you may encounter warnings about removed VIBs. In our case, we saw warnings about an NFS v8i plugin and a CLI tool. These warnings are generally safe to acknowledge, but always double-check if they might impact your specific environment.
Benefits of Using vLCM for ESXi Patching
VLCM offers several advantages over manual “dirty upgrade” methods:
Streamlined process for upgrading multiple hosts
Incorporation of vendor add-ons, firmware, and drivers
Reduced risk of human error
Improved consistency across your environment
Many administrators still rely on manual methods, such as using SSH and ESXCli commands to update their hosts. While these methods can work, they’re more prone to errors and don’t offer the same level of integration and automation as vLCM.
VMware Support and Licensing Considerations
A common question that arises when discussing VMware updates is whether ongoing support is necessary. Here are some key points to consider:
ESXi licenses are perpetual and don’t expire
Support entitles you to contact VMware (now Broadcom) for assistance
Updates are currently available without active support
The support structure has changed, with some support now handled by resellers or distributors
It’s important to evaluate whether paid support meets your needs or if community resources and third-party support options might be sufficient. Keep in mind that while updates are currently available without active support, this could change in the future.
Best Practices for VMware vSphere Management
To maintain a healthy vSphere environment, consider the following best practices:
Regularly patch and update your ESXi hosts
Utilize VLCM for automated updates
Keep your vCenter Server up-to-date
Explore alternative support options, such as Experts Exchange
By following these practices, you can ensure your VMware environment remains secure, stable, and up-to-date.
Wrapping Up
Upgrading VMware ESXi using vLCM is a straightforward process that offers numerous benefits over manual methods. By leveraging vLCM, you can save time, reduce errors, and ensure consistency across your environment. As VMware continues to evolve, staying current with updates and best practices is key to maintaining a robust virtualization infrastructure.
FAQ (Frequently Asked Questions)
Do I need active VMware support to download and install ESXi updates?
Currently, ESXi updates for version 7.0 and 8.0 are available without requiring active support. However, this could change in the future, and it’s best to check with Broadcom or your reseller for the most up-to-date information.
What are the advantages of using vLCM over manual upgrade methods?
VLCM offers automated updates, incorporates vendor add-ons and firmware, reduces human error, and provides a consistent upgrade process across multiple hosts. It’s generally more efficient and reliable than manual “dirty upgrade” methods.
Are ESXi licenses perpetual?
Yes, ESXi licenses are perpetual and do not expire. However, active support is a separate consideration and may be necessary for certain benefits and assistance.
How often should I update my ESXi hosts?
It’s recommended to keep your ESXi hosts regularly updated to ensure security, stability, and compatibility with the latest hardware and software. The frequency may depend on your specific environment and requirements, but quarterly updates are a common practice in many organizations.
Can I use vLCM to update ESXi hosts without internet access?
Yes, vLCM can be used in environments without direct internet access. You can download update packages and create custom images that include all necessary components, then use these for offline updates through vLCM.
In 2010, I made my return to Experts Exchange, the original and No.1 tech community, first launched in 1996. My journey actually began in 2003 when I first stumbled across the platform while seeking assistance with an Outlook Exchange OWA issue. Experts Exchange quickly became my go-to resource for problem-solving.
A significant part of my re-engagement was thanks to my friend from the University of Plymouth, Richard Quadling, a PHP expert and passionate advocate for Experts Exchange. Seeing Richard proudly wearing his EE “Genius” t-shirt made me want one of my own. Naturally, I asked him, “How do I get one?”
Richard’s advice was straightforward: contribute to the community and answer questions. I asked if there were VMware or Virtualization topics I could help with, and he pointed me in the right direction. My goal was set—earn that Genius t-shirt and top the VMware leader board.
Early Achievements
I started answering questions in late 2010 and, within a few weeks, had earned 50,000 points, achieving my first milestone and receiving my Master T-shirt. Over the next few months, my journey continued with more milestones:
Guru: January 8, 2011
Wizard: January 23, 2011
Sage: February 18, 2011
Genius: May 13, 2011
By the end of 2011, I had secured a position as one of the top contributors. At the 8th Annual Expert Awards, I was honoured with:
Expert of the Year: 1st place
Juggernaut: 1st place
The Ally: 1st place
Titan – VMware: 4th place
My journey had only just begun. The Quarterly Awards were discontinued in 2012, but my contributions continued to be recognized unofficially, later becoming known as “Front Runners.”
Rising Through the Ranks
As I moved forward, I broke several records. In 2012, I became the first VMware Savant, reaching 10,000,000 points on November 25. Other notable achievements followed:
Prodigy in VMware (December 2012)
Genius in VMware (May 2011)
The first Virtualization Prodigy (November 2013)
By this time, I had earned a life membership to Experts Exchange and received their 5 Million Point Club email.
The community became a significant part of my life, and my achievements continued to stack up. By the end of 2015, I was named Expert of the Year, The Detective, and The Scribe for five consecutive years (2011-2015)—a record I believe no other Expert has achieved!
Unforgettable Milestones
In 2017, I hit another high, receiving the coveted ELITE Experts Exchange T-shirt on February 20. That year also marked my last Expert of the Year title, capping off an incredible seven consecutive years at the top.
VMworld 2015
Alongside these achievements, Experts Exchange awarded me an all-inclusive trip to VMworld 2015 in Barcelona,
Experts Exchange Core 2023
and in 2023, I received an invitation to Experts Exchange Core 2023.
The Secret Milestone
Hall of Fame – No.1
In addition to these well-known achievements, there was one secret milestone I had been chasing for over 11 years: becoming the No. 1 expert on the Experts Exchange leader board. On May 6, 2022, I surpassed Guy Hengel (angelIII), reaching 40,983,813 points and claiming the top spot. Today, as I write this in Autumn 2024, I have accumulated 43,843,073 points—a testament to years of dedication and passion for helping others.
Testimonials from the Community
Over the years, I’ve received some incredible testimonials that highlight the impact of my contributions:
“Cheers Hancocka for your out-of-hours help, you deserve all the points and more!”
“Andrew responds quickly, competently, and zeros in on the fix. He’s like a VMware Yoda!”
“What VMware couldn’t solve, hanccocka could!”
“Dude, when you finally get your pic of you wearing cape + mask I want my Xlarge pre-ordered.”
These words from the community mean the world to me, and they have fuelled my drive to continue giving back.
Wrapping Up
In conclusion, if you have the patience, dedication, and passion for an IT topic, and want to teach, share knowledge, and help others solve their tech problems, join Experts Exchange. Answer questions, write articles, publish videos—you never know, you might just become the next No. 1 point earner or even an Expert of the Year.
As my brother always says, “Follow your dreams.” While this wasn’t exactly a dream, it was a secret desire:
Obtain a Genius T-Shirt
Earn 1,000,000 points in the VMware Topic
Be No. 1 on the VMware Leaderboard
Get an Elite T-shirt
Become the No. 1 Overall Point Earner
Thanks to Experts Exchange for providing such an incredible platform, and to the community for asking the questions that allowed me to grow and achieve these milestones. Here’s to many more years of collaboration and success in the No. 1 technology community on the web!
![[Valid RSS]](http://andysworld.org.uk/images/valid-rss.png "Validate my RSS feed")