locked
Hyper-V+RemoteFX+RemoteApp RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Heya.

    I have a bare-metal Windows Server 2012 r2 machine with a Windows 8.1 Ent guest running in Hyper-V. Without the RemoteFX GPU added to the VM configuration, I can RemoteApp in with no problem. However, when I add the RemoteFX GPU I can RDP in normally (not RemoteApp), however when I try to run the RemoteApp RDP file (that worked fine without the GPU) it shows the "connecting" window for a split second, and then closes.

    In the RdpCoreTS event logs there is an entry: "The disconnect reason is 0"

    Let me know if there is any more information I can give.

    -B

    • Moved by BrianEhMVP Thursday, February 18, 2016 4:51 PM
    Sunday, November 3, 2013 8:04 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    What you are experiencing is normal.  The Server 2012 R2 RemoteFX vGPU feature is not supported for RemoteApp sessions.

    -TP

    • Proposed as answer by TP []MVP Saturday, February 20, 2016 2:24 AM
    • Marked as answer by TP []MVP Saturday, February 20, 2016 2:24 AM
    Saturday, February 20, 2016 2:24 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Base on experience the most possible is setting up the incorrect GPU RAM resource to the child vm, please try to shut down the Windows8.1 then reconnect the Remote APP, the Remote APP work as normal you need to adjust the child vm GPU resource.

    More information:

    Hardware Considerations for RemoteFX

    http://technet.microsoft.com/en-us/library/ff817602(v=ws.10).aspx

    Configure a RemoteFX 3D Video Adapter

    http://technet.microsoft.com/en-us/library/ff830364.aspx

    Hope this helps.

    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.
    </p

    • Marked as answer by Alex Lv Thursday, November 14, 2013 9:42 AM
    • Unmarked as answer by TP []MVP Saturday, February 20, 2016 2:24 AM
    Thursday, November 7, 2013 3:11 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Just want to confirm the current situations.

    Please feel free to let us know if you need further assistance.

    Regards.

    Alex Lv <p style="margin:0cm 0cm 0pt"><a href="http://social.technet.microsoft.com/Forums/en-US/0ab8c4d1-9620-462f-a02f-ed888d7dce58/looking-to-do-some-brief-interviews-with-technet-forum-users" style="text-decoration:NONE"><span lang="EN-US" style="color:black; font-family:&quot;Segoe UI&quot;,&quot;sans-serif&quot;; font-size:10pt">We are trying to better understand customer views on social support experience, so your participation in this <span style="color:green"><b>interview project</b></span> would be greatly appreciated if you have time.<br/> Thanks for helping make community forums a great place.<br/> </span></a></p>

    Monday, November 11, 2013 2:12 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am having the same problems. I am currently running A 2012 R2 STD + HyperV + RemoteApp with Windows 8.1 x64 Ent as the guest OS. When I have no GPU adapter attached it connects and launches the RemoteApp just fine. When I add the adapter (I am running 2 x Quadro 2000s both enabled for GPU with RemoteFX in Hyper-V layer) it briefly connects and disconnects with no errors. I have multiple VDI sessions running with RemoteFX GPU enabled and they function/connect perfectly. GPU memory resources are @ 25% so there is plenty of usable memory on the GPU.
    Tuesday, January 14, 2014 7:56 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am having the same problems. I am currently running A 2012 R2 STD + HyperV + RemoteApp with Windows 8.1 x64 Ent as the guest OS. When I have no GPU adapter attached it connects and launches the RemoteApp just fine. When I add the adapter (I am running 2 x Quadro 2000s both enabled for GPU with RemoteFX in Hyper-V layer) it briefly connects and disconnects with no errors. I have multiple VDI sessions running with RemoteFX GPU enabled and they function/connect perfectly. GPU memory resources are @ 25% so there is plenty of usable memory on the GPU.
    I have the exact same issue and always have with remotefx enabled. I have a intel xeom e5-2620 which hyperthreads to 12 cores and a NVidia Quadro K200D 2GB DDR5 installed on my host box. VDI with RemoteFX enabled works fine in a Desktop Collection Deployment; however, when I add the RemoteFX vGPU in a RemoteApp VDI deployment I receive the old David Copperfield disappearing window trick after my credentials successfully authenticate with my RDG Server.  As, of now I do not have a working solution. 
    Saturday, September 27, 2014 1:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Heya.

    I have a bare-metal Windows Server 2012 r2 machine with a Windows 8.1 Ent guest running in Hyper-V. Without the RemoteFX GPU added to the VM configuration, I can RemoteApp in with no problem. However, when I add the RemoteFX GPU I can RDP in normally (not RemoteApp), however when I try to run the RemoteApp RDP file (that worked fine without the GPU) it shows the "connecting" window for a split second, and then closes.

    In the RdpCoreTS event logs there is an entry: "The disconnect reason is 0"

    Let me know if there is any more information I can give.

    -B

    I'm experiencing the exact same symptoms (and the exact same event log entry) while running both 2012 R2 with an 8.1 guest and, as an experiment, Windows Server 2016 Technical Preview 4 (four) for both server and guest.

    I have tried the group policies related to remoteapp and remotefx, to no avail. As soon as the remotefx gpu is present in the vm, remoteapp stops working (while remote desktop works fine and with remotefx fully working). Remove the remotefx adapter from the vm, and remoteapp immediatly works again. This seems to be ignoring the "use remotefx for remoteapp group policy" completely.


    • Edited by Joao M Correia Saturday, November 21, 2015 10:40 AM typo: fm -> vm
    • Proposed as answer by Joao M Correia Monday, November 23, 2015 2:45 PM
    • Unproposed as answer by Joao M Correia Monday, November 23, 2015 2:45 PM
    Saturday, November 21, 2015 9:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I am also having the exact same issue. I only really had a clue that this is related to remotefx and remoteapp because I had the following warning in the event logs -

    The network characteristics detection function has been disabled because of Reason Code: 2(Server Configuration)..

    My configuration is a win 10 pro hyper v host with a win 10 enterprise guest configured to host remoteapps. As above, as soon as I enable the RemoteFX adapter on the guest, remoteapp stops working and any attempt to connect leads to the warning above. Removing the adapter immediately resolves the issue. At no point does remote desktop stop working.

    Thursday, February 18, 2016 4:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This thread is wrongly marked as answered. The proposed answer in no way helps or solves the problem, and should not be marked as such.

    Thank you,

    Joao

    Friday, February 19, 2016 10:02 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    What you are experiencing is normal.  The Server 2012 R2 RemoteFX vGPU feature is not supported for RemoteApp sessions.

    -TP

    • Proposed as answer by TP []MVP Saturday, February 20, 2016 2:24 AM
    • Marked as answer by TP []MVP Saturday, February 20, 2016 2:24 AM
    Saturday, February 20, 2016 2:24 AM