VDI - RemoteApp does not start in "Virtual machine-based desktop deployment" environment

Question

Hello dear community,
I would like to familiarize myself to the subject of desktop virtualization and have built up a test environment for this purpose. Most went smoothly, but now I'm trying for days to figure out, why the deployed RemoteApp programs in my test environment not
start. Unfortunately posts here and in other blogs were not helpful. I hope you can point me to the right direction. :)
My environment
Server 1
Windows Server 2012 R2 Std with the roles
    AD DS,
    DNS,
    DHCP
Server 2
Windows Server 2012 R2 Std with the roles
    Hyper-V,
    Remote Desktop Services (Connection Broker, Virtualization Host, Web Access),
    IIS
VMs
Windows 8.1
RD Client 1
Laptop with Windows 7 and Internet Explorer 9, Firefox 28, RemoteApp and Desktop Connections
RD client 2
iPad with Microsoft Remote Desktop App
Setting up the environment
The installation of the environment I made as mentioned ​​in the following blog post. http://blog.itvce.com/?p=1569 But with only two physical servers.
What does work?
Prepared with SysPrep and "cloned" Windows 8.1 VMs created in the collections of virtual desktops are accessible via WebAccess (RDWeb) using IE, FF, Windows Start menu and also from the iPad as a complete desktop for authorized users/groups. The VMs
wake up in Hyper- V from the saved state and roll back to it after the user logs off. So far so good.
What does not work?
Now to what does not work. One collection of virtual desktops I have reserved for the publication of RemoteApp programs. So this new collection - like the above - was created. The VMs were built and successfully registered in AD. Then I used "publish RemoteApp
Programs" wizard in the collection. The available programs were successfully read from the VM. WordPad, Calc and Paint I used for the test. The programs/apps will then appear in RDWeb.
In RDWeb I now click on the Calculator, the warning described in many blogs appears that resources are passed through and then that the certificate could not be verified. Although I have already added the certificate to the trusted root CA in the user and the
computer area, I acknowledge that I would like to connect despite the certificate error with "Yes".
After about 20 seconds the "Connect to ..." window disappears and that it was. In Hyper-V Manager the corresponding VM does not move even if it's running. If the VM was not running and in saved state, it is at least started. But the Calculator will
still not start.
Can anyone give me a proper hint what to do, which Bing, Google and Technet did not have?
Thank you in advance!
Kay
PS: Since I am from Germany, I have asked the question first in the German forum. Unfortunately, without success.

Answer 1

Hi Kay,
Thank you for contacting Microsoft.
From your description, I learnt that the issue you are experiencing is that you want to eliminate the certificate warning when launching the Remote App applications. Please let me know if I misunderstand your purpose.
Firstly, please let me know what certificate you are using. Then please export and import the certificate on the RDSH server. We need to manage the certificates. Please refer to
the steps below.
1. Open the Collections which you want to manage, click
Edit Deployment Properties.
2. On the Certificates page, select
Select existing certificate.
3. When the
Select Existing Certificate page appear, please select Choose a different certificate, locate to the right exported certificate path, and type the correct password, and
select Allow the certificate to be added to the Trusted Root Certification Authorities certificate store on the destination computers.
4. Repeat steps 2 and 3 to finish the certificate configuration, here we can use the same certificate.
If anything unclear, please feel free to let me know.
Best regards,
Sophia Sun 
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.