A customized Windows installed is available on request. This is usually necessary when an installation at machine level is required, instead of per user account on the machine.
The main differences between the custom installer and the default installer are as follows:
- This installer accepts an installation path when running the .exe
- Automatic app updates are disabled
- A shortcut is created on the public desktop of the machine, which will place a shortcut on all user desktops
The installer will need to be run with a single argument defining the installation path, and the default installation location is the main drive of the machine.
- Custom install
Folder> .\App.exe -customInstall -installDir “Path” - Custom install with custom user data directory
Folder> .\App.exe -customInstall -installDir “Path” -userDataDir “Path”
Using command line with the 'InstallDir' argument will look something like this:
| c:\Users\test\Downloads> start AppInstaller.exe -installDir "C:\ProgramDate" |
Note: The installer will need to be run as admin, or it may fail with a setup error message.
To update existing installations, simply download the latest installer and run it again, making sure to point it to the same installation directory where the app is currently installed by using the 'InstallDir' argument.
Please contact Support if this installer option is needed.
Remote Desktop (RDP Environment)
Suppose your organization uses a shared RDP server for Windows apps, each user needs to run an independent instance of the app, and you will need to install the Windows app separately in each user’s AppData folder.
Custom install
Folder> .\App.exe -customInstall -installDir “Path”
Failure to install separate instances of the app will cause issues the moment more than one user tries to work in the app simultaneously. If an instance of the app is already running on the server, users will either be prevented from logging into the app or logged out.
Virtual Desktop (VM Environment)
Suppose your organization uses a VM/Citrix environment. In that case, the app can be installed on a master VM. However, the userDataDir parameter is expected to point to a dedicated folder on a network drive, allowing users to access their user data regardless of the assigned VM.
Custom install with custom user data directory
Folder> .\App.exe -customInstall -installDir “Path” -userDataDir “Path”
Example of a dedicated folder on a network drive:
\\Fileserver\OrgnizationAppUserData
/48901/ (user-level folder created by the app)
/56310/ (user-level folder created by the app)
/77551/ (user-level folder created by the app)
etc...