Hi all, "Image managment" is marked as Preview in 2402 LTSR, marked as GA in 2411. Does anybody know if this will ever become GA in 2402 (with a CU or whatever) ?

2402 CU2 has been released ??

Not to GA, but early release is available: https://www.citrix.com/downloads/citrix-early-access-release/ear/cvad.html I have heard Image Management will be available in 2402 LTSR CU2.

exactly, the statement above is from citrix blogs article. Will be GA in CU2 but not released yet.

I reached out to my Citrix rep as well as he's the one that told me, from his SE, that Image Management was included in CU2. Image Management still says Tech Preview in the docs and not listed in the "What's New" section.

Have you guys already worked with it? Hard for me to understand it. When I create an image without "Machine Profile" the MCS process seems like before, cloning the Master, Image PrepVM etc, and adding the image to Image Management. But what happens when you add a Machine Profile? What is the benefit? In my case the clone of master fails with an OVF/OVA error and nothing happens.. (I created a pvs-like empty template VM with just a cache disk for Machine Profile)

@Yuhua Lu Is the best person for these kind of questions.

> I reached out to my Citrix rep as well as he's the one that told me, from his SE, that Image Management was included in CU2. Image Management still says Tech Preview in the docs and not listed in the "What's New" section. Yes, it is TP on 2402 LTSR, a bit unusual because typically we don't do TP on LTSR. The feature has very large code change touching many places in MCS but it is also a very useful feature (we believe) for customer, so we took TP approach. Goal is to go GA in one of CU if there is no critical issue uncovered. @Fenfen Hu is PM owner for this feature, she can help with our planning of GA in 2402 LTSR. Looks like it is officially GA'ed in CU2

@Yuhua Lu Thanks for this very quick reply. In my case I got some major painpoints: 1. The creation of a new Version mandatory needs a snapshot of a VM. It does not work with a VM directly 2. This snapshot is not created by Studio, so compared to the "old" MCS rollout the customer has to create a snapshot manually on the VM before capturing the image 3. The captured version is still 100% related to the VMs snapshot. So if someone merges or deletes the snapshot on the BaseVM or even deletes the BaseVM completely all Image Versions based on these snapshot cannot be rollout anymore despite the Base Image is relying on the storage. This feature sounds so good and I got a lot of customers to rollout. Was really happy when it got "GA" and i could plan a rollout, but whith the points above it makes nearly no sense (on VMware) to use... Many customers deploy their master everytime from scratch (rollout and delete afterwards), so this incl. versioning would be really a game changer.. without the snapshot dependency

Hello all, Image Management feature is GAed in 2402CU2. It provides basic function, image versioning and quick image rollout and rollback. More advanced features, like share prepared image within or across data center will be released in following LTSR.

Hi Marco, thank you for the feedback, below is my comments

1. The creation of a new Version mandatory needs a snapshot of a VM. It does not work with a VM directly

This is intentional, actually I made that request, I will take blame 🙂 Our PoSH New-ProvScheme or Publish-ProvMasterVMImage only takes snapshot/template as image input, however Studio take VM as input and will create snapshot, then supply the snapshot as input for backend PoSH to create or update catalog(ProvScheme). In the backend, MCS has no mechanism to manage lifecycle of the snapshot as it is considered admin supplied object and to be managed by admin. In my opinion, creator has the responsibility to manage resource lifecycle. This Studio workflow is a bug to me, because we create an object and we don't manage its lifecycle. We can have enhancement to make it convenient so that admin can just point at VM, studio then take a snapshot, finish creation/update, then delete the snapshot. I think it is useful specially for quick test, POC but in production, I expect admin want to have read-only content so things can be tracked, audited, rolled back, etc

@Yuhua Lu Thanks for clarifing this. Snapshot-requirement is not a problem, this can be done by script or other ways. Regarding Snapshot linked to base VM: You say it is fixed in main branch. Do you mean CR? If yes, in what version? I cant find any info in release notes of 2407 or 2411

Not in onprem LTSR or CR release, it is in Cloud release.

Getting familar with it, when the snapshot dependency is no more it´ll be a nice feature.

I am trying to find out which on-prem CR version the fix is available. There seems to be a feature toggle related to fix and it is not enabled for on-prem release yet.

@Fenfen Hu ping

Any plans for this to support xenserver?

Snapshot dependency is gone in 2503. Now this feature is getting cool 😎