Article ID: 959757 - View products that this article applies to.
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:
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.
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
Note This issue does not occur if you create the Windows Installer packages in the following scenario:
This issue occurs when the following conditions are true:
HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\RemoteApplications\UNC_PathIn 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.
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:
For more information about how to create Windows Installer packages for deployment, visit the following TechNet Web site:
HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\RemoteApplications
TS RemoteApp Step by Step Guide: Create a Windows Installer package from a RemoteApp program
Article ID: 959757 - Last Review: October 21, 2009 - Revision: 1.0
Contact us for more help
Connect with Answer Desk for expert help.