This message was deleted.

Only when you add new Machines to the mcs catalog

oh shoot

Just create a new machine catalog, new non-persistent and join them to the delivery group. You're good to go then

anything you edit at the VMWare object level meaning CPU/Ram/Disk size after the machine catalog was deployed need to be edited on each machine. The only thing that will get update is things in the OS level. But as @Daniel Madsen said if you redo or build a new catalog then you the machine catalog provisioning scheme will allow this. Here is a example were I had to do something simliar

##Records the Powershell transcript
##Import the VMware module
##Connects to vCenter, you can let it prompt you for username password or you can define it. Example(Connect-VIServer vcenter.lab.local -user Domain\username -password "password") 
Start-Transcript -Path "C:\Temp\transcript0.txt" -NoClobber
Import-Module VMware.VimAutomation.Core
Connect-VIServer vcenter.lab.local -user VSPHERE.LOCAL\Administrator -password "password-example"

##Finds the VDI with a name like LABDaaS and exports it to a CSV
##Imports the CSV file
##Does a Loop and shuts down each VM and enables hotadd for memory and CPU. There is a 60 second sleep between each VM. You can change this
##Starts each
$VMsToUpgrade = get-vm |?{$_.Name -like "*LABDaaS*"} | select name | export-csv -Path C:\Temp\VMsToUpgrade.csv
$vmName = (Import-Csv -Path C:\Temp\VMsToUpgrade.csv).Name
ForEach ($vm in $vm_name){
Shutdown-VMGuest -VM $vm_name -Confirm:$False
Sleep 60
Get-VM -Name $vm_name |Set-VM -MemoryGB 12 –NumCpu 2 –Confirm:$False
$vm = Get-VM -Name $vmName
$spec = New-Object VMware.Vim.VirtualMachineConfigSpec
$spec.CpuHotAddEnabled = $true
$spec.MemoryHotAddEnabled = $true
$vm.ExtensionData.ReconfigVM($spec)
Start-VM $vm_name
Stop-Transcript
}