Please provide your feedback in this short Flings' survey.
Jul 18, 2020

Just upgraded to 4.1 from 2.18.
Trying to run the Migration Utility and getting :
AppVolumes Manager is invalid
Tried varies ways of putting the URL in but nothing is working.
Anyone else had this issue ?

Jul 20, 2020

Having same issue with App Volumes Manager 4.1.0. Unable to get past "AppVolumes Manager is invalid"

Jul 22, 2020

Hello,

Please confirm if you are connecting to 4.x or 2.x AVM. Also confirm if the certificate in the AVM is imported to the VM where the tool is installed. Please refer the video/instructions for more details.

Thanks,
-Mani.

Jul 21, 2020

The issue is that you cannot run the tool against a version 4 server. You have to run it against the old 2.18 Server.
So what I did was I created a Post update snapshot, then I reverted back to the my Pre update snapshot (2.18 version), then ran the tool and pulled off all the apps. Then I reverted to the Post Upgrade snapshot (4.1) and imported them.

Aug 16, 2020

If you can not use the utility against a manager that is running v4. The requirements are miss leading as it implies that it does.

Administrative access to VMware App Volumes 2.18 or 4.0

I understand that you meed admin access to upload the appstacks to the datastore. There just isn't anywhere that I can find that explicitly states that it does not work on v4 managers for migrating, which would have been helpful knowledge while planning our migration.

Aug 19, 2020

Hello,

The tool should work with both 2.x or 4.x. If its not working, kindly share the logs. C:\ProgramData\VMware\AppCapture\AppCaptureGUI\AppCapture Client.log and C:\ProgramData\VMware\AppCapture\logs\*

Thanks,
-Mani.

Aug 26, 2020

Hello,

One bug related to connecting to AVM 4.1 is fixed in the latest update of the fling, (v1.0.4). Please give it a try and update if there are any issues still.

Thanks,
-Mani.

Jul 22, 2020

It is unfortunate you can't leverage this fling against an already upgraded App Volumes manager (4.1.0 in my case). Will this be changing in a near future update? Yes, I've imported the certs into the Computer Trusted Root Certificates store, but still get invalid message.

Unfortunately for me, I don't have the ability to snap back and snap forward on a production system. I suppose I could stand up a new 2.18.4 App Volumes manager and copy the AppStacks into it in order to complete the AppStack conversion to Packages. Might be worth the effort for my 90+ AppStacks.

Aug 07, 2020

Hello,

Apologies for late response. Seem to have missed this. Latest update of this fling provide logging for the UI. Please give it a try and share the log file available at C:\ProgramData\VMware\AppCapture\AppCaptureGUI\AppCapture Client.log. We will try to get this sorted out with AVM 4.x.

Thanks,
-Mani.

Jul 22, 2020

Thanks for the update, glad that you were able to migrate the apps. Comment here or open bug incase if you faced many issues during migration.

Thanks,
-Mani.

Jun 30, 2020

Hi good morning,

I have a App Volumes Manager 2.18.4 in place and I want to migrate all my AppStacks to a newly deployed App Volumes Manager 4.0.1.

I have installed the utility in my Apps Volume Manger 2.x and when connecting to it, shows all my AppStacks as incompatible. I have captured the AppStacks with 2.12.0.32U agent for Windows7 machines and 2.14.2.4U for Win10 ones.

What could be the issue?

Thank you.

Jul 19, 2020

Don't worry. figured it out. Actually have to run this against a 2.18 Appv Manager

Jul 22, 2020

Thanks for the update!

-Mani.

Jun 30, 2020

Hello,

Good Morning! Thanks for using the tool.

The tool shouldn't be installed on the App Volumes Manager, rather it should be installed on a standalone VM which has access to the datastore hosting the app stacks submitted for migration. The tool will connect to the AVM using the credentials entered in the tool to migrate the appstacks.

Also regarding the incompatible issue, the tool should be installed/used on a VM whose OS is same as the one in which it was provisioned. Ie if you have provisioned the appstacks on a Win 10 VM, you can use any Win 10 VM to install this tool and migrate those appstacks. Same for other OSes.

Please try as per the recommendation, you can also check the instructions/video tab for more details on how the tool should be installed/used.

Thanks,
-Mani.

Jul 01, 2020

Hi Mani,

We have installed the tool in a W7 and W10 machines and we were able to import 6/9 Appstacks. There are three saying Error after clicking Migrate.

Where can I find the logs to review the issue?

Thank you.

Jul 01, 2020

Hello,

Logs will be under C:\ProgramData\VMware\AppCapture\logs [AppCapture.log & AppMigrate.log]

Thanks,
-Mani.

Jul 02, 2020

Hi Mani good morning,

I have tried a new migration to see the error in the log files and I see the following:

AppMigrate.log
8:51:35 INFO: Not proceeding to calculate size as requested.
8:51:35 INFO : migrating file system: 00 %
8:53:33 INFO : migrating registry
8:53:33 INFO : migrating metadata
8:53:34 INFO : creating meta database..
8:53:34 ERROR: unable to open registry key MACHINE\WEM_MIGRATE\MACHINE\SOFTWARE\Classes\.swk\5872. Error: 0x2
8:53:34 ERROR: unable to unload registry hive. Error: 0x5
8:53:34 ERROR: failed to create database (registry).
8:53:34 INFO : creating meta database..failed

AppCapture.log
8:51:34 INFO : preparing output virtual disk for capture
8:51:34 INFO : attaching the migration disk
8:51:34 INFO : waiting for disk attachment
8:51:34 INFO : disk attachment complete in 0 secs
8:53:34 INFO : unable to migrate
8:53:34 ERROR: failed to migrate data[Error: 0x362aabde]
8:53:34 ERROR: program failed in install mode CmdNew (Error: 0x0)

What can we try to migrate at leaste this AppStack? The other two are not important.

Thank you again.

Jul 05, 2020

We have posted a new update to this fling V1.0.2.
Please check if this resolves the issue.

Thanks
Rizwan

Jul 06, 2020

Hi Rizwan,

With the new release I've been able to migrate the last AppStack. Thank you so much for your help!

Jul 02, 2020

Hello,

Thanks for the logs. Will check and update.

Thanks,
-Mani,

Jul 06, 2020

Hi Mani,

There's no need anymore to check them as your colleague Rizwan gave me the option to use the new release and I have already migrated the last AppStack. Thank you for your help!

Jul 06, 2020

Hello,

That comment was added on July 02. Somehow it appears last. Good to know that you were able to migrate the appstack. I will go ahead and close this bug, if you dont have any more issues.

Thanks,
-Mani.

Jun 08, 2020

1. I am getting quite a few apps that after running the migration, copying the files to the packages directory in AppVol4 and selecting them under the StorageTab - I get the following error:

Unable to upload file "C:/Program Files (x86)/CloudVolumes/Manager/ppv/packages/Name_of_AppVol.vmdk" because it does not exist.

It's weird because other App migrations work just fine.

2. As well there are a few AppVols that won't even migrate out of AppVol2x and I only get an "Error". Here are the logs:

AppMigrate LOG

9:16:06 Computer: WIN10IC1903 (WIN10IC1903.moncton.loc)
9:16:06 Date-Time: June 8, 2020 9:16:06
9:16:06 Commandline: C:\Program Files (x86)\VMware\AppCapture\AppCapture.exe
9:16:06 Arguments: /migrate "Fleet 16.0.1 V2" /sourcepath "C:\Program Files (x86)\VMware\AppCapture\VolumeMount\Fleet 16.0.1 V2_appstacks" /o \\nasch\apps$\VMWareVDI-IMAGES\zzTEMP-AppStacks
9:16:06 INFO: Not proceeding to calculate size as requested.
9:16:07 INFO : migrating file system: 00 %
9:16:10 INFO : migrating registry
9:16:10 INFO : migrating metadata
9:16:10 INFO : creating meta database..
9:16:10 ERROR: failed to get old appID from YML entries
9:16:10 ERROR: failed to replace YML App ID
9:16:10 ERROR: unable to update app GUID in app YML

AppCapture LOG

Application Capture Command Line Program
Version 4.0.0.6
Copyright (c) VMware, Inc. All rights reserved.
9:16:04 Computer: WIN10IC1903 (WIN10IC1903.moncton.loc)
9:16:04 Date-Time: June 8, 2020 9:16:04
9:16:04 Commandline: C:\Program Files (x86)\VMware\AppCapture\AppCapture.exe
9:16:04 Arguments: /migrate "Fleet 16.0.1 V2" /sourcepath "C:\Program Files (x86)\VMware\AppCapture\VolumeMount\Fleet 16.0.1 V2_appstacks" /o \\nasch\apps$\VMWareVDI-IMAGES\zzTEMP-AppStacks
9:16:04 INFO : processing commandline options
9:16:04 INFO : application name: Fleet 16.0.1 V2
9:16:04 INFO : migration(source) path: C:\Program Files (x86)\VMware\AppCapture\VolumeMount\Fleet 16.0.1 V2_appstacks
9:16:04 INFO : output vhd folder: \\nasch\apps$\VMWareVDI-IMAGES\zzTEMP-AppStacks
9:16:04 INFO : source vhd: C:\Program Files (x86)\VMware\AppCapture\templates\wemcapture.vhd
9:16:04 INFO : source disk file attributes: 0x00000020
9:16:04 INFO : output vhd folder attributes: 0x00000010
9:16:04 INFO : output vhd file: \\nasch\apps$\VMWareVDI-IMAGES\zzTEMP-AppStacks\Fleet 16.0.1 V2.vhd
9:16:04 INFO : copying C:\Program Files (x86)\VMware\AppCapture\templates\wemcapture.vhd to \\nasch\apps$\VMWareVDI-IMAGES\zzTEMP-AppStacks\Fleet 16.0.1 V2.vhd
9:16:05 INFO : Going to add Full Access for Authenticated users [icacls.exe "\\nasch\apps$\VMWareVDI-IMAGES\zzTEMP-AppStacks\Fleet 16.0.1 V2.vhd" /grant *S-1-5-11:(F)].
9:16:05 INFO : preparing output virtual disk for capture
9:16:05 INFO : attaching the migration disk
9:16:05 INFO : waiting for disk attachment
9:16:05 INFO : disk attachment complete in 0 secs
9:16:10 INFO : unable to migrate
9:16:10 ERROR: failed to migrate data[Error: 0xf2ec0b57]
9:16:10 ERROR: program failed in install mode CmdNew (Error: 0x0)

Jun 08, 2020

Hello,

Will check and get back regarding the first issue you mentioned, regarding the second one, can you confirm if the latest version of the tool is used for migration(1.0.1, a similar bug was fixed in that version?

Thanks,
-Mani.

May 29, 2020

Quick question - does the migration remove or alter the 2.x appstacks at all? I would like to do a test on a handful of AppStacks, but want to verify they won't be altered first.

Thanks!

May 29, 2020

Hello Josh,

The tool doesn't remove or alter the 2.x appstacks. During the migration process, 2.x appstacks are mounted in read-only mode to read data.

Thanks,
-Mani.