Has anyone created an app volume for this?
It appears to provision correctly.
I'm having a great amount of difficulty, keeps running an installer when launched from a session.
Windows 10 1809
App Vol 2.18
Thanks!
VMware support supplied the fix:
HKLM\System\ControlSet001\Services\svdriver\parameters
Name: CleanupWritable
Type: REG_DWORD
Value: 0
We are using SAGE as well however it is added to the Master Image of that department.
In the past when application would be running configuration each time I found that sometimes shortcut is corrupt. Can you try to launch it directly from the installation folder? If so then just replace shortcut
pbastiaans
We have successfully packaged Sage Fixed Assets for several years now (2018, 2019, 2019.1 and 2020 and now 2020.1). We run the Premier Depreciation piece of FAS. It's been a long time so I cannot remember if we ran into the same issue you have, but several things we have done special for this application to run correctly in our environment.
During AppVolumes Packaging:
DEM Settings:
# Flex config file generated with VMware User Environment Manager Application Profiler version 9.2
[IncludeRegistryTrees]
HKCU\Software\Sage Small Business Division Desktop
[IncludeIndividualRegistryValues]
HKCU\SOFTWARE\ODBC\ODBC.INI\BESTSYS32\AnsiNPW
HKCU\SOFTWARE\ODBC\ODBC.INI\BESTSYS32\Database
HKCU\SOFTWARE\ODBC\ODBC.INI\BESTSYS32\Description
HKCU\SOFTWARE\ODBC\ODBC.INI\BESTSYS32\Driver
HKCU\SOFTWARE\ODBC\ODBC.INI\BESTSYS32\LastUser
HKCU\SOFTWARE\ODBC\ODBC.INI\BESTSYS32\Server
HKCU\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources\BESTSYS32
HKCU\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources\WINFAS32
HKCU\SOFTWARE\ODBC\ODBC.INI\WINFAS32\AnsiNPW
HKCU\SOFTWARE\ODBC\ODBC.INI\WINFAS32\Database
HKCU\SOFTWARE\ODBC\ODBC.INI\WINFAS32\Description
HKCU\SOFTWARE\ODBC\ODBC.INI\WINFAS32\Driver
HKCU\SOFTWARE\ODBC\ODBC.INI\WINFAS32\LastUser
HKCU\SOFTWARE\ODBC\ODBC.INI\WINFAS32\Server
Thank you - That's a 'when all else fails' option for us.
Thank you very much!
Can you comment on:
"We overwrite a license file after the install. (This is is directly from Sage Support, this allows non-persistent desktops to function correctly using their licensing scheme). As their licensing used to be tied each user to a computer name."
Screenshot from the email we get from Sage support. This was a fix they provided several years ago that allowed us to have non-persistent VDI users with our licensing scheme.
Thank you. We use the single user install, no server to grab that DLL from.
VMware support supplied the fix:
HKLM\System\ControlSet001\Services\svdriver\parameters
Name: CleanupWritable
Type: REG_DWORD
Value: 0