You receive a "1402" error when you use RemoteApps to deploy Windows Installer packages to thin clients from a server that is running Windows Server 2008

Article translations Article translations
Article ID: 959757 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

You try to use RemoteApps from a share on a Terminal Services server that is running Windows Server 2008 to deploy remote applications to thin clients. You use Windows Installer packages (.msi) to perform this installation. Then, you receive the following error message:
Error 1402. Could not open key:
HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\RemoteApplications\\\UNC_Path\AppName.rdp.
Verify that you have sufficient access to that key or contact
In this error message, the UNC_Path placeholder represents the path of the location where the RDP files are located and the AppName placeholder represents the name of the application's Remote Desktop Protocol (.rdp) file.

Note This issue does not occur if you create the Windows Installer packages in the following scenario:
  • You create the Windows Installer packages on the same Terminal Services server from which the MSI packages will be shared.
  • You do not use a UNC path for these packages.
  • You then copy the Windows Installer packages to the client computers.

CAUSE

This issue occurs when the following conditions are true:
  • The following registry key already exists on the thin clients:
    HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\RemoteApplications
  • Remote applications are already installed on the thin clients.
  • The Windows Installer packages for the remote applications are created on a different server.
When these conditions occur, the Registry tables within the MSI packages contain three registry subkeys that begin with the following registry path:
HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\RemoteApplications\UNC_Path
In this example, the UNC_Path placeholder represents the path of the folder in which the Windows Installer package file was created. If this folder is located on a network share, the registry subkey has backslash characters (\\) in front of the folder name and the path. The backslash characters make the registry subkey invalid, and this generates the "1402" error when you try to deploy applications by using these Windows Installer packages.

RESOLUTION

To resolve this issue, you must remove the whole UNC path of the folder in which the Windows Installer packages are created from the registry subkey when you create the Windows Installer packages. This results in the following registry subkey:
HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\RemoteApplications
For more information about how to create Windows Installer packages for deployment, visit the following TechNet Web site:
TS RemoteApp Step by Step Guide: Create a Windows Installer package from a RemoteApp program

Properties

Article ID: 959757 - Last Review: October 21, 2009 - Revision: 1.0
APPLIES TO
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Standard
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Standard
  • Windows Server 2008 for Itanium-Based Systems
Keywords: 
kbremoteprog kbdeployment kbexpertiseinter kbtshoot kbsurveynew kbprb KB959757

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com