You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 4, 2024. It is now read-only.
When doing an advanced installation, the data directory defaults to %APPDATA%\FAHclient which makes sense for the standard install, but if you intend to run the client as a service, a more appropriate location would be %ALLUSERSPROFILE%\FAHclient so that the client isn't tied to a folder in a user profile that may get removed or reset. As part of that, the following changes would be helpful.
For the advanced install option, move the choice to run as a service before the option to set the data directory.
If the user has selected to install the client as a service, set the default data directory to %ALLUSERSPROFILE%\FAHclient. Otherwise use %APPDATA%\FAHclient.
Add a command line option that can be used during a silent install to specify installation as a service and populate the DataDirectory registry value to the default location (%ALLUSERSPROFILE%\FAHclient).
These changes would improve the experience for organizations which are interested in mass deployments as a service, especially across pools of machines that don't have GPUs.
The text was updated successfully, but these errors were encountered:
When doing an advanced installation, the data directory defaults to
%APPDATA%\FAHclient
which makes sense for the standard install, but if you intend to run the client as a service, a more appropriate location would be%ALLUSERSPROFILE%\FAHclient
so that the client isn't tied to a folder in a user profile that may get removed or reset. As part of that, the following changes would be helpful.%ALLUSERSPROFILE%\FAHclient
. Otherwise use%APPDATA%\FAHclient
.%ALLUSERSPROFILE%\FAHclient
).These changes would improve the experience for organizations which are interested in mass deployments as a service, especially across pools of machines that don't have GPUs.
The text was updated successfully, but these errors were encountered: