Ironically enough, shortly after posting Using VCF’s Async Patch Tool on Windows I was contacted by a VMware colleague who had seen the post. As it turns out, his team at VMware had been working on including PowerShell as an option for the Async Patch Tool. Big shout out to Ryan Johnson over at VMware – check out his post about Using the VMWare Cloud Foundation Async Patch Tool with PowerShell. His post outlines the usage of the tool in the context of PowerShell.
As you step through Using the VMWare Cloud Foundation Async Patch Tool with PowerShell you will notice that each section has its own script block instead of one large all-encompassing script. You will also notice that various arguments can be added to these script blocks in order to fit needs of each environment. I have not heard anything official about this being productized but knowing the guys at VMware I’m sure these script blocks are just paving the road for something bigger?
I’m only going to walk through setting up the environment and running the list command in this post, since I don’t currently have a need to patch my lab system. However, all the constructs of populating PowerShell variables and running the invoke commands are the pretty much the same over and over.
Setup
Install and Configure Async Patch Tool on Jump Host
Install or upgrade to the required Operating System, PowerShell, PowerShell Modules, 7-zip, and Java version.
You will be starting off with just the AP Tool downloaded. If Windows folder settings aren’t changed, you might not see the .gz portion of the extension. 
A directory will be created for the asynPatchTool itself and a directory will be created for apToolBundles to be stored once downloaded. 
vcf-async-patch-tool-1.1.0.2.tar.gz will get extracted into the Downloads directory as a .tar file. 
The extracted vcf-async-patch-tool-1.1.0.2.tar will get extracted into the asyncpathTool directory where the Async Patch Tool artifacts will be stored.
Install and Configure Async Patch Tool on SDDC Manager
The SDDC Manager setup is pretty straight forward as along as all the directory names are aligned so that the intended source and destination match.
You will notice that the home directory does not yet have any files or directories in it. 
After variables have been defined, the first command will copy files to SDDC Manager and the second command will set permissions/ownership. 
Here you can see the copied artifacts as well as their permissions and ownership.
List Available Patches
Just like the rest of the script blocks, once you’ve populated all the proper information it’s pretty simple to do what you need in order to work with the Async Patch Tool in Windows and PowerShell. Notice I am using the VCF_ON_VXRAIL sku and I am able to see the available VxRail versions available. When using the VCF_ON_VXRAIL during download, the partnerBundleDepotUserName and partnerBundleDepotPassword should be included in the list of variables and then added to the $AP_COMMAND variable.
Once you’re environment is setup running the commands for the Async Patch Tool become a little less cumbersome! Really looking forward to how this patching tool evolves within the product.