I've come up with a workaround:
Before installing App Volumes, install SQL Server Express and specify Windows Authentication mode. Add the local [SYSTEM] account as a SQL Server administrator.
Now install App Volumes and choose the option to connect to an existing SQL Server Database.
Would anyone from VMware care to comment on why I needed this workaround for something that worked in AppVols 2.13? I'm just asking because I haven't had any reply yet to my original post so I'm wondering if VMware monitors this forum or is it left purely to the community.
Sometimes vmware employees do comment on here but it is still community driven.
By the way, we had the same issue when creating a new database on a centralized SQL server. It seems as if during installation it tries to creae the database before it sets the correct permissions. What we did back then was just uninstall and install again, correct permissions were set then and it could create the database.
Now we just add the machine account to the database with the correct permissions..
2 people found this helpful
we just had the same issue : a workaround is to copy the install files locally on a local drive instead of launching on the CD iso image
Same issue. Not sure how to make the "local [SYSTEM] account a SQL Server administrator." though... couldn't find the ID to assign.
Issue is as well.. that VMware's 3rd lvl support takes about 3 days to get back to you.. so every issue we have getting win 10 rev 1809 working will take 3 days each issue .. or at least that's been the norm.
i installed sql 1st then app manager.
Still not working .. its now looking for App Volumes Manager. URL ?? it just placed the shortcut but cant find it ?..huh ?