Non-Administrator installation of DB2 Connect (Windows)

 

For a non-Administrator's installation, the account you are logged on as must belong to Power Users group.

Some information about DB2 Connect™ that must appear in the registry must be entered in the HKEY_CURRENT_USER folder in the registry. Although many items will be stored under the HKEY_LOCAL_MACHINE folder in the registry for non-Administrator installations of DB2 Connect, the environment settings must be changed in HKEY_CURRENT_USER.

A member of the Windows Administrators group must configure the Windows® elevated privileges settings to allow a non-Administrator user account to perform an installation. For example, on a 64-bit operating system manually grant full permission on HKLM\Software\Wow6432Node before DB2 Connect Personal Edition can be successfully installed.

Note: If a non-Administrator user account is going to do the product installation, then the VS2005 runtime library must be installed before attempting to install a DB2® product. The VS2005 runtime library is needed on the operating system before the DB2 product can be installed. The VS2005 runtime library is available from the Microsoft® runtime library download web site. There are two choices: choose vcredist_x86.exe for 32-bit systems or vcredist_x64.exe for 64-bit systems.

System shortcuts must be changed to user shortcuts for the non-Administrator install. Moreover, since services are required to install any of the DB2 Connect products, but cannot be created without administrative authority, services that would be automatically started are run as processes when a non-administrator installs.

The following are installation situations you might encounter in an environment where both administrator and non-administrator installations exist:

Parent topic: Installing a DB2 Connect server product (Windows)

Parent topic: Installing DB2 Connect Personal Edition (Windows)

Related tasks
Installing a DB2 Connect server product (Windows)