This message was deleted.
# citrix-vad
s
This message was deleted.
m
Are they non-persistent?
you can do pretty much the same thing, it’s a bit more involved though
t
Sorry left that out. They are all non-persistent desktops.
l
Similar except you go through a process of copying a snapshot and linking machines to that new snapshot on a shutdown and reboot. It can be scheduled and applied on reboot though, as mike said.
k
Rolling machine catalogs would work?
t
Thanks. Are you still running scripts to perform regular reboots, or using the power management features in Studio to set the percentage of available VMs and reboots after logouts for the updates? I was planning on splitting them VMs into two catalogs for phased image updates.
l
You'll need to trigger your machine reboots using the SDK so that studio issues the reboot command for the image update process to work. You can script the whole lot though.