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

Cause

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

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

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=supportNote 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.

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 notesImportant 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:

    Version

    Product

    Milestone

    Service branch

    6.2.920 0.16 xxx

    Windows Server 2012

    RTM

    GDR

    6.2.920 0.20 xxx

    Windows Server 2012

    RTM

    LDR

  • 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 name

File version

File size

Date

Time

Platform

Tscpub.mof

Not Applicable

14,166

2-Jun-12

14:31

Not Applicable

Tscpubwmi.dll

6.2.9200.20783

334,336

26-Jul-13

4:44

x64

Rdpsign.exe

6.2.9200.16384

68,608

26-Jul-12

3:08

x64

Tsallow.mof

Not Applicable

17,067

2-Jun-12

14:31

Not Applicable

Tspubwmi.dll

6.2.9200.20783

204,800

26-Jul-13

4:44

x64

Certificate.psm1

Not Applicable

12,659

17-Jun-12

15:31

Not Applicable

Common.psm1

Not Applicable

48,066

2-Jun-12

20:25

Not Applicable

Customrdpproperty.psm1

Not Applicable

9,535

2-Jun-12

14:31

Not Applicable

Deployment.psm1

Not Applicable

83,448

23-Jun-12

23:24

Not Applicable

Deploymentproperties.psm1

Not Applicable

15,105

17-Jun-12

15:31

Not Applicable

Livemigrate.psm1

Not Applicable

11,691

17-Jun-12

15:31

Not Applicable

Rdmgmt.format.ps1xml

Not Applicable

53,311

2-Jun-12

14:31

Not Applicable

Remoteappicon.psm1

Not Applicable

2,955

2-Jun-12

14:31

Not Applicable

Remoteapppublishing.psm1

Not Applicable

58,445

25-Jul-13

22:08

Not Applicable

Remotedesktop.psd1

Not Applicable

14,298

2-Jun-12

14:31

Not Applicable

Remotedesktoppublishing.psm1

Not Applicable

7,254

17-Jun-12

15:31

Not Applicable

Remotesessionmanagement.psm1

Not Applicable

9,075

17-Jun-12

15:31

Not Applicable

Sessioncollectionproperties.psm1

Not Applicable

21,443

17-Jun-12

15:31

Not Applicable

Sessiondesktopcollection.psm1

Not Applicable

23,630

17-Jun-12

16:08

Not Applicable

Startmenuapplications.psm1

Not Applicable

4,958

17-Jun-12

15:31

Not Applicable

Utility.psm1

Not Applicable

36,057

2-Jun-12

20:25

Not Applicable

Virtualdesktopcollection.psm1

Not Applicable

160,032

17-Jun-12

16:08

Not Applicable

Virtualdesktopcollectionproperties.psm1

Not Applicable

39,859

27-Jun-12

2:05

Not Applicable

Workspacemgmt.psm1

Not Applicable

8,439

17-Jun-12

15:31

Not Applicable

Microsoft.windows.servermanager.rdsplugin.dll

6.2.9200.20783

2,793,472

26-Jul-13

4:56

x86

Rdmsinst.dll

6.2.9200.16384

20,992

26-Jul-12

3:07

x64

Rdmsres.dll

6.0.0.0

2,048

26-Jul-12

2:35

x64

Remotedesktop.events.xml

Not Applicable

3,089

2-Jun-12

20:25

Not Applicable

Tspubiconhelper.dll

6.2.9200.16384

14,336

26-Jul-12

3:07

x64

Rdpsign.exe

6.2.9200.16384

60,416

26-Jul-12

3:20

x86

Tsallow.mof

Not Applicable

17,067

2-Jun-12

14:31

Not Applicable

Tspubwmi.dll

6.2.9200.20783

168,960

26-Jul-13

3:47

x86


Status

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

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

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×