Ok, so a little background. vSphere 6, 7 hosts, 400 virtual desktops. I personally set up the cluster, and Horizon View. Running without any problems. Our licensing also includes AppVolumes, but we aren't using it in production yet. Started testing 2.10, got it up and running, worked great. Upgraded to 2.9, a few issues (had to delete\recreate all appstacks), but got it working. So now, I see 3.0 is out, i'm like YAY! I uninstall our 2.9 environment, so I can perform a clean install of 3.0.
Every. Single. Step. Is. A. Hurdle.
I've finally got the appliance installed (had to recreate 3 times just so I could create a NEW PASSWORD, token manipulation errors galore).
Added my vCenter instance (had to turn off SSL authentication via appliance console to finally work, and still not clear on what the prefixes are actually used for).
Added a file share (I previously had these on a dedicated datastore. Fine, I'll create a share on a Win server with full NTFS\share permissions).
I have a VDI pool with the agent installed, and updated my capture machine with the latest software. Create a simple appstack (Notepad++), the command line tool was so far the easiest and least problematic step of the whole process. Copy the JSON\VMDK files to the file share, perform a sync.. nothing.
Start looking at the documentation (which I'm following, jumping around because it's not in any sensible order) for logs so I can see why my applications aren't showing up. I open the log URL and... it's the old AppVolumes interface (from 2.1\2.9). What the hell?
Really, I just want to understand why my app isn't showing why I sync. And why is the old interface even still there?
VMWare, please put up some videos. More documentation. A hands-on lab for AppVolumes 3 would be fantastic.