This tool proposed in this fling addresses this migration so that customers don't have to provision applications again after upgrading to 4.0 and also get improved performance.
this tool only for AppStacks ? there is any tool for Writable Volume ?
This tool is applicable only for appstacks. As of now, writable volumes are not supported by this tool.
I made a few comments below but didn't hear anything back.
Is this Fling still being maintained?
Apologies for the delayed. Hope my answers help you. Also don't forget to check VHD check box in UI.
Could I get some clarification on a few things please?
1. What do you mean by "This should be installed on a VM having access to the datastore having the appstacks to be migrated"? The VM I am using resides on the VDI cluster which is backed by VSAN.
2. What versions of App Volumes Manager do you support for the source? 4 / 4.1 / 4.2
I'm here because I want to migrate my on-prem App Stacks from App Volumes 2006 / 2009 (VMDK format) into Horizon Cloud Service on Azure which requires JSON and VHD?
1. What it means is that say you have an appstack Office.vmdk in a datastore [Storage] and installed this tool in a VM, say, MigrationVM. This MIgrationVM will attempt to add the office.vmdk to itself to migrate. So the ESX hosting this MigrationVM should have access to datastore [Storage]. HTH.
2. Both 2.18 and 4.x are supported as source.
Thanks for getting back to me.
I have the same issue in 2 different environments, no AppStacks are displayed after logging in!
Environment 1: Win10 2004, vSphere 6.7, NFS, Horizon 7.12, AVM 2009 using signed cert.
Environment 2: Win10 2004, vSphere 7.0, VSAN, Horizon 7.12, AVM 2006 using self signed cert.
In both environment the AppStacks are loading perfectly when I connect via a Pool.
Would it be possible to get some assistance please?
Please let me know how you'd like to proceed.
Can you run the tool once in both working/non-working scenario and send this log file?
It doesn't work in either environment.
How do I get the log file to you please?
As of now, the only way seems to be pasting the logs here. I am checking internally if there is any other way to share logs.
The tool can list only 2.x appstacks, in case you are connecting to 4.x AVM and it doesn't have any 2.x appstacks, there is a possibility that you might not see any appstacks listed. Just sharing since it could be a case here.
Thanks for sharing that.
The AVM where the AppStacks reside is 4.2 and as this is a greenfield deployment the AppStacks are all in the latest format. At least that explains why I can't see them!
I am attempting to use the Fling to migrate a VMDK based ApStack into VHD and JSON format so that I can use them in Horizon Cloud Service on Azure.
If this is not the tool for the job are you able to recommend another way to get the VMDK based AppStacks into VHD and JSON format please?
I think customers that have Horizon on-prem and Horizon Cloud Service on Azure will need a utility like this, otherwise they will have to package apps twice.
I had been considering configuring the Machine Manager to use "VHD / In-Guest-Services" mode, but this would only work for greenfield.
Is this the recommended way to migrate my on-prem App Stacks from App Volumes 2006 (VMDK format) into Horizon Cloud Service on Azure which requires JSON and VHD?
Yes this is the recommended way.