An interesting thought to ponder... What would you do? This is the scenario:
We re-baseline our desktop master images every quarter, ie. 4 times a year, to include all latest software updates. This will include the master image for statically assigned virtual desktops.
For obvious reasons, XenDesktop does not provide the ability to update Static (Dedicated) machine catalogs, only Random (Pooled). On the one hand this is ok, because once deployed by MCS, Static desktops will thereafter be maintained by SCCM, so we simply don't touch the already deployed machine catalog. But where does that leave new desktops?
I'm thinking that we would have to deploy a new machine catalog pointing to the new image/snapshot whenever we re-baseline each quarter. This is where it starts to get interesting. This approach would mean 4 new machine catalogs per year, per customer. And we need to maintain these catalogs as long as there are people connecting to them. The list of catalogs will become huge over time.
This gets even more interesting when you throw App Orchestration and CPSM into the mix. For each of our customers, we would also need to also create the new catalog in App Orchestration, + a new Offering, + do the setup in CPSM Hosted Apps and Desktops service to point to the new Offering.
And how do we stop users from requesting the old (pre re-baselined) desktop in CPSM? As far as I know, this is not possible (see attached), which is a bit of an issue.
Apologies for the length of this and I hope it makes sense to someone. Hopefully this is not as big of a potential nightmare as it first appears. Am I missing a trick somewhere? Any thoughts on this would be appreciated.