I’ve been wanting to write about my first-ever VMworld experience even before the plane departed from McCarran airport, but I just couldn’t seem to find the time to actually sit down and “put my thoughts to paper” as they say. I can’t believe it’s already been a month since the conference events first kicked off in Las Vegas! The time sure does fly by! But, I at least wanted to share my experience with others who maybe haven’t been to a VMworld conference yet, or who might be going for the first time next year. (Hey, you never know!)
This script is an idea that spun off of my previous post, PowerCLI: Find UEFI-Enabled VMs. If you’re preparing to enable Secure Boot in a VMware environment, it may be helpful to identify the VMs that cannot be upgraded. As you might recall, enabling secure boot requires the following:
- VMware vSphere 6.5 or higher
- Virtual hardware version 13 or higher
- VMs need to be configured with EFI boot firmware
With all the news regarding the Spectre and Meltdown CPU vulnerabilities over the past several months, there’s been a greater focus to get VMware virtual machines to virtual hardware version 9 or higher, as noted by Andrea Mauro’s post regarding these vulnerabilities. In addition to that, several companies and organizations may be looking to enable Secure Boot, a feature first introduced with vSphere 6.5. However, in order to enable secure boot, the virtual machine needs to be configured with both EFI boot firmware AND be on virtual hardware version 13 or higher.
For the fifth and final portion of my Git Integration with VS Code blog series, this post focuses on Synchronizing Content with GitHub. Previously in Part 4, we configured Visual Studio Code to establish a connection and download content from GitHub. In this post, I wanted to focus on staging, committing, and pushing content back up to GitHub. Continue reading “Git Integration with VS Code: Part 5 – Syncing with GitHub”
Now that PowerShell has been upgraded, and we installed both Git and VS Code, let’s go ahead and configure our environment for synchronization with GitHub. For me, this part was really the meat and potatoes of getting VS Code to integrate with Git and GitHub.
Installing the PowerShell Module
Now that VS Code is installed, let’s install the PowerShell Module so that it can properly understand PowerShell scripts and *.ps1 files.Continue reading “Git Integration with VS Code: Part 4 – Configuring Visual Studio Code”
This blog post picks up where Part 2 – Installing PowerCLI and Git left off. Now that we have some momentum going with this Git Integration with VS Code blog series, let’s keep it going with Part 3 – Installing Visual Studio Code! Continue reading “Git Integration with VS Code: Part 3 – Installing Visual Studio Code”
In case you missed it, this blog post picks up where Part 1 – Upgrading PowerShell left off. In continuing on with the Git Integration with VS Code blog series, I now present Part 2 – Installing PowerCLI and Git!
NOTE: This process assumes a Windows-based installation, and for the Git install, most of the options were left to defaults unless otherwise noted. Continue reading “Git Integration with VS Code: Part 2 – Installing PowerCLI and Git”
So, I’ve been wanting to do this blog series for quite some time, and I’ve been working to put all of the various bits together. When I first started writing scripts for PowerCLI, I would simply write them using either the native Windows PowerShell ISE or some other text editor like Notepad++. It was fine for a while, but I soon began running into issues with version control. Before I knew it, I quickly ended up with a multitude of files in a folder. Things like script-draft.ps1, script-edited.ps1, script-edit2.ps1, script-working.ps1, script-final.ps1, script-FINAL-20180311.ps1, etc. It quickly got to the point where I didn’t know which files had the latest changes to them, or which ones had the newest feature I implemented (or was trying to implement). Does any of this sound familiar?
At a recent Western PA VMUG meeting, I was introduced to this new product (to me, at least) called Visual Studio Code. Sure, it was another place to work on developing and even running PowerShell and PowerCLI scripts, but I had no idea how about the concept of version control or Git integration that lied within. All of that stuff was completely foreign to me, but sounded interesting. And, with the help of the #vCommunity and some of my own research, I finally got to a point where I understood how I could integrate my VS Code editor with my online GitHub account, and keep them in sync across multiple devices.
Hello again, everyone! Last Friday, I hit a rather significant milestone in my career as an IT professional, as I made the cut for the VMware vExpert advocacy program for 2018! As exciting as it was to receive this news, I actually didn’t find out until about two hours after the announcements were made. Why the long delay? Well, here’s what happened…
I actually got a phone call from to go check my email, as the vExpert announcement emails were starting to go out. I immediately checked my corporate email, but didn’t see anything. So, I began checking my personal email accounts, and I didn’t see anything there either. I figured maybe there was a delay of some sort and I’d check back in 15-30 minutes to be safe. Well, I checked again, but I still didn’t see any announcement email in any of my accounts. Now, I was beginning to think that I honestly didn’t make it! Continue reading “Achievement Unlocked! VMware vExpert 2018”
Ok. I know what you’re probably thinking… It’s now 2018, so why are you still rocking a 13″ MacBook Pro from early 2011? Well, the simple reason is that for the most part, it still does what I need it to do. It’s got a Core i7, 8GB of RAM, and an SSD drive. Another reason is that I just simply don’t have the funds to plop down on a newer model MacBook Pro. It has become clear, however, that the internal graphics card is starting to become one of its weakest components.
Earlier this year, I upgraded from MacOS Sierra 10.12.6 to High Sierra 10.13.2. Even before the update, I noticed a few websites that utilized the WebGL API said that WebGL wasn’t enabled on my browser. From what I’ve researched, it appears that WebGL was disabled in my browser because the Intel HD Graphics 3000 card isn’t supported. (See WebGL Browser Report over at https://browserleaks.com/webgl).