This message was deleted.
# citrix-vads
Slackbot
06/03/2020, 4:59 PMThis message was deleted.
r
Ray Davis
06/03/2020, 5:25 PMWhen you promote it from studio, The MCS machine will ask you to appliy now or schedule reboot to apply. Think this is what you're asking.
w
Webster Webster
06/03/2020, 5:30 PMThe VMs must reboot at some point to get the updated image
l
langsbr
06/03/2020, 5:48 PMThat makes sense for VMs that are powered on already - or does it mean even a VM that's been in a powered off state must power on, get updated, and reboot?
c
Cormac Long
06/03/2020, 7:16 PMYes. It has to be powered on from studio (only) to get the new image. Powering on at the host won’t trigger the vm reconfig.
l
langsbr
06/03/2020, 7:18 PMSo let's say I have 1000 vms but 500 are off. I update the image, and then go to push out the update. Will the 500 that are powered off need to do a reboot to get updated on do they get the new image on next boot?
w
Webster Webster
06/03/2020, 7:21 PMThe powered off VMs will received the updated image when they are powered on either by manually powering them on in Studio or they are powered on as part of the catalog's power management settings.
c
Cormac Long
06/03/2020, 7:22 PMThey will get it on the next boot. MCS snapshots your master (or master snapshot) and copies it to storage creating a new base disk for your catalog. The catalog doesn’t really care about your master image/snapshot anymore after that. Not that I would recommend deleting it.
w
Webster Webster
06/03/2020, 7:22 PMIf you do power management from the host, the VMs will not "know" to get anything from Studio and Studio will not "know" how to tell them there are changes. Restarting a VM from the host also does not clear the differential disk
Webster Webster
06/03/2020, 7:23 PMMy understanding is if you want to revert an image, you need the prior snapshot
l
langsbr
06/03/2020, 7:24 PMGot it. Just wanted to make sure a single specific reboot was required and that all of the image update stuff happens purely on the storage side
c
Cormac Long
06/03/2020, 7:24 PMsorry, @Webster Webster is right. You need it for the rollback. I was just saying in theory you could delete and it wouldn’t break a non persistent catalog.
Cormac Long
06/03/2020, 7:25 PMYou can use get-provvm cmdlet to check the “assignedimage” for the catalog and the “bootedimage” that vm is running off. If these have the same guid then you know the vm is on the most recent basedisk.
m
Mike Streetz (O_P)
06/03/2020, 8:41 PMGet-ProvScheme -adminaddress DDC-machine-name | select ProvisioningSchemeName, masterimagevm
Mike Streetz (O_P)
06/03/2020, 8:41 PMypu can also look for the pending update flag