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

A new KB article (2862077) was released yesterday in regards to changing the properties of a Remote app inside the RDMS if this Remote App is installed on a non-system drive of the RD Session Host.

“…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

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

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

Source & download: http://support.microsoft.com/kb/2862077/en-us?sd=rss

New article: Using PowerShell to control RDS in Windows Server 2012

My new article entitled "Using PowerShell to control RDS in Windows Server 2012" on virtualizationadmin.com just got published. In this article I do dive into some of the new PowerShell commands for the Remote Desktop Services scenarios that are available with Windows Server 2012. The article discusses the installation of a RDS deployment, the creation of a Session Collection and the creation of RemoteApps. All using Powershell. I’m already working on a part II of this article in which we’ll dive even deeper. Stay tuned!

“…Introduction. PowerShell has been around for many years now. There is no way to work around PowerShell anymore, and you should not even want to work around it. With every new release of every new Microsoft product or service, we see an even tighter integration with PowerShell. With the upcoming release, it’s even bigger than before. With Windows Server 2012, we have over 2400 cmdlets available! That is a huge number! In this article, we will take a look at how PowerShell is integrated with Remote Desktop Services in Windows Server 2012. We will dive into PowerShell commands for both RDS scenarios that are available with Windows Server 2012. That is, the Virtual machine-based desktop deployment as well as the Session-based desktop deployment…”

Source: http://www.virtualizationadmin.com/articles-tutorials/vdi-articles/general/using-powershell-control-rds-windows-server-2012.html