VMware Software Manager: The Good…The Bad…The Alternative!
In this post, I am going to discuss a little, “not-so-well-known” utility, called VMware Software Manager. This little “beast” was first released as v1.0 back on 2015-03-12, and its most current release, v1.5, came out on 2016-08-25. So as you can see, it’s been quite a while since this tool has seen a new update release. The problem now is that this utility seems to have been forgotten and/or neglected by VMware, but I will get into more of that a little later. Let’s start off with the positive stuff.
The VMware Software Manager allowed valid VMware-account holders the ability to download various software, such as ESXi or vCenter server, quickly and easily. The installation was a breeze, the interface was clean and downloading software was effortless. It basically just worked flawlessly! The new software was readily available for download shortly after it was announced/released since this utility would read configuration files to see what software is available from the VMware repository and then provided that software for download.
So, having said that, what could possibly be wrong with this thing? Let’s continue…
My main gripe with this utility was that support was only community-based, so if you had issues, you could forget about raising an official SR with support. You had to rely patiently on the VMTN community and hope that users were knowledgeable enough and willing to help out. Not saying anything bad about the community though, it’s a great forum full of some really smart people and it provides a wealth of information.
As I mentioned earlier, when this thing worked…it just plain WORKED! Then, vSphere 6.0U3A was released with some bad/corrupt or missing files and upon launching the utility, it would simply hang at login or error out due to the missing files not being available! (Shhhh!..someone never updated the configuration files… ¯\_(ツ)_/¯ ) There is a thread over on the VMTN community that myself and others have contributed to and another describing this issue and a workaround method to ultimately get you to log in again. This involved looking at log files to find which missing file was causing the error, then editing the configuration file to remove the missing files, and it was a major pain!
Lastly, it’s become extremely out of date and it seems as if VMware has completed forgotten about and/or decided to neglect and give up on it as there has not been any new software available for download in at least 6 months. It’s also possible that the original responsible for this thing disbanded or moved onto other roles…who really knows? Luckily, a friend and fellow community/vExpert member has provided a solution!
Fellow vExpert, Edward Haletky aka Texiwill, has created a Linux-based port of the utility, titled “VSM“, which he updates almost daily to add new software and simply improve the appliance and it runs on an RHEL type distro like CentOS. You can hit the ground running with this appliance in about 30 mins or less. I have been fortunate enough to serve as a beta tester for him and have been doing so since he released v0.95, just shortly after the initial public launch. At the time of this writing, the most recent release was v3.7.7 but has now been updated to the newest 4.5.3. Screenshots may reflect previous versions.
Well…How do you get it?
In this post, I am going to cover how to install this bad-boy on a CentOS 7 minimal installation on ESXi using NFS, and on VMware Workstation leveraging the “Shared Folders” feature using VMHGFS. Another vExpert, Michael White, has a similar post on setting up this appliance and using SMB/CIFS for storing the downloaded software. Let’s get to it, shall we!
- CentOS 7 x64 (Minimal) w/ open-vm-tools installed
- a non-root user account
- NFS storage or Local Storage (if running this on VMware Workstation/Fusion)
I will assume that you already have a basic installation of CentOS 7 running, or know how to set up a minimal installation, so that process is out of scope for this post.
If you plan on running this on VMware Workstation/Fusion, run the following command to install the prerequisites needed for installing VMware Tools to get the vmhgfs driver for Shared Folders support.
sudo yum install -y perl gcc binutils make fuse kernel-headers kernel-devel net-tools policycoreutils-python
Otherwise, if you plan on using NFS to store the software, run the following command to install the NFS utilities.
sudo yum install -y nfs-utils
VMware Tools Installation:
Note: Enables vmhgfs driver support for Shared Folders on VMware Workstation or VMware Fusion
I will be installing the latest version of VMware Tools, version 10.2.0. This can be obtained here. Extract the .zip and attach the linux.iso to your CentOS VM in Workstation or Fusion. Once connected, do the following.
Make a directory to mount the cdrom to.
sudo mkdir /mnt/cdrom
Mount the cdrom to this new directory.
sudo mount /dev/cdrom /mnt/cdrom
With the cdrom now mounted, let take a look at whats on the .iso
sudo ls /mnt/cdrom
We can see the compressed file that we will need to extract
Extract/Uncompress this file by running the following. This is going to extract the file to my current working directory, $HOME
sudo tar zxpf /mnt/cdrom/VMwareTools-10.2.0-7253323.tar.gz
When that completes, we can see what was extracted by running
At this point, we are done with the .iso and can unmount it by running.
sudo umount /dev/cdrom
Now, let’s navigate to the extracted folder and see what we’ve got.
cd vmware-tools-distrib/ ls
The Perl script is what we’re looking for here to install VMware Tools. This will uninstall “open-vm-tools” if that is already installed on this machine. Let’s go ahead and run it.
Proceed to answer all the questions asked and select all of the defaults until the installation completes.
(Optional:) If you’d prefer to bypass the questions and force-install with all defaults run the following instead
sudo ./vmware-install.pl --force-install --default
This completes the VMware Tools installation and not the vmhgfs driver is installed. Onto the good stuff!
Texiwill has provided an installation script on his GitHub page which will take care of the installation and its prerequisites. This is the preferred installation method so I’d advise that you download this script, and run it. You’ll first have to make the script “executable” by running
chmod +x install.sh
For those who prefer the manual approach, you’ll first need to install “wget“, then run the following commands to install the utility.
Note: please change timezone location to your respective location
sudo yum install -y wget mkdir aac-base cd aac-base wget -O aac-base.install https://raw.githubusercontent.com/Texiwill/aac-lib/master/base/aac-base.install chmod +x aac-base.install ./aac-base.install -u America/New_York sudo ./aac-base.install -i vsm America/New_York
Congrats! You’ve successfully installed the utility. Now to configure it for use.
By default, the VSM script will save the config file (.vsmrc) to “$HOME“. It will also save the index.html and credstore files in “/tmp/vsm“. I highly recommend you create an alternate directory to store these files in if you are using a system that has multiple users or change it to save them in the users $HOME directory. Again, this is optional and can be skipped, but if you’d like to do so, run the following
VSM Initial Configuration:
The last step before you can use the VSM script utility is to configure it. To list the all available parameters, execute the script with the help parameter.
Based on the help info, the required parameters to set are:
- -v | –vsmdir VSMDirectory (this will be the “my_vsm” directory we created earlier)
- –repo repopath (this will be the path to the directory we’ll create to save our download)
When first executing the script utility, you will be required to enter valid MyVMware credentials which will be saved to the configuration file.
Let’s go ahead and create our repo directories first. Feel free to use my examples or anything else you’d like. We will also use the same steps mentioned about to take ownership of these directories and then mount our physical storage to the newly created mount point directory.
Note: Be sure to enable “Shared Folders” on Workstation or Fusion and select the shared folder to mount it to the VM. Commands may be different from screenshots as I’ve updated some commands.
sudo mkdir -pvm 755 /mnt/vmhgfs/depot/content sudo chown -R <non-root_username>.<non-root_username> /mnt/vmhgfs
sudo mkdir -pvm 755 /mnt/nfs/depot/content sudo chown -R <non-root_username>.<non-root_username> /mnt/nfs
With our directories ready, let’s go ahead and mount our storage to them!
Note: I have mounted the following shared folder to the VM to use for this command.
sudo mount -t fuse.vmhgfs-fuse .host:/content /mnt/vmhgfs/depot/content -o allow_other
sudo mount -t nfs <IP_address>:/<volume#>/<path_to_share> /mnt/nfs/depot/content
For NFS 4.1 (optional):
sudo mount -t nfs4 -o vers=4,minorversion=1 <IP_address>:/<volume#>/<path_to_share> /mnt/nfs/depot/content
Now, with our storage mounted we can run the VSM script and configure for use.
Note: You will be prompted to enter your VMware credentials unless you supply the “-u” and “-p” parameters
vsm.sh -y -v /tmp/my_vsm --repo /mnt/vmhgfs/depot/content --save
vsm.sh -y -v /tmp/my_vsm --repo /mnt/nfs/depot/content --save
That about does it! The appliance is ready to use and you can navigate through the menus to find your desired software.
To make your mount points persistent through reboots, edit the “fstab” file with your editor of choice. I prefer to use vi or vim, but many may choose to use nano instead.
sudo vi /etc/fstab
Then, add the following line and save the file.
.host:/content /mnt/vmhgfs/depot/content fuse.vmhgfs-fuse allow_other 0 0
<IP_address>:/<volume#>/<path_to_share> /mnt/nfs/depot/content nfs soft,bg,rsize=8192,wsize=8192 0 0
For NFS 4.1 (optional):
<IP_address>:/<volume#>/<path_to_share> /mnt/nfs/depot/content nfs nfsvers=4.1,soft,bg,rsize=8192,wsize=8192 0 0
Updates are released quite frequently. To update VSM to the latest version, you can run the following commands manually or add them to a shell script within “/etc/cron.daily” which will run around 3 AM.
Note: please change timezone location to your respective location
cd /home/<user_name>/aac-base; ./aac-base.install -u; ./aac-base.install -i vsm America/New_York
Additionally, if you’d like to keep your favorite download repository up-to-date, edit crontab
Note: This requires that you first “mark” a repository by using that menu option
Then add the following line to it and save. This will run daily at 6 AM.
0 6 * * * /usr/local/bin/vsm.sh -y -mr -c --favorite
I tend to use the following command when running VSM to get missing suites and packages from MyVMware. If you do not use the “-m” parameter, it will only pull the same software available in the original VMware Software Manager tool from VMware. The “-mr” parameter resets the “MyVMware” software info and implies “-m” hence why this is also used in the crontab line above. The “-c” tells VSM to generate sha256sum checks against each downloaded file.
vsm.sh -y -mr -c
Note: Depending on what you downloaded, there may be certain .txt files that will fail the checksum. This is expected and can be safely ignored.
Well, I hope you’ve found this post useful and I thank you for reading! Special thanks again to Texiwill for making this awesome utility, as well as Mike White for posting his similar article using SMB/CIFS.
- Installing the Linux VMware Software Manager tool
- vSphere Upgrade Saga: Linux VMware Software Manager (VSM)
- Texiwill’s VSM GitHub
- 03.23.18 – Updated to reflect changes in manual install commands for VSM v4.0.2, and cron.daily entry since cron runs as root so no need to use sudo
- 04.12.18 – Added TZ (Time Zone) setting to manual install commands and modified /etc/fstab command for NFS mounts
- 04.15.18 – Added “-c” parameter reference
- 01.17.19 – Added some command syntaxes for NFS 4.1
Install PowerShell and VMware PowerCLI on CentOS
Just a few days ago, PowerShell Core v6.0 was released for Windows, Linux, and macOS systems. Alongside this release came the release of VMware PowerCLI 10.0.0.78953 which is VMware’s own “PowerShell-like” utility.
In my previous post, I covered how to install those on to a macOS 10.13.x “High Sierra” system. In this post, I am going to show how to install both on to a CentOS 7 system as this is the distro I mostly use in my environments. I may follow this up with an Ubuntu install version. Anyway, let’s get to it!
Note: If you’re interested in installing this on other Linux distros, please consult the following link.
There is a prerequisite needed before PowerShell can be installed on CentOS and that is to add the PowerShell Core repository (recommended) to your CentOS system.
sudo curl https://packages.microsoft.com/config/rhel/7/prod.repo | sudo tee /etc/yum.repos.d/microsoft.repo
This will prompt you to enter your password since “sudo“ is being used. Great! With the prerequisite complete, it’s time to install PowerShell Core 6.0.1. Run the following command to do so and enter your password when prompted.
sudo yum install -y powershell
sudo yum update -y powershell
While leveraging the PowerShell Core repository is the recommended installation method, there are alternate methods as well. For more information on that along with uninstallation commands, please see the following link.
Congratulations! You’ve successfully installed PowerShell Core 6.0.1 onto CentOS! Next comes the fun stuff for us VMware enthusiasts, installing VMware PowerCLI from the “PSGallery”. Let’s continue!
Since VMware PowerCLI has moved from being its own native installer to the PSGallery, the PSGallery needs to be “Trusted” before anything from it can be installed. To trust the PSGallery, entering the following command in the PowerShell session.
Note: This is optional and if it is skipped, you will be prompted to trust the gallery when entering the PowerCLI module install command
Set-PSRepository -Name "PSGallery" -InstallationPolicy "Trusted"
Find-Module "VMware.PowerCLI" | Install-Module -Scope "CurrentUser" -AllowClobber
Note: Alternatively, you could set the “-Scope” parameter to “AllUsers” and if you wanted to install a different version you could use the “-RequiredVersion” parameter and specify the version number.
Get-Module "VMware.PowerCLI" -ListAvailable | FT -Autosize
Get-Module "VMware.*" -ListAvailable | FT -Autosize
With VMware.PowerCLI now installed, you can connect to your vCenter Server or ESXi host and begin using its cmdlets to obtain information or automate tasks!
I went ahead and ran the following to ensure the module was imported.
Let’s test connecting to vCenter server…
Connect-VIServer -Server "<Server_Name>"
I also noticed an error when running the above command stating that the “InvalidCertificateAction” setting was “Unset” and not supported.
Set-PowerCLIConfiguration -InvalidCertificateAction "Ignore"
Now, if we try to connect to vCenter again, we should be successful.
Well, that about does it! I hope that you have found this post useful and I thank you for stopping by and reading my content. I’d like to give a shoutout to Jim Jones for his post on the same topic. Until next time!
Pingbacks: From Zero to PowerCLI: CentOS Edition