In Windows Server 2003, Windows Server 2008 and Windows Server 2008 R2 there was a nifty feature buried in Terminal/Remote Desktop services that allowed you to create an .MSI installer for RemoteApp applications. RemoteApp is that nifty Terminal/Remote Desktop services function that has each application run in its own window, rather than requiring you to run it through the full desktop window of Remote Desktop Connection.
Up until Windows Server 2012, you could take any application installed on a Terminal/Remote Desktop services server, use the console to create an .MSI file and then distribute that MSI file to clients who could install it and then run the RemoteApp application as they would any other application (as long as they had a connection to the Remote Desktop Server). The MSI file would ensure that all of the correct file type associations were created, even if you were deploying the RemoteApp to a computer that wasn’t a part of the Active Directory domain.
What has me scratching my head is that this MSI creation functionality is no longer available in Remote Desktop Services in Server 2012. RemoteApp exists, but you can’t publish them via MSI – you can publish RemoteApps to clients via Group Policy.
Why this is a bummer is that it means you can no longer deploy RemoteApp through Configuration Manager, Intune, or any other 3rd party product that supports MSI files. RemoteApp was a great solution in BYOD/Consumerization of IT environments as it allowed access to RemoteApp applications without requiring a domain join.
Hopefully one day there will be a way of deploying RemoteApp on Server 2012 through products like Intune and Configuration Manager. It was a great bit of functionality and the product is diminished for its loss.