Please provide your feedback in this short Flings' survey.
Oct 07, 2020

I was able to convert the appstacks, copied them to each \\AVserver\c$\Program Files (x86)\CloudVolumes\Manager\ppv\packages_templates\

Then I went to Configuration tab, Storage, Upload Templates and select all the appstacks. It says upload completed but nothing showed up in Application tab. I tried uploading twice already.

Oct 08, 2020

Hello,

Thanks for using the tool. Can you copy them to packages folder instead of packages_templates and upload? (Create the folder if it doesnt exist) Let me know if it doesnt work.

Thanks,
-Mani.

Sep 22, 2020

I have migrated all of my packages to the packages_templates folder and they are showing correctly in v4 as well as attaching properly to VMs. However I am unable to update a package. Manager shows that it is attached to the packaging machine and is packaging, but the prompt never shows on the packaging machine to create the package.

Sep 23, 2020

Hello,

Thanks for trying the tool. Please confirm if you are seeing this behavior for a specific package or for all of your packages?

Thanks,
-Mani.

Sep 25, 2020

Hello,
Updating migrated package works fine without any reboots during the update process in my environment. Can you share svservice.log and svcapture.log for more investigations?

Thanks,
-Mani.

Sep 25, 2020

Apologies, this appears to be an issue with the App Volumes agent and not with the migrated app stacks. Updating works fine on an older agent.

Sep 25, 2020

Thanks for the update! You can comment here for any issues.

-Mani.

Sep 16, 2020

I have a question about the converted packages. I was able to migrate all of my packages and they show up correctly in v4. Now the problem is that I can't update any of these packages. If I attach the package to the Packaging machine and do some updates as soon as not reboot the machine everything is fine. If I reboot all applications are gone from add/remove program. All shortcuts of the applications on a desktop and start menu are there. If I finish the packaging in Manager I see the new package with 0 programs and 0 operations system. Size of the package seems to be the same as the original package. BTW all of the migrate packages are listed as Template Unknown.
Why this is happening on the migrated packages?
I tested of creating and updating the new package and everything is working fine. Please let me know how can I fix that issue?
Thanks in advance.

Sep 17, 2020

Hello,

Thanks for using the tool. Got a question - did you reboot the machine as part of the application update or is it the normal reboot required for provisioning? It will help us understand the problem better.

Thanks,
-Mani,

Sep 17, 2020

Hi,
The Packaging machine is reverted to a clean snap before the packaging process. It happens to any reboot after the attachment of the package (if is part of application update or normal reboot). If I don't reboot and finish the packaging process it seems to be fine, but I usually reboot to avoid any problems on the package.
Thanks

Sep 18, 2020

Did you guys able to reproduce the issue in your environment? I can show you what is going on if you need a prove.

Sep 23, 2020

Hello,

One of my colleagues has fixed a similar bug, I will discuss on this and update.

Thanks,
-Mani.

Sep 30, 2020

Hi Mani,
Like you mention in Britt_H the update works as far as you don't reboot, but some of the applications are required reboot. At that point everything is gone. Usually I'm rebooting the machine before finishing the capture just to avoid any configuration issues. Did you able to find any solution?

Oct 05, 2020

Hello,

We are working on a fix to resolve this issue and provide additional instructions as necessary. We will provide an update when we have more information.

Thanks,
-Mani.

Oct 22, 2020

Hi Mani,
Is the version 1.0.5 fixed that problem with updating the converted packages?
Thanks

Jul 21, 2020

Hi, I am unable to migrate my AppStacks from v2.18 to v4.

I can log into the migration utility, I can see all the AppStacks. Once I try any AppStack, it immediately errors.

The log file shows something similar to this for each AppStack tried:

2020-07-21 13:58:29,635 [4] DEBUG AppCaptureUI.Common.HttpRequest: HTTP POST -> https://vsfvappvols.vsfcd.com/cv_api/appstacks/373/mount
2020-07-21 13:58:29,920 [4] ERROR AppCaptureUI.Common.HttpRequest: GetResponse Fails
System.Net.WebException: The remote server returned an error: (400) Bad Request.
at System.Net.HttpWebRequest.GetResponse()
at AppCaptureUI.Common.HttpRequest.GetResponse()
2020-07-21 13:58:29,920 [4] ERROR AppCaptureUI.Avm.AvmCommunicator: SendRequest(eVolumeMount-eAppStack-373-id=373&uuid=4C4C4544-0058-3410-8031-C8C04F445632&ip=192.168.100.249) failed.
2020-07-21 13:58:29,920 [4] ERROR AppCaptureUI.Avm.AvmController: AvmCommunicator::MountVolume([eAppStack]-[373]) failed.
2020-07-21 13:58:29,920 [4] ERROR AppCaptureUI.Avm.AvmController: AvmController::MountVolume([eAppStack][373][VSSPRO]) faield.

Any ideas?

Thanks!

Jul 22, 2020

Hello,

Thanks for using the tool. It looks like mounting of VMDK is failing. Did you see any errors in the vSphere web/client console related to this?

Also please confirm if the VM where the tool is installed has access to the datastore holding the appstacks you are trying to migrate?

Thanks,
-Mani.

Jul 22, 2020

Well, first problem was I was trying to run it on my physical IT administrating machine. HAHA!

When I installed the utility on a virtual machine in the cluster and ran it, it worked for 10 of my 11 AppStacks. One of them, a very basic ancient Windows application, does not migrate correctly.

I'll try recreating it in App Volumes 4.

Jul 22, 2020

Hello,

Thanks for the update. If you could share the logs for the migration of that appstack which failed, I can try to help to fix it.

Logs : Under C:\ProgramData\VMware\AppCapture\logs [AppCapture.log & AppMigrate.log]

Thanks,
-Mani.

Jul 22, 2020

Hi, I'll do that shortly. In the meantime, I made a mistake and imported the packages as templates instead of packages. How can I delete them? :(

Aug 07, 2020

Hello,

Apologies for the late response. Seem to have missed this. I will check with the team and get back.

Thanks,
-Mani.