thedotsource / vumxtra

Additional PowerShell functions for VMware Update Manager.

VUMXtra

VUM module to add additional functions for managing VUM, in particular around baseline groups and content import.

New in 1.3

A number of significant changes are present in this release:

VUMXtra now requires PowerCLI 12.7 or above and PowerShell Core. VMWare have ported the Update Manager module to PowerCLI Core which has resulted in significant changes to how the VUM API is called. All functions in this module have been reworked for the new API and are not backwards compatible. As such, support for PowerShell for Windows and PowerCLI versions prior to 12.7 has been dropped. If this is still a requirement you have, please continue to use VUMXtra 1.2.

Dropped support for Windows hosted vCenters. Most notably the Import-VUMContent function will no longer import to a Windows hosted vCenter. Most likely other functions will still work, but have not been tested. If this is a requirement, please continue to use VUMXtra 1.2.

Added functions to configure host remediation settings. This can be passed to Update-EntityBaselineGroup for remediation runtime settings, or applied as VUM default remediation settings. This includes enabling host Quick Boot where the hardware is supported.

Added support for cluster level remediation to Update-EntityBaselineGroup.

Many thanks to Lyuboslav Asenov @ VMWare for helping me with the new Update Manager API. Without his help this would not have been possible.

New in 1.2

Added support for HTTP locations to Import-VUMContent. This is considerably faster than VM tools file copy in most instances.

If the user PowerCLI session is configured to ignore invalid certificates, then Connect-VUM will also ignore them.

New in 1.1

General code tidy up and improvements to comply with PS Script Analyser. As a result some CMDlet names have changed to remove the use of unapproved verbs. CMDlets function exactly the same way as previously.

Support for none self managed vCenters when using Import-VUMContent. Previously, the VCSA would need to be managing it's own virtual machine object. With the use of an additional parameter multiple VI connections can be used to allow for a none self-managed scenario. Review the Import-VUMContent help for further details and examples.

vumxtra's Issues

Problem when Processing Multiple hosts in Loop

If you have a foreach and a group of hosts. There is a bug in that if one of the hosts has already been remediated then the function breaks out the script completely.

Calling
Update-EntityBaselineGroup -BaselineGroupName $baselineGroup -Entity $VMHost -confirm:$false

if entity $vmhost has been patched already then the next host isnt processed.

Solution is to change the Break to a Return at line 219 in Return Update-EntityBaselineGroup

Unable to add baselines to new baseline group when having many groups

In larger environments there may be the case that there are more than 100 baselines. You can then create a new group but you won't be able to add baselines to the group.

Attach-BaselineGroup missing

Great job with this, very excited about it since VMware hasn't addressed it!
The article here: https://thedotsource.com/2019/04/01/vum-extra-module-automating-baseline-groups-and-more/

Shows that attach-baselinegroup is a cmdlet but it is not available in the download. Any chance we can get that added into the module?

Remove-EntityBaselineGroup fails to remove group

Hello,
With version 1.3 it seems Remove-EntityBaselineGroup is failing.

Here is the verbose output which shows the group ID as 15:

VERBOSE: Function start.
VERBOSE: Function start.
VERBOSE: Assuming connection to default vCenter.
VERBOSE: Fetching PowerCLI configuration and checking certificate policy.
VERBOSE: Got PowerCLI configuration.
VERBOSE: Invalid certificates will be ignored as per PowerCLI configuration.
VERBOSE: Getting VUM extension.
VERBOSE: 8/3/2023 9:08:57 AM    Get-View        Finished execution
VERBOSE: Got VUM extension.
VERBOSE: Loading VUM assemblies.
VERBOSE: 8/3/2023 9:08:57 AM    Get-Patch       Finished execution
VERBOSE: Loaded VUM assemblies.
VERBOSE: Initialising VUM service.
VERBOSE: 8/3/2023 9:08:57 AM    Get-View        Finished execution
VERBOSE: VUM service initialised.
VERBOSE: Adding type and creating WCF client.
VERBOSE: WCF client created.
VERBOSE: Connecting to VUM.
VERBOSE: Connected to VUM.
VERBOSE: Got VUM connection.
VERBOSE: Baseline group BB-Group was found, ID 15
VERBOSE: Processing entity redacted.com
VERBOSE: Entity object configured.
VERBOSE: Performing the operation "Remove-EntityBaselineGroup" on target "".
VERBOSE: Baseline group detached.
VERBOSE: Completed entity redacted.com
VERBOSE: All entities completed.
VERBOSE: Disconnected from VUM API.
VERBOSE: Function completed.

But the group is not detached from the host.

However, if I change line 136 of the function from

$reqType.group = 39

to

$reqType.group = [int]$baselineGroup.key

The group is successfully removed. Perhaps some test code wasn't removed from the final function?

Thanks for a great product!

Updating this package to provide functionality to configure vLCM

I know the intension of this package is to automate the VUM configuration, but with vSphere 7, which replaces VUM with vLCM and as I tried to use this package to upload the updates, it was uploading but the updates were not visible on the "Image Depot" tab with vLCM.
With the effort that has been put in bringing this package, it will be a great if this package adds the ability to configure vLCM as well.