Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Error when you try to change the properties of a published RemoteApp in Windows Server 2012

Error when you try to change the properties of a published RemoteApp in Windows Server 2012

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You deploy Remote Desktop Service on a Windows Server 2012-based computer.
  • A Remote Desktop Connection Broker is installed in the environment. The computer is joined in a session-based collection.
  • You install an application on a non-system drive of the computer.
  • You publish this application as a RemoteApp.
  • You try to use Remote Desktop Management Server (RDMS) UI to change and save the properties of the RemoteApp.
In this scenario, the operation fails, and you receive the following message:
Cannot bind argument to parameter 'VirtualPath' because it is an empty string

↑ Back to the top

Cause

This issue occurs because the script that RDMS UI calls receives an empty parameter unexpectedly.

↑ Back to the top

Workaround

To work around this issue, use the Set-RDRemoteApp cmdlet to change the properties of the RemoteApp.

For more information about the Set-RDRemoteApp cmdlet, go to the following Microsoft website:
General information about the Set-RDRemoteApp cmdlet

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that 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 website:
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.

Notes
  • This update must be installed on the computer from which you use Server Manager to manage the session-based collection.
  • We recommend that you install this update on the remote desktop session hosts that have the application installed.

Prerequisites

To apply this hotfix, you must be running Windows Server 2012.

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2012 file information notes
Important Windows Server 2012 hotfixes are included in the Windows 8 packages.
  • The files that apply to a specific product, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.2.920 0.16 xxxWindows Server 2012RTMGDR
    6.2.920 0.20 xxxWindows Server 2012RTMLDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Tscpub.mofNot Applicable14,1662-Jun-1214:31Not Applicable
Tscpubwmi.dll6.2.9200.20783334,33626-Jul-134:44x64
Rdpsign.exe6.2.9200.1638468,60826-Jul-123:08x64
Tsallow.mofNot Applicable17,0672-Jun-1214:31Not Applicable
Tspubwmi.dll6.2.9200.20783204,80026-Jul-134:44x64
Certificate.psm1Not Applicable12,65917-Jun-1215:31Not Applicable
Common.psm1Not Applicable48,0662-Jun-1220:25Not Applicable
Customrdpproperty.psm1Not Applicable9,5352-Jun-1214:31Not Applicable
Deployment.psm1Not Applicable83,44823-Jun-1223:24Not Applicable
Deploymentproperties.psm1Not Applicable15,10517-Jun-1215:31Not Applicable
Livemigrate.psm1Not Applicable11,69117-Jun-1215:31Not Applicable
Rdmgmt.format.ps1xmlNot Applicable53,3112-Jun-1214:31Not Applicable
Remoteappicon.psm1Not Applicable2,9552-Jun-1214:31Not Applicable
Remoteapppublishing.psm1Not Applicable58,44525-Jul-1322:08Not Applicable
Remotedesktop.psd1Not Applicable14,2982-Jun-1214:31Not Applicable
Remotedesktoppublishing.psm1Not Applicable7,25417-Jun-1215:31Not Applicable
Remotesessionmanagement.psm1Not Applicable9,07517-Jun-1215:31Not Applicable
Sessioncollectionproperties.psm1Not Applicable21,44317-Jun-1215:31Not Applicable
Sessiondesktopcollection.psm1Not Applicable23,63017-Jun-1216:08Not Applicable
Startmenuapplications.psm1Not Applicable4,95817-Jun-1215:31Not Applicable
Utility.psm1Not Applicable36,0572-Jun-1220:25Not Applicable
Virtualdesktopcollection.psm1Not Applicable160,03217-Jun-1216:08Not Applicable
Virtualdesktopcollectionproperties.psm1Not Applicable39,85927-Jun-122:05Not Applicable
Workspacemgmt.psm1Not Applicable8,43917-Jun-1215:31Not Applicable
Microsoft.windows.servermanager.rdsplugin.dll6.2.9200.207832,793,47226-Jul-134:56x86
Rdmsinst.dll6.2.9200.1638420,99226-Jul-123:07x64
Rdmsres.dll6.0.0.02,04826-Jul-122:35x64
Remotedesktop.events.xmlNot Applicable3,0892-Jun-1220:25Not Applicable
Tspubiconhelper.dll6.2.9200.1638414,33626-Jul-123:07x64
Rdpsign.exe6.2.9200.1638460,41626-Jul-123:20x86
Tsallow.mofNot Applicable17,0672-Jun-1214:31Not Applicable
Tspubwmi.dll6.2.9200.20783168,96026-Jul-133:47x86

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012
File nameAmd64_0e595e6f647a5dbadc55741265ee4b8b_31bf3856ad364e35_6.2.9200.20783_none_e902351c50057d4f.manifest
File versionNot applicable
File size714
Date (UTC)26-Jul-2013
Time (UTC)14:16
PlatformNot applicable
File nameAmd64_430c33424318e52bb4d2e855c87f175b_31bf3856ad364e35_6.2.9200.20783_none_a1367f35202a2dda.manifest
File versionNot applicable
File size729
Date (UTC)26-Jul-2013
Time (UTC)14:16
PlatformNot applicable
File nameAmd64_a9755969a4500a26b4c33d66e95abdaf_31bf3856ad364e35_6.2.9200.20783_none_8ba5a4f076d1ecd8.manifest
File versionNot applicable
File size724
Date (UTC)26-Jul-2013
Time (UTC)14:16
PlatformNot applicable
File nameAmd64_cdce364a5f2712fbc4ce0f35f913783d_31bf3856ad364e35_6.2.9200.20783_none_54098b8ceb438f58.manifest
File versionNot applicable
File size731
Date (UTC)26-Jul-2013
Time (UTC)14:16
PlatformNot applicable
File nameAmd64_f2178beaf4a9aa8a3e16aec560462be2_31bf3856ad364e35_6.2.9200.20783_none_7d3ec53ca501c409.manifest
File versionNot applicable
File size725
Date (UTC)26-Jul-2013
Time (UTC)14:16
PlatformNot applicable
File nameAmd64_microsoft-windows-t..es-cpub-wmiprovider_31bf3856ad364e35_6.2.9200.20783_none_a666bbc81cf8c2f1.manifest
File versionNot applicable
File size15,048
Date (UTC)26-Jul-2013
Time (UTC)06:09
PlatformNot applicable
File nameAmd64_microsoft-windows-t..lishing-wmiprovider_31bf3856ad364e35_6.2.9200.20783_none_8e8aa230366bd39e.manifest
File versionNot applicable
File size23,839
Date (UTC)26-Jul-2013
Time (UTC)14:16
PlatformNot applicable
File nameAmd64_microsoft.remotedes...management.scripts_31bf3856ad364e35_6.2.9200.20783_none_1a8d3d3321f562c7.manifest
File versionNot applicable
File size17,725
Date (UTC)26-Jul-2013
Time (UTC)06:09
PlatformNot applicable
File nameMsil_microsoft.windows.s..ermanager.rdsplugin_31bf3856ad364e35_6.2.9200.20783_none_beefc01ad4d6ecaa.manifest
File versionNot applicable
File size10,079
Date (UTC)26-Jul-2013
Time (UTC)14:16
PlatformNot applicable
File nameX86_microsoft-windows-t..lishing-wmiprovider_31bf3856ad364e35_6.2.9200.20783_none_326c06ac7e0e6268.manifest
File versionNot applicable
File size23,695
Date (UTC)26-Jul-2013
Time (UTC)14:16
PlatformNot applicable

↑ Back to the top

Keywords: kb, kbhotfixserver, kbautohotfix, kbsurveynew, kbexpertiseadvanced, kbqfe, kbfix

↑ Back to the top

Article Info
Article ID : 2862077
Revision : 1
Created on : 1/7/2017
Published on : 9/10/2013
Exists online : False
Views : 296