Orange County, Tustin, CA 92780
how to upgrade vm version

In today's article, I'll be showing how to upgrade the VM hardware version using PowerCLI for either one VM or multiple VMs at a time to version 11, 12, 13, 14, 15, or any version. Additionally, I'll show you how to target a specific group of VMs by name or based on their location in a given cluster using a one-line command.

Recently, we had a client migrate printers to a new print server from Windows Server 2012 to Windows Server 2019. All their printer mappings on the clients needed to be updated; printer ports and printer names would remain the same, but the print server name would change.

Rubrik Forward Digital Summit

Rubrik hosted its Forward Digital Summit today. Due to Covid-19, this year the company went completely online, and instead of a 3-day in-person conference, it hosted a 1-day event for FREE. If you missed any of the live sessions, you can still register and watch the recorded sessions at a later date.

Use PowerCli to create and remove snapshots from your VMs

One of the major benefits of working with VMs is that you can easily take a snapshot, make a change, test out your change or changes, and if something goes horribly wrong, you can easily revert back your changes at a click of a button. Backup software also uses snapshots.

My current physical lab consists of three Dell R620s that boot off an internal Dual SD module (IDSDM) with ESXi 6.5 as the hypervisor. I've been putting off upgrading to vSphere 7 for several reasons but now that I've committed to upgrading to vCenter Server 7 and ESXi 7, I did encounter an issue with the boot partition for ESXi of it not having enough space - I use 2 GB cards. Time for an upgrade.

download and install vmware powercli module

VMware regularly releases updates to its Powershell module, known as PowerCLI. While in the past you had to go to the vmware.com website, download the executable - by the way, you still can for older versions - and install PowerCLI, you no longer have to since there's an easier way directly from a PowerShell console.

Lot's of us running a vSphere Lab at home have to be mindful of the electrical costs associated with using physical servers. In my case, I have three (3) Dell R620's, one FreeNAS server, and two Cisco switches. Electrical costs are always on my mind, especially now that I work from home and use more electricity. 

Deploy RSAT tools on Windows

Microsoft has, for a long time, provided tools called Remote Server Administration Tools (RSAT) to do remote administration of servers and desktops. These tools are handy if you are regularly having to look at configurations or make changes for machines joined to a Microsoft Windows Domain. Unfortunately, installing these tools is not always that easy since Microsoft changes the install method with each version of Microsoft Windows.

There are plenty of solutions out on the market for backing up your VMware vSphere environment and all are constantly being updated. As you move from one version of VMware vSphere to the next, vendor documentation sometimes is not updated properly to include the necessary permissions for your backup software to properly do its tasks. Calling support is not always the ideal solution because some techs are just going by what their official documentation states - we just covered that their manuals aren't constantly updated (or specific sections). So what do you do?

Configure SNMP for ESXi - "Mini Robot" - Krypton / Doragon / CC BY-SA (https://creativecommons.org/licenses/by-sa/3.0)

VMware documentation is excellent, but not if you're a beginner with PowerCLI. While you will find documentation on how to configure SNMP for your ESXi hosts, the way it's presented is not very clear and will leave you scratching your head in confusion since you'll be thinking how does this configure SNMP on all my ESXi hosts?

GitHub Repository: https://github.com/virtualization247/vmware-scripts.git
Script Name: snmp_config.ps1

You've upgraded to the latest version of vCenter Server, ESXi, VMware Tools, and either scheduled the VM Hardware upgrade on the next reboot or you've manually upgraded the hardware version for each machine. Everything has gone according to plan with no issues during the scheduled maintenance. However, after everything has been done, you find that one of your 3rd party solutions no longer works and you find yourself staring at a list of errors.