- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Update Manager cmdlets and "Baseline Groups"
Hi all,
just wondering....
Within Update Manager (5.0) I have created a Baseline group, containing a upgrade baseline, security patch baseline and an extension baseline.
Now I want to remediate our ESXi (4.1) hosts with this baseline group to do a complete upgrade using PowerCLI 5.0.1.
But it seems like there is no cmdlet to remediate a host with a "baseline group" only to separate baselines.
Is this correct? Anyone got a solution to this?
Thanks and kind regards,
Harold
@hharold
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Afaik, the current Update Manager snapin doesn't support the concept of baseline groups.
And I'm afraid I have no solution or bypass for this problem.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Luc,
Thanks for the answer, that was what I was afraid for.
I think for now, I will try whether I can remediate against the separate baseline one by one, with the least amount of exiting/entering maintenance mode.
I would really like to use the parallel remediation function to remediate multiple host at a time. That could save us a lot of time.
Thanks again.
Regards,
Harold
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As a workaround as the Update Manager cmdlets do not support baseline groups,
I create my own baseline group in the PowerCLI script:
# Get MyTestCluster
$cluster = Get-Cluster MyTestCluster
# Create a Baseline Group from multiple baselines
$baselines = get-baseline | `
Where {$_.name.contains("ESXi5 Upgrade") `
-or $_.name.contains("- Dell -") `
-or $_.name.contains("VMware ESXi 5.x Patches")}
# Start remediating the cluster
$Cluster | Remediate-Inventory -Baseline $baselines `
-ClusterDisableHighAvailability:$true `
-ClusterEnableParallelRemediation:$true `
-HostIgnoreThirdPartyDrivers:$true -Confirm:$False
Based on the baseline names, I get one upgrade baseline (ESXi4.1 -> ESXi5) and a baseline with the latest patches,
and a vendor specific extension baseline. Update Manager puts these automatically in the correct order and upgrades and patches all hosts