Select the product you need help with
After you sign an .rdp file by using the Rdpsign.exe utility, signed .rdp file permissions are changed, or a signed .rdp file does not provide the name and password information in Windows Server 2008Article ID: 962947 - View products that this article applies to. On This PageSYMPTOMSAfter you sign a Remote
Desktop Protocol (RDP) file
by using the Rdpsign.exe utility on a Windows Server 2008-based system, you
experience one of the following issues. Issue 1
Issue 2 An .rdp file contains a terminal server name, a user name, and password information. Additionally, the .rdp file works correctly before it is signed. However, when you double-click the signed .rdp file, the server name, user name, and password fields are blank. CAUSEIssue 1 This problem occurs because a temporary file is created in the current user's profile and then moved to the destination folder. If the profile and the destination folder reside on the same volume, the permission settings are not inherited correctly. Issue 2 This problem occurs if the 2-byte Unicode header is missing from the signed .rdp file. This causes the Mstsc.exe utility to incorrectly interpret the file as ASCII. Therefore, the utility cannot read the connection data. RESOLUTIONHotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support Note The "Hotfix download available" form displays the languages for
which the hotfix is available. If you do not see your language, it is because a
hotfix is not available for that language.
(http://support.microsoft.com/contactus/?ws=support)
Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page. PrerequisitesTo apply this hotfix, you must have Windows Server 2008 installed.Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace a previously released hotfix.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows Vista and Windows Server 2008 file information notesThe .manifest files and the .mum files that are installed in each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.For all supported x86-based versions of Windows Server 2008Collapse this table
For all supported x64-based versions of Windows Server 2008Collapse this table
For all supported IA-64-based versions of Windows Server 2008Collapse this table
WORKAROUNDTo work around Issue 1, use one of the following methods:
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. REFERENCESFor more information about the Rdpsign.exe utility, visit
the following Microsoft Web site: http://technet.microsoft.com/en-us/library/cc753982.aspx
(http://technet.microsoft.com/en-us/library/cc753982.aspx)
MORE INFORMATIONAdditional file information for Windows Server 2008Additional files for all supported x86-based versions of Windows Server 2008Collapse this table
Additional files for all supported IA-64-based versions of Windows Server 2008Collapse this table
Additional files for all supported x64-based versions of Windows Server 2008Collapse this table
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updatesPropertiesArticle ID: 962947 - Last Review: October 7, 2011 - Revision: 2.0 APPLIES TO
|
Back to the top
