Installation fails when Remote Desktop is used

You can use Terminal Services Remote Desktop to run the WebSphere® Business Monitor Launchpad on a Windows® operating system to install WebSphere Application Server, WebSphere Process Server, or WebSphere Portal. If the Launchpad shows, upon completion of the installation, that the installation failed and WebSphere Business Monitor is not installed, check that Windows has placed the vpd.properties file in the correct location.

The vpd.properties file is the location where InstallShield registers installed software. On the Windows system, this file is usually placed in the %WINDIR% directory, which is either C:\WINDOWS or C:\WINNT.

In certain cases, the vpd.properties file is placed in %USERPROFILE%\WINDOWS. %USERPROFILE% is usually on C:\Documents and Settings\<User_Name>. If the vpd.properties file in %WINDIR% was not created or updated during installation, the Launchpad cannot locate the installed products.

To fix this problem, shut down Launchpad, locate the vpd.properties file that was created, and either copy it into %WINDIR% or append it to the vpd.properties file already there. If you know that Terminal Services will be running on the installation machine, run the command change user /install from a Windows command prompt before you run the Launchpad. This action will prevent the Windows system from redirecting vpd.properties to the %USERPROFILE% directory.


Copyright IBM Corporation 2005. All Rights Reserved.