As far as RemoteApp goes, there is no difference whatsoever. The RemoteApp technology itself belongs to Microsoft, and it comes from the underlying Windows installation. As such, a RemoteApp is just a RemoteApp on all Windows computers/servers. It doesn’t really matter where the RemoteApp comes from, how it is initialized, etc. (seeing as it’s still relying on the underlying Remote Desktop/RemoteApp capabilities of the Windows operating system itself).

That being said… RemoteApp functionality on a Windows server is traditionally enabled by creating a separate “application” server via installing the full gamut of Remote Desktop Services (RDS) server roles onto an instance of Windows Server Standard or Datacenter. However, you cannot install RDS on a Windows Server Essentials server seeing as doing so messes up the default configuration of the Essentials server (Remote Desktop Gateway, Remote Web Access, etc., etc.), and will cause you nothing but grief in the long run.

The WSE RemoteApp product resolves this issue by allowing you to use RemoteApps with your Essentials server without having to install the full gamut of RDS server roles onto the Essentials server. Rather, it utilizes the underlying RemoteApp functionality that is part of the Essentials server itself in order to work its magic (it does not enable any of the RDS server roles on the Essentials server, nor does it change the default configuration of the Essentials server in any way). Additionally, WSE RemoteApp is built as a standard “Windows Server Solutions” add-in that allows the product to deeply integrate itself (and the RemoteApp functionality it affords) into the Essentials server’s built-in Remote Web Access website, Launchpad, Dashboard, etc.