Azure/Daas/MCS question for the gang. We've had to mirgrate our catalog from one subnet to another. I was hoping power cycling VDAs from DaaS console would cause them to recreate the NIC in the new subnet defined in the catalog but it doesn't. If i add a new machine to the catalog, it lands in the new subnet. anyone know of a way to migrate the existing ones without having to del and recreate?

Pretty sure this should do the trick https://developer-docs.citrix.com/en-us/citrix-virtual-apps-desktops-sdk/2407/machinecreation/set-provvmupdatetimewindow

Thank you James, yes, this is cmdlet to update VM configuration to be same as ProvScheme. The cmdlet allows you to setup time window during which you need to perform power action: shutdown (if VM is running) or reboot from Broker. And for NIC change on existing VM, it is implemented for Azure so it should work. Let me know if you encounter any issue Note, we are working a new mechanism for HW config change (such as NIC, SKU, etc) or operation (such as disk reset, backup & restore), so this cmdlet will be deprecated in the near future. New mechanism will not require admin to coordinate power action and update window, necessary power action will be performed automatically within update window. Will make announcement when that happens