Personal installations

If the end-users' company cannot support Administrator instances, then each end user must install their own personal instance. When the WebClient installer determines that an end user cannot perform an Administrator install, the installer automatically switches to performing a personal install.

The following table lists the default values that the installer supplies during a personal installation. If the user enters a different value, the installer verifies that the user has write privileges for the new choice.

Table 6. Personal installation default values
Directory	Default
WebClient install	%USERPROFILE%\Application Data\Progress Software\WebClient
Program shortcuts	C:\Documents and Settings\<user>\Start Menu\Programs\PSC WebClient <release-number>
WebClient application install	%APPDATA%\WebClientApps Note: In some circumstances, the installer might choose a different default: %LOCALAPPDATA%\WebClientApps (Vista only, non-roaming data) %USERPROFILE%\Application Data\WebClientApps

The lack of Administrator write privileges imposes some limitations on WebClient applications deployed as personal instances. There are common types of files that require Administrator privileges to install, and if you intend to support personal instances of your WebClient application, your application cannot use these types of files. For more information, see the System Tasks and personal installations.

In this section:

InstallShield Setup Player add-on and personal installations